Specific Dependence And Inherence¶
Source: BFO · Published by: basic-formal-ontology.org · Category: structural · Domain: upper ontology
What it means for one entity to depend on another. Inherence and its inverse - the quality, role, disposition or function that a bearer carries - sitting on generic and specific dependence, with the realizable entities and the processes that realize them.
What it answers¶
- Which qualities, roles, dispositions or functions inhere in a given entity, and which entity bears a given one?
- What must exist for a given dependent entity to exist?
The pattern¶
The graph is the axioms the pattern asserts; nothing here is inferred. Drag to rearrange, scroll to zoom, and use the graph's own search box to find a term inside it.
Opens at level of detail 3: classes, individuals, properties and restrictions, without the literals. Raise it with the LOD control in the graph's own toolbar to see annotation values and anything a reasoner adds.
Should you use this one?¶
| Size | 14 classes, 6 properties, 92 axioms |
| Brings in | nothing - it stands on its own |
| Reasoning | HermiT finds this pattern consistent, with no unsatisfiable class, and its worked example consistent with the pattern. |
Its IRI is https://ontoboard.org/patterns/bfo-specific-dependence-and-inherence.owl - a name rather than an address: nothing answers there, so the download link above is the file.
Check it yourself: the published pattern · an archived copy.
If a link does not open
ontologydesignpatterns.org, which publishes most of this library, does
not currently answer over HTTPS, and its wiki redirects submission pages
to its front page. The archived copy is there for exactly that reason.
The ontology files themselves are still served over plain HTTP.
Terms it declares¶
The 20 classes and properties this pattern models, as the recommender scores them. Annotation properties and built-ins are excluded, because an annotation property is not modelling.
http://purl.obolibrary.org/obo/BFO_0000002http://purl.obolibrary.org/obo/BFO_0000003http://purl.obolibrary.org/obo/BFO_0000004http://purl.obolibrary.org/obo/BFO_0000006http://purl.obolibrary.org/obo/BFO_0000015http://purl.obolibrary.org/obo/BFO_0000016http://purl.obolibrary.org/obo/BFO_0000017http://purl.obolibrary.org/obo/BFO_0000019http://purl.obolibrary.org/obo/BFO_0000020http://purl.obolibrary.org/obo/BFO_0000023http://purl.obolibrary.org/obo/BFO_0000031http://purl.obolibrary.org/obo/BFO_0000034http://purl.obolibrary.org/obo/BFO_0000054http://purl.obolibrary.org/obo/BFO_0000055http://purl.obolibrary.org/obo/BFO_0000141http://purl.obolibrary.org/obo/BFO_0000145http://purl.obolibrary.org/obo/BFO_0000194http://purl.obolibrary.org/obo/BFO_0000195http://purl.obolibrary.org/obo/BFO_0000196http://purl.obolibrary.org/obo/BFO_0000197
An example of it in use¶
The pattern says what may be asserted; this says it. The graph below is a small set of individuals that instantiate the classes above and are connected by its properties, so the shape the pattern describes is visible as data rather than as a schema.
Import this pattern into your own ontology from inside Protégé: OntoBoard → Reuse → Pattern library…, which hands it to Import terms… and writes the term list, the module, the import and the catalog entry the way ODK expects. See Working with ODK.
Something wrong with this pattern, its example or this page? Report a problem with this pattern - the form opens with the pattern filled in, and a title and a sentence are all it needs.