[OASIS Issue Tracker] Commented: (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:comment-tabpanel&focusedCommentId=31261#action_31261 ] 

Stefan Drees commented on ODATA-115:
------------------------------------

I suggest the second proposed resolution, i.e. to consistently state, that whitespace MUST NOT be placed around the equal sign (=) nor a clause-separating comma (,).


Motivation: 
1. Whitespace around these tokens never has been a MUST and the client and server side construction and parsing tasks are simplified.
2. HTTP GET URLs should spend characters wisely, since the real world  length limits are between 255 and approx. 2000 characters
3. Least strong motivation for this is the decoupling from ODATA-127 ;-)


> 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