OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

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

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

     [ 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 the value rdf:nil means do not return any member properties.  (was: If the proposal for https://issues.oasis-open.org/browse/OSLCCORE-123 is accepted, we can close this issue without additional changes.

However, if we the specification states that implementations MAY return some [undefined] member properties if oslc.select is not specified, we should allow oslc.select to be blank, or define a meta-value meaning no properties should be returned.)

> 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: James Amsden
> 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

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