Ontologies Classes Object Properties Data Properties Annotation Properties Individuals Datatypes Clouds

Annotation Property: rdfs:comment

Usage (13)

  • entity 'editor note' "Entity doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. For example Werner Ceusters 'portions of reality' include 4 sorts, entities (as BFO construes them), universals, configurations, and relations. It is an open question as to whether entities as construed in BFO will at some point also include these other portions of reality. See, for example, 'How to track absolutely everything' at http://www.referent-tracking.com/_RTU/papers/CeustersICbookRevised.pdf" @en 
    • 'has axiom label' http://purl.obolibrary.org/obo/bfo/axiom/0000004
    • rdfs:comment "per discussion with Barry Smith"
    • rdfs:seeAlso http://www.referent-tracking.com/_RTU/papers/CeustersICbookRevised.pdf
  • occurrent 'editor note' "Occurrent doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. An example would be the sum of a process and the process boundary of another process." @en 
    • 'has axiom label' http://purl.obolibrary.org/obo/bfo/axiom/0000006
    • rdfs:comment "per discussion with Barry Smith"
  • 'spatial region' 'editor note' "Spatial region doesn't have a closure axiom because the subclasses don't exhaust all possibilites. An example would be the union of a spatial point and a spatial line that doesn't overlap the point, or two spatial lines that intersect at a single point. In both cases the resultant spatial region is neither 0-dimensional, 1-dimensional, 2-dimensional, or 3-dimensional." @en 
    • 'has axiom label' http://purl.obolibrary.org/obo/bfo/axiom/0000002
    • rdfs:comment "per discussion with Barry Smith"
  • 'temporal region' 'editor note' "Temporal region doesn't have a closure axiom because the subclasses don't exhaust all possibilites. An example would be the mereological sum of a temporal instant and a temporal interval that doesn't overlap the instant. In this case the resultant temporal region is neither 0-dimensional nor 1-dimensional" @en 
    • 'has axiom label' http://purl.obolibrary.org/obo/bfo/axiom/0000003
    • rdfs:comment "per discussion with Barry Smith"
  • 'specifically dependent continuant' 'editor note' "Specifically dependent continuant doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. We're not sure what else will develop here, but for example there are questions such as what are promises, obligation, etc." @en 
    • 'has axiom label' http://purl.obolibrary.org/obo/bfo/axiom/0000005
    • rdfs:comment "per discussion with Barry Smith"
  • 'realized in' rdfs:comment "Paraphrase of elucidation: a relation between a realizable entity and a process, where there is some material entity that is bearer of the realizable entity and participates in the process, and the realizable entity comes to be realized in the course of the process" 
  • realizes rdfs:comment "Paraphrase of elucidation: a relation between a process and a realizable entity, where there is some material entity that is bearer of the realizable entity and participates in the process, and the realizable entity comes to be realized in the course of the process" 
  • 'occurs in' rdfs:comment "Paraphrase of definition: a relation between a process and an independent continuant, in which the process takes place entirely within the independent continuant" 
  • 'contains process' rdfs:comment "Paraphrase of definition: a relation between an independent continuant and a process, in which the process takes place entirely within the independent continuant" 
  • 'zero-dimensional continuant fiat boundary' 'editor note' "zero dimension continuant fiat boundaries are not spatial points. Considering the example 'the quadripoint where the boundaries of Colorado, Utah, New Mexico, and Arizona meet' : There are many frames in which that point is zooming through many points in space. Whereas, no matter what the frame, the quadripoint is always in the same relation to the boundaries of Colorado, Utah, New Mexico, and Arizona." @en 
    • 'has axiom label' http://purl.obolibrary.org/obo/bfo/axiom/0000001
    • rdfs:comment "requested by Melanie Courtot"
    • rdfs:seeAlso https://groups.google.com/d/msg/bfo-owl-devel/s9Uug5QmAws/ZDRnpiIi_TUJ
  • rdfs:comment "Please see the project site https://github.com/BFO-ontology/BFO, the bfo2 owl discussion group http://groups.google.com/group/bfo-owl-devel, the bfo2 discussion group http://groups.google.com/group/bfo-devel, the tracking google doc http://goo.gl/IlrEE, and the current version of the bfo2 reference http://purl.obolibrary.org/obo/bfo/dev/bfo2-reference.docx. This ontology is generated from a specification at https://github.com/BFO-ontology/BFO/tree/master/src/ontology/owl-group/specification/ and with the code that generates the OWL version in https://github.com/BFO-ontology/BFO/tree/master/src/tools/. A very early version of BFO version 2 in CLIF is at http://purl.obolibrary.org/obo/bfo/dev/bfo.clif." @en
  • rdfs:comment "The BSD license on the BFO project site refers to code used to build BFO." @en
  • rdfs:comment "This BFO 2.0 version represents a major update to BFO and is not strictly backwards compatible with BFO 1.1. The previous OWL version of BFO, version 1.1.1 will remain available at http://ifomis.org/bfo/1.1 and will no longer be updated. The BFO 2.0 OWL is a classes-only specification. The incorporation of core relations has been held over for a later version."

OWL HTML inside