@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <http://www.ontologydesignpatterns.org/cp/owl/situation.owl#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix metadata: <http://data.bioontology.org/metadata/> .
@prefix metadata_def: <http://data.bioontology.org/metadata/def/> .
@prefix ns1: <http://www.ontologydesignpatterns.org/cp/owl/> .
@prefix cito: <http://purl.org/spar/cito/> .
cito:Citation
rdfs:subClassOf ns0:Situation .
ns0:Situation
metadata_def:mappingLoom "situation" ;
metadata_def:mappingSameURI ns0:Situation ;
metadata_def:prefLabel "Situation"@en ;
metadata:prefixIRI "situation:Situation" ;
a owl:Class ;
rdfs:comment """A view on a set of entities. It can be seen as a 'relational context', reifying a relation.
For example, a PlanExecution is a context including some actions executed by agents according to certain parameters and expected tasks to be achieved from a Plan; a DiagnosedSituation is a context of observed entities that is interpreted on the basis of a Diagnosis, etc.
Situation is also able to represent reified n-ary relations, where isSettingFor is the top-level relation for all binary projections of the n-ary relation. If used in a transformation pattern for n-ary relations, the designer should take care of:
- creating only one situation for each instance of an n-ary relation, otherwise the 'identification constraint' (Calvanese et al., IJCAI 2001) could be violated
- adding an 'exact cardinality' restriction corresponding to the arity of the n-ary relation, otherwise the designer would actually represent a polymorphic relation.""" ;
rdfs:isDefinedBy <http://www.ontologydesignpatterns.org/cp/owl/situation.owl> ;
rdfs:label "Situation"@en ;
rdfs:subClassOf owl:Thing .
ns0:hasSetting
rdfs:range ns0:Situation .
ns0:isSettingFor
rdfs:domain ns0:Situation .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <http://www.ontologydesignpatterns.org/cp/owl/situation.owl#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix metadata: <http://data.bioontology.org/metadata/> .
@prefix metadata_def: <http://data.bioontology.org/metadata/def/> .
@prefix ns1: <http://www.ontologydesignpatterns.org/cp/owl/> .
@prefix cito: <http://purl.org/spar/cito/> .
cito:Citation
rdfs:subClassOf ns0:Situation .
ns0:Situation
metadata_def:mappingLoom "situation" ;
metadata_def:mappingSameURI ns0:Situation ;
metadata_def:prefLabel "Situation"@en ;
metadata:prefixIRI "situation:Situation" ;
a owl:Class ;
rdfs:comment """A view on a set of entities. It can be seen as a 'relational context', reifying a relation.
For example, a PlanExecution is a context including some actions executed by agents according to certain parameters and expected tasks to be achieved from a Plan; a DiagnosedSituation is a context of observed entities that is interpreted on the basis of a Diagnosis, etc.
Situation is also able to represent reified n-ary relations, where isSettingFor is the top-level relation for all binary projections of the n-ary relation. If used in a transformation pattern for n-ary relations, the designer should take care of:
- creating only one situation for each instance of an n-ary relation, otherwise the 'identification constraint' (Calvanese et al., IJCAI 2001) could be violated
- adding an 'exact cardinality' restriction corresponding to the arity of the n-ary relation, otherwise the designer would actually represent a polymorphic relation.""" ;
rdfs:isDefinedBy <http://www.ontologydesignpatterns.org/cp/owl/situation.owl> ;
rdfs:label "Situation"@en ;
rdfs:subClassOf owl:Thing .
ns0:hasSetting
rdfs:range ns0:Situation .
ns0:isSettingFor
rdfs:domain ns0:Situation .