<?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-12-27T08:31:01Z" version="1.2" xmlns:g-colstat="http://dc.g-vo.org/ColStats-1" xmlns:ri="http://www.ivoa.net/xml/RegistryInterface/v1.0" xmlns:vg="http://www.ivoa.net/xml/VORegistry/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/VORegistry/v1.0 http://vo.ari.uni-heidelberg.de/docs/schemata/VORegistry.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>Global TAP Schema Simple Search</title><shortName>GloTS plain</shortName><identifier>ivo://org.gavo.dc/glots/q/plain</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>
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><referenceURL>http://dc.g-vo.org/glots/q/plain/info</referenceURL></content><capability><interface xsi:type="vr:WebBrowser"><accessURL use="full">http://dc.g-vo.org/glots/q/plain/form</accessURL><mirrorURL>https://dc.g-vo.org/glots/q/plain/form</mirrorURL></interface></capability><capability standardID="ivo://ivoa.net/std/VOSI#capabilities"><interface role="std" xsi:type="vs:ParamHTTP"><accessURL use="full">http://dc.g-vo.org/glots/q/plain/capabilities</accessURL><mirrorURL>https://dc.g-vo.org/glots/q/plain/capabilities</mirrorURL></interface></capability><capability standardID="ivo://ivoa.net/std/VOSI#availability"><interface role="std" xsi:type="vs:ParamHTTP"><accessURL use="full">http://dc.g-vo.org/glots/q/plain/availability</accessURL><mirrorURL>https://dc.g-vo.org/glots/q/plain/availability</mirrorURL></interface></capability><capability standardID="ivo://ivoa.net/std/VOSI#tables"><interface role="std" version="1.1" xsi:type="vs:ParamHTTP"><accessURL use="full">http://dc.g-vo.org/glots/q/plain/tableMetadata</accessURL><mirrorURL>https://dc.g-vo.org/glots/q/plain/tableMetadata</mirrorURL></interface></capability><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><name>glots.allcols</name><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><column><name>column_name</name><description>Column name</description><dataType arraysize="*" xsi:type="vs:VOTableType">char</dataType><flag>nullable</flag></column><column><name>description</name><description>Brief description of column</description><dataType arraysize="*" xsi:type="vs:VOTableType">char</dataType><flag>nullable</flag></column><column><name>ucd</name><description>UCD of column (some services still have 1.0 UCDs).</description><dataType arraysize="*" xsi:type="vs:VOTableType">char</dataType><flag>nullable</flag></column><column><name>unit</name><description>Unit in VO standard format</description><dataType arraysize="*" xsi:type="vs:VOTableType">char</dataType><flag>nullable</flag></column><column><name>indexed</name><description>Is there an index on this column?</description><dataType xsi:type="vs:VOTableType">int</dataType><flag>nullable</flag></column><column><name>table_name</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><column><name>ivoid</name><description>IVOA identifier of providing service</description><dataType arraysize="*" xsi:type="vs:VOTableType">char</dataType><flag>nullable</flag></column><column><name>accessurl</name><description>Base URL of TAP endpoint</description><dataType arraysize="*" xsi:type="vs:VOTableType">char</dataType><flag>nullable</flag></column></table></schema></tableset></ri:Resource>