@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix ns1: <http://www.ivoa.net/rdf/product-type#> .
@prefix metadata_def: <http://data.bioontology.org/metadata/def/> .
@prefix ns2: <http://www.ivoa.net/rdf/ivoasem#> .
@prefix metadata: <http://data.bioontology.org/metadata/> .
ns0:ca
metadata_def:mappingLoom "catalogue" ;
metadata_def:mappingSameURI ns0:ca ;
metadata_def:prefLabel "Catalogue" ;
metadata:prefixIRI "ca" ;
ns2:preliminary ":__" ;
a owl:Class ;
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:label "Catalogue" ;
rdfs:seeAlso ns1:event-list, ns1:measurements ;
rdfs:subClassOf owl:Thing .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <http://voparis-ns.obspm.fr/rdf/epn/2.0/product-type#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix ns1: <http://www.ivoa.net/rdf/product-type#> .
@prefix metadata_def: <http://data.bioontology.org/metadata/def/> .
@prefix ns2: <http://www.ivoa.net/rdf/ivoasem#> .
@prefix metadata: <http://data.bioontology.org/metadata/> .
ns0:ca
metadata_def:mappingLoom "catalogue" ;
metadata_def:mappingSameURI ns0:ca ;
metadata_def:prefLabel "Catalogue" ;
metadata:prefixIRI "ca" ;
ns2:preliminary ":__" ;
a owl:Class ;
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:label "Catalogue" ;
rdfs:seeAlso ns1:event-list, ns1:measurements ;
rdfs:subClassOf owl:Thing .