[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: OSLC Query Capability question
Dear Core TC, I am not sure if the Core TC is meant to deal with public questions, but we got a question from Ricardo (Koneksys) about the OSLC Query and I thought maybe someone from this TC can help? Ricardo cannot directly send emails to this mailing list. But I found the question interesting myself. Anyone that can clarify how the reponse for a query request with “oslc.order” meant to work? regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45 From: Ricardo Herrera [mailto:ricardo.herrera@koneksys.com]
Good day, I'm implementing an OSLC adapter where I need to use the oslc.orderBy clause in a QueryCapability, I couldn't find in 2.0 spec (neither in 3.0) the standard way to keep the order of the members in the
Query Resource representation. This is what I could find in 2.0: "The OSLC client then uses HTTP GET to request a Query Resource representation of the query results. The Query Resource representation will contain property values about the query and a collection of resources that
match the query criteria." This description does not mention any shape for the Query Resource representation and less for a given important order of the members. So far I've seen examples that uses this shape: ===================================================== a oslc:ResponseInfo; oslc:totalCount 3; rdfs:member a oslc_rm:Requirement ; dcterms:title "..." . dcterms:description "..." ; a oslc_rm:Requirement ; ... a oslc_rm:Requirement ; ... ===================================================== However rdfs:member predicate is not enough to establish an order. OSLC 3.0 focus on the use of LDP containers but I think does not meet this requirement also. I was thinking the solution should be something like: ===================================================== a oslc:ResponseInfo; oslc:totalCount 3; oslc:members [
a rdf:Seq ; rdf:li <http://example.com/services/requirements/6802> ; rdf:li <http://example.com/services/requirements/2875>; rdf:li
<http://example.com/services/requirements/103> ] ===================================================== but I wanted to know whether you have something different to address this scenario that I missed. Thanks in advance. Regards, Ricardo. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]