CommonCoreOntologies

CommonCoreOntologies copied to clipboard

Capacity and Payload Capacity be made Qualities, not Functions.

43

I suggest that a generic term Capacity be introduced as a subclass of Quality and Payload Capacity be moved accordingly. A function is the reason that something exists. I am...

cameronmore

Always include a BFO import

1

AFAICT the only ontology that explicitly imports BFO is the extended relation ontology. If that doesn't happen to be imported when you open one of the component files then there...

alanruttenberg

The definition of cco:Organism is too narrow

9

The present definition is "An Object that is an Animal or Plant." This rules out bacteria, fungi, and hence is at odds with scientific standards.

neilotte

Data sets, Data collections, Data aggregates - what is the proper BFO branch?

1

I am trying to sort out what a collection of information entities is. If someone says, "I have a dataset", I want to translate that into either the Information Bearing...

jonathanvajda

There is a need for basic hunting terms at a mid-level of generality. It seems like a good idea to add hunting, fishing, and trapping together and allow users to...

cameronmore

Make cco:acronym a sub-property of skos:altLabel

3

During the one-off Annotation meeting on 12-15-23, consensus was reached that (see "Annotation-Discussion-12-15" minutes on TRMC): - either skos:altLabel or cco:acronym will be used for all acronyms - cco:acronym will...

johnbeve

Issue found on line 12454 of MergedAllCoreOntology-v1.5-2024-02-14.ttl

2

The cco:definition_source on line 12454 has a type of xsd:anyURI. However the string for the definition_source reads "https://oceanservice.noaa.gov/facts/cryosphere.html (accessed 03/06/2023)". The "(accessed 03/06/2023)" portion of the value needs to be...

sgranite

Issue importing bfo-core.ttl

8

I'm having a problem with the owl:imports directives in the current version of master (commit a9e8c72e), I'm using Protege 5.5. When it loads ExtendedRelationOntology.ttl, it processes the imports directive but...

swartik

May I suggest adding has_role, has_dispostion, and has_quality back as object properties. Their presence clarifies design patterns. Aggregate_bearer_of still has the equivalent sub-object properties.

CarterBeauBenson

Avoid (Ontological) Weasel Words in Definitions (unnecessary phrases or clauses that merely suggest a boundary)

1

I had conversation with the CUBRC team offline, but I was told to make this request public. Definitions should avoid examples and intentionally vague language. This isn't an inviolable rule,...

jonathanvajda