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

Gilbert Pilz commented on CAMP-198:

Comments on the proposal "camp-spec-v1.2-wd12-issue-198-mgn.doc".

1.) In the first paragraph of Section 7.3.2 it says "If an attribute listed in the value of the ‘select_collection_attr’ query parameter is not part of the resource, the provider shall return null for that attribute [PR-XX]". I'm a bit uncomfortable with any language that says a Provider "SHALL return a null" because, up until now, we have been careful to avoid the semantic thicket of "this resource has this attribute and its value is null" vs. "this resource does not have this attribute". If we are going to open that can of worms I would like to see a clear justification for doing so.

2.) The last sentence of Section 7.3.2 should be a requirement.

3.) I think the example in Section needs to be expanded a bit. As it stands, it doesn't really show how duplicates have been eliminated.

4.) Section contains the paranthetical statement "including null if any component does not have a description". Apply comment from (1).

> 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

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