Computes the xmi:ID for each element in the domain of the element2document map of the ResolvedDocumentSet
Computes the xmi:ID for each element in the domain of the element2document map of the ResolvedDocumentSet
Computes the xmi:UUID for each element in the domain of the element2document map of the ResolvedDocumentSet
Computes the xmi:UUID for each element in the domain of the element2document map of the ResolvedDocumentSet
Rule #1 (InstanceValue)
Rule #1 (NamedElement) case (a): Feature or ValueSpecification
Rule #1 (NamedElement) case (b): not Feature, not ValueSpecification
Rule #2: any Element on which Rule#1 does not apply and which is owned as an ordered set
Rule #3: any Element on which Rule#2 does not apply and which is a DirectedRelationship
Rule #3: any Element on which Rule#2 does not apply and which is a DirectedRelationship
Check if the source & target of a directed relationship are elements of a Built-In Document (e.g., UML Metamodel, StandardProfile, etc...) As of OMG UML 2.5, such source/target elements may have a legacy xmi:ID such as "_0" which is is insufficient to avoid duplication. (For example, a package that imports both UML Metamodel and StandardProfile)
To strengthen the unicity and reproducibility of the XMI:ID of the directed relationship, references to elements in built-in documents include the built-in document URI in addition to the xmi:ID of the referenced element.
Rule #4: any Element on which Rule#3 does not apply and which is a uml::Slot
Rule #5: any Element on which Rule#4 does not apply and which is uml::Comment
Rule #6: any Element on which Rule#5 does not apply and which is uml::Image
The xmi:ID of an element depends on what kind of document it is contained in.
The xmi:ID of an element depends on what kind of document it is contained in. - BuiltInDocument: this is deferred to builtInID, which is implementation-specific. - SerializableDocument: this is the OTI implementation of Canonical XMI ID unless it is overriden by an application of the OTI::Identity stereotype
The xmi:UUID of an element depends on what kind of document it is contained in.
The xmi:UUID of an element depends on what kind of document it is contained in. - BuiltInDocument: this is deferred to builtInUUID, which is implementation-specific. - SerializableDocument: this is the OTI implementation of Canonical XMI UUID unless it is overriden by an application of the OTI::Identity stereotype