Issue 13980: owlValue and allValuesFrom (odm-rtf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Critical
Summary: owlValue and allValuesFrom. The stereotype owlValue has property allValuesFrom, but the rest of the section, including the title, only describes someValuesFrom and owl:hasValue. Why is the allValuesFrom property needed on owlValue? 

Resolution: This issue and a number of others related to representation of restrictions in OWL have been addressed via extensive changes in the resolution to issue 12563.  As a part of that resolution, the «owlValue» stereotype was eliminated altogether, making this issue moot.


Revised Text: Resolution:  Closed to the resolution of Issue 12563.
Actions taken:
June 11, 2009: received issue
April 25, 2014: closed issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 11 Jun 2009 17:11:57 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report



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

Name: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.gov
Notification: Yes
Specification: Ontology Definition Metamodel
Section: UML Profile for OWL and RDF
FormalNumber: ptc/2008-09-06
Version: 
RevisionDate: 
Page: 
Nature: Revision
Severity: Critical
HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080219 Firefox/2.0.0.12 Navigator/9.0.0.6
Description
owlValue and allValuesFrom. The stereotype owlValue has property allValuesFrom, but the rest of the section, including the title, only describes someValuesFrom and owl:hasValue. Why is the allValuesFrom property needed on owlValue?