[OASIS Issue Tracker] Commented: (CAMP-42) Spec should say how to limit/specify the scope of returned data

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

    [ http://tools.oasis-open.org/issues/browse/CAMP-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32242#action_32242 ] 

Jacques Durand  commented on CAMP-42:
-------------------------------------

My suggestion to *support* a full-blown QL like JAQL does not mean a Provider has to implement it. - I believe we all agree we should NOT do Tobias' option #4.

My suggestion to *support* something like JAQL rather falls under Tobias' #2 option: the only aspect that needs be standardized here could be the invocation or binding to such a 3rd party language.  E.g. for JAQL, standardizing on the use of ?jaql=...  query parameter would make it possible for my CLient side scripts to work with any  CAMP Provider that supports JAQL. (and if no support, the standard behavior could be just to ignore the ?jaql parameter).

So supporting #2 in my view means that CAMP says something like: "IF you support server-side QL xyz, THEN your server must recognize query parameter ?xyz=<some_script_name>, ELSE your server must just ignore such a parameter."

As for a limited built-in query capability, assuming we have the use case to back it (how likely do we have to deal with  large Q results?)  then something very basic along #3 ("limit", "start") might be reasonable. I agree it is a slippery slope to go beyond controlling enumeration/pagination.

> Spec should say how to limit/specify the scope of returned data
> ---------------------------------------------------------------
>
>                 Key: CAMP-42
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-42
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Task
>          Components: Spec
>            Reporter: Alex Heneveld
>            Assignee: Alex Heneveld
>
> Currently the spec only dictates requests whose response is an entire Resource object.  These Resources could be very large however, and it is wasteful for everyone to send the entire object if, as will commonly be the case I expect, the client is only interested in a small piece of the Resource.
> This spec should define how a client can restrict a query to selected items of the Resource.  This should include:
> * filtering: selecting a specific key or restricting to a set of keys
> * pagination: selecting a specific element or range of elements (where a key's value is of type list)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira