Issue 13938: NamespaceDefinition is defined as a metaclass, without a stereotype (odm-rtf) Source: Thematix Partners LLC (Mrs. Elisa F. Kendall, ekendall(at)thematix.com) Nature: Revision Severity: Significant Summary: NamespaceDefinition is defined as a metaclass, without a stereotype, in the UML profile for RDF, which is not allowed in UML 2. The definition requires revision to include a stereotype. Resolution: This is a fairly straightforward correction, as described in the resolution, below Revised Text: Revise section 14.1.2.1 NamespaceDefinition, as follows: 1. Rename the section from “NamespaceDefintion” to “Namespace Definitions” 2. Under Stereotype and Base Class, change “None” to “«namespaceDefinition» with base class of UML::InstanceSpecification” 3. Under Properties, change namespaceURI: String [1] – the string representing the namespace URI to namespaceIRI: String [1] – the string representing the namespace IRI 4. Under Constraints, change [2] The string value of the namespace URI must conform to the character encoding (including escape sequences and so forth) defined in [RDF Syntax] and [XMLNS]. to [2] The string value of the namespace IRI must be a Unicode string that conforms to the syntax defined in RFC 3987, normalized according to Section 5 of RFC 3987 if possible. Actions taken: May 27, 2009: received issue April 25, 2014: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 27 May 2009 20:08:02 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Elisa Kendall Company: Sandpiper Software, Inc. mailFrom: ekendall@sandsoft.com Notification: No Specification: Ontology Definition Metamodel (ODM) Section: 14.1.2.1 FormalNumber: ptc/2008-09-07 Version: Beta 3 / 1.0 RevisionDate: 09/2008 Page: 132 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729) Description NamespaceDefinition is defined as a metaclass, without a stereotype, in the UML profile for RDF, which is not allowed in UML 2. The definition requires revision to include a stereotype.