[OASIS Issue Tracker] (ODATA-1171) Consider using matrix parameters for filter segments

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

Michael Pizzo created ODATA-1171:
------------------------------------

             Summary: Consider using matrix parameters for filter segments
                 Key: ODATA-1171
                 URL: https://issues.oasis-open.org/browse/ODATA-1171
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: Protocol, URL Conventions
    Affects Versions: V4.01_CS01
            Reporter: Michael Pizzo
             Fix For: V4.01_CS02


In 4.01 CS01, we introduced the ability to insert a filter into a path using a $filter=@predicat segment (where @predicate is a query string parameter).

It turns out, the facility to append parameter information to a segment was defined many years ago using "matrix parameters" -- basically, a matrix parameter is a way to add a parameter to a path segment using a semi-colon (and, in many cases, can be used instead of a query string parameter, which is exactly the scenario we are trying to enable).

4.01 CS01 syntax:
   Customers/$filter=@q?$@q=name eq 'Smith'
Matrix parameter syntax:
   Customers;$filter=@q?$@q=name eq 'Smith'

Advantages of using matrix parameters:
1) Not inventing something new
2) May already be supported by some systems
3) Similar to syntax for nested expand (and now select) options




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)