Affects Version/s: V4.0_WD01
Fix Version/s: V4.0_WD01
Component/s: CSDL XML
- Add IncludeAnnotations child element to the Reference element
- Remove the AnnotationsReference element and its Include child element
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/edmx.xsd?rev=205https://www.oasis-open.org/committees/download.php/48440/odata-core-v4.0-wd01-part3-csdl-2013-03-05-RH.doc https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/edmx.xsd?rev=205 Accepted: https://www.oasis-open.org/committees/download.php/48549/odata-meeting-29_on-20130314-minutes.html#odata-234 https://www.oasis-open.org/committees/download.php/48584/odata-core-v4.0-wd01-part1-protocol-2013-03-19.doc
Currently there are two ways of referring to other EDMX documents: Reference and AnnotationsReference.
Their purpose is slightly different:
- Reference brings model elements defined in the referenced document into scope,
- AnnotationsReference includes annotations from the referenced document into the current document as if they would have been declared "locally".
In some situations we want to include annotation elements as well as refer to them, e.g. point in a UI "view" annotation to a vCard annotation and thus express the intent of rendering the vCard information in the UI "view".
To increase readability I'd like to introduce an Alias via a Using element, and It is unclear whether I'd also need a Reference element pointing to the same document in addition to the AnnotationsReference, or whether the AnnotationsReference also brings the referenced document, or just the included annotations, into scope.
While we could clarify that in the prose description of these elements, it seems more intuitive to have only one Reference element with an IncludeAnnotations child element instead of an AnnotationsReference element with an Include child element.