CORBA26 — PACKAGING AND DEPLOYMENT METAMODEL

1) Some concepts from the CORBA metamodel (component, facet, receptacle,
event publishing/emission/consumption) are also in P/D metamodel but the
definitions from the CORBA metamodel are not directly reused.

Recommendation: Analyze where reuse is appropriate and adjust the P/D
metamodel accordingly.

2) The P/D metamodel has the notion of files (e.g. configuration property
files and some other files) where some metadata are stored. The hand-coded
DTDs treat these files as types in their own right, i.e. they conceptualize
them as files, and some of the other types point to the file types. This
is approach is mimicked in the metamodel. However, it might not make sense
in the metamodel because, in a repository context, you are referencing
other information in the repository and not necessarily a file. The way
the metamodel is now, when something references one of these files you lose
the metadata trail. The file metaclass itself does not have structural
features pointing to metaclasses that define the contents of the file. You
have to go elsewhere (i.e. to the property file Package) to get that
metadata and there is no reference to the property file Package.

Recommendation: It might make more sense for references to the file
metaclass to instead reference the top level element of the property file
Package so that you can "follow the metadata trail." If someone wants to
break out the properties metadata in a file, then the generated DTD should
allow that, i.e. the part that needs to go into a properties file should be
able to be self-contained without external references.

rejected, See issue 4575.