[mdt-ocl.dev] Compliance Statement

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

I just added http://wiki.eclipse.org/MDT/OCL/Compliance and 
http://wiki.eclipse.org/MDT/OCL/Limitations.

I see http://wiki.eclipse.org/MDT/OCL/Compliance evolving into a table 
for which the OMG specification would provide a blank template and which 
OCL implementations would be expected to fill in. It currently has some 
content but needs much more.

I see http://wiki.eclipse.org/MDT/OCL/Limitations as a top level list of 
our known inadequacies that users may wish to know about, but not every 
single Bugzilla, perhaps just those we have little intention of fixing 
any time soon.

    Regards

        Ed




On 23/04/2011 15:49, Axel Uhl wrote:
> Hi Ed,
>
> well, then maybe you can make a suggestion for the layout. I currently 
> feel unable to provide the content for the other things you mention 
> are noteworthy, but I assume you have something in mind what to write 
> there?
>
> Best,
> -- Axel
>
> On 4/23/2011 2:55 PM, Ed Willink wrote:
> > Hi Axel
> >
> > It's a start; I was looking for something more tabular.
> >
> > We have many more things to comment on:
> >
> > oclIsNew
> > @pre
> > oclType()
> > eContainer()
> > OclMessage
> > OclState
> > XMI persistence
> >
> > A few pages of comment paragraphs is unreadable, so a table (possibly
> > multiple tables for major themes) allows a particular concern to be
> > identified from a 'summary' column, more detail from a 'description'
> > column and compliance from 'Ecore', 'UML, 'Pivot' columns.
> >
> > Ed
> >
> > On 20/04/2011 14:46, Axel Uhl wrote:
> > > I added http://wiki.eclipse.org/MDT/OCL_3.1.0_API_Changes. Does that
> > > go in the right direction?