<?xml version='1.0'?><?xml-stylesheet href='/static/xsl/oai.xsl' type='text/xsl'?><ri:Resource created="2010-07-26T13:39:00Z" status="active" updated="2024-02-06T08:59:18Z" version="1.2" xmlns:g-colstat="http://dc.g-vo.org/ColStats-1" xmlns:ri="http://www.ivoa.net/xml/RegistryInterface/v1.0" xmlns:vr="http://www.ivoa.net/xml/VOResource/v1.0" xmlns:vs="http://www.ivoa.net/xml/VODataService/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://dc.g-vo.org/ColStats-1 http://vo.ari.uni-heidelberg.de/docs/schemata/Colstats.xsd http://www.ivoa.net/xml/RegistryInterface/v1.0 http://vo.ari.uni-heidelberg.de/docs/schemata/RegistryInterface.xsd http://www.ivoa.net/xml/VOResource/v1.0 http://vo.ari.uni-heidelberg.de/docs/schemata/VOResource.xsd http://www.ivoa.net/xml/VODataService/v1.1 http://vo.ari.uni-heidelberg.de/docs/schemata/VODataService.xsd" xsi:type="vs:CatalogService"><title>GloTS tables for service</title><shortName>GloTS tables</shortName><identifier>ivo://org.gavo.dc/glots/q/showtables</identifier><curation><publisher>The GAVO DC team</publisher><creator><name>GAVO Data Centre</name><logo>http://vo.ari.uni-heidelberg.de/docs/GavoTiny.png</logo></creator><date role="Updated">2024-08-08T11:40:49Z</date><contact><name>GAVO Data Centre Team</name><address>Mönchhofstrasse 12-14, D-69120 Heidelberg</address><email>gavo@ari.uni-heidelberg.de</email><telephone>+49 6221 54 1837</telephone></contact></curation><content><subject>virtual-observatories</subject><subject>astronomy-databases</subject><description>A list of tables for a TAP service specified in the URL by its ivo-id.</description><referenceURL>http://dc.g-vo.org/glots/q/showtables/info</referenceURL></content><tableset><schema><name>glots</name><title>GloTS, the Global TAP Schema</title><description>
The global TAP schema collects information on
tables and columns from known TAP servers.  This facilitates locating
queriable data by physics (via UCD) or keywords (via description).

Note that this shouldn't really be necessary as all information
present here should be exposed through Registry records.  However,
in reality data providers currently are much more liable to give
column metadata in their tap_schema than in their Registry records.
Hence, for the time being, we maintain this service by harvesting
tap_schemas about monthly.</description><table type="output"><name>output</name><description>A list of tables for a TAP service specified in the URL by its ivo-id.</description><column><name>tablelink</name><description>Fully qualified table name</description><dataType arraysize="*" xsi:type="vs:VOTableType">char</dataType><flag>nullable</flag></column><column><name>table_desc</name><description>Brief description of the table</description><dataType arraysize="*" xsi:type="vs:VOTableType">unicodeChar</dataType><flag>nullable</flag></column></table></schema></tableset></ri:Resource>