[OASIS Issue Tracker] (ODATA-1119) Add CollectionPropertyRestrictions capability term

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

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

Ralf Handl updated ODATA-1119:
------------------------------

    Fix Version/s: V4.0_CSD02

> Add CollectionPropertyRestrictions capability term
> --------------------------------------------------
>
>                 Key: ODATA-1119
>                 URL: https://issues.oasis-open.org/browse/ODATA-1119
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Vocabularies
>    Affects Versions: V4.01_CS01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.01_CS02, V4.0_CSD02
>
>
> In ODATA-545 we added the value "Collection" as a valid value for AppliesTo to specify that a term can target any collection.  At the time we said that it should only be returned for 4.01 or greater clients.  We said that, for 4.0 clients, we could just say "EntitySet Property NavigationProperty" and underspecify the restriction (i.e., it would only apply to collection-valued (nav) properties) but that would be implied by the semantics of the term.
> Then, in ODATA-631, we used the new term in our vocabularies for things like CountRestrictions, FilterRestrictions,TopSupported,SKipSupported, etc.  This is problematic, as we didn't want to return this to 4.0 clients, yet we only have one version of the vocabulary.
> It also violates our best practice of applying annotation in the container, in order to support type-reuse, rather than annotate the type directly.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)