Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [modeling-pmc] MDT/OCL Text Editor and EMFT Model Registrysuggestion

Hi

Would anyone on the PMC like to comment on this thread?

> 
> Kenn, Ed, Rich, Frederic, Jean, ...  Please advise on how best
> to proceed with a fairly small EMFT Model Registry project.
> 

Perhaps the concept are sufficiently adjacent to the EMF Index
proposal to merge?

	Regards

		Ed Willink

> -----Original Message-----
> From: modeling-pmc-bounces@xxxxxxxxxxx 
> [mailto:modeling-pmc-bounces@xxxxxxxxxxx] On Behalf Of Ed Willink
> Sent: 01 February 2009 10:43
> To: modeling-pmc@xxxxxxxxxxx
> Cc: imp-dev@xxxxxxxxxxx
> Subject: [modeling-pmc] MDT/OCL Text Editor and EMFT Model 
> Registrysuggestion
> 
> 
> (Resending to lists I was not subscribed to. Original message
> was also sent to mdt.dev@xxxxxxxxxxx, mdt-ocl.dev@xxxxxxxxxxx,
> m2m-dev@xxxxxxxxxxx.)
> 
> Hi All
> 
> In https://bugs.eclipse.org/bugs/show_bug.cgi?id=261742 #2
> Christian Damus revealed that we are discussing migrating
> the (currently M2M/QVT Declarative) OCL Editor to MDT/OCL.
> 
> This incurs two dependency problems.
> 
> The text editor uses IMP, which is an incubation project,
> so the additional optional MDT/OCL editor plugins might
> have API stability issues. IMP has hopefully only very
> minor IP issues.
> 
> The semantic validation of OCL requires a solution to the
> problem of where is the (potentially user-defined non-plugin)
> package named Xyzzy? The (currently M2M/QVT Declarative)
> Model Registry solves this problem. The Model Registry
> was originally part of UMLX, it has moved to QVT Declarative.
> A further move of generic modeling functionality to MDT/OCL
> does not seem right. Therefore a new EMFT project seems more
> appropriate.
> 
> Kenn, Ed, Rich, Frederic, Jean, ...  Please advise on how best
> to proceed with a fairly small EMFT Model Registry project.
> 
> All: Please be aware of the plans and please comment, especially
> if you have ideas or available resources for further Model Registry
> development.
> 
> Please respond on mdt.dev@xxxxxxxxxxx only.
> 
> Attached PDF provides more background on the project dependencies.
> 
>       Regards
> 
>           Ed Willink
> 
> 




Back to the top