-
Key: UML14-81
-
Legacy Issue Number: 4735
-
Status: closed
-
Source: Anonymous
-
Summary:
According to the UML 1.4 standard, the abstract metaclass Namespace
compositely contains any type of ModelElement, but does however state that
subclasses may restrict this containment [UML 1.4, pp. 2-45].The metaclasses Node, Artifact [UML 1.4, pp.1-16], Package and Model [UML
1.4, pp.1-188] - all deriving from Namespace - make no such restrictions
however.This means that Node, Artifact, Package and Model can compositely contain
the following concrete metaclasses as ownedElements:Method
Attribute
Operation
ReceptionState
ActionState
ObjectFlowState
Transition
CallState
Pseudostate
SimpleState
SubactivityState
SynchState
CompositeState
SubmachineState
SubState
FinalStateCallAction
TerminateAction
CreateAction
DestroyAction
SendAction
ActionSequence
UninterpretedAction
ReturnActionExtensionPoint
Stimulus
ParameterPermission
UseCase
ProgrammingLanguageDataType
StateMachine
Comment
LinkObject
Enumeration
Association
Dependency
ClassifierInState
SignalEvent
Constraint
NodeInstance
Usage
Signal
Actor
Interface
Component
Link
Primitive
Collaboration
SubsystemInstance
ChangeEvent
Generalization
Stereotype
Subsystem
TagDefinition
Abstraction
Extend
ActivityGraph
Flow
UseCaseInstance
DataType
Object
Class
TimeEvent
ComponentInstance
Exception
Include
CollaborationInstanceSet
AssociationClass
CallEvent
Binding
Package
Node
Artifact
Model
DataValue
TaggedValueThe question is: are all these ownedElement types intended for all the
mentioned containers? Especially the first 28 in the list appear out of
place. -
Reported: XMI 1.3 — Wed, 5 Dec 2001 05:00 GMT
-
Disposition: Resolved — UML 1.4.2
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
UML14 — UML 1.4: Node, Artifact, Package and Model contents problem
- Key: UML14-81
- OMG Task Force: UML 1.4 RTF