Steve, The client only can parse the result and determine thisCount if the server is following the guideline, but that's just a SHOULD.
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: Steve K Speicher <[email protected]> To: oslc-core <[email protected]> Date: 12/03/2010 01:02 PM Subject: Re: [oslc-core] oslc:totalSize Clarification Sent by: [email protected] -1 for oslc:thisCount. A client has a way to parse and determine what the "this count" is if desired. Adding it to the response, just adds more work for the service provider and also gives them a chance to get it wrong (conflict with what the actual response format has). Thanks, Steve Speicher | IBM Rational Software | (919) 254-0645 > From: Arthur Ryman <[email protected]> > To: Dave <[email protected]> > Cc: oslc-core <[email protected]>, [email protected] > Date: 12/03/2010 10:33 AM > Subject: Re: [oslc-core] oslc:totalSize Clarification > Sent by: [email protected] > > Dave, > > Since you are making these SHOULDs, that leaves the door open for > implementers to use other measures. I am therefore submitting a friendly > amendment to define an optional oslc:thisCount property that says how much > of whatever is meant by oslc:totalCount is included in the current page. > > 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: > Dave <[email protected]> > To: > oslc-core <[email protected]> > Date: > 12/03/2010 10:05 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 _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
