Re: [oslc-core] Draft query spec

["Nicholas Crossley" <nick_crossley@us.ibm.com>]

Jim asked "- Regarding the oslc:resourceShape
(similar comments apply to TRS membership), why is it necessary or even
useful to have different ways of packaging the results of a query into
a container? Why not simply state that the query results are in an ldp:Container,
and members are declared using the ldp:contains property? Why introduce
additional variability? This would seem to add client and server complexity
with limited value. If we need to do this, then it should be motivated
here." Several other comments address membership issues.

OSLC query was originally developed
before LDP, and so had some concepts such as membership properties that
it defined for itself. Several existing applications use this - in fact,
I do not know of any IBM CLM application that uses ldp:contains for query
results. Most seem to use rdfs:member, though RQM uses a type-specific
membership property such as oslc_qm:testcase.

For compatibility, the OSLC query specification
must allow this kind of membership definition - though it need not encourage
it for future implementations.

Nick.