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] (ODATA-948) Versions of vocabularies and their relation with a version of the specification


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

Michael Pizzo commented on ODATA-948:
-------------------------------------

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

There is a separate question as to whether we can define new values for existing string-valued attributes like AppliesTo.  I believe that is already addressed in ODATA-631, although we may want to revisit that proposal, or at least consider the ramifications for 4.0 clients.

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


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