[OASIS Issue Tracker] Updated: (ODATA-115) Inconsistent use of WSP in system query options

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

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

Ralf Handl updated ODATA-115:
-----------------------------

    Proposal: 
Consistently allow whitespace around "=" and ","

XOR

Consistently disallow whitespace around "=" and ","

In any case: use percent-encded whitespace for URL fragments, see ODATA-127

  was:
Consistently allow whitespace around "=" and ","

XOR

Consistently disallow whitespace around "=" and ","


> Inconsistent use of WSP in system query options
> -----------------------------------------------
>
>                 Key: ODATA-115
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-115
>             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
>            Assignee: Ralf Handl
>             Fix For: WD01
>
>
> Some system query options ($filter, $orderby) allow whitespace around the equal sign ($filter=Name eq 'Ralf' / $filter = Name eq 'Ralf'), others ($expand, $format, $inlinecount, $select, $skip, $skiptoken, $top) don't allow any whitespace around the equal sign or the clause-separating comma, and one ($select) only allows it after the equal sign.
> Similar situation with whitespace before or after a clause-separating comma: $select allows it before and after, $orderby allows it after the comma but not before if preceded by "asc" or "desc", $expand does not allow whitespace at all.

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