Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] general UML 2.5 questions

Hi, Robert,

From a purely practical perspective, in the Eclipse implementations of both UML and (E)MOF/XMI, the snippet that you quote can be loaded and processed sensibly.

The Eclipse UML2 project's UMLResource configures itself to load unrecognized content, including objects such as the UML-DI diagram for which the EMF run-time cannot find a containment reference (as would be the case here).  An application that loads this resource would be able to find the diagram in the "extensions" of the UML package, in the resource's extension map (see the XMLResource::getEObjectToExtensionMap() API).  The diagram would end up in some grab-bag feature of the AnyType that is the package's evil twin in the extension map.

Cheers,

Christian


On Oct 16, 2014, at 7:32 AM, Robert Lemmen <robertle@xxxxxxxxxxxxxx> wrote:

> hi ed,
> 
> On Wed, Oct 15, 2014 at 07:57:38PM +0100, Ed Willink wrote:
>> <xmi:XMI ...>
>>    <uml:Package xmi:type="uml:Package" ...>
>>        ...
>>        <umldi:Diagram xmi:type="umldi:UMLClassDiagram" ...>
>>            ....
>>        </umldi:Diagram>
>>    </uml:Package>
>> </xmi:XMI>
>> 
>> and uml:Package is nested in xmi:XMI. Does that make XMI inherently dependent on UML?
> 
> admittedly, and this is a bit confusing. however the top-level XMI
> element is special anyway, and explicitely talked about in the XMI spec
> ([0], page 10). In this particular case, with only one top-level uml
> element, you could even omit the encapsulating XMI element and move the
> namespace declarations right onto the uml:Package.
> 
> more importantly however, there is no object in the abstract model that
> represents the XMI element, it is purely notation of the serialization.
> The uml:Package element however does have a representation in the
> abstract model.
> 
> But it really boils down to the question from earlier in the thread: do
> you think that in the snippet above the fact that umldi:Diagram is
> nested in uml:Package has any meaning? would the XMI have the same
> meaning if it was somewhere else? And if it does have meaning, how would
> that manifest itself in the abstract model?
> 
> regards  robert
> 
> [0] http://www.omg.org/spec/XMI/2.4.2/PDF/
> 
> -- 
> Robert Lemmen                               http://www.semistable.com 
> _______________________________________________
> mdt-papyrus.dev mailing list
> mdt-papyrus.dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev



Back to the top