[OASIS Issue Tracker] (OSLCCORE-101) oslc.properties confusion in OSLC Query spec

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

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

James Amsden commented on OSLCCORE-101:
---------------------------------------

I think we should consider removing the notion of property tree and member list patterns. OSLC Query doesn't really include oslc.property anymore, as that is the so called "Selective Properties" capability that applies to any resource.

The member list pattern applies to collections which are specified using the oslc:queryBase URI property of oslc:QueryCapability in the oslc:Service discovery resource. So OSLC query may be only oslc.where...oslc.select and there is little need to confuse selective properties and query. 



> oslc.properties confusion in OSLC Query spec
> --------------------------------------------
>
>                 Key: OSLCCORE-101
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-101
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> https://open-services.net/bin/view/Main/OSLCCoreSpecQuery secdtion Property Tree Patterns describes the oslc.properties query parameter. That spec does not define the syntax of that query parameter. However, it is defined in OSLC Core 3.0 Part 1 section 4.7 Selective Properties.
> The query parameter can be used in two different contexts:
> 1) Selective properties for a GET of a resource. This is what is described in section 4.7.
> 2) Selective properties for the results of an OSLC Query. This isn't described in section 4.7. It is described in the OSLC Query spec, but there's no reference to the syntax in Core Part 1 section 4.7, and its functionality overlaps oslc.select. The spec does not clearly describe the difference between oslc.properties and olsc.select, and the Query spec has no examples of query results to explain this. I believe the intended behaviour is control which properties of the container itself are returned. In most use cases, this isn't very useful and some implementations might support oslc.select but ignore oslc.properties in their query implementation.
> The whole section about property tree patterns is unclear and could do with improvement.



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