${taskforce.name} Avatar
  1. OMG Task Force

ODM FTF — Closed Issues

  • Key: ODM
  • Issues Count: 6
Open Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

Bi-directional URIReferenceForNamespace association

  • Key: ODM-4
  • Legacy Issue Number: 11105
  • Status: closed  
  • Source: International Business Machines ( Mr. Guo Tong Xie)
  • Summary:

    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.

  • Reported: ODM 1.0b1 — Wed, 20 Jun 2007 04:00 GMT
  • Disposition: Resolved — ODM 1.0b2
  • Disposition Summary:

    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.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Role name of superProperty

  • Key: ODM-3
  • Legacy Issue Number: 11104
  • Status: closed  
  • Source: International Business Machines ( Mr. Guo Tong Xie)
  • Summary:

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

  • Reported: ODM 1.0b1 — Wed, 20 Jun 2007 04:00 GMT
  • Disposition: Resolved — ODM 1.0b2
  • Disposition Summary:

    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.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Role name of superClass

  • Key: ODM-2
  • Legacy Issue Number: 11103
  • Status: closed  
  • Source: International Business Machines ( Mr. Guo Tong Xie)
  • Summary:

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

  • Reported: ODM 1.0b1 — Wed, 20 Jun 2007 04:00 GMT
  • Disposition: Resolved — ODM 1.0b2
  • Disposition Summary:

    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.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Cardinality of OWLInverseOf

  • Key: ODM-5
  • Legacy Issue Number: 11106
  • Status: closed  
  • Source: International Business Machines ( Mr. Guo Tong Xie)
  • Summary:

    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

  • Reported: ODM 1.0b1 — Wed, 20 Jun 2007 04:00 GMT
  • Disposition: Resolved — ODM 1.0b2
  • Disposition Summary:

    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.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Set value for annotation property in UML profile for OWL

  • Key: ODM-6
  • Legacy Issue Number: 11107
  • Status: closed  
  • Source: International Business Machines ( Mr. Guo Tong Xie)
  • Summary:

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

  • Reported: ODM 1.0b1 — Wed, 20 Jun 2007 04:00 GMT
  • Disposition: Duplicate or Merged — ODM 1.0b2
  • Disposition Summary:

    Disposition: See issue 12391 for disposition

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Common Logic Metamodel is out of sync with the ISO FDIS CL specification

  • Key: ODM-1
  • Legacy Issue Number: 11101
  • Status: closed  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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

  • Reported: ODM 1.0b1 — Wed, 13 Jun 2007 04:00 GMT
  • Disposition: Resolved — ODM 1.0b2
  • Disposition Summary:

    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)

  • Updated: Fri, 6 Mar 2015 20:58 GMT