| [mdt-ocl.dev] OCL versions |
|
Hi This gets more confusing. OMG->Members->Work In Progress now identifies the OCL 2.3 RTF. A few days ago this was OCL 2.2 RTF. The voting list deadline is passed, the public comment deadline is 10 April 2010. OMG->Members->Issues leads to http://www.omg.org/issues/ocl2-rtf.open.html the "Issues for OCL 2.2 Revision Task Force mailing list" from which the 2.1 resolutions have been pruned. OMG->Specifications->UML...->OCL->Revision:Contact gets to http://www.omg.org/techprocess/meetings/schedule/OCL_2_RTF.html that identifies the OCL 2.1 RTF with a Beta 2 specification just awaiting a Fax vote by 28th August. This resolves about 33% of the issues. Neither 09-05-01 nor 09-05-02 provides a changebar free copy of the specification. So I think that we will be implementing the OCL 2.1 in so far as possible given the number of outstanding issues. OCL 2.1 seems to be the next version, possibly released in September. No 2.2. The next next OCL possibly in 2010 will be 2.3. There is no point discussing issues resolved in 2.1. They are ballotted and approved regardless of how few people voted and even fewer understood their meaning. I shall therefore probably raise new issues for null/invalid to avoid confusion with resolved issues. It would appear that the low level of member participation encourages submissions that are formatted as resolutions. This should increase our confidence in raising issues that have a reasonable prospect of adoption. NB. Issue 13944: [OCL-2.1 RTF] Transitive closure operator (ocl2-rtf), which I think everyone can agree on. We could do it. Oops, reading on. Christian has already implemented it and provided a ProblemOption.CLOSURE_ITERATOR mechanism for switching it on and off by configuring the environment. This is similar to my extensibility suggestions. Adolfo: Have you had time to consider the discussion leading to MDT-OCL 3.0.0? Regards Ed Willink |