[OASIS Issue Tracker] (ODATA-984) Make $-prefix optional for system query options

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

Michael Pizzo created ODATA-984:
-----------------------------------

             Summary: Make $-prefix optional for system query options
                 Key: ODATA-984
                 URL: https://issues.oasis-open.org/browse/ODATA-984
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData URL Conventions
    Affects Versions: V4.0_ERRATA03
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.01_WD01


In OData V1, when we originally defined query options for filter, ordering, expand, etc., we prefixed them with "$" so as not to conflict with "custom" query options that a service might implement.

In reality, it is highly unlikely that an OData-compliant service would need to implement a query option named "filter" that is different than "$filter", or "expand" that is different than "$expand", etc.

At the same time, we've been getting pushback that services don't want to have query options prefixed with "$".  In fact, this has been an adoption blocker in cases, especially since it apparently raises issues with some tools.  

Prefixing query options with "$" just creates one more difference between how customers want to implement a service and how they have to implement the service in order to be OData-compliant.



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