Issue 8343: Section: 14.3.19 (uml2-rtf) Source: (, ) Nature: Clarification Severity: Minor Summary: Change class name for the association selector to OpaqueExpression (as per fig. 328) or change class name on fig. 328. Interaction:Interaction[1] subsets namespace according to the fig. Mention the specialization in the text definition. Typo - First sent. of Semantics change "OccurrenceSpecification" to "OccurrenceSpecifications." Resolution: see above Revised Text: Before (14.3.19 page 536) • selector : Expression[0..1] If the referenced ConnectableElement is multivalued, then this specifies the specific individual part within that set Revised text: • selector : ValueSpecification[0..1] If the referenced ConnectableElement is multivalued, then this specifies the specific individual part within that set Before (14.3.19 page 537) The order of OccurrenceSpecifications along a Lifeline is significant denoting the order in which these OccurrenceSpecification will occur. Revised text: The order of OccurrenceSpecifications along a Lifeline is significant denoting the order in which these OccurrenceSpecifications will occur. [Only an ‘s’ is added to the revised text to make the last OccurrenceSpecifications into plural.] Editor’s note: fixed in formal copy edit Actions taken: February 24, 2005: received issue August 23, 2006: closed issue Discussion: The modeling of expressions and valuespecifications has changed since the typing of the ‘selector’ attribute. I believe the correct typing now should be ValueSpecification because the selector in general refers to something that will yield a value at runtime. End of Annotations:===== m: webmaster@omg.org Date: 24 Feb 2005 12:55:33 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Jane Messenger Company: U. S. Geological Survey mailFrom: jmessenger@usgs.gov Notification: Yes Specification: Superstructure Section: 14.3.19 FormalNumber: ptc/04-10-02 Version: 2.0 Draft Adopted RevisionDate: 10/08/2004 Page: 536-537 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description Change class name for the association selector to OpaqueExpression (as per fig. 328) or change class name on fig. 328. Interaction:Interaction[1] subsets namespace according to the fig. Mention the specialization in the text definition. Typo - First sent. of Semantics change "OccurrenceSpecification" to "OccurrenceSpecifications." To: uml2-rtf@omg.org, oysteinh@ifi.uio.no Subject: Re: Draft ballot 8 X-Mailer: Lotus Notes Release 6.0.1CF1 March 04, 2003 From: Branislav Selic Date: Mon, 15 Aug 2005 16:01:15 -0400 X-MIMETrack: Serialize by Router on D25ML01/25/M/IBM(Release 6.5.4|March 27, 2005) at 08/15/2005 16:01:22, Serialize complete at 08/15/2005 16:01:22 A few comments on proposed resolutions in draft ballot 8 (I still have to review the resolutions associated with profiles). Except for the first one, I believe all of these relate to resolutions proposed by Oystein. 8094 -- needs a bit more explanation where the information requested can be found. 8327 - this really should include an OCL constraint. However, in looking at it, the constraint does not seem easy to write, so it may not be practical to do this now. (Note that there is an outstanding general issue about missing OCL constraints that will ensure the issue of the missing OCL will not get swept under the rug.) 8330 - The discussion claims that the FTF made a change that removed the term "expression" for an attribute of CombinedFragment. However, the FTF record shows no such change. 8340, 8343, 8345, 8346, 8351 - Each one of these makes the excuse that, by its own convention, the Interactions chapter does not provide the subsetting information in its description of association ends. However, this information is provided in every other chapter of the spec and, making an exception here will only confuse readers. This information must be included for every association end that subsets another. The preferred format is "Subsets ::". 8341- This resolution needs to include a change to figure 331 and not use a non-conformant subsection heading ("Literals") [I will make these changes in the proposed resolution -- there is no need to resubmit the resolution] 8343 - The revised text should refer to an "operation call" and not a "method call" (both operations and signals have corresponding methods, but only operations have reply messages) [I can fix this -- there is no need to resubmit the resolution] Cheers...Bran To: uml2-rtf@omg.org, oysteinh@ifi.uio.no Subject: Re: Draft ballot 8 X-Mailer: Lotus Notes Release 6.0.1CF1 March 04, 2003 From: Branislav Selic Date: Mon, 15 Aug 2005 16:01:15 -0400 X-MIMETrack: Serialize by Router on D25ML01/25/M/IBM(Release 6.5.4|March 27, 2005) at 08/15/2005 16:01:22, Serialize complete at 08/15/2005 16:01:22 A few comments on proposed resolutions in draft ballot 8 (I still have to review the resolutions associated with profiles). Except for the first one, I believe all of these relate to resolutions proposed by Oystein. 8094 -- needs a bit more explanation where the information requested can be found. 8327 - this really should include an OCL constraint. However, in looking at it, the constraint does not seem easy to write, so it may not be practical to do this now. (Note that there is an outstanding general issue about missing OCL constraints that will ensure the issue of the missing OCL will not get swept under the rug.) 8330 - The discussion claims that the FTF made a change that removed the term "expression" for an attribute of CombinedFragment. However, the FTF record shows no such change. 8340, 8343, 8345, 8346, 8351 - Each one of these makes the excuse that, by its own convention, the Interactions chapter does not provide the subsetting information in its description of association ends. However, this information is provided in every other chapter of the spec and, making an exception here will only confuse readers. This information must be included for every association end that subsets another. The preferred format is "Subsets ::". 8341- This resolution needs to include a change to figure 331 and not use a non-conformant subsection heading ("Literals") [I will make these changes in the proposed resolution -- there is no need to resubmit the resolution] 8343 - The revised text should refer to an "operation call" and not a "method call" (both operations and signals have corresponding methods, but only operations have reply messages) [I can fix this -- there is no need to resubmit the resolution] Cheers...Bran