OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

Michael Pizzo updated ODATA-963:
--------------------------------

    Summary: Make query options, built-in functions, and built-in operators case insensitive  (was: Make query options 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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]