Issue 13850: The segmentation 'Thing in Context' is inconsistent with the definitions of 'role' and 'facet' (sbvr-rtf) Source: Business Rule Solutions, LLC (Mr. Ron Ross, rross(at)brsolutions.com) Nature: Revision Severity: Significant Summary: The segmentation 'Thing in Context' is inconsistent with the definitions of 'role' and 'facet'. The segmentation is based on an assumption that the extensions of 'role' and 'facet' are completely disjoint. But there is nothing in the definitions of 'role' or 'facet' that cause them to be disjoint. It is possible that a situational role is relevant only from a certain viewpoint. Recommendation: Remove 'Thing in Context' and all references to it. Change Figure 11.1.5 to not show segmentation between 'role' and 'facet'. Resolution: Revised Text: Actions taken: April 2, 2009: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 02 Apr 2009 10:12:36 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Ronald G. Ross Company: Business Rule Solutions, LLC mailFrom: rross@BRSolutions.com Notification: Yes Specification: Thing in Context Section: 11.1.5 FormalNumber: SBVR Version: 1.0 RevisionDate: 2008-01-02 Page: 147 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Comcast Install 1.0; .NET CLR 1.1.4322) Description The segmentation 'Thing in Context' is inconsistent with the definitions of 'role' and 'facet'. The segmentation is based on an assumption that the extensions of 'role' and 'facet' are completely disjoint. But there is nothing in the definitions of 'role' or 'facet' that cause them to be disjoint. It is possible that a situational role is relevant only from a certain viewpoint. Recommendation: Remove 'Thing in Context' and all references to it. Change Figure 11.1.5 to not show segmentation between 'role' and 'facet'. X-Yahoo-SMTP: MhfrpU2swBDLgYiYhNQDHBu0cE4o.vu2We1FRN9o X-YMail-OSG: Sx5hE.EVM1kXMklQ2AAhnIk6Som0z6Z5dhPA_kDT3ZT6HFTKS.fLdCgfkPiJhf3Y.akaa7clA.ws6oORm4Nh_85qGpgssvZEcA4tp9imoSzGorlVV4TMUmBKdTxijlfodpyFJaEZ7r41_AAOwrLeL0lIOLQw.gYNOX8bXcDxOBa5EOtQ0hXDIkZBw2xO.hk6gRXH.LPVLeNsIoNG1bjJk5nBnfiT9MjtIFwRdbm8cKGvnofOt0sgIqcuKUr5arQ- X-Yahoo-Newman-Property: ymail-3 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 19 Jan 2010 20:33:20 -0600 To: Donald Chapin , Cheryl Estep From: "Ronald G. Ross" Subject: SBVR Issue 13850 Resolution Cc: sbvr-rtf@omg.org Here is the Revised Text and revised diagram as agreed for this Issue (a while back). Ron SBVR Issue 13850 Resolution v2-with Figure2.doc Fig11.5 -ISSUE 13849-13850.eps Subject: Re: SBVR Issue 13850 Resolution X-KeepSent: C1FE23E0:9EB249BE-852576B3:004A7416; type=4; name=$KeepSent To: sbvr-rtf@omg.org X-Mailer: Lotus Notes Release 8.0.2 HF623 January 16, 2009 From: Mark H Linehan Date: Fri, 22 Jan 2010 08:41:10 -0500 X-MIMETrack: Serialize by Router on D01MC604/01/M/IBM(Release 8.0.2FP1|November 13, 2008) at 01/22/2010 08:41:11 A minor comment about this one is that a simpler update would be to change "Thing in Context" from a "segmentation" to a "categorization scheme". On the other hand, the definition of "conceptualized concept" as "role or facet" already tells us that a "conceptualized concept" is the union of these two concepts. I don't care which way we go on this. -------------------------------- Mark H. Linehan STSM, Model Driven Business Transformation IBM Research phone: (914) 784-7002 or IBM tieline 863-7002 internet: mlinehan@us.ibm.com "Ronald G. Ross" ---01/19/2010 09:35:54 PM---Here is the Revised Text and revised diagram as agreed for this Issue "Ronald G. Ross" 01/19/2010 09:33 PM To Donald Chapin , Cheryl Estep cc sbvr-rtf@omg.org Subject SBVR Issue 13850 Resolution Here is the Revised Text and revised diagram as agreed for this Issue (a while back). Ron[attachment "SBVR Issue 13850 Resolution v2-with Figure2.doc" deleted by Mark H Linehan/Watson/IBM] [attachment "Fig11.5 -ISSUE 13849-13850.eps" deleted by Mark H Linehan/Watson/IBM] pic16286.gif