In section 10.7.3, URIReferenceForNamespace should be changed to two uni-directional associations between URIReference and Namespace. In the current model, if two URIReference have the same Namespace, it could not be represented.

This issue really identifies the need for two relationships between these classes.
It calls for an additional role that would yield links to all the URIReferences
"contained" in a Namespace. The current association between these two classes is meant to represent URIReferences which identify namespaces, hence the association name URIReferenceForNamespace, while the URIReferences in question would identify elements in an owl ontology or rdfs vocabulary and not Namespaces. As the model stands, there is no easy way to derive this information.

The change to address this involves the addition of a new bi-directional association, URIReferenceInNamespace, between the URIReference and Namespace classes, as shown below.

In section 10.5.1, the role name of superProperty in PropertyGeneralization is confusing. It might be changed to subProperty

During the Jun 27th telecon, participants agreed that superProperty seems synonymous with RDFSsubPropertyOf, and that it should be changed to superPropertyOf, for consistency with other naming conventions in the metamodel.

In section 10.4.1, the role name of superClass in ClassGeneralization is confusing. It might be changed to subClass

During the June 27th telecon, participants agreed that superClass seems synonymous with RDFSsubClassOf, and that it should be changed to superClassOf, for consistency with other naming conventions in the metamodel.

In section 11.4.5, the cardinality of OWLInverseOf in InverseProperty association should be changed from 0..1 to 0..*. One property can have multiple inverse properties

In section 11.4.5, the cardinality of OWLInverseOf in InverseProperty association should be changed from 0..1 to 0..*. One property can have multiple inverse properties.

In section 14.2.3.1, it is not clear on how to set values for annotation property

Disposition: See issue 12391 for disposition

Specification: Ontology Definition Metamodel
FormalNumber: ptc/06-10-11
Section: 12
Summary: Common Logic Metamodel is out of sync with the ISO FDIS CL specification.

Description: Minor changes were made to the CL language as it was finalized through the ISO process, which are not reflected in the ODM specification. These include text and diagram / model / xmi changes, which, although minor, should be resynchronized now that the ISO standardization process is complete

Revise the CL metamodel and related text as follows. Changes include:
§ Revised reference to the FDIS CL specification
§ Addition of Association CommentedText to and elimination of Association CommentedPhrase from the Phrases Diagram (Figure 12.1)
§ Rename Association ArgumentsForFunctionalTerm to ArgumentSequenceForFunctionalTerm (Figure 12.2)
§ Rename Association ArgumentsForAtomicSentence to ArgumentSequenceForAtomicSentence (Figure 12.3)
§ Rename Association BindingSequence to BindingSequenceForQuantifiedSentence (Figure 12.6) and provide missing paragraph (12.7.1 Binding)