OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (CAMP-189) Filtering

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

Anish Karmarkar updated CAMP-189:

    Affects Version/s: 1.2

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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]