Issue 18393: Alf should be based on fUML 1.1 (alf-rtf) Source: Ivar Jacobson International AB (Mr. Ed Seidewitz, eseidewitz(at)ivarjacobson.com) Nature: Uncategorized Issue Severity: Summary: Specification: Action Language for Foundational UML (Alf): Concrete Syntax for a UML Action Language, FTF-Beta 2 (ptc/2012-08-43) The Alf syntax and the description of its semantics are based in UML 2.4.1. However, the formal semantic mapping is to fUML 1.0, which is based on UML 2.3. This means that the normative XMI for the Alf Standard Model Library is also UML 2.3, since it uses the fUML 1.0 Foundational Model Library. This situation occurred because the fUML 1.1 revision, based on UML 2.4.1, was not completed in time before the Alf 1.0 FTF had to deliver its report. Now that fUML 1.1 has been adopted, the Alf specification should be updated to use it as the target of the normative semantic mapping, which would also allow the Alf Standard Model Library to be UML 2.4.1. (Note that this issue is not intended to request that Alf incorporate the new Real type, which would require syntactic changes to the language and extension of the Standard Model Library. It is simply intended to request that the technical specification and normative artifacts for Alf all be consistently based on UML 2.4.1.) Resolution: Revised Text: Actions taken: January 29, 2013: received issue Discussion: End of Annotations:===== m: Ed Seidewitz To: "issues@omg.org" Date: Tue, 29 Jan 2013 14:37:39 -0500 Subject: Alf should be based on fUML 1.1 Thread-Topic: Alf should be based on fUML 1.1 Thread-Index: Ac3+Vxyw7988CNhnTWOacyfOOBaFvA== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Mailprotector-Decision: deliver X-Mailprotector-Connection: TLSv1|[10.1.50.225]|10.1.50.225|outbound.mailprotector.net|0.0|0.0|0|||0|0|0|0 X-Mailprotector-Results: null_ptr clean X-Mailprotector-Score: 40 X-Mailprotector-IP-Analysis: 0, 10.1.50.225, Ugly c=0.815 p=-0.961779 Source White X-Mailprotector-Scan-Diagnostics: 0-0-0-7729-c X-Mailprotector-ID: 5805df4b-db08-4744-a831-284d5ea4785b X-Brightmail-Tracker: AAAAAQr+n5E= X-Brightmail-Tracker: AAAAAA== Specification: Action Language for Foundational UML (Alf): Concrete Syntax for a UML Action Language, FTF-Beta 2 (ptc/2012-08-43) The Alf syntax and the description of its semantics are based in UML 2.4.1. However, the formal semantic mapping is to fUML 1.0, which is based on UML 2.3. This means that the normative XMI for the Alf Standard Model Library is also UML 2.3, since it uses the fUML 1.0 Foundational Model Library. This situation occurred because the fUML 1.1 revision, based on UML 2.4.1, was not completed in time before the Alf 1.0 FTF had to deliver its report. Now that fUML 1.1 has been adopted, the Alf specification should be updated to use it as the target of the normative semantic mapping, which would also allow the Alf Standard Model Library to be UML 2.4.1. (Note that this issue is not intended to request that Alf incorporate the new Real type, which would require syntactic changes to the language and extension of the Standard Model Library. It is simply intended to request that the technical specification and normative artifacts for Alf all be consistently based on UML 2.4.1.) From: Ed Seidewitz To: "Andrew Watson (andrew@omg.org)" CC: Juergen Boldt , "alf-rtf@omg.org" Date: Sun, 24 Feb 2013 17:58:44 -0500 Subject: RE: issue 18393 -- Alf RTF issue Thread-Topic: issue 18393 -- Alf RTF issue Thread-Index: Ac3+XQ0TP7ZrItJ3QrOMysjzzsqqWQUhRx/A Accept-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US X-Mailprotector-Decision: deliver X-Mailprotector-Connection: TLSv1|[10.1.50.226]|10.1.50.226|outbound.mailprotector.net|0.0|0.0|0|||0|0|0|0 X-Mailprotector-Results: null_ptr clean X-Mailprotector-Score: 40 X-Mailprotector-IP-Analysis: 0, 10.1.50.226, Ugly c=0.699024 p=-0.99547 Source White X-Mailprotector-Scan-Diagnostics: 0-0-0-32767-c X-Mailprotector-ID: 2e361b4e-7ffc-4abd-bbad-57f320208496 X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAR0YqvE= X-Brightmail-Tracker: AAAAAA== Andrew . I would like to request that Issue 18393, attached below, be declared an âurgent issueâ. A proposed resolution is attached, for consideration by the Alf RTF. I would like to have this issue resolved before the publication of the formal specification document for Alf (which would then presumably be for Alf 1.0.1). Thank you. Ed Seidewitz Alf 1.1 Revision Task Force Chair From: Juergen Boldt [mailto:juergen@omg.org] Sent: Tuesday, January 29, 2013 3:13 PM To: issues@omg.org; alf-rtf@omg.org Subject: issue 18393 -- Alf RTF issue From: Ed Seidewitz To: "issues@omg.org" Date: Tue, 29 Jan 2013 14:37:39 -0500 Subject: Alf should be based on fUML 1.1 Thread-Topic: Alf should be based on fUML 1.1 Thread-Index: Ac3+Vxyw7988CNhnTWOacyfOOBaFvA== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Mailprotector-Decision: deliver X-Mailprotector-Connection: TLSv1|[10.1.50.225]|10.1.50.225|outbound.mailprotector.net|0.0|0.0|0|||0|0|0|0 X-Mailprotector-Results: null_ptr clean X-Mailprotector-Score: 40 X-Mailprotector-IP-Analysis: 0, 10.1.50.225, Ugly c=0.815 p=-0.961779 Source White X-Mailprotector-Scan-Diagnostics: 0-0-0-7729-c X-Mailprotector-ID: 5805df4b-db08-4744-a831-284d5ea4785b X-Brightmail-Tracker: AAAAAQr+n5E= X-Brightmail-Tracker: AAAAAA== Specification: Action Language for Foundational UML (Alf): Concrete Syntax for a UML Action Language, FTF-Beta 2 (ptc/2012-08-43) The Alf syntax and the description of its semantics are based in UML 2.4.1. However, the formal semantic mapping is to fUML 1.0, which is based on UML 2.3. This means that the normative XMI for the Alf Standard Model Library is also UML 2.3, since it uses the fUML 1.0 Foundational Model Library. This situation occurred because the fUML 1.1 revision, based on UML 2.4.1, was not completed in time before the Alf 1.0 FTF had to deliver its report. Now that fUML 1.1 has been adopted, the Alf specification should be updated to use it as the target of the normative semantic mapping, which would also allow the Alf Standard Model Library to be UML 2.4.1. (Note that this issue is not intended to request that Alf incorporate the new Real type, which would require syntactic changes to the language and extension of the Standard Model Library. It is simply intended to request that the technical specification and normative artifacts for Alf all be consistently based on UML 2.4.1.) 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 Alf-1.1-Resolution-18393.doc Date: Fri, 1 Mar 2013 16:12:55 +0000 To: alf-rtf@omg.org From: Andrew Watson Subject: Issue 18393 now declared Urgent Cc: Juergen Boldt , Ed Seidewitz , Linda Heaton X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAR0YqyA= X-Brightmail-Tracker: AAAAAA== Dear ALF 1.1 RTF members, After discussions with Ed Seidewitz (ALF 1.1 RTF chair), I'm now formally declaring issue 18393 as Urgent in accordance with the procedure laid out in section 4.4.1.5 of the P&P (pp/12-12-01). The summary of this issue can be found here: http://www.omg.org/issues/alf-rtf#Issue18393 This issue will be voted on by the ALF 1.1 RTF. The default resolution is to apply the changes described in OMG document ptc/13-02-03 to the ALF 1.0 Beta2 Specification, ptc/12-08-43, and associated documents listed in the inventory ptc/12-08-40. http://doc.omg.org/ptc/13-02-03 Default resolution http://doc.omg.org/ptc/12-08-40 ALF 1.0 Beta 2 http://doc.omg.org/ptc/12-08-43 ALF 1.0 FTF inventory If a resolution in response to this applied to ALF 1.0 Beta2, the resulting ALF 1.0.1 will be published instead of ALF 1.0. The deadline for resolving this issue is 1700 GMT on Friday 15th March 2013. The decision on the issue resolution will fall to me if the ALF 1.1 RTF fails to resolve it by that time. However, even if the RTF decides to apply the default resolution shown above, I strongly recommend that it makes this decision by a recorded vote, rather than by letting the time limit expire and passing responsibility back to me. Regards, Andrew Andrew Watson Tel: +44 7710 469624 Technical Director, Email: andrew@omg.org Object Management Group http://www.omg.org/~andrew