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-956) Do we need to add SchemaVersion to ContextURL?


Michael Pizzo created ODATA-956:
-----------------------------------

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

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



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