<?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="2025-09-24T03:35:53Z" 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>Global TAP Servers List</title><shortName>GloTS servers list</shortName><identifier>ivo://xaovo/glots/q/servers</identifier><curation><publisher>Xinjiang Astronomical Observatory,CAS</publisher><creator><name>Zhang Hailong</name><logo>https://data.xao.ac.cn/favicon.png</logo></creator><date role="Updated">2025-09-24T03:44:55Z</date><contact><name>Zhang Hailong</name><address>150 Science 1-Street, Urumqi, Xinjiang 830011, China</address><email>zhanghailong@xao.ac.cn</email><telephone>+86 18699134012</telephone></contact></curation><content><subject>virtual-observatories</subject><subject>astronomy-databases</subject><description>A list of TAP servers in the VO, mostly taken from the registry.</description><referenceURL>https://data.xao.ac.cn/glots/q/servers/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><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>