[OASIS Issue Tracker] (ODATA-956) Do we need to add SchemaVersion to ContextURL?

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

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

Michael Pizzo commented on ODATA-956:
-------------------------------------

How does schemaversion work, in general, with federated systems? Do we need to specify different schemaversions for different context urls within a payload? Do we need to be able to annotate include statements in metadata with schemaversion? Do we need a way to specify a schema version as part of an expand?

>>If we specify as part of the include, then we shouldn't need to specify as part of expand and only need one per response.

> Do we need to add SchemaVersion to ContextURL?
> ----------------------------------------------
>
>                 Key: ODATA-956
>                 URL: https://issues.oasis-open.org/browse/ODATA-956
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.01_WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> In ODATA-928 we added the ability for a service to make breaking changes to metadata, and for a client to request a specific version of the metadata using the new SchemaVersion header.
> Do we need a way to encode the schemaversion as part of the contextUrl, or must the client processing the response know the schemaversion to use when requesting the metadata (including for nested contextUrls)?
> Perhaps using the SchemaVersion annotation as an instance annotation on the result payload?



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