I agree with Arthur. The current draft spec. (in convergence) seems to work for me, at least for an example on paper. So, not sure what problem are we trying to address?
Tack Tong IBM Rational software [email protected] 905-413-3232 tie line 313-3232 ------------------------------ Message: 4 Date: Fri, 28 May 2010 16:18:02 -0400 From: Arthur Ryman <[email protected]> To: Ian Green1 <[email protected]> Cc: oslc-core <[email protected]>, [email protected] Subject: Re: [oslc-core] Issue: need for a query resource definition Message-ID: <ofa44a8f21.d58e5350-on85257731.006e4f78-85257731.006f9...@ca.ibm.com> Content-Type: text/plain; charset="US-ASCII" Ian/Dave, Sorry if I am misunderstanding the use case, but I disagree. The result of a query is just a set of RDF triples and we have defined how to present that in RDF/XML. If we want to support queries that don't return triples and just return tuples of values, then we can use the query result format defined for SPARQL. Why invent yet another query result format? Regards, ___________________________________________________________________________ Arthur Ryman, PhD, DE Chief Architect, Project and Portfolio Management IBM Software, Rational Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063 Twitter | Facebook | YouTube From: Ian Green1 <[email protected]> To: Dave <[email protected]> Cc: oslc-core <[email protected]>, [email protected] Date: 05/28/2010 03:56 AM Subject: Re: [oslc-core] Issue: need for a query resource definition Sent by: [email protected] I think we do need an query result resource that domains could/should/must adopt. best wishes, -ian [email protected] (Ian Green1/UK/IBM@IBMGB) Chief Software Architect, Requirements Definition and Management IBM Rational [email protected] wrote on 27/05/2010 14:22:55: > [image removed] > > [oslc-core] Issue: need for a query resource definition > > Dave > > to: > > oslc-core > > 27/05/2010 14:23 > > Sent by: > > [email protected] > > I just added an issue to the OSLC Core DRAFT issues page. > http://open-services.net/bin/view/Main/OslcCoreV1Issues > > Here' the issue: As things stand today in the OSLC Core spec DRAFT, > OSLC domain specs will have to specify the data model for query > resources. Domains can use OSLC defined resources terminology or a > shape to do this, but the result could be a different query > representation for each domain. I think this is a problem and my > preferred solution to this is to define a simple query shape in > Appendix A, make it optional and encourage OSLC domains to use it > rather than defining new query data models and representations. > > I know we are in convergence and not supposed to be adding things to > the spec, but this seems like a significant gap. Wouldn't it be > preferable for specs to point at a common resource definition for > query rather than defining their own? > > We're almost there now. We've defined the oslc:Repsonse > > Or we could simply define a property to hold query result property > values, e.g. oslc:member (Resource or Inline Resource of any class, > one-or-many) each value represents one query result. > > What is the consensus on this topic? Do we need to define a query > resource in OSLC Core? > > Thanks, > - Dave > > _______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net ------------------------------ _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net End of Oslc-Core Digest, Vol 4, Issue 23 ****************************************
