[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=62591#comment-62591 ] 

Anish Karmarkar commented on CAMP-189:
--------------------------------------

Filtering related requirements from Mike: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/58265/Proposal%20for%20aggregations%20in%20collections.docx

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