SBVR 1.2 RTF Avatar
  1. OMG Issue

SBVR12 — "Three Editing Instructions Overlooked in Issue 17017 Resolution

  • Key: SBVR12-76
  • Legacy Issue Number: 17098
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Edward J. Barkmeyer)
  • Summary:

    Problem: The Revised Text of 17017 makes no mention of clause 13.2.2.

    In clause 13.2.2, the first paragraph contains the sentence: "The signifier of each synonym of the designation is an alias for the class." Nothing is said in 13.2.2 about how to encode the "alias", but the diagram in 13.2.2 shows an "element import". The revised text does not, but should, delete this drawing element as well.

    Further, under the Rationale subhead in 13.2.2, the first sentence

    reads: "Use of aliasing, though not common in MOF-based metamodels, keeps a strong alignment of the SBVR Metamodel with the SBVR vocabulary." Presumably, that will no longer be the case if the element imports are deleted.

    I suggest it should rather read:

    "In general, MOF does not provide a mechanism for declaring synonyms.

    Therefore, the Synonym elements of the SBVR vocabularies do not have counterparts in the SBVR MOF metamodel. They are, however, captured in SBVR vocabularies that are instances of the SBVR MOF metamodel."

  • Reported: SBVR 1.1 — Wed, 1 Feb 2012 05:00 GMT
  • Disposition: Resolved — SBVR 1.2
  • Disposition Summary:

    Add the three overlooked editing instuctions to complete those in Issue 17017 resolution.

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