<?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="2023-02-28T08:03:30Z" 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:CatalogResource"><title>GloTS, the Global TAP Schema</title><shortName>glots.services</shortName><identifier>ivo://aip.gavo.org/glots/q/services</identifier><curation><publisher>GAVO at Leibniz-Institute for Astrophysics Potsdam</publisher><creator><name>The GAVO data center team</name><logo>http://vo.ari.uni-heidelberg.de/docs/GavoTiny.png</logo></creator><contact><name>Harry Enke</name><address>Leibnitz-Institut fr Astrophysik</address><email>henke@aip.de</email><telephone>++49 6221 541837</telephone></contact></curation><content><subject>virtual-observatories</subject><subject>astronomy-databases</subject><description>A table of TAP services harvested from the registry (and some
spoon-fed).</description><referenceURL>http://gavo.aip.de/tableinfo/glots.services</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><name>glots.services</name><description>A table of TAP services harvested from the registry (and some
spoon-fed).</description><column><name>ivoid</name><description>IVOA identifier of providing service</description><dataType arraysize="*" xsi:type="vs:VOTableType">char</dataType><flag>indexed</flag><flag>primary</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><column><name>nextharvest</name><description>Next scheduled harvest of data</description><dataType arraysize="19" extendedType="timestamp" xsi:type="vs:VOTableType">char</dataType><flag>nullable</flag></column><column><name>harvestinterval</name><description>Approximate interval of harvest</description><unit>d</unit><dataType xsi:type="vs:VOTableType">int</dataType><flag>nullable</flag></column><column><name>lastsuccess</name><description>Last successful harvest of this service</description><dataType arraysize="19" extendedType="timestamp" xsi:type="vs:VOTableType">char</dataType><flag>nullable</flag></column></table></schema></tableset></ri:Resource>