[OASIS Issue Tracker] (ODATA-925) Define Core term for service/schema/model version

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

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

Ralf Handl updated ODATA-925:
-----------------------------

    Environment: Proposed
       Proposal: 
Add a Core term for a service/schema/model version.

    <Term Name="SchemaVersion" Type="String" AppliesTo="Schema">
        <Annotation Term="Core.Description" String="Version of the schema (not to be confused with the protocol version)" />
    </Term>

Clarify relationship between version and metadataEtag: first is semantic, second could be technically derived (timestamp of development artifacts), so the latter may change without the former changing, but if the former changes, the latter SHOULD/MUST change.

  was:
Add a Core term for a service/schema/model version.

Clarify relationship between version and metadataEtag: first is semantic, second could be technically derived (timestamp of development artifacts), so the latter may change without the former changing, but if the former changes, the latter SHOULD/MUST change.


> Define Core term for service/schema/model version
> -------------------------------------------------
>
>                 Key: ODATA-925
>                 URL: https://issues.oasis-open.org/browse/ODATA-925
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON CSDL, Vocabularies
>    Affects Versions: V4.0_WD01, V4.0_CSD01
>         Environment: Proposed
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD02, V4.0_CSD01
>
>
> Part 1 Protocol describes rules for compatible changes to the data model of a service. 
> Yet clients may need to know which version of the model they are accessing.



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