Issue 4913: Multiplicity of ReadExtentAction pins (action-semantics-ftf) Source: International Business Machines (Mr. Sridhar Iyengar, siyengar@us.ibm.com) Nature: Uncategorized Issue Severity: Summary: [Sridhar Iyengar] 27.5 ReadExtentAction class: Check the multiplcity of the Output pins - it is 1 only in the metamodel diagram (see Other Actions diagram) - However there is a well formedness rule [3] which states that the result output pin has a multiplicity of unlimited - which would make sense since we are dealing with extents. Fix the metamodel multiplicity and removing the wellformedness rule would resolve this confusion. Resolution: decline Revised Text: Actions taken: March 5, 2002: received issue December 11, 2002: closed issue Discussion: The metamodel multiplicity refers to how many pins there are. The pin multiplicity refers to how many values the pin may have at runtime. End of Annotations:===== Summary: Multiplicity of ReadExtentAction pins Text: [Sridhar Iyengar] 27.5 ReadExtentAction class: Check the multiplcity of the Output pins - it is 1 only in the metamodel diagram (see Other Actions diagram) - However there is a well formedness rule [3] which states that the result output pin has a multiplicity of unlimited - which would make sense since we are dealing with extents. Fix the metamodel multiplicity and removing the wellformedness rule would resolve this confusion. From: Edwin Seidewitz To: "'action-semantics-ftf@omg.org'" Subject: [Issue # 4913] Multiplicity of ReadExtentAction pins Date: Tue, 5 Mar 2002 17:54:55 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1C498.C452FA50" X-UIDL: DdOe9I*P!!;&?!!T_k!! This is issue 4913: > Multiplicity of ReadExtentAction pins > > [Sridhar Iyengar] 27.5 ReadExtentAction class: Check the multiplcity > of > the Output pins - it is 1 only in the metamodel diagram (see Other > Actions diagram) - However there is a well formedness rule [3] which > states that the result output pin has a multiplicity of unlimited - > which would make sense since we are dealing with extents. Fix the > metamodel multiplicity and removing the wellformedness rule would > resolve this confusion. The specification is correct as written. The issue confuses the required multiplicity of the number of output pins of the action, which is 1, as shown on the metamodel diagram, and the required multiplicity that must be specified for the "multiplicity" attribute of the single output pin, which is required to be unlimited. The "multiplicity" attribute of the output pin is a specification of the multiplicity of the value that the pin can hold (remember that pins can actually hold collections), not a metamodel-level multiplicity. That is, a ReadExtentAction must have a single output pin. The result of a ReadExtentAction is a collection of all current instances of the given classifier. This collection is placed on the single output pin. Since the collection is potentially unlimited in size, that single output pin must have a specified multiplicity of "unlimited" FOR THE VALUES THAT IT HOLDS. -- Ed Ed Seidewitz, Chief Architect InteliData Technologies Office: +1.703.259.3076 Mobile: +1.301.455.3681