[OASIS Issue Tracker] (ODATA-948) Versions of vocabularies and their relation with a version of the specification

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

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

Michael Pizzo updated ODATA-948:
--------------------------------

    Proposal: 
1) We should not add 4.01 to the edmx Version element, as we are not defining a new version of the edmx (i.e., no new elements or attributes).
2) Tell 4.01 clients that they should be prepared for the set of valid applies to elements to expand in the future.  

  was:
1) We should not add 4.01 to the edmx Version element, as we are not defining a new version of the edmx (i.e., no new elements or attributes).
2) If we think "Collection" will break clients, clarify that the new "Collection" value added in ODATA-631 can only be returned for 4.01 and greater payloads
3) For 4.0 clients, the service can include a subset of valid values (i.e., just entityset) or can specify more generically (i.e., property, navigationproperty). 
4) Tell 4.01 clients that they should be prepared for this set to expand in the future.  


> Versions of vocabularies and their relation with a version of the specification
> -------------------------------------------------------------------------------
>
>                 Key: ODATA-948
>                 URL: https://issues.oasis-open.org/browse/ODATA-948
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL, OData Protocol, Vocabularies
>         Environment: [Proposed]
>            Reporter: Hubert Heijkers
>             Fix For: V4.01_WD01
>
>
> Need to specify more clearly what the versioning scheme is for vocabularies and how they relate to versions of the specification. For one current vocabularies refer to version 4.0 of the edmx namespace as is (<edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx"; Version="4.0">) which kind of ties them to a specific version of the specification anyway. Would we add version 4.01 here as well (see ODATA-846)?
> We have parked ODATA-545 and made it dependent on this issue as discussion of that issue surfaced the issues to be resolved here.



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