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 <[email protected]> To: oslc-core <[email protected]> Date: 12/03/2010 10:34 AM Subject: Re: [oslc-core] oslc:totalSize Clarification Sent by: [email protected] 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 | [email protected] | 919.486.2197(w) | 919.244.3387(m) | 919.254.5271(f) [email protected] wrote on 12/03/2010 10:01:08 AM: > From: Dave <[email protected]> > To: oslc-core <[email protected]> > Date: 12/03/2010 10:01 AM > Subject: Re: [oslc-core] oslc:totalSize Clarification > Sent by: [email protected] > > 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 > [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
