Community
Participate
Working Groups
Package names in sysml.ecore are all lowercase while those in sysml.profile.uml follow the UML capitalized convention. sysml.ecore should have 'originalName' EAnnotations to indicate that it has corrupted names otherwise OCL tooling that works on UML names gets confused.
(In reply to Ed Willink from comment #0) > sysml.ecore should have 'originalName' EAnnotations to indicate that it has > corrupted names otherwise OCL tooling that works on UML names gets confused. Fortunately the erroneous nested packages all have URIs, so OCL tooling can be adjusted to prefer a defined URI for both nested and root packages over the nested name.
The SysML 1.4 profile is properly formatted (Upper case for UML Packages, lower case for Ecore Package, with originalName EAnnotation), so I think this will be fixed as soon as SysML 1.4 is promoted in Papyrus
Since the originalName EAnnotation was introduced in Luna, there is a case for the Luna maintenance release exploiting it. But changing models in maintenance releases is risky. My understanding is that SysML 1.4 will be an option, not a replacement in Mars, so perhaps the Mars SysML 1.2 model could be corrected.
> My understanding is that SysML 1.4 will be an option, not a replacement in Mars, so perhaps the Mars SysML 1.2 model could be corrected. It's not decided yet. *If* we can provide a 100% SysML 1.1 to SysML 1.4 automated translation, then we will only ship SysML 1.4. Otherwise, we will ship two independent versions Otherwise, we may simply regenerate SysML 1.1 to provide the originalName EAnnotation
(In reply to Camille Letavernier from comment #4) > > My understanding is that SysML 1.4 will be an option, not a replacement in Mars, so perhaps the Mars SysML 1.2 model could be corrected. > > It's not decided yet. *If* we can provide a 100% SysML 1.1 to SysML 1.4 > automated translation, then we will only ship SysML 1.4. Otherwise, we will > ship two independent versions > > Otherwise, we may simply regenerate SysML 1.1 to provide the originalName > EAnnotation What's the status on this one?
I want to make the ocl constraint works before adding profiled informations
(In reply to Benoit Maggi from comment #6) > I want to make the ocl constraint works before adding profiled informations What does this mean? This bug is about a bug that prevents OCL working so surely it must be fixed to "make the ocl constraint works".
