[OASIS Issue Tracker] (ODATA-1583) Clarify representation of context URLs in JSON payloads

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

Gerald Krause created ODATA-1583:
------------------------------------

             Summary: Clarify representation of context URLs in JSON payloads
                 Key: ODATA-1583
                 URL: https://issues.oasis-open.org/browse/ODATA-1583
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: JSON Format
    Affects Versions: V4.01_OS
         Environment: Context URLs may include characters outside of the unreserved set, e.g. a '(', ')', '/' like for a collection of entities reached via a path to a containment navigation property: "$metadata#set('<key_value>')/cont_nav_prop"

Some implementations return such a context URL in a JSON payload with percent-encoded '(', ')', '/', e.g. "$metadata#set%28'<key_value>'%29%2Fcont_nav_prop", others return it with plain characters.

Question is if servers are free to choose the representation of context URLs and service consumers must be prepared to do a percent-decoding before interpreting the context URL

References:
 - The JSON Format specification in section [4.3 Relative URLs |http://docs.oasis-open.org/odata/odata-json-format/v4.01/odata-json-format-v4.01.html#sec_RelativeURLs] mention _colons_ inside the path part that must be percent-encoded
 - The ABNF includes a statement for the grammar on the necessity of a percent-decoding a URL before parsing it. Shall this rule also be applied for URLs in JSON payloads?
            Reporter: Gerald Krause
             Fix For: V4.01_ERRATA01






--
This message was sent by Atlassian Jira
(v8.3.3#803004)