[oslc-core] TRS spec cutoffEvent property

[Steve K Speicher]

> From: Jim des Rivieres <Jim_des_Rivieres at ca.ibm.com>
> To: oslc-core at open-services.net
> Date: 05/15/2013 02:25 PM
> Subject: Re: [oslc-core] TRS spec cutoffEvent property
> Sent by: "Oslc-Core" <oslc-core-bounces at open-services.net>
> 
...snip...

> Jim then replied to Joe: 
> 
> I agree. There should be additional words in the spec explaining the 
> essential properties of base paging. I suggest adding a para like this 
after
> the para "Because of the highly dynamic nature of ...": 
> 
> When a Base is broken into pages, the Client will discover and retrieve 
Base
> page resources to determine the Resources in the Base. A Client MUST 
> retrieve all the page resources of the Base. A Client MAY retrieve the 
Base 
> page resources in any order, including retrieving some Base page 
resources 
> in parallel. A Client retrieves the Base page resources at its own pace, 
and
> MAY retrieve any of the Base page resources more than once. If the 
Server 
> allows the representation of Base page resources to vary over time, the 
> Server MUST ensure that the set of Resources a Client would infer as 
members
> is necessarily an approximation of the Resource Set which, when 
corrected by
> Change Events after the Base's cutoff event, yields the correct set of 
> member Resources in the Resource Set. 
> 

+1 for adding this

- Steve