[OASIS Issue Tracker] (CAMP-187) Sort

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

    [ https://issues.oasis-open.org/browse/CAMP-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62587#comment-62587 ] 

Anish Karmarkar commented on CAMP-187:
--------------------------------------

The Sorting, Pagination, Filtering (SPF) Task Force discussed this for the month of May 2016 and had the following recommendations:

  * SPF is only for collection resources
  * SPF only applies to GET
  * SPF order: filter, sort, page (if you are doing all then that is the order)
  * Support count and distinct-count over the selected attribute set and 
    associated list
  * Index can be 0-based or 1-based: we are free to choose what we want
  * Need to have a general stmt in the spec that authorization 
    can affect the results.
  * Add a note in the spec pointing out variations with SCIM and
    inviting feedback.
  * Address filtering of resources in a collection based on values in related
    resources by a considering a "virtual resource" in which every related
    resource has been pulled into the JSON object (recursively) and the
    expression evaluated in the context of this virtual resource.
  * Postpone filtering for now
  * Pagination: If client specifies a count, the server can deliver less than
      or equal to that, but not more than that.


> Sort
> ----
>
>                 Key: CAMP-187
>                 URL: https://issues.oasis-open.org/browse/CAMP-187
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>    Affects Versions: 1.2
>            Reporter: Michael Norman
>            Priority: Minor
>
> Clients consuming the List resources such as assemblies would expect to ask the server side to sort them by the value of certain attributes using a syntax of the form ?sort([+|-]<attribute>) or one of many variations thereof.  There's no standard way of doing this so we should specify one or more in the spec.  
> The List resources specify the entities as Links which are name/URI pairs, so the most obvious sort option is on the name field.  However most clients would expect to be able to sort on other attributes.  See [CAMP-188]



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)