{"@context":{"ns0":"http://www.ontologydesignpatterns.org/cp/owl/situation.owl#","rdf":"http://www.w3.org/1999/02/22-rdf-syntax-ns#","owl":"http://www.w3.org/2002/07/owl#","rdfs":"http://www.w3.org/2000/01/rdf-schema#","metadata":"http://data.bioontology.org/metadata/","metadata_def":"http://data.bioontology.org/metadata/def/","ns1":"http://www.ontologydesignpatterns.org/cp/owl/","cito":"http://purl.org/spar/cito/"},"@graph":[{"@id":"ns0:Situation","@type":"owl:Class","rdfs:subClassOf":{"@id":"owl:Thing"},"rdfs:comment":"A view on a set of entities. It can be seen as a 'relational context', reifying a relation.\nFor 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.\nSituation 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:\n- creating only one situation for each instance of an n-ary relation, otherwise the 'identification constraint' (Calvanese et al., IJCAI 2001) could be violated\n- adding an 'exact cardinality' restriction corresponding to the arity of the n-ary relation, otherwise the designer would actually represent a polymorphic relation.","rdfs:label":{"@language":"en","@value":"Situation"},"metadata:prefixIRI":"situation:Situation","metadata:def/prefLabel":{"@language":"en","@value":"Situation"},"metadata:def/mappingLoom":"situation","metadata:def/mappingSameURI":{"@id":"ns0:Situation"},"rdfs:isDefinedBy":{"@id":"ns1:situation.owl"}},{"@id":"cito:Citation","rdfs:subClassOf":{"@id":"ns0:Situation"}},{"@id":"ns0:isSettingFor","rdfs:domain":{"@id":"ns0:Situation"}},{"@id":"ns0:hasSetting","rdfs:range":{"@id":"ns0:Situation"}}]}