[oslc-core] oslc:totalSize Clarification
Andrew J Berner
ajberner at us.ibm.com
Fri Dec 3 12:49:35 EST 2010
Total Count typically isn't essentially a paging issue, it's something you
want to know about a query, but in a paged situation, the client can't
figure it out on their own when they get the first page of results.
In the paged single resource setting, probably some idea of number of pages
could be useful (and also for a query), but that's a different animal,
needed more for purposes of deciding how to retrieve the info, rather than
process it.
Andy Berner
Lead Architect, ISV Technical Enablement and Strategy
IBM Rational Business Development
972 561-6599
ajberner at us.ibm.com
Ready for IBM Rational software partner program -
http://www.ibm.com/isv/rational/readyfor.html
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Arthur Ryman <ryman at ca.ibm.com> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Scott Bosworth/Raleigh/IBM at IBMUS |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Cc: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|oslc-core <oslc-core at open-services.net>, oslc-core-bounces at open-services.net |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|12/03/2010 10:04 AM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [oslc-core] oslc:totalSize Clarification |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|oslc-core-bounces at open-services.net |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Scott,
There are precedents for paging in a non-query context, e.g in Atom. [1]
You may start out requesting a feed that is not so big, but over time it
may get big and the server then needs to either fail or start paging.
In my domain, the list-like resources are queryable. However, my spec
doesn't put any size restrictions on the other document-like resources and
it's conceivable that some of them, in my case Measurement resources,
could get very large.
So the question is, do we spec this now in the Core spec, or do we wait
until we hit the requirement? Any domain spec could define their own
paging mechanism in the absence of paging defined by the Core.
[1] http://tools.ietf.org/html/rfc5005
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
From:
Scott Bosworth <bosworth at us.ibm.com>
To:
oslc-core <oslc-core at open-services.net>
Date:
12/03/2010 10:34 AM
Subject:
Re: [oslc-core] oslc:totalSize Clarification
Sent by:
oslc-core-bounces at open-services.net
As pointed out before, the use of totalCount with paging of "other
resources" seems a bit suspect. Do we really need to say that it SHOULD be
the number of property values (triples)? Is this proposed definition
useful? Is there a use case where someone is needing this capability?
Seems like we are specing something that doesn't need to be spec'd. Maybe
we should just say that totalCount is used in conjunction with query
responses?
Scott
Scott Bosworth | IBM Rational CTO Team | bosworth at us.ibm.com |
919.486.2197(w) | 919.244.3387(m) | 919.254.5271(f)
oslc-core-bounces at open-services.net wrote on 12/03/2010 10:01:08 AM:
> From: Dave <snoopdave at gmail.com>
> To: oslc-core <oslc-core at open-services.net>
> Date: 12/03/2010 10:01 AM
> Subject: Re: [oslc-core] oslc:totalSize Clarification
> Sent by: oslc-core-bounces at open-services.net
>
> Thanks for feedback, Steve and Arthur.
>
> Here's what I have added to the spec:
>
> oslc:totalCount - This optional property indicates the total number of
> results across all pages, its value should be non-negative. In the
> context of a query resource, this value *SHOULD* be the total number
> of result resources, i.e. the member property values that match the
> query. In the context of other resources, the value *SHOULD* be the
> total number of property values (i.e. RDF triples) of the resource.
>
> Any objections?
>
> Thanks,
> Dave
>
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net
> _______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net
_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net
More information about the Oslc-Core
mailing list