Issue 13076: The concrete syntax given is extremely difficult to implement (ocl2-rtf) Source: (, ) Nature: Revision Severity: Significant Summary: The concrete syntax given is extremely difficult to implement, as documented in several places, including University of Dresden http://dresden-ocl.sourceforge.net/papers/ParserDesign.pdf Many languages have a syntax specified in a machine-readable form, (e.g. lex/yacc format). A standard, working, syntax for OCL would be very useful. Resolution: Disposition: See issue 10439 for disposition Revised Text: Actions taken: November 10, 2008: received issue April 25, 2011: closed issue Discussion: Good suggestion. A lot of people has expressed the need for having an alternate BNF based way of providing the syntax. This could be done but requires some analysis to ensure it will be compatible with the way it is actually provided. Disposition: Deferred End of Annotations:===== iler: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 12 Nov 2008 13:57:07 -0500 To: issues@omg.org, ocl2-rtf@omg.org From: Juergen Boldt Subject: issue 13076 -- OCL 2 RTF issue From: webmaster@omg.org Date: 10 Nov 2008 04:36:31 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Craig Lucas Company: InferMed Ltd mailFrom: craig.lucas@infermed.com Notification: Yes Specification: Object Constraint Language (OCL) Section: 9 FormalNumber: OMG Available Specification Version: formal/06-05-01 RevisionDate: 06/05/01 Page: 61--94 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 1.1.4322) Description The concrete syntax given is extremely difficult to implement, as documented in several places, including University of Dresden http://dresden-ocl.sourceforge.net/papers/ParserDesign.pdf Many languages have a syntax specified in a machine-readable form, (e.g. lex/yacc format). A standard, working, syntax for OCL would be very useful. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org From: "Christian W. Damus" To: ocl2-rtf@omg.org Subject: Re: issue 13076 -- OCL 2 RTF issue Date: Wed, 12 Nov 2008 14:17:15 -0500 X-Mailer: Apple Mail (2.929.2) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - s014.panelboxmanager.com X-AntiAbuse: Original Domain - omg.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - zeligsoft.com X-Source: X-Source-Args: X-Source-Dir: Issue 12562 also mentions the need for an adjunct document to the spec, defining the grammar in a standard form, in addition to XMI renderings of the abstract syntax models. I recommend this approach over including the grammar in the document as in chapter 9, currently. This is also an opportunity to update the grammar rules, which are to a large extent still lagging the rest of the document in UML 2.x alignment. Cheers, Christian On 12-Nov-08, at 1:57 PM, Juergen Boldt wrote: From: webmaster@omg.org Date: 10 Nov 2008 04:36:31 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Craig Lucas Company: InferMed Ltd mailFrom: craig.lucas@infermed.com Notification: Yes Specification: Object Constraint Language (OCL) Section: 9 FormalNumber: OMG Available Specification Version: formal/06-05-01 RevisionDate: 06/05/01 Page: 61--94 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 1.1.4322) Description The concrete syntax given is extremely difficult to implement, as documented in several places, including University of Dresden http://dresden-ocl.sourceforge.net/papers/ParserDesign.pdf Many languages have a syntax specified in a machine-readable form, (e.g. lex/yacc format). A standard, working, syntax for OCL would be very useful. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org -- Christian W. Damus Senior Software Developer, Zeligsoft Inc. Component Lead, Eclipse MDT OCL and EMF-QTV E-mail: cdamus@zeligsoft.com From: "Christian W. Damus" To: ocl2-rtf@omg.org Subject: Re: issue 13076 -- OCL 2 RTF issue Date: Wed, 12 Nov 2008 14:17:15 -0500 X-Mailer: Apple Mail (2.929.2) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - s014.panelboxmanager.com X-AntiAbuse: Original Domain - omg.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - zeligsoft.com X-Source: X-Source-Args: X-Source-Dir: Issue 12562 also mentions the need for an adjunct document to the spec, defining the grammar in a standard form, in addition to XMI renderings of the abstract syntax models. I recommend this approach over including the grammar in the document as in chapter 9, currently. This is also an opportunity to update the grammar rules, which are to a large extent still lagging the rest of the document in UML 2.x alignment. Cheers, Christian On 12-Nov-08, at 1:57 PM, Juergen Boldt wrote: From: webmaster@omg.org Date: 10 Nov 2008 04:36:31 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Craig Lucas Company: InferMed Ltd mailFrom: craig.lucas@infermed.com Notification: Yes Specification: Object Constraint Language (OCL) Section: 9 FormalNumber: OMG Available Specification Version: formal/06-05-01 RevisionDate: 06/05/01 Page: 61--94 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 1.1.4322) Description The concrete syntax given is extremely difficult to implement, as documented in several places, including University of Dresden http://dresden-ocl.sourceforge.net/papers/ParserDesign.pdf Many languages have a syntax specified in a machine-readable form, (e.g. lex/yacc format). A standard, working, syntax for OCL would be very useful. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org -- Christian W. Damus Senior Software Developer, Zeligsoft Inc. Component Lead, Eclipse MDT OCL and EMF-QTV E-mail: cdamus@zeligsoft.com X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAIdI6ErUnw4U/2dsb2JhbADbIIQ/BA Date: Wed, 28 Oct 2009 20:38:25 +0000 From: Ed Willink User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) To: "'ocl2-rtf@omg.org'" Subject: Re: Issue 13076 The concrete syntax given is extremely difficult to implement X-Plusnet-Relay: 77d3802d0ae9d4839d602adc830470ca Hi Mariano The duplicate of 10439. Regards Ed Willink