[OASIS Issue Tracker] Commented: (ODATA-143) Define processing order for system query options

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31518#action_31518 ] 

Michael Pizzo commented on ODATA-143:
-------------------------------------

Agree we should define the ordering specified. one small nit; $skiptoken is an implementation detail that should not be defined in the spec anywhere. We should apply some other means of expressing the skip token, for example:

The following query options are evaluated, in order, prior to applying any server driven paging: $filter, $inlinecount, $orderby.
The following query options are evaluated, in order, after applying any server driven paging: $skip, $top, $expand, $select, $format.

> Define processing order for system query options
> ------------------------------------------------
>
>                 Key: ODATA-143
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-143
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: WD01
>
>


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