| Transforming UML associations to Ecore [message #625782] |
Wed, 26 December 2007 17:55 |
 Dave Carlson
Messages: 402
Registered: July 2009 |
Senior Member |
|
|
It seems that the UML to Ecore transformation needs to be enhanced to
consider Associations where both ends are owned by the Association. In the
OMG's SBVR cmof metamodel, there is NO use of composition, and all
associations own both property ends. Neither property is composition, nor
navigable.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=213894
I would expect that these associations must be transformed into Ecore
classes. I don't know what tools were used by the SBVR spec authors to
create their XSD for serialized XMI models (apparently not EMF...), but the
cmof associations appear in XSD as shown below, which implies that EMF would
need an EClass for each Association that owns both of its ends.
<xs:element name="placeholderUsesDesignation"
type="sbvr:placeholderUsesDesignation"/>
<xs:complexType name="placeholderUsesDesignation">
<xs:all>
<xs:element name="placeholder" form="unqualified" minOccurs="0">
<xs:complexType>
<xs:attributeGroup ref="xmi:LinkAttribs"/>
</xs:complexType>
</xs:element>
<xs:element name="designation" form="unqualified" minOccurs="0">
<xs:complexType>
<xs:attributeGroup ref="xmi:LinkAttribs"/>
</xs:complexType>
</xs:element>
<xs:element ref="xmi:Extension" minOccurs="0"/>
</xs:all>
<xs:attribute name="placeholder" type="xs:IDREF" use="optional"/>
<xs:attribute name="designation" type="xs:IDREF" use="optional"/>
</xs:complexType>
|
|
|
Powered by
FUDForum. Page generated in 0.02967 seconds
] 
Search
Help
Register
Login
Home
