<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ns0="http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:ns1="http://www.ivoa.net/rdf/product-type#" xmlns:metadata_def="http://data.bioontology.org/metadata/def/" xmlns:ns2="http://www.ivoa.net/rdf/ivoasem#" xmlns:metadata="http://data.bioontology.org/metadata/">
<owl:Class rdf:about="http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#ca">
<rdfs:subClassOf rdf:resource="http://www.w3.org/2002/07/owl#Thing"/>
<rdfs:label>Catalogue</rdfs:label>
<rdfs:comment>Applies to a granule providing a catalogue of object parameters,
a list of features, a table of granules in another TAP service, a list of events...
The result metadata table of a service query can be considered as a catalogue.
Catalogues can be provided as VOtable (possibly containing multiple tables, although
this is not supported by SAMP). It is good practice to describe the type of data
included in the catalogue using a hash-separated-list (e.g., a table of spectra should
be described by ca#sp, so that it will respond to a query for spectra).</rdfs:comment>
<rdfs:seeAlso rdf:resource="http://www.ivoa.net/rdf/product-type#event-list"/>
<rdfs:seeAlso rdf:resource="http://www.ivoa.net/rdf/product-type#measurements"/>
<metadata_def:prefLabel>Catalogue</metadata_def:prefLabel>
<metadata_def:mappingLoom>catalogue</metadata_def:mappingLoom>
<metadata_def:mappingSameURI rdf:resource="http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#ca"/>
<ns2:preliminary>:__</ns2:preliminary>
<metadata:prefixIRI>ca</metadata:prefixIRI>
</owl:Class>
<rdf:Description rdf:about="http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#ca">
<metadata_def:mappingSameURI rdf:resource="http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#ca"/>
</rdf:Description>
</rdf:RDF>
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ns0="http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:ns1="http://www.ivoa.net/rdf/product-type#" xmlns:metadata_def="http://data.bioontology.org/metadata/def/" xmlns:ns2="http://www.ivoa.net/rdf/ivoasem#" xmlns:metadata="http://data.bioontology.org/metadata/">
<owl:Class rdf:about="http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#ca">
<rdfs:subClassOf rdf:resource="http://www.w3.org/2002/07/owl#Thing"/>
<rdfs:label>Catalogue</rdfs:label>
<rdfs:comment>Applies to a granule providing a catalogue of object parameters,
a list of features, a table of granules in another TAP service, a list of events...
The result metadata table of a service query can be considered as a catalogue.
Catalogues can be provided as VOtable (possibly containing multiple tables, although
this is not supported by SAMP). It is good practice to describe the type of data
included in the catalogue using a hash-separated-list (e.g., a table of spectra should
be described by ca#sp, so that it will respond to a query for spectra).</rdfs:comment>
<rdfs:seeAlso rdf:resource="http://www.ivoa.net/rdf/product-type#event-list"/>
<rdfs:seeAlso rdf:resource="http://www.ivoa.net/rdf/product-type#measurements"/>
<metadata_def:prefLabel>Catalogue</metadata_def:prefLabel>
<metadata_def:mappingLoom>catalogue</metadata_def:mappingLoom>
<metadata_def:mappingSameURI rdf:resource="http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#ca"/>
<ns2:preliminary>:__</ns2:preliminary>
<metadata:prefixIRI>ca</metadata:prefixIRI>
</owl:Class>
<rdf:Description rdf:about="http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#ca">
<metadata_def:mappingSameURI rdf:resource="http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#ca"/>
</rdf:Description>
</rdf:RDF>