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-650) Clarify the use of $format in delta links and next links

Matthew Borges created ODATA-650:

             Summary: Clarify the use of $format in delta links and next links
                 Key: ODATA-650
                 URL: https://tools.oasis-open.org/issues/browse/ODATA-650
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData Protocol 
    Affects Versions: V4.0_OS
            Reporter: Matthew Borges
            Priority: Minor
             Fix For: V4.0_OS, V4.0_ERRATA01

Currently the spec does not make any mention of $format in a delta or next link.  Since $format overrides the Accept header, an encoded $format in a delta link or next link means that the response format can not be changed between requests by the client.

During the TC meeting on 04/24/2014, some members suggested concerns of changing the response format when following next links.  The only way to prevent this change would be to encode it in the next link using $format (regardless of whether the client originally used $format or not).

Format for a delta response should not depend on the original format.  However, if a client explicitly used $format, they may have done so because they couldn't use the Accept header (for whatever reason), in which case they may not be able to change the Accept header when using a delta link, in which case they would expect the delta link to include $format as well.

This message was sent by Atlassian JIRA

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