Bug 522257 - Diagnose missing Profile URI
Summary: Diagnose missing Profile URI
Status: NEW
Alias: None
Product: MDT.UML2
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows NT
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: UML2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2017-09-13 13:56 EDT by Ed Willink CLA
Modified: 2017-12-19 08:06 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2017-09-13 13:56:30 EDT 
Probably the most common problem for OCL UML users is that they neglect to specify an explicit Profile URI. Not a problem in UML, not even possible in UML 2.4. But in Eclipse UML, a Profile implies an embedded EPackage which has an auto-generated changing nsURI. Consequently OCL is struggling to correlate a variety of run-time EPackages with nsURIs and specification UML Profile without URIs. When the correlation fails users get strange obscure Constraint malfunctions.

If the UML Profile URI is explicit, UML2Ecore re-uses it and everything is easy.

Suggest a warning validation in UML for at least a missing URI on a Profile.

Possibly also a warning for a missing URI on a Model.
Comment 1 Ed Willink CLA 2017-09-14 03:34:25 EDT 
I think we have INFOs these days. Probably a better severity.