Fix sortOrder in standard query string parameters

[mmarum-sugarcrm]

Original author: [email protected] (April 20, 2012 20:32:24)

SPECIFICATION BUGS ONLY - Description
=====================================
Currently, the Core API defines "sortOrder" as a MUST support query string parameter but does not define any means of specifying the field to which the sortOrder applies. For 3.0, i recommend deprecated the "sortOrder" parameter and introducing a new "sort" parameter whose value follows the basic syntax below:

sort-default-order = field
sort-default-field = "+" / "-"
sort-order-field = ("+" / "-") field
sort = 1*(sort-default-order / sort-default-field / sort-order-field)

For example:

&sort=+ (sort ascending by the server's chosen default sort field)
&sort=updated (sort by the "updated" field using the server's chosen default ordering)
&sort=+updated (sort ascending by the "updated" field)
&sort=-updated (sort descending by the "updated" field)
&sort=-updated,+name (sort descending by the "updated" field, then "descending" by the name field

Document affected:
==================
1.) Please attach a patch for the document if appropriate.
2.) Post a thread at
http://groups.google.com/group/opensocial-and-gadgets-spec/topics
linking to this issue report.
3.) Post a comment on this issue, linking back to the thread.

Original issue: http://code.google.com/p/opensocial-resources/issues/detail?id=1304