Issue 12563: UML Profile for RDF and OWL, Section 14.2.5 (odm-ftf)
Source: Thematix Partners LLC (Mrs. Elisa F. Kendall, ekendall(at)thematix.com)
Nature: Revision
Severity: Significant
Summary: The current method for specifying OWL restrictions (e.g., owl:allValuesFrom, owl:someValuesFrom, owl:hasValue) in the profile does not provide a means to differentiate, on a diagram, between the restriction types. Further, it does not create the proper "necessary and sufficient" or "necessary" relationships between the class to which the restriction applies and the anonymous class specified by the restriction.

Resolution: 
Revised Text: 
Actions taken:
July 10, 2008: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 10 Jul 2008 12:59:33 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report



--------------------------------------------------------------------------------

Name: Elisa Kendall
Company: Sandpiper Software
mailFrom: ekendall@sandsoft.com
Notification: No
Specification: Ontology Definition Metamodel 1.0 Beta 2
Section: UML Profile for RDF and OWL, Section 14.2.5
FormalNumber: ptc/07-09-09
Version: 1.0 Beta 2
RevisionDate: 11/01/07
Page: 155
Nature: Revision
Severity: Significant
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
The current method for specifying OWL restrictions (e.g., owl:allValuesFrom, owl:someValuesFrom, owl:hasValue) in the profile does not provide a means to differentiate, on a diagram, between the restriction types. Further, it does not create the proper "necessary and sufficient" or "necessary" relationships between the class to which the restriction applies and the anonymous class specified by the restriction.