Issue 18367: The SBVR document is far larger than optimal. It needs to be reduced in size (sbvr-rtf) Source: Business Rule Solutions, LLC (Mr. Ron Ross, rross(at)brsolutions.com) Nature: Uncategorized Issue Severity: Summary: The SBVR document is far larger than optimal. It needs to be reduced in size. Many of the Annexes do not contribute directly to core content. Resolution Delete Annexes that are not essential to the SBVR specification. Evaluation of the Annexes: Annexes essential to the correct interpretation of the normative specification and that must be kept: Annex C - SBVR Structured English Annex E - EU-Rent Example Annex H - Use of UML Notation in a Business Context to Represent SBVR-Style Vocabularies Annex M - Additional References Annexes that are not essential and can be deleted. Their owners can choose whether to publish them independently: Annex F - The RuleSpeak® Business Rule Notation* Annex G - Concept Diagram Graphic Notation Annex I - The ORM Notation for Verbalizing Facts and Business Rules* Annex J - ORM Examples Related to the Logical Foundations for SBVR Annex L - A Conceptual Overview of SBVR and the NIAM2007 Procedure to Specify a Conceptual Schema The SBVR RTF should decide on a case by case basis whether the following Annexes are essential to the correct interpretation of the normative clauses or can be deleted: Annex A - Overview of the Approach Annex B - The Business Rules Approach Annex D - SBVR Structured English Patterns Annex K - Mappings and Relationships to Other Initiatives *To be discussed by the RTF: Since (a) SBVR-SE is not normative, and (b) RuleSpeak and ORM (Norma) served as reference notations in creating the specification, it might be useful to illustrate parts or all of Annexes C and/or E, and/or examples given in the specification itself, in these other two notations. Annexes F and I already did something like this, but (a) are much too large, (b) not well-focused on complementing SBVR, and (c) may need to be revised. Resolution: Revised Text: Actions taken: January 9, 2013: received issue Discussion: End of Annotations:===== hoo-Newman-Id: 261404.51495.bm@smtp108.sbc.mail.mud.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: l5xnKl0VM1lKY5LOI59Ti6mpp6U_YdLBX.g1ihhu6Id2rgc ag5tZO8a2PCKjO3KxTKvQhlFgEEx3922dGrvLvrKbN7ZZgPu1.gw80.xvUdY YHdni51Z8m7fx4b0RBpYKkMW0dEopFKuQNUJ9DqtzqBn8UC6ID7xMEOiesPB ZZq_LnEqr1W1T1FL4ZUfnHuOLkskgStDH8hlBBrtGqC9ATgqp7xMniYjnku_ OJMU7DnhBKTHZ5p2hCD5OqsAB_1zRMLlhywyaTSKHBrCaMf6puSmeMq6uonF b3vF2Kw__QrdsTuwCIvZlWuZE7GEqNsev2DtHn5Z9y9SqnOHceCMxsd8SHDo AjiLH5PaGDLTl9.2fVNuc9h.XJ6_et6N7aaXRSQM.cfBYhGe.jE8WWJnb76x NkfOggUYgHYyaKh2YxMhACXAL4V7oWxNbQ.2KRw3pMvSaak1OoDw_MZoS7.X 2YRVoe9TQp9vYdE4kleoNRFL4Uzfn5Ss1vkvhWFAni_CdoXVAKjAsQtwC8Vq 7rZzefU_DYtd6DU_jDj1GxL0EtHEtDd_yxYWInu6FHYVqIJQ3nP30Xe5lR5H fdFcad8QGntR3.kL.55k_bZKedm9FpV44KhnpmTxvHwp4oR0G6ZXZ6HOKeo3 KS32hgIMubR.zwgPiIqrPsbN3ss9z8CkVvniLXctv4gjkgXQszwXuTHcAMBI S7Ye0c8iFntlEGVTulAZz56PD3SZbtZEurhKZzZ4- X-Yahoo-SMTP: MhfrpU2swBDLgYiYhNQDHBu0cE4o.vu2We1FRN9o X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 09 Jan 2013 20:04:33 -0600 To: Juergen Boldt From: "Ronald G. Ross" Subject: please post this new SBVR issue (Thx) Cc: Donald Chapin Problem The SBVR document is far larger than optimal. It needs to be reduced in size. Many of the Annexes do not contribute directly to core content. Resolution Delete Annexes that are not essential to the SBVR specification. Evaluation of the Annexes: Annexes essential to the correct interpretation of the normative specification and that must be kept: Annex C - SBVR Structured English Annex E - EU-Rent Example Annex H - Use of UML Notation in a Business Context to Represent SBVR-Style Vocabularies Annex M - Additional References Annexes that are not essential and can be deleted. Their owners can choose whether to publish them independently: Annex F - The RuleSpeak® Business Rule Notation* Annex G - Concept Diagram Graphic Notation Annex I - The ORM Notation for Verbalizing Facts and Business Rules* Annex J - ORM Examples Related to the Logical Foundations for SBVR Annex L - A Conceptual Overview of SBVR and the NIAM2007 Procedure to Specify a Conceptual Schema The SBVR RTF should decide on a case by case basis whether the following Annexes are essential to the correct interpretation of the normative clauses or can be deleted: Annex A - Overview of the Approach Annex B - The Business Rules Approach Annex D - SBVR Structured English Patterns Annex K - Mappings and Relationships to Other Initiatives *To be discussed by the RTF: Since (a) SBVR-SE is not normative, and (b) RuleSpeak and ORM (Norma) served as reference notations in creating the specification, it might be useful to illustrate parts or all of Annexes C and/or E, and/or examples given in the specification itself, in these other two notations. Annexes F and I already did something like this, but (a) are much too large, (b) not well-focused on complementing SBVR, and (c) may need to be revised. Blog || http://www.RonRoss.info/blog/ LinkedIn || http://www.linkedin.com/pub/ronald-ross/1/3b/346 Twitter || https://twitter.com/Ronald_G_Ross Homepage || http://www.RonRoss.info From: "Donald Chapin" To: Subject: RE: issue 18367 -- SBVR RTF issue -- "The SBVR document is far larger than optimal" Date: Thu, 14 Feb 2013 18:40:16 -0000 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac4K4rQX15FRq2g5Ry2ZFMypWe+HJQ== X-Mirapoint-IP-Reputation: reputation=Good-1, source=Queried, refid=tid=0001.0A0B0301.511D2F97.0021, actions=tag X-Junkmail-Premium-Raw: score=12/50, refid=2.7.2:2013.2.14.180619:17:12.185, ip=81.149.51.65, rules=__HAS_FROM, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __HAS_MSGID, __SANE_MSGID, __MIME_VERSION, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART, __CTYPE_MULTIPART_MIXED, __HAS_X_MAILER, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, DOC_ATTACHED, __ANY_URI, LINK_TO_IMAGE, URI_ENDS_IN_HTML, INFO_TLD, __FRAUD_BODY_WEBMAIL, __FRAUD_CONTACT_NUM, __STOCK_PHRASE_24, ECARD_KNOWN_DOMAINS, __CP_URI_IN_BODY, __C230066_P5, SUPERLONG_LINE, __HTML_MSWORD, __HTML_FONT_BLUE, __HAS_HTML, BODY_SIZE_10000_PLUS, __MIME_HTML, __TAG_EXISTS_HTML, __STYLE_RATWARE_2, RDNS_GENERIC_POOLED, HTML_90_100, HTML_95_100, HTML_98_100, HTML_99_100, HTML_999_100, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL, FORGED_MUA_OUTLOOK X-Junkmail-Status: score=12/50, host=c2bthomr13.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020C.511D2F99.0017,ss=1,re=0.000,vtr=str,vl=0,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine X-Junkmail-IWF: false X-Virus-Scanned: amavisd-new at omg.org All . Attached is the draft resolution of SBVR Issue 18367 âThe SBVR document is far larger than optimalâ for discussion in tomorrowâs SBVR RTF telecon, and for inclusion in SBVR v1.2 scheduled to be presented to the Architecture Board at the March OMG Technical Meeting. Donald From: Juergen Boldt [mailto:juergen@omg.org] Sent: 10 January 2013 14:38 To: issues@omg.org; sbvr-rtf@omg.org Subject: issue 18367 -- SBVR RTF issue X-Yahoo-Newman-Id: 261404.51495.bm@smtp108.sbc.mail.mud.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: l5xnKl0VM1lKY5LOI59Ti6mpp6U_YdLBX.g1ihhu6Id2rgc ag5tZO8a2PCKjO3KxTKvQhlFgEEx3922dGrvLvrKbN7ZZgPu1.gw80.xvUdY YHdni51Z8m7fx4b0RBpYKkMW0dEopFKuQNUJ9DqtzqBn8UC6ID7xMEOiesPB ZZq_LnEqr1W1T1FL4ZUfnHuOLkskgStDH8hlBBrtGqC9ATgqp7xMniYjnku_ OJMU7DnhBKTHZ5p2hCD5OqsAB_1zRMLlhywyaTSKHBrCaMf6puSmeMq6uonF b3vF2Kw__QrdsTuwCIvZlWuZE7GEqNsev2DtHn5Z9y9SqnOHceCMxsd8SHDo AjiLH5PaGDLTl9.2fVNuc9h.XJ6_et6N7aaXRSQM.cfBYhGe.jE8WWJnb76x NkfOggUYgHYyaKh2YxMhACXAL4V7oWxNbQ.2KRw3pMvSaak1OoDw_MZoS7.X 2YRVoe9TQp9vYdE4kleoNRFL4Uzfn5Ss1vkvhWFAni_CdoXVAKjAsQtwC8Vq 7rZzefU_DYtd6DU_jDj1GxL0EtHEtDd_yxYWInu6FHYVqIJQ3nP30Xe5lR5H fdFcad8QGntR3.kL.55k_bZKedm9FpV44KhnpmTxvHwp4oR0G6ZXZ6HOKeo3 KS32hgIMubR.zwgPiIqrPsbN3ss9z8CkVvniLXctv4gjkgXQszwXuTHcAMBI S7Ye0c8iFntlEGVTulAZz56PD3SZbtZEurhKZzZ4- X-Yahoo-SMTP: MhfrpU2swBDLgYiYhNQDHBu0cE4o.vu2We1FRN9o X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 09 Jan 2013 20:04:33 -0600 To: Juergen Boldt From: "Ronald G. Ross" Subject: please post this new SBVR issue (Thx) Cc: Donald Chapin Problem The SBVR document is far larger than optimal. It needs to be reduced in size. Many of the Annexes do not contribute directly to core content. Resolution Delete Annexes that are not essential to the SBVR specification. Evaluation of the Annexes: Annexes essential to the correct interpretation of the normative specification and that must be kept: Annex C - SBVR Structured English Annex E - EU-Rent Example Annex H - Use of UML Notation in a Business Context to Represent SBVR-Style Vocabularies Annex M - Additional References Annexes that are not essential and can be deleted. Their owners can choose whether to publish them independently: Annex F - The RuleSpeak Business Rule Notation* Annex G - Concept Diagram Graphic Notation Annex I - The ORM Notation for Verbalizing Facts and Business Rules* Annex J - ORM Examples Related to the Logical Foundations for SBVR Annex L - A Conceptual Overview of SBVR and the NIAM2007 Procedure to Specify a Conceptual Schema The SBVR RTF should decide on a case by case basis whether the following Annexes are essential to the correct interpretation of the normative clauses or can be deleted: Annex A - Overview of the Approach Annex B - The Business Rules Approach Annex D - SBVR Structured English Patterns Annex K - Mappings and Relationships to Other Initiatives *To be discussed by the RTF: Since (a) SBVR-SE is not normative, and (b) RuleSpeak and ORM (Norma) served as reference notations in creating the specification, it might be useful to illustrate parts or all of Annexes C and/or E, and/or examples given in the specification itself, in these other two notations. Annexes F and I already did something like this, but (a) are much too large, (b) not well-focused on complementing SBVR, and (c) may need to be revised. Blog || http://www.RonRoss.info/blog/ LinkedIn || http://www.linkedin.com/pub/ronald-ross/1/3b/346 Twitter || https://twitter.com/Ronald_G_Ross Homepage || http://www.RonRoss.info Juergen Boldt Director, Member Services 109 Highland Ave Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org Issue 18367 - The SBVR document is far larger than optimal.doc Disposition: Resolved OMG Issue No: 18367 Title: The SBVR document is far larger than optimal Source: Ronald G. Ross, Business Rule Solutions, LLC, rross@BRSolutions.com Summary: The SBVR document is far larger than optimal. It needs to be reduced in size. Many of the Annexes do not contribute directly to core content. Proposed Resolution Delete Annexes that are not essential to the SBVR specification. Evaluation of the Annexes: Annexes essential to the correct interpretation of the normative specification and that must be kept: . Annex C - SBVR Structured English . Annex E - EU-Rent Example . Annex H - Use of UML Notation in a Business Context to Represent SBVR-Style Vocabularies . Annex M - Additional References Annexes that are not essential and can be deleted. Their owners can choose whether to publish them independently: . Annex F - The RuleSpeak Business Rule Notation* . Annex G - Concept Diagram Graphic Notation . Annex I - The ORM Notation for Verbalizing Facts and Business Rules* . Annex J - ORM Examples Related to the Logical Foundations for SBVR . Annex L - A Conceptual Overview of SBVR and the NIAM2007 Procedure to Specify a Conceptual Schema The SBVR RTF should decide on a case by case basis whether the following Annexes are essential to the correct interpretation of the normative clauses or can be deleted: . Annex A - Overview of the Approach . Annex B - The Business Rules Approach . Annex D - SBVR Structured English Patterns . Annex K - Mappings and Relationships to Other Initiatives *To be discussed by the RTF: Since (a) SBVR-SE is not normative, and (b) RuleSpeak and ORM (Norma) served as reference notations in creating the specification, it might be useful to illustrate parts or all of Annexes C and/or E, and/or examples given in the specification itself, in these other two notations. Annexes F and I already did something like this, but (a) are much too large, (b) not well-focused on complementing SBVR, and (c) may need to be revised. Resolution: 1. Keep Annexes A, C, D, E, H and M in the main SBVR specification document and adjest the Annex letters to be sequential in the same sequence. 2. Separate Annexes B, F, G, I, J and K and L each into a separate supplemental document to appear in the list of SBVR specification documents on the OMG website with the commitment to review each of these Annexes as to their relevance and being up to date with the normative clauses in the SBVR v1.3 RTF, which is scheduled to complete in June 2013. 3. Review Annexes A, C and D for being up to date with the normative clauses during SBVR v1.3 RTF. Revised Text: 1. Rename Annex C to Annex B and replace all current references to .Annex C. with .Annex B.. 2. Rename Annex D to Annex C and replace all current references to .Annex D. with .Annex C.. 3. Rename Annex E to Annex D and replace all current references to .Annex E. with .Annex D.. 4. Rename Annex H to Annex E and replace all current references to .Annex M. with .Annex E.. 5. Rename Annex M to Annex F and replace all current references to .Annex M. with .Annex E.. 6. Rename Annex B to Annex G and replace all current references to .Annex B. with .Annex G. and put the entire content of the current Annex B into a separate specification document. 7. Rename Annex F to Annex H and replace all current references to .Annex F. with .Annex H. and put the entire content of the current Annex F into a separate specification document. 8. Rename Annex G to Annex I and replace all current references to .Annex G. with .Annex I. and put the entire content of the current Annex G into a separate specification document. 9. Rename Annex I to Annex J and replace all current references to .Annex I. with .Annex J. and put the entire content of the current Annex I into a separate specification document. 10. Rename Annex J to Annex K and replace all current references to .Annex J. with .Annex K. and put the entire content of the current Annex J into a separate specification document. 11. Rename Annex K to Annex L and replace all current references to .Annex K. with .Annex L. and put the entire content of the current Annex K into a separate specification document. 12. Rename Annex L to Annex M and replace all current references to .Annex L. with .Annex M. and put the entire content of the current Annex L into a separate specification document. Disposition: Resolved X-Forefront-Antispam-Report: CIP:157.56.254.181;KIP:(null);UIP:(null);IPV:NLI;H:DBXPRD0711HT001.eurprd07.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: -1 X-BigFish: PS-1(z21cR551bizc89bh936eIdbeehc857h12d5Idbf2idbb0izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz17326ah18c673h1954cbh18602eh186068h8275eh8275bh1b9c21h8275dh19bc3dn19bc52ia1495iz2dh2a8h668h839hd24he5bhf0ah10d2h1249h1288h12a5h12bdh137ah139eh1441h1537h162dh1631h1758h17f1h1898h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1bfbh1c97h1d0ch1d2eh1d3fh34h1155h) Reply-To: From: Donald Chapin To: "sbvr-rtf " Subject: FW: issue 18367 -- SBVR RTF issue Date: Tue, 7 May 2013 14:03:49 +0100 Organization: Business Semantics Ltd X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJvZ07m7D+3c9cU1+1i8dMx/c5leZe3djIA X-Originating-IP: [157.56.253.53] X-FOPE-CRA-SourceIpAddress: 157.56.254.181 X-FOPE-CRA-DRYRUN: 1207119;1 X-FOPE-BFA-SENDER: donald.chapin@btconnect.com X-FOPE-BFA-RECEIVER: sbvr-rtf@omg.org X-OriginatorOrg: btconnect.com X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAh15Qr0deRps X-Brightmail-Tracker: AAAAAA== All . Attached is the resolution to SBVR Issue 18367 updated as a result of a consultation with Andrew Watson. The update reflects that, just as is true for Annex C (SBVR Structured English), Annexes D (SBVR Structured English Patterns) and H (Use of UML Notation in a Business Context to Represent SBVR-Style Vocabularies) define how to interpret the syntax in which the normative SBVR specification clauses are written. As these two Annexes are essential to accurate interpretation of the normative SBVR specification, there are retained in the main SBVR specification document. Additionally, a Note is inserted at the beginning of each Annex to be packaged in a separate document making it explicit that being packaged in a separate document in no way changes the status of the Annex as part of the SBVR specification. This Issue Resolution is ready for ballot. Donald From: Juergen Boldt [mailto:juergen@omg.org] Sent: 10 January 2013 14:38 To: issues@omg.org; sbvr-rtf@omg.org Subject: issue 18367 -- SBVR RTF issue X-Yahoo-Newman-Id: 261404.51495.bm@smtp108.sbc.mail.mud.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: l5xnKl0VM1lKY5LOI59Ti6mpp6U_YdLBX.g1ihhu6Id2rgc ag5tZO8a2PCKjO3KxTKvQhlFgEEx3922dGrvLvrKbN7ZZgPu1.gw80.xvUdY YHdni51Z8m7fx4b0RBpYKkMW0dEopFKuQNUJ9DqtzqBn8UC6ID7xMEOiesPB ZZq_LnEqr1W1T1FL4ZUfnHuOLkskgStDH8hlBBrtGqC9ATgqp7xMniYjnku_ OJMU7DnhBKTHZ5p2hCD5OqsAB_1zRMLlhywyaTSKHBrCaMf6puSmeMq6uonF b3vF2Kw__QrdsTuwCIvZlWuZE7GEqNsev2DtHn5Z9y9SqnOHceCMxsd8SHDo AjiLH5PaGDLTl9.2fVNuc9h.XJ6_et6N7aaXRSQM.cfBYhGe.jE8WWJnb76x NkfOggUYgHYyaKh2YxMhACXAL4V7oWxNbQ.2KRw3pMvSaak1OoDw_MZoS7.X 2YRVoe9TQp9vYdE4kleoNRFL4Uzfn5Ss1vkvhWFAni_CdoXVAKjAsQtwC8Vq 7rZzefU_DYtd6DU_jDj1GxL0EtHEtDd_yxYWInu6FHYVqIJQ3nP30Xe5lR5H fdFcad8QGntR3.kL.55k_bZKedm9FpV44KhnpmTxvHwp4oR0G6ZXZ6HOKeo3 KS32hgIMubR.zwgPiIqrPsbN3ss9z8CkVvniLXctv4gjkgXQszwXuTHcAMBI S7Ye0c8iFntlEGVTulAZz56PD3SZbtZEurhKZzZ4- X-Yahoo-SMTP: MhfrpU2swBDLgYiYhNQDHBu0cE4o.vu2We1FRN9o X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 09 Jan 2013 20:04:33 -0600 To: Juergen Boldt From: "Ronald G. Ross" Subject: please post this new SBVR issue (Thx) Cc: Donald Chapin Problem The SBVR document is far larger than optimal. It needs to be reduced in size. Many of the Annexes do not contribute directly to core content. Resolution Delete Annexes that are not essential to the SBVR specification. Evaluation of the Annexes: Annexes essential to the correct interpretation of the normative specification and that must be kept: Annex C - SBVR Structured English Annex E - EU-Rent Example Annex H - Use of UML Notation in a Business Context to Represent SBVR-Style Vocabularies Annex M - Additional References Annexes that are not essential and can be deleted. Their owners can choose whether to publish them independently: Annex F - The RuleSpeak Business Rule Notation* Annex G - Concept Diagram Graphic Notation Annex I - The ORM Notation for Verbalizing Facts and Business Rules* Annex J - ORM Examples Related to the Logical Foundations for SBVR Annex L - A Conceptual Overview of SBVR and the NIAM2007 Procedure to Specify a Conceptual Schema The SBVR RTF should decide on a case by case basis whether the following Annexes are essential to the correct interpretation of the normative clauses or can be deleted: Annex A - Overview of the Approach Annex B - The Business Rules Approach Annex D - SBVR Structured English Patterns Annex K - Mappings and Relationships to Other Initiatives *To be discussed by the RTF: Since (a) SBVR-SE is not normative, and (b) RuleSpeak and ORM (Norma) served as reference notations in creating the specification, it might be useful to illustrate parts or all of Annexes C and/or E, and/or examples given in the specification itself, in these other two notations. Annexes F and I already did something like this, but (a) are much too large, (b) not well-focused on complementing SBVR, and (c) may need to be revised. [Ronald G. Ross Contact Information] http://www.brsolutions.com/email/wordpress-2.png Blog || http://www.RonRoss.info/blog/ http://www.brsolutions.com/email/linkedin.png LinkedIn || http://www.linkedin.com/pub/ronald-ross/1/3b/346 http://www.brsolutions.com/email/twitter.png Twitter || https://twitter.com/Ronald_G_Ross http://www.brsolutions.com/email/button-green.png Homepage || http://www.RonRoss.info Juergen Boldt Director, Member Services 109 Highland Ave Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org [] Content-Type: application/msword; name="Issue 18367 - The SBVR document is" far larger than optimal (2013-05-03) WITH CHANGES.doc" Content-Disposition: attachment; filename="Issue 18367 - The SBVR document is" far larger than optimal (2013-05-03) WITH CHANGES.doc" Issue 18367 - The SBVR document is.doc Issue 18367 - The SBVR document is.doc