OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Updated: (ODATA-234) Merge Reference and AnnotationReference element

     [ http://tools.oasis-open.org/issues/browse/ODATA-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-234:

Note that this gives us no way to bring in annotations without also bringing into scope other types, functions, etc. from the referenced document. Probably not a huge deal, but wanted to point out the loss of functionality from what we have today.

Would Reference not bring any annotations unless explicitly specified in an <IncludeAnnotations> child element?

What are the scenarios where we want to reference a model and bring into scope types, functions, etc., but not apply annotations (or apply only select annotations)? Is this worth having treating annotations differently, or should we just get rid of the <IncludeAnnotations> all together, and say that referencing a document brings all schema elements from that document into scope, with all annotations applied?

> Merge Reference and AnnotationReference element
> -----------------------------------------------
>                 Key: ODATA-234
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-234
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Priority: Minor
>             Fix For: WD01
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]