Eclipse Community Forums: UML2 » Should ValueSpecification be really a TypedElement?

Help

Home

Home » Modeling » UML2 » Should ValueSpecification be really a TypedElement?

Show: Today's Messages :: Show Polls :: Message Navigator

Should ValueSpecification be really a TypedElement? [message #626758]

Thu, 03 July 2008 12:42

Timothy Marc

Messages: 547
Registered: July 2009

Senior Member

Hi all,

after studying the values and instances concepts of the UML2 superstructure,
i was wondering that a ValueSpecification is also inhereting TypedElement.
What's the main reason for this? In the case of being a
LiteralSpecification, its type is directly combined with the value argument.
In the case of beeing a InstanceValue, the instance references a
InstanceSpecification, that points to a concrete classifier.
IMHO, there is no sense in defining the ValueSpecification as a
TypedElement, or is it for the enhancing mechanism of the metamodel?

Hope, this question isn't too silly.

-- Timothy

Report message to a moderator

Previous Topic:	EditDomains and EAnnotation.getDetails() returns java.lang.ArrayStoreException?
Next Topic:	Should ValueSpecification be really a TypedElement?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Apr 20 06:18:33 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter