Issue 12395: OWL Cardinality Constraints text revision (odm-ftf) Source: Thematix Partners LLC (Mrs. Elisa F. Kendall, ekendall(at)thematix.com) Nature: Clarification Severity: Minor Summary: From the ODM FTF2 meeting minutes of February 20th: Cardinality constraints -- the second paragraph of the description states: "Additionally, isOrdered = false on OWL properties, and isUnique = true on owl properties...". These "constraints" are not specified in the owl properties section (14.2.6) - should they apply to all owl properties, or only to cardinality constraints? According to Conrad, this text should apply to all RDF and OWL properties, but it comes from the text on multiplicities in UML, which is why it landed in this section of the document. Note that it does occur under the rdfProperty section of the profile specification, so it does apply to all properties ... thus we might remove the "OWL" from the sentence for further clarification. Resolution: In section 14.2.5.4, clarify the text for OWL cardinality constraints as suggested. Revised Text: Currently, the second paragraph under the 14.2.5.4 heading reads as follows: Value specifications for multiplicities in OWL must be non-negative integer literals. Additionally, isOrdered = false on OWL properties, and isUnique = true on OWL properties, meaning that the values are a set, not a bag. Revise the second sentence to be: Additionally, isOrdered = false and isUnique = true on all RDF and OWL properties, meaning that the values are a set, not a bag. Actions taken: April 17, 2008: received issue January 19, 2009: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 17 Apr 2008 20:20:53 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Elisa Kendall Company: Sandpiper Software, Inc. mailFrom: ekendall@sandsoft.com Notification: No Specification: OWL Cardinality Constraints text revision Section: 14.2.5.4 FormalNumber: ptc/07-09-09 Version: ODM 1.0 Beta 2 Specification RevisionDate: 11/2007 Page: 285 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1) Description From the ODM FTF2 meeting minutes of February 20th: Cardinality constraints -- the second paragraph of the description states: "Additionally, isOrdered = false on OWL properties, and isUnique = true on owl properties...". These "constraints" are not specified in the owl properties section (14.2.6) - should they apply to all owl properties, or only to cardinality constraints? According to Conrad, this text should apply to all RDF and OWL properties, but it comes from the text on multiplicities in UML, which is why it landed in this section of the document. Note that it does occur under the rdfProperty section of the profile specification, so it does apply to all properties ... thus we might remove the "OWL" from the sentence for further clarification.