eclipse-uml2-bot
commented
1 week ago By Ed Willink on Jun 18, 2022 05:58
This inconsistency was revealed when https://www.eclipse.org/forums/index.php/m/1852932/#msg_1852932 provoked Bug 580143 work gor OCL to support the semantically clear x.oclExtensions(Standard::Create) rather than the semantically inadequate idiom x.extension_Create.
Correcting the longstanding original name from Standard to StandardProfile is breaking, but does anyone actually use it after exploiting the wrong spelling? Probably not since its only from OCL and only once names are actually qualified.
Suggest correcting the original name and introducing a dummy profile package with the wrong name that imports the right name.
| --- | --- | | Bugzilla Link | 580202 | | Status | NEW | | Importance | P3 normal | | Reported | Jun 18, 2022 05:51 EDT | | Modified | Jun 18, 2022 05:58 EDT | | Reporter | Ed Willink |
Description
The correct name for the standard profile would appear to be "StandardProfile", but "Standard" seems to have been implemented.
/org.eclipse.uml2/model/StandardProfile.xmi suggests that http://www.omg.org/spec/UML/20131001/StandardProfile should be named "StandardProfile". (The OMG site has a dead link so I cannot confirm.)
https://www.omg.org/members/spec/UML/20161101/StandardProfile.xmi defines the name of http://www.omg.org/spec/UML/20161101/StandardProfile as "StandardProfile".
The ultimate Ecore implementation imposes Java policies and so http://www.eclipse.org/uml2/5.0.0/UML/Profile/Standard defines "standard".
The name changes to suit Ecore are neutralized for UML usage purposes (by OCL) via an originalName annotation. Unfortunately /org.eclipse.uml2.uml.profile.standard/model/Standard.ecore defines the original name as "Standard", presumably because /org.eclipse.uml2.uml.profile.standard/model/Standard.merged.uml defines the package name as "Standard" as a consequence of an inaccurate merge by /org.eclipse.uml2.uml.profile.standard/model/Standard.uml.