[OASIS Issue Tracker] (CAMP-189) Filtering

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

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

Anish Karmarkar edited comment on CAMP-189 at 6/2/16 4:43 PM:
--------------------------------------------------------------

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.



was (Author: akarmark):
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

> Filtering
> ---------
>
>                 Key: CAMP-189
>                 URL: https://issues.oasis-open.org/browse/CAMP-189
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Michael Norman
>            Priority: Minor
>
> Similar issue to sort [camp-187].  GUI clients woudl typically expect to be able to issue API requests to filter the List resources by attributes of the entities referred to in the Links, including (but not restricted to) the name.  Typical syntax is of the form ?attr=value or ?attr=val*  Again there is no obvious convention to follow
> Need to understant how to avoid conflict with the select_attr query parameter in the (slightly obscure) case where an attribute in an extension happens to be called "select_attr", which is allowed by the spec.



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