Issue 18377: Simplification of SBVR by Integrating Clauses 8 & 11 (sbvr-rtf)
Source: Business Semantics Ltd. (Mr. Donald R. Chapin, Donald.Chapin(at)BusinessSemantics.com)
Nature: Uncategorized Issue
Severity: 
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

Resolution: 
Revised Text: 
Actions taken:
January 18, 2013: received issue
Discussion: 

End of Annotations:=====
sposition: Resolved
OMG Issue No:  18377
Title:	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
Disposition:	Resolved