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

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: V4.0_ERRATA03
Fix Version/s: V4.01_WD01
Component/s: Protocol, URL Conventions
Labels:
None
Environment:

[Proposed]

Proposal:

Hide

4.01 services must support case insensitive system query options. built-in functions, and built-in operators
Interoperable 4.01 clients must continue to use the 4.0 defined casing.

Show
4.01 services must support case insensitive system query options. built-in functions, and built-in operators Interoperable 4.01 clients must continue to use the 4.0 defined casing.
Resolution:

Hide

https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-construction-rules.txt?op=diff&rev=916
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-testcases.xml?op=diff&rev=916

Show
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-construction-rules.txt?op=diff&rev=916 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-testcases.xml?op=diff&rev=916

Description

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.

Attachments

Activity

People

Assignee:

Unassigned

Reporter:

Michael Pizzo

Watchers:

1 Start watching this issue

Dates

Created:

08/Aug/16 5:25 PM

Updated:

05/Dec/16 9:37 AM

Resolved:

08/Sep/16 4:30 PM