[oslc-core] Proposal: oslc:Query should become oslc:ResponseInfo

[Dave]

Another great idea Arthur. ResponseInfo makes much more sense to me.

However, please note that the Resource Paging stuff has been moved
into the Query Capability section and now applies only to Query
Resources. An issue was raised against the Resource Paging because it
is a) overly ambitious, b) not implemented and places too much of a
burden on existing client implementations which will have to change to
deal with the possibility that a resource might be partial.

Please add an issue to the issue page for this and we'll get it into the spec.

Thanks,
- Dave


On Tue, Apr 20, 2010 at 5:18 PM, Arthur Ryman <ryman at ca.ibm.com> wrote:
> The original intention for oslc:Query was that it should represent the
> results of a query. However, we don't use it for that purpose. We now use
> rdf:RDF for multiple subjects or a node element for the resource type as
> the document roots in RDF/XML.
>
> We do use oslc:Query to convey paging information via the oslc:nextPage
> property. However, we might need to page any resource, not just the result
> of a query.
>
> Therefore, this resource should become a blank node of type, e.g.
> oslc:ResponseInfo, because it really tells about about an HTTP response.
> We can then use it in any response to indicate paging and potentially
> other properties that are about the response.
>
> 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
>
>
>
>
>
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net
>