SBVR 1.2 RTF Avatar
  1. OMG Issue

SBVR12 — Simplification of SBVR by Integrating Clauses 8 & 11

  • Key: SBVR12-95
  • Legacy Issue Number: 18377
  • Status: closed  
  • Source: Rule ML Initiative ( Mr. Donald R. Chapin)
  • Summary:

    Simplification of SBVR by Integrating Clauses 8 & 11 which Cover the Same Topics and Removing Multiple Compliance Points
    Source:
    Business Semantics Ltd, Donald Chapin, (Donald.Chapin@BusinessSemantics.com)
    Summary:
    It is not possible to see all of the SBVR “Meaning and Representation” model constructs (terminological entries) on the same subtopics in one place because there are split almost evenly between Clause 8 and Clause 11.
    Since “Meaning” and “Representation” are the foundation topics of SBVR, this is a particularly significant problem.
    It is not easy to see how the whole of SBVR fits together on any one topic. Ambiguities, inconsistencies, and internal disconnects, which lead to significant confusion and misinterpretation, are masked and therefore persist.
    In addition there are a number of Issues that require moving terminological entries between Clause 8 and Clause 11, with equal arguments for having then in both Clauses.
    Further, it is not possible to re-sequence the entries in Clause 8 and Clause 11 in a cohesive way while those two clauses remain as separate top level SBVR Clauses.
    Part of the simplification of SBVR to gain full benefits should follow the example of Simplified UML. UML v2.5 has removed separate conformance levels related to subject areas and relies on vendors providing lists of specific model constructs that they support.
    SBVR already has a very formal requirement for providing list of model constructs supported. Since conformance is already defined in SBVR at the terminological entry level, removing the four level 1 Clause conformance levels will free up the structure of SBVR Clauses to enable the principles below to be implemented.
    Resolution:
    1. Integrate the terminological entires in Clauses 8 and 11 by subtopic.
    2. Remove the four Comformance Levels following the example of UML 2.5.
    Revised Text:
    … to follow

  • Reported: SBVR 1.1 — Fri, 18 Jan 2013 05:00 GMT
  • Disposition: Resolved — SBVR 1.2
  • Disposition Summary:

    1. Restructure the SBVR Table of Contents and Regroup/Resequence Terminological Entries from Clauses 8, 11 & 12 under the New Sub-clauses following these principles:
    General Simplification / Clarification Guidelines
    • As part of the simplification of UML, UML v2.5 removed separate conformance levels related to subject areas and now relies on vendors providing lists of specific model constructs that they support.

    SBVR already has a formal requirement at the terminological entry level for providing a list of model constructs supported. Since conformance is already defined in SBVR, it has remained essentially unchanged. Four level-1 Clause conformance levels were removed, thereby freeing up the SBVR clause structure to enable the principles below to be implemented.
    • No changes are proposed to any individual SBVR vocabulary entries in the SBVR Re-sequencing/Reorganizing Issue Resolutions (Ballots 2 & 3) except for updating of clause references.
    o After ballot 3, consistency of styling will be addressed as a separate issue.
    Clause Grouping Guidelines used in the proposed resequencing
    • Existing Clauses 8 and 11, which extensively covered the same topics, have been consolidated and reorganized into topic-focused subclauses.
    • The depth of clause levels has been limited to 3 in all cases. This approach avoids poorly-differentiated, confusing ‘deep dives’ into narrowly-focused topical areas. Some clauses have only 2 levels; 3 levels were not forced where unnecessary. The number of level-1 clauses has been more than doubled to provide clearer, more selective entry points into overall document content.
    • Short, descriptive clause headings were chosen at each of the 3 levels. These headings focus on essential subject matter, not mechanics or underlying assumptions. This approach keeps them as understandable and as unbiased as possible.
    • The reorganization makes it easy for business users who are primarily concerned with terminological dictionary content to recognize the SBVR clauses they need for concept definitions and definitional rules. Similarly, those primarily concerned with rulebooks can easily recognize the SBVR clauses they need for behavioral guidance.
    • "Meaning" entries and "representation" entries have been included under the same level-1 clause only in special circumstances (e.g., the guidance clauses). This separation visibly reflects the importance of the distinction between these kinds of entries, a fundamental principle in SBVR.
    • With a few important exceptions, including those listed below, sets and collections (sometimes referred to as “containers”) are treated in their own unified clause. This clause, which includes vocabularies, terminological dictionaries and rulebooks, forms a natural grouping of entries. These containers are quite different from the individual things making them up. This new clause has been placed after all clauses that introduce the kinds of individual members the containers might include. Also, the definitions and relationships of these containers are carefully separated from the verb concepts that indicate what goes into them.
    o Exception: The concept “extension” is included in the very first clause since it is fundamental to understanding of Semiotic Triangle, part of the linguistic foundation of SBVR.
    o Exception: Communities and Authorities are included in an early, level-1 clause. Without them, no meanings or elements of guidance can be birthed.
    • Adoption also forms a natural grouping in its own right and therefore is the basis of a new clause. This new clause follows the new clause on sets and collections (containers).
    Terminological Entry Grouping Guidelines
    • The re-sequencing and reorganization of entries is based on natural groupings, which build logically from one to the next. Generally (but not always) this permits introduction of terminological entries before they are referenced by other entries.
    • List verb concepts near the general concepts and roles they refer to.
    • List synonyms and antonyms near each other.
    • List 2 concepts that exhibit an interesting difference near each other.
    • Sub-clauses have been kept as small as possible, and based on tightly-related concepts. In turn, this permits small, focused diagrams to illustrate them.
    Unchanged Clauses
    • No changes were made to existing Clauses 1 and 3-6, except for clause reference numbers.
    • The following existing Clauses have not been re-sequenced or reorganized. They have been placed (and renumbered) after all business vocabulary and business rules level-1 clauses, as well as the new clauses devoted to sets and collections (“containers”) and adoption.
    .1. Clause 9 “Logical Formulation of Semantics Vocabulary”.
    .2. Clause 10 “Providing Semantic and Logical Foundations for Business Vocabulary and Rules”.
    .3. Clause 13 “SBVR’s Use of MOF and XMI”.
    .4. Clause 15 “Supporting Documents”.
    • The existing Clause 14 “Index of Vocabulary Entries (Informative)” will be regenerated from terminological entry headings.

    2. Align SBVR Clause 2 Conformance with Simplified UML Conformance and the SBVR Restructured Table of Contents
    The three objectives required to accomplish this alignment are to:
    • Add the equivalent of the two Simplified UML Types of Compliance that are relevant to SBVR.
    • Remove all references to specific compliance points except for the overall compliance with the SBVR specification.
    • Clean up language to use terms agreed for SBVR v1.2 and simplify wording for clarity.
    In the revised Clause 2 Conformance, Sub-clause 2.2 follows the pattern of Simplified UML where a parallel exists:

    Simplified UML SBVR v1.3
    Abstract syntax conformance Abstract syntax conformance
    Concrete syntax conformance (not applicable – no normative SBVR syntax)
    Model interchange conformance Terminological Dictionary and/or Rulebook interchange conformance
    Diagram interchange conformance (not applicable – no normative SBVR syntax)
    Semantic conformance Semantics conformance

    Sub-clause 2.2 provides the specifics for “support for SBVR concepts that are defined in Clauses 8-21 of this specification and implemented in the SBVR XMI Metamodel as specified in Clause 23”
    Sub-clause 2.4 provides the specifics for “Terminological Dictionary and/or Rulebook interchange conformance”.

    3. Spin-off SBVR Issue 19439 for regrouping of concepts in SBVR Diagram Figures based on the Restructured SBVR Table of Contents and make fixes to narrative text resulting from Items 1. and 2. above.

    Note: Except for Clause 2 Conformance, Clause 13 SBVR’s Use of MOF and XMI, and the four Vocabulary Container Headers, references in narrative text to the removed vocabularies are updated in this Spin-off Issue.

  • Updated: Tue, 14 Apr 2015 17:27 GMT