mlhim-owners team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

>         
>  If you think it is appropriate, you can publish the MLHIM
> rm.ecore metamodel into a repository of metamodels.
> This repository is called "Zoo of metamodels".

Hi Marcos,

I haven't committed this to the Zoo yet because I have a couple of
concerns. 

1) The model didn't created the the separate packages as marked by each
XSD.  For example; datatypes.xsd should be a package with the classes
built from its contents. This makes for a confusingly useless diagram :)
Is there an easy solution to this?


2)  Though the ecore model seems to be correct. When I generate a
diagram; the attributes that are not a Java type or an EcoreType are not
included.    For example; The Composition class has three String type
attributes: language, predecessor and original. The appear as expected
in the diagram.  However, the other attributes from the model that are
typed according to classes from the reference model do not show up in
the diagram; i.e. content:Locatable  and context:EventContext 

So now I am wondering if we should go with UML modelling?  If my
impression is correct that the classes of the reference model will need
to be defined as EDataTypes so they can be assigned to attributes then
this REALLY pulls us into the Java world.  Not a good thing at this
level.  

Thoughts?

Regards,
Tim

Attachment: signature.asc
Description: This is a digitally signed message part