@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix ns0: <http://purl.org/goodrelations/v1#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix metadata_def: <http://data.bioontology.org/metadata/def/> . @prefix schema: <http://schema.org/> . @prefix metadata: <http://data.bioontology.org/metadata/> . @prefix ns1: <http://purl.org/goodrelations/> . ns0:Brand owl:disjointWith ns0:Location . ns0:BusinessEntity owl:disjointWith ns0:Location . ns0:BusinessEntityType owl:disjointWith ns0:Location . ns0:BusinessFunction owl:disjointWith ns0:Location . ns0:DayOfWeek owl:disjointWith ns0:Location . ns0:DeliveryMethod owl:disjointWith ns0:Location . ns0:Location metadata_def:mappingLoom "location" ; metadata_def:mappingSameURI ns0:Location ; metadata_def:prefLabel "Location" ; metadata:prefixIRI "gr:Location" ; a owl:Class ; rdfs:comment """A location is a point or area of interest from which a particular product or service is available, e.g. a store, a bus stop, a gas station, or a ticket booth. The difference to gr:BusinessEntity is that the gr:BusinessEntity is the legal entity (e.g. a person or corporation) making the offer, while gr:Location is the store, office, or place. A chain restaurant will e.g. have one legal entity but multiple restaurant locations. Locations are characterized by an address or geographical position and a set of opening hour specifications for various days of the week. Example: A rental car company may offer the Business Function Lease Out of cars from two locations, one in Fort Myers, Florida, and one in Boston, Massachussetts. Both stations are open 7:00 - 23:00 Mondays through Saturdays. Note: Typical address standards (vcard) and location data (geo, WGC84) should be attached to a gr:Location node. Since there already exist established vocabularies for this, the GoodRelations ontology does not provide respective attributes. Instead, the use of respective vocabularies is recommended. However, the gr:hasGlobalLocationNumber property is provided for linking to public identifiers for business locations. Compatibility with schema.org: This class is equivalent to http://schema.org/Place."""@en ; rdfs:isDefinedBy ns1:v1 ; rdfs:label "Location"@en ; rdfs:subClassOf owl:Thing ; owl:disjointWith ns0:Offering, ns0:OpeningHoursSpecification, ns0:PaymentMethod, ns0:PriceSpecification, ns0:QuantitativeValue, ns0:TypeAndQuantityNode, ns0:WarrantyPromise, ns0:WarrantyScope ; owl:equivalentClass ns0:LocationOfSalesOrServiceProvisioning, schema:Place . ns0:availableAtOrFrom rdfs:range ns0:Location . ns0:hasPOS rdfs:range ns0:Location .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <http://purl.org/goodrelations/v1#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix metadata_def: <http://data.bioontology.org/metadata/def/> .
@prefix schema: <http://schema.org/> .
@prefix metadata: <http://data.bioontology.org/metadata/> .
@prefix ns1: <http://purl.org/goodrelations/> .

ns0:Brand
    owl:disjointWith ns0:Location .

ns0:BusinessEntity
    owl:disjointWith ns0:Location .

ns0:BusinessEntityType
    owl:disjointWith ns0:Location .

ns0:BusinessFunction
    owl:disjointWith ns0:Location .

ns0:DayOfWeek
    owl:disjointWith ns0:Location .

ns0:DeliveryMethod
    owl:disjointWith ns0:Location .

ns0:Location
    metadata_def:mappingLoom "location" ;
    metadata_def:mappingSameURI ns0:Location ;
    metadata_def:prefLabel "Location" ;
    metadata:prefixIRI "gr:Location" ;
    a owl:Class ;
    rdfs:comment """A location is a point or area of interest from which a particular product or service is available, e.g. a store, a bus stop, a gas station, or a ticket booth. The difference to gr:BusinessEntity is that the gr:BusinessEntity is the legal entity (e.g. a person or corporation) making the offer, while gr:Location is the store, office, or place. A chain restaurant will e.g. have one legal entity but multiple restaurant locations. Locations are characterized by an address or geographical position and a set of opening hour specifications for various days of the week.
		
Example: A rental car company may offer the Business Function Lease Out of cars from two locations, one in Fort Myers, Florida, and one in Boston, Massachussetts. Both stations are open 7:00 - 23:00 Mondays through Saturdays.

Note: Typical address standards (vcard) and location data (geo, WGC84) should be attached to a gr:Location node. Since there already exist established vocabularies for this, the GoodRelations ontology does not provide respective attributes. Instead, the use of respective vocabularies is recommended. However, the gr:hasGlobalLocationNumber property is  provided for linking to public identifiers for business locations.
		
Compatibility with schema.org: This class is equivalent to http://schema.org/Place."""@en ;
    rdfs:isDefinedBy ns1:v1 ;
    rdfs:label "Location"@en ;
    rdfs:subClassOf owl:Thing ;
    owl:disjointWith ns0:Offering, ns0:OpeningHoursSpecification, ns0:PaymentMethod, ns0:PriceSpecification, ns0:QuantitativeValue, ns0:TypeAndQuantityNode, ns0:WarrantyPromise, ns0:WarrantyScope ;
    owl:equivalentClass ns0:LocationOfSalesOrServiceProvisioning, schema:Place .

ns0:availableAtOrFrom
    rdfs:range ns0:Location .

ns0:hasPOS
    rdfs:range ns0:Location .