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-198) select_attr for collections


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

David Laurance commented on CAMP-198:
-------------------------------------

Use cases for filtering collections are driven by two different actors:
1. In displaying a long collection, an end user may want to filter on some attribute or attributes of the collection elements:
   * As a cloud administrator, I want to view only the Assemblies that are currently in an Active state.
   * As a cloud administrator, I want to view only the Assemblies that were created from a specific Plan.

For smaller Cloud installations, Sort functionality will provide an adequate substitute for this capability.

2. A provider may be required to filter collection elements to reflect visibility rules, and show only those elements that a user is allowed to see.

In this case, visibility is not requested by the user, but rather it is determined by the server, based upon the user identity or other user attributes.

We have agreed that ownership of collections will not be managed within the CAMP model.  If ownership or other permission attributes are required, they must be associated with collection elements by a separate mapping or mechanism, and any policy engine or other access control mechanism must understand and use that mechanism. 

However, note that the server must be able to determine the user identity or other user attributes in order to evaluate and enforce access control rules.  If requests are truly stateless, this will mean that user attributes (at a minimum, user identity) must be provided in the user's request for the collection.  If session state is maintained so that the server can track a session across requests, then it is possible for the server to authenticate a user in a separate interaction and rely on session identity to track the user and authorize user access.

> select_attr for collections
> ---------------------------
>
>                 Key: CAMP-198
>                 URL: https://issues.oasis-open.org/browse/CAMP-198
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: New Feature
>          Components: Spec
>    Affects Versions: 1.2
>            Reporter: Anish Karmarkar
>            Assignee: Michael Norman
>            Priority: Minor
>             Fix For: 1.2
>
>
> [Mike Norman is having difficulty w/ Jira login, posting on his behalf --Anish]
> The spec says:
> -----
> 6.5 Request Parameters
> To retrieve a subset of the attributes in a resource, the Consumer MAY use the ‘select_attr’ query parameter in conjunction with the HTTP GET
> -----
> a) Can we add this (or a similar filter) the collection resources in such a way that it relates to the attributes of the entities within the collection, not to the collection itself.
> b) Given that if you leave off the uri, the attribute-filtered collections can contain duplicates we need to define the behaviour around duplication.  It would be helpful to have a version that shows only non-duplicated values so you can retrieve the set of possible values for an attribute (a kind of SELECT DISTINCT/Group By).  We need this functionality in the UI to build filters.
>  



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


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