BACM 1.1b1 RTF Avatar
  1. OMG Issue

BACM11 — Change naming convention of OWL object properties and datatype properties

  • Key: BACM11-40
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. James Rhyne)
  • Summary:

    In the OWL, namespaces were translated as IRI segments. Object properties and datatype properties were considered to be in the namespace created by their owning class (class stereotyped associations are reified in the translation to XMI and OWL). This made the use of qnames infeasible as the name part of the qname cannot contain multiple segments. Yet simple names cannot be used in the XMI or OWL because of name conflicts that are resolved by including the owning class namespace.

  • Reported: BACM 1.0b2 — Thu, 4 Apr 2024 14:57 GMT
  • Disposition: Resolved — BACM 1.1b1
  • Disposition Summary:

    Create dot-separated names for object properties and datatype properties

    In the MOF XMI translation that reifies stereotyped associations, name the generated associations as <class_name>.<assn_name>. This name syntax is legal in both MOF XMI and in OWL. It resolves name conflicts by prefixing the association name with the name of its owning class.
    Carry out the same name translation for ownedAttributes.
    This is an exception to the basic name translation that creates namespaces for packages and classes.

  • Updated: Mon, 24 Mar 2025 13:37 GMT