ODM 1.0b2 NO IDEA Avatar
  1. OMG Issue

ODM — 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