[OASIS Issue Tracker] (ODATA-1541) Forward slashes in /$filter segments

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

Heiko Theissen created ODATA-1541:
-------------------------------------

             Summary: Forward slashes in /$filter segments
                 Key: ODATA-1541
                 URL: https://issues.oasis-open.org/browse/ODATA-1541
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: URL Conventions
         Environment: Proposed
            Reporter: Heiko Theissen


[OData-URL, section 4.12|https://docs.oasis-open.org/odata/odata/v4.01/os/part2-url-conventions/odata-v4.01-os-part2-url-conventions.html#sec_AddressingaSubsetofaCollection] says:
bq. If the filter path segment appears in the resource path and the parentheses contain a filter expression, that expression MUST NOT use forward slashes.

Can an offending forward slash be replaced by {{%2f}} (the ABNF does not accept this at the moment)? Or must an alias be used to avoid forward slashes in paths? Clarify if necessary.

On the other hand, the rule is too strict, because forward slashes are not a problem if the {{/$filter}} segment occurs in a URL query option, as in [this test case|https://github.com/oasis-tcs/odata-abnf/blob/ad7fc9b1f391b84bcccb5fd7080b863c77d516c6/abnf/odata-aggregation-testcases.yaml#L560-L572].



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