[OASIS Issue Tracker] Updated: (ODATA-117) Case-sensitivity of system query options

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-117:
--------------------------------

    Proposal: Confirm that this is intentional (even if not all current implementations ignore case) - see comments for discussion and alternate proposals.  (was: Confirm that this is intentional (even if not all current implementations ignore case))

system query options should be case sensitive. there is no value in allowing the client to express in arbitrary casing, and overhead in server to support different casings. the fact that strings in abnf by default happen to be case-insensitive shouldn't cause us to add burden to the implementations.

I propose we correct the abnf to clarify system query options are case-sensitive.



> Case-sensitivity of system query options
> ----------------------------------------
>
>                 Key: ODATA-117
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-117
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: WD01
>
>
> According to the ABNF rules the system query options ($expand, ...) are case-insensitive (defined as quoted strings, e.g. "$expand")
> This also affects operators ("eq", "and", ...) and functions ("startswith", ...) used in the option values

-- 
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