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-102) Query result container issues in Query spec

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

James Amsden commented on OSLCCORE-102:

In OSLC Core 3.0 Discovery, the oslc:resourceShape property for QueryCapability is described as: "The Query Capability should provide a Resource Shape that describes the query base URI."

It is unclear what this means. What does it mean to describe a URI? It was never clear to me that this was intended to define the shape for the members of the entity response body resulting from the query.

I can see that providing a standard way to describe these members using a shape could be used to reflectively discovery how the server returns the results of the query. What is less clear to me is why this is needed or a good idea. Why not just use rdfs:member and/or ldp:member? What is to be gained by making the result format so flexible and complicated?

I suppose it provides some flexibility to describe what existing implementations do. 

In any case, I think servers SHOULD use ldp:member for 3.0 and SHOULD use rdfs:member for 2.0 compatibility, and the oslc:resourceShape would then be optional and unnecessary. Servers MAY specify the oslc:resourceShape to describe the query result member properties, and if so MUST specify oslc:isMemberProperty in that shape.

> Query result container issues in Query spec
> -------------------------------------------
>                 Key: OSLCCORE-102
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-102
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
> The description of the query result could do with at least one example.
> The current specification does not describe any container, but related guidance documents do. The current position is that an oslc:QueryCapability may reference Zero-or-one oslc:resourceShape. If specified, that resource shape is the resource shape of the query result container, and it MUST denote at least one OSLC property as being a member property using the oslc:isMemberProperty. That predicate is defined in OSLC Core 3.0 Resource shapes, but was not described in the query spec. If a query capability does not reference a resource shape, then the current [undocumented] behaviour is to use rdfs:member.
> Some implementations also provide a resource shape for the query result members by providing an oslc:valueShape for the OSLC property that has oslc:isMemberProperty set to true. However, the semantics of that referenced shape is ambiguous - see https://issues.oasis-open.org/browse/OSLCCORE-145.
> In many cases, both OSLC Core and OSLC Configuration Management provide other containers, and these are specified as LDPCs. These LDPCs have some similarity with a query base except that they do not support oslc.where or oslc.searcdhTerms. We should align the query result container with LDPCs. This has the advantage that it's backwards compatible with OSLC 2.0 query, but has the usual semantics of LDPCs widely used in OSLC Core 3.0. 

This message was sent by Atlassian JIRA

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