[oslc-core] Fw: oslc:totalSize Clarification

[Scott Bosworth]

I'm not questioning the need for paging of resources. I'm questioning
whether we believe the definition of totalCount meaning the number of
properties (triples) makes sense or not.  For Atom, is it the number of
entries in the feed? That seems useful. In our case, does having a total
count of the number of triples have any particular meaning for a client? I
don't have a particular axe to grind either way. I would however suggest
that we see some practical examples of how totalCount would be used. In the
case of query, we already understand this (e.g. a client may want to
present in a ui a list of filtered resources and may want to indicate that
the current view is say 1-100 of totalCount resources in the list). If the
use of totalCount meaning the number of triples has some value, then fine.
I'm just saying no one has asserted how they would actually use it.

As for adding more to the Core spec, we can certainly tee new stuff up in
our core spec backlog and address it post V2..Scott



Scott Bosworth | IBM Rational CTO Team | bosworth at us.ibm.com | 919.486.2197
(w) | 919.244.3387(m) | 919.254.5271(f)
----- Forwarded by Scott Bosworth/Raleigh/IBM on 12/03/2010 11:05 AM -----

Arthur Ryman <ryman at ca.ibm.com> wrote on 12/03/2010 11:03:18 AM:

> 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 11:03 AM
> Subject: Re: [oslc-core] oslc:totalSize Clarification
>
> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20101203/d09b4731/attachment-0003.html>