[OASIS Issue Tracker] (ODATA-1606) Separation of concerns: ABNF for URL components instead of whole URLs

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

Heiko Theissen created ODATA-1606:
-------------------------------------

             Summary: Separation of concerns: ABNF for URL components instead of whole URLs
                 Key: ODATA-1606
                 URL: https://issues.oasis-open.org/browse/ODATA-1606
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: ABNF
            Reporter: Heiko Theissen


We have published ABNF rules for OData request URLs
- odataUri
- odataRelativeUri
- resourcePath
- queryOptions

which are much complicated by the fact that they produce percent-encoded URLs. Because of ODATA-1583, much of these rules must be duplicated for the context rule, which (being a URL fragment) does not use percent-encoding.

It would be much easier if we only had ABNF rules for the components of a URL:
- path segment
- search parameter name
- search parameter value
- fragment

and then assemble a URL from these parts, with the necessary percent-encoding.

Consider writing an alternative set of ABNF rules with this approach.



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