-
Key: COMMONS-12
-
Status: closed
-
Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
-
Summary:
Users are confused as to whether they need comprises or hasConstituent or hasMember or hasPart.
In order to address this, we need to augment some of the properties with disjointness, such as between comprises and hasPart. Then we need to make clear that membership involves discrete elements and constituency may or may not involve discrete elements. hasConstituent can be used with cardinality constraints whereas hasPart cannot be due to OWL reasoning constraints.
-
Reported: Commons 1.0b1 — Fri, 12 Aug 2022 19:13 GMT
-
Disposition: Resolved — COMMONS 1.0
-
Disposition Summary:
Clarify the use of several properties in the Collections ontology
Clarify the definition of properties related to inclusion, including when to use comprises vs. hasPart (which is transitive), and hasConstituent vs. hasMember (whose elements are discrete and countable), making hasConstituent and hasMember disjoint in the Collections ontology
-
Updated: Tue, 28 Mar 2023 17:31 GMT
-
Attachments:
- Collections.rdf 12 kB (application/rdf+xml)
COMMONS — The properties in the collections ontology are confusing to users
- Key: COMMONS-12
- OMG Task Force: Commons Ontology Library (Commons) 1.0 FTF