Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

SBVR Exchange Metamodel

Revision as of 18:24, 10 April 2008 by dcarlson.xmlmodeling.com (Talk | contribs) (Issue 1: designation::signifier)

This page summarizes issues that were encountered in the SBVR 1.0 metamodel CMOF definition and how they are resolved in this EMF-based implementation.

  • The SBVR CMOF model as published with the OMG specification
  • The revised model is available as SBVR.uml in CVS org.eclpse.sbvr/models

Issues

Issue 1: designation::signifier

Class diagram created from the original SBVR 1.0 metamodel specification:

representation::expression has multiplicity [1..1] and is thus required in all specializations. The SBVR 1.0 specification indicates that designation::signifier {subsets expression}, but the {subsets} reference is not included in the CMOF model. Without the subsets reference, the designation subclass will require values for both expression and signifier.

  • Change designation::signifier to add {subsets expression}

The specification also shows that designation::signifier has multiplicity [1..1], but it is [0..*] in the CMOF model. This expanded multiplicity is also incompatible with use of {subsets}.

  • Change designation::signifier multiplicity to [1..1]

Issue 2:

Issue 3:

Resolutions

Track the resolution by OMG SBVR revision task force committee.

Back to the top