2: Clarify interpretation of path segments and query option values with respect to percent-encoded punctuation

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.0_ERRATA01
    • Affects Version/s: V4.0_CS02
    • Component/s: ABNF, URL Conventions
    • None
    • Environment:

      [Applied]

    • Hide

      Make clear that percent-decoding happens exactly once, and that the "OData rules" are the ABNF rules minus the percent-encoded representation of the punctuation characters.

      Accepted: https://www.oasis-open.org/committees/download.php/52637/odata-meeting-69_on-20140327-minutes.html#odata-565

      Show
      Make clear that percent-decoding happens exactly once, and that the "OData rules" are the ABNF rules minus the percent-encoded representation of the punctuation characters. Accepted: https://www.oasis-open.org/committees/download.php/52637/odata-meeting-69_on-20140327-minutes.html#odata-565

      Chapter 2 states the parsing rules for OData URLs. Unfortunately the last of the six rules

      • Interpret path segments, query option names, and query option values according to OData rules

      is rather fluffy and leaves it to the reader to decide what the "OData rules" are.

      Later sections mainly refer to the ABNF, and the ABNF accepts percent-encoded values for most of the OData-significant delimiters in section 9. Punctuation.

      This in conjunction with the fifth parsing rule

      • Percent-decode path segments, query option names, and query option values

      may mislead implementers into double-decoding OData delimiters.

            Assignee:
            handl
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: