[OASIS Issue Tracker] Created: (ODATA-565) 2: Clarify interpretation of path segments and query option values with respect to percent-encoded punctuation

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

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

                 Key: ODATA-565
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-565
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData ABNF Construction Rules, OData URL Conventions 
    Affects Versions: V4.0_CS02
            Reporter: Ralf Handl
             Fix For: V4.0_ERRATA01


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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira