BFO 2020
Features
Temporal
-
-
To satisfy needs of the community then, the BFO development team encourages a strategy of developing and deploying Temporal Extensions which will provide users options for representing time in their domains.
-
Given the need to represent time and change in many domains and the wide use of OWL in ontology circles, proposals have been offered by users of BFO for representing such phenomena within the binary constraints of OWL. Examples include:
-
Competency Questions for temporal representation
How to turn dates into into temporal information
- https://github.com/CommonCoreOntology/CommonCoreOntologies/issues/118#issuecomment-810285200
- Purposes:
- reasoning and inferencing; when rules can't be express in (OWL?) DL, use Spin
- sparql queries for now or historical
- recording provenance. "text in a document that denotes a day, month, or year is typically as close as I can get to knowing the temporal region during which a process occurs."
- assumption: "The temporal region does not explicitly state the starting and ending moments, but these values can be calculated."
- I assert the process to be the subject of an Information Content Entity, which in turn generically depends on an Information Bearing Entity. The Information Bearing Entity is the subject of a triple in the above form, where the predicate is cco:has_date_value and the object is a literal, either with a language tag or of type xsd:string.
- I create a temporal interval based on the text literal. I associate the temporal interval with the process and the Information Content Entity.
:process occupies-temporal-region :tr .
:tr designated-by :ice .
:ice generically-depends-on-at-all-times :ibe .
:ibe has-date-value "March 31"@en .
This establishes provenance. Next I create temporal instants representing the first and last instants of March 31:
:instant-01 a cco:TemporalInstant .
:instant-02 a cco:TemporalInstant .
:tr has-first-instant :instant-01 .
:tr has-last-instant :instant-02 .
Backlinks