[OASIS Issue Tracker] (ODATA-963) Make query options, built-in functions, and built-in operators case insensitive

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

    [ https://issues.oasis-open.org/browse/ODATA-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64343#comment-64343 ] 

Michael Pizzo edited comment on ODATA-963 at 11/16/16 11:21 PM:
----------------------------------------------------------------

What about the following:
-null literal
-AND, OR, NOT in search expressions (generally these are case sensitive)




was (Author: mikep):
What about the null literal; should it be case insensitive?

> Make query options, built-in functions, and built-in operators case insensitive
> -------------------------------------------------------------------------------
>
>                 Key: ODATA-963
>                 URL: https://issues.oasis-open.org/browse/ODATA-963
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol, OData URL Conventions
>    Affects Versions: V4.0_ERRATA03
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> Today, query options in OData are case-sensitive (all lower case). I've personally seen (and at times experienced) getting tripped up by using the wrong casing of query options and getting unexpected results.
> Certain programming languages and APIs have casing rules (InitialCaps, camelCase, lowercase, etc.) that they might want to be consistent across system-defined and custom query options.
> Services should support system-defined query options regardless of casing.



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