[OASIS Issue Tracker] Commented: (ODATA-267) Allow Qualifier attribute on Annotation elements within an Annotations element that does NOT specify a Qualifier attribute

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ODATA-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32648#action_32648 ] 

Michael Pizzo commented on ODATA-267:
-------------------------------------

I actually see (at least) four options:
  1) Don't support qualifiers on annotation elements within an annotations element (current spec)
  2) Support qualifiers only on annotation elements within an annotations element that doesn't specifies a qualifier attribute (current proposal)
  3) Support qualifiers on any annotation, and define that the one on the annotation overrides any qualifier on the Annotations element
  4) Only support qualifiers on the annotation

Of these options, #2 (the current proposal) seems the best balance of functionality and ease of use. It's slightly harder to validate than #3, but much easier to apply.

So I'm in favor of the proposal, I just wanted to be clear some of the other alternatives.

> Allow Qualifier attribute on Annotation elements within an Annotations element that does NOT specify a Qualifier attribute
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-267
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-267
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> Currently the Qualifier attribute is only allowed for Annotation elements that are "inlined" within their target model element, and forbidden when nested within an Annotations element.
> While this makes some sense for qualifier values like UI.Device.Slate and UI.Device.Phone, it makes less sense for qualifiers like VCard.Type.Work and VCard.Type.Home. Separating these into several Annotations elements that targets the same model element makes getting the full picture actually harder.

-- 
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