RE: proposal for issues 8070, 8071, 8072

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.



Ram Jeyaraman <Ram.Jeyaraman@microsoft.com> 
Sent by: public-ws-resource-access-request@w3.org
11/05/2009 06:30 PM

To
Doug Davis/Raleigh/IBM@IBMUS, "public-ws-resource-access@w3.org" 
<public-ws-resource-access@w3.org>
cc

Subject
RE: proposal for issues 8070, 8071, 8072






Hi Doug,
 
I have a few comments below.
 
Thanks.
 
1)
Ø  That is, the enumeration has an indefinite lifetime. It will terminate 
when the end of the enumeration is reached, or if the consumer sends a 
Release request, or by the data source at any time for reasons such as 
connection termination, resource constraints, or system shut-down. 
To
Ø  That is, the enumeration has an indefinite lifetime. It will terminate 
when the enumeration context contained in this message becomes invalid for 
some reason. 
2)
 
Ø  [Body]/wsen:PullResponse/wsen:EndOfSequence
Ø  This OPTIONAL element indicates that no more elements are available 
from this enumeration and the enumeration context becomes invalid.
 
 
Suggest change "the enumeration context" to "the prior representation of 
the enumeration context" or "the enumeration context sent by the consumer 
in the request", for consistency with the required handling ofPullResponse 
EnumerationContext which refers the "prior representation".
 
3)
 
I noticed there is an error in section 4.8
Ø  This fault is generated if the data source times out is the 
wsen:MaxTime is reached. 
Could instead say the following: 
 
?This fault is generated if the data source times out during processing of 
a Pull operation, if the wsen:MaxTime is reached.?
 
4)
 
Change
 
Ø  [body]/wsen:EnumerateResponse/wsen:EnumerationContext 
The required EnumerationContext element contains the XML representation of 
the new enumeration context. The consumer is required to pass this XML 
data in Pull requests for this enumeration context, until and unless a 
PullResponse message updates the enumeration context. 
To
 
Ø  [body]/wsen:EnumerateResponse/wsen:EnumerationContext 
The required EnumerationContext element contains the XML representation of 
the new enumeration context. The consumer is required to pass this XML 
data in Pull requests for this enumeration context, until and unless a 
PullResponse or RenewResponse message updates the enumeration context. 
5)
 
GetStatus:
 
Change:
 
Ø  If the enumeration is valid and has not expired, the data source MUST 
reply with a response of the following form
 
To
 
Ø  If the enumeration is valid, the data source MUST reply with a response 
of the following form
 
From: public-ws-resource-access-request@w3.org 
[mailto:public-ws-resource-access-request@w3.org] On Behalf Of Doug Davis
Sent: Wednesday, November 04, 2009 8:48 AM
To: public-ws-resource-access@w3.org
Subject: proposal for issues 8070, 8071, 8072
 

Issues 8070, 8071 and 8072 all deal with enum contexts and when they're 
invalid and what to do with them when they are.  Its easier to combine 
these all into one joint proposal since they seem to hit the same spots in 
the specs.  See attachment. 


thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.