odata message

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

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: odata@lists.oasis-open.org
Date: Wed, 6 Jul 2016 01:29:49 +0000 (UTC)

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

Michael Pizzo updated ODATA-956:
--------------------------------

    Description: 
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?

  was:
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)?

Seems like we will need to somehow add the schema version to the context url...


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