[OASIS Issue Tracker] (OSLCCORE-148) How to specify that no member properties should be returned

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

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

David Honey updated OSLCCORE-148:
---------------------------------

    Proposal: 
The specification should say that:

Servers SHOULD accept the value rdf:nil. If specified as the only property, servers SHOULD omit all properties of the member resources. If oslc.select specifies rdf:nil and other properties, servers MAY choose to respond with 400 Bad Request, or ignore the rdf:nil, or have other implementation dependent behavior.

  was:
The specification should say that:
1) If oslc.select just specifies rdf:nul, then a server SHOULD not return any member properties.
2) If oslc.select includes rdf:nil and one or more additional properties, a server MAY choose to  means do not return any member properties.


> How to specify that no member properties should be returned
> -----------------------------------------------------------
>
>                 Key: OSLCCORE-148
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-148
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Query
>            Reporter: David Honey
>            Assignee: David Honey
>
> How does a query capability consumer specify that no properties of members should be returned in a query result?
> The syntax of oslc.select requires that at least one property is specified. The spec does not define the behaviour if oslc.select is omitted - see https://issues.oasis-open.org/browse/OSLCCORE-123.
> If the query result is an LDPC, then one solution is to use LDPC Prefer capabilities such as: Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMembership http://www.w3.org/ns/ldp#PreferMinimalContainer";.
> However, this seems like a complex solution to meet this requirement, and implementations that do not use LDPCs are unlikely to support it.



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