RE: [mdt-ocl.dev] Making useful progress

["Ed Willink" <ed@xxxxxxxxxxxxx>]

Title: Message

Hi All

 

I'm prepared to take responsibility for anything that seems editor, parser or AST/CST related.

This might extend towards rationalising Environment/TypeChecker/UMLReflection and

may include support for an extensible OCL 2.0/2.1 behavioural selection.

 

There is an editor ready to go as part of QVT Declarative, but it depends on IMP

which is an incubation project and also LPG2; I think the IP issues are at last resolved.

The editor also depends on the (formerly UMLX) now QVT Declarative Model Registry

to locate referenced models.

 

It would be helpful if one person can try to produce a coherent list of OCL 2.1 changes broken

down into different possible activities. This may need very tedious and careful textual

comparison.

 

The list and bugzillas are good for discussion but very bad for concise conclusions

and plans. I think it would be better to try to have plans and conclusions in a wiki page or two.

 

The deferred items are:

 

OCL Specification Currency [156363] (target milestone: 2.0.0)

- well, the milestone was correct.

 

Adding a parsing option to exclude non-standard operations from OCL Standard Library [228839] (target milestone: ---)

- this looks to have much in common with an OCL 2.0/2.1 behavioural option

 

Adding the edit and editor plugin to have OCL models editable in the EMF's Sample Ecore Editor [196973] (target milestone: ---)

- the code is all ready and part of QVT declarative. It would be nice to increase stylistic commality between the OCL and UML icons.

 

Reorganize features to better reflect dependencies [192506] (target milestone: ---)

- maybe we lose the obsolete emf.ocl and add the editor as an optional feature

- the LPG support could be abstracted to an 'OCL-independent' base feature

 

Overhaul the OCL Example [259922] (target milestone: ---)

- any takers?

- I think we may need more than one example.

- QVT Declarative has obtained IP approval to use the Kleppe&Warmer RoyalAndLoyal

example: http://dev.eclipse.org/ipzilla/show_bug.cgi?id=2652

 

We probably want to draw up a list of all the different ways in which OCL can be used, so

that we have examples and JUnit tests for them. Something for the wiki.

 

    Ed

 

-----Original Message-----
From: mdt-ocl.dev-bounces@xxxxxxxxxxx [mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Adolfo Sánchez-Barbudo Herrera
Sent: 19 June 2009 13:53
To: MDT OCL mailing list
Subject: Re: [mdt-ocl.dev] Making useful progress

Hi team,

The new OCL spec should be presented (and hopefully approved) by the AB (Architecture Board) in the next OMG's meeting scheduled 22-26 on June.

I hope to answer to the interesting topics, you have mentioned, as soon as possible...

Cheers,
Adolfo.

Alexander Igdalov escribió:

Hi all,

 

I agree with Kenn and Ed that our plans on OCL for the next release should be discussed via this mailing list.

As it has already been mentioned, keeping in mind the new ideas in bug 237438 we will need to review the bugzillas which are not yet resolved and select those which are to be done in Helios. Deferred features in the Galileo project plan (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/mdt/ocl/project-info/plan.xml&component=OCL) deserve special consideration. I am going to review the requests and start a discussion on that next week.

I would also like to clarify the current status of the next version of the OCL standard which may become (if it appears) the key point of the next release. Adolfo, have you got any news on that?

 

Cheers,

- Alex.

_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
  

--

Adolfo Sánchez-Barbudo Herrera adolfosbh(at)opencanarias(dot)com C/Elías Ramos González, 4, ofc. 304 38001 SANTA CRUZ DE TENERIFE Tel.: +34 922 240231 / +34 617 718268