Issue 8252: Section: 12.3.34 (uml2-rtf) Source: (, ) Nature: Clarification Severity: Minor Summary: Add the package name IntermediateActivities to the first Associations sub-section. Add the subsets ownedElement statement (as shown in fig 193) to the association joinSpec:ValueSpecification[1..1]. Typo - remove the second a between containing and join in the 4th sent of the Notation sub-section 1st para. Change AcceptOrder behavior to SendInvoice behavior (as shown in fig 277) in the 1st sentence in the Examples sub-section. Add OCL notation to the constraints Resolution: Revised Text: Associations section of 12.3.34: Replace header Associations with Associations (IntermediateActivities) Editor’s note: the above change was not entered because it does not conform to the standard format Associations (CompleteActivities) section of 12.3.34: Replace • joinSpec : ValueSpecification [1..1] A specification giving the conditions under which the join will emit a token. Default is “and”. with • joinSpec : ValueSpecification [1..1] {subsets Element::ownedElement} A specification giving the conditions under which the join will emit a token. Default is “and”. Editor’s note: added constraint at the end of the text to conform to standard format Notation section of 12.3.34, 1 st paragraph, 4 th sentence: Replace This case maps to a model containing a a join node with all the incoming edges shown in the diagram and one outgoing edge to a fork node that has all the outgoing edges shown in the diagram. with This case maps to a model containing a join node with all the incoming edges shown in the diagram and one outgoing edge to a fork node that has all the outgoing edges shown in the diagram. (Note: removed “a” between containing and join) Editor’s note: fixed in formal copy edit Examples section of 12.3.34, 1 st paragraph, 1 st sentence: Replace The example at the left of the figure indicates that a Join is used to synchronize the processing of the Ship Order and Accept Order behaviors. with The example at the left of the figure indicates that a Join is used to synchronize the processing of the Ship Order and Send Invoice behaviors. (Note: replaced “Accept Order” by “Send Invoice”) Constraints section of 12.3.34: Add OCL to constraints: [1] A join node has one outgoing edge. self.outgoing->size()=1 [2] If a join node has an incoming object flow, it must have an outgoing object flow, otherwise, it must have an outgoing control flow. (self.incoming.select( e | e.isTypeOf(ObjectFlow)->notEmpty() implies self.outgoing.isTypeOf(ObjectFlow)) and (self.incoming.select( e | e.isTypeOf(ObjectFlow)->empty() implies self.outgoing.isTypeOf(ControlFlow)) Actions taken: February 7, 2005: received issue August 23, 2006: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 07 Feb 2005 16:49:51 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Jane Messenger Company: U. S. Geological Survey mailFrom: jmessenger@usgs.gov Notification: Yes Specification: Superstructure Section: 12.3.34 FormalNumber: ptc/04-10-02 Version: 2.0 Draft Adopted RevisionDate: 10/08/2004 Page: 411-413 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description Add the package name IntermediateActivities to the first Associations sub-section. Add the subsets ownedElement statement (as shown in fig 193) to the association joinSpec:ValueSpecification[1..1]. Typo - remove the second a between containing and join in the 4th sent of the Notation sub-section 1st para. Change AcceptOrder behavior to SendInvoice behavior (as shown in fig 277) in the 1st sentence in the Examples sub-section. Add OCL notation to the constraints.