[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Hi Philipp
omelet-home is now populated, though you have to access it via the
CVS repository at present.
I'll pupulate org.eclipse.omelet this weekend, once I get my
broadband connection going.
> This is as well intended as an example for you how EMF is
> used. And it
> is an excercise for me to use
> OMLET terminology to formalize our setting.
The various OMELET registries should themselves be models,
a) since OMELET should be consistently meta-modelled
b) so that transaformations can operate within and upon them
c) to support non-Eclipse usage where they are populated from XML.
The registries are currently hand-crafted Java class databases.
I have been toying with hand-crafted to/from DOM transformations
which can then use the DOM to/from XML transformations. Indeed
handcrafted approaches is what was in the omelet.wfc plug-in
that I based on the PDE functionality.
I suspect this is an area where EMF may already have the solution.
I started reading your thesis a while ago, but haven't got much further
than page 20 yet... It all looks sort of promosing. Do you have a
notation that can express the schema corrolaries of 'class A'
inherits from 'class B'? I had a bit of think whoile wandering
around the hills.
it seems that many of the more complex concepts
should be mapped to simpler concepts, so possibly inheritance is
a combination of static flattening to create a standalone AwithB
and substitutability that allows AwithB and B to be used as B,
which coincidentally? is exactly what my FlattenedSchema does.
A schema is just a set of constraints that
must not be violated by an instnace, and conversely every part of
a schema instance must satisfy some any consstraint