[oslc-core] OSLC Core spec query shapes example

[Arthur Ryman]

Dave,

Yes. We can use ResponseInfo to contain any useful information about the 
response when it really is not a property of a  "real" resource.  I 
previously suggested including links to the previous page, first page, 
last page, etc. These would be optional of course, but we could at least 
define them in the spec.

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:
Dave <snoopdave at gmail.com>
To:
Arthur Ryman/Toronto/IBM at IBMCA
Cc:
oslc-core <oslc-core at open-services.net>, 
oslc-core-bounces at open-services.net
Date:
05/05/2010 09:35 AM
Subject:
Re: [oslc-core] OSLC Core spec query shapes example



Good point, Arthur.

Perhaps response info should be expanded a little to cover some of the
things that are commonly found at the start of an Atom feed: title,
update time, self link (oslc:request would map to self;), next link,
etc.

- Dave



On Wed, May 5, 2010 at 8:46 AM, Arthur Ryman <ryman at ca.ibm.com> wrote:
> Dave,
>
> I looked at the example and have a comment. In the query response use 
use
> the following attribute value [1]:
>
> rdf:about="
> 
http://example.com/query?oslc.from=blog:comment&oslc.where=blog:entry=<http://example.com/blogs/entry/42&gt

> ;"
>
> We discussed this many months ago (perhaps before you joined OSLC) and
> came to the conclusion that although we are indeed sending the HTTP
> request to that URL, the response contains a set of triples and the
> triples must have the correct subject nodes, which in this case means 
that
> the rdf:about attribute must be just the query base URL. Recall that the
> meaning of rdf:about is simply to set the subject node for a set of
> triples that are formed from the following property elements. The 
correct
> value is therefore:
>
> rdf:about="http://example.com/query"
>
> I do agree that it seems useful to include the full query URL. The 
client
> already knows that since it sent the request. However, to make it an
> explicit part of the response, the appropriate place would be inside the
> ResponseInfo resource. We'd introduce a new property for that, e.g.
> oslc:request
>
> [1]
> 
http://open-services.net/bin/view/Main/OslcCoreQueryDiscussion?sortcol=table;up=#Executing_Queries

>
> 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:
> Dave <snoopdave at gmail.com>
> To:
> oslc-core <oslc-core at open-services.net>
> Date:
> 05/04/2010 05:21 PM
> Subject:
> [oslc-core] OSLC Core spec query shapes example
> Sent by:
> oslc-core-bounces at open-services.net
>
>
>
> To better understand how queries work in the OSLC Core spec today,
> here's an example that shows how to define a blogging service with
> blog entries, blog comments and a query capability that can query
> across both types of resources.
>
>  http://open-services.net/bin/view/Main/OslcCoreQueryDiscussion
>
> Examples are provided in RDF/XML of these resources:
> - Blog Entry, Blog Comment and Query Resource shapes
> - Service Provider
> - Query response
>
> Thanks to Arthur for a quick review and the one query URI example in
> the document.
>
> Feedback is welcome, as are additional query URI examples.
>
> Thanks,
> Dave
>
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net
>
>
>
>