Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354608 - [oclinecore] not all EAnnotation.references feasible
Summary: [oclinecore] not all EAnnotation.references feasible
Status: CLOSED FIXED
Alias: None
Product: OCL
Classification: Modeling
Component: Core (show other bugs)
Version: 3.1.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: M7   Edit
Assignee: OCL Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-12 08:07 EDT by Ed Willink CLA
Modified: 2013-05-20 11:36 EDT (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 2011-08-12 08:07:32 EDT 
An EAnnotation.reference can refer to any element, which requires every element to be able to have a referenceable textual handle. This is not true for e.g. an Annotation since although it has a name, it is not unique and not a name with respect to its parent.

It would seem that a referenceable name overlay is needed so that e.g. 

annotation#xyzzy ...

defines xyzzy as the referenceable handle for the annotation allowing subsequent usage as

annotation ...
{
    reference xyzzy;
}

---

The improvements to allow references to work at all emanating from Bug 354336 will probably provide URIs as the handles.
Comment 1 Ed Willink CLA 2012-04-05 11:53:13 EDT 
The Fix for Bug 363141 ensures any awkward reference should serialize as a URI. This closes the loophole whereby not all *.ecore could be viewed/edited as *.oclinecore.

The residual ergonomic problem of editing awkward references as URIs is an enhancement addressed by Bug 376195.
Comment 2 Ed Willink CLA 2013-05-20 11:36:32 EDT 
CLOSED after a year in the RESOLVED state.