RE: [Bug 6916] Event and Enum: change MAY generate to MUST generate

Thanks to Yves, they're now on the w3c site:
http://www.w3.org/2002/ws/ra/9/05/wseventing-6916.html
http://www.w3.org/2002/ws/ra/9/05/wsenum-6916.html

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.



Doug Davis/Raleigh/IBM@IBMUS 
Sent by: public-ws-resource-access-request@w3.org
06/02/2009 11:40 AM

To
public-ws-resource-access@w3.org
cc

Subject
RE: [Bug 6916] Event and Enum: change MAY generate to MUST generate







let's just go thru each one in context by looking at my proposed changes 
in these marked-up docs. 
[1] http://www.soaphub.org/public/files/w3c/wseventing-6916.html 
[2] http://www.soaphub.org/public/files/w3c/wsenum-6916.html 

Can I upload these to the w3c site by myself?  If so, what's the URL to 
the page? 

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. 


Geoff Bullen <Geoff.Bullen@microsoft.com> 
Sent by: public-ws-resource-access-request@w3.org 
06/02/2009 10:57 AM 


To
"public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org> 
cc

Subject
RE: [Bug 6916] Event and Enum: change MAY generate to MUST generate








Hi all,

In general we believe the intent here is not that it "MUST generate" a 
fault,  but that if it does generate a fault it "MUST generate this 
specific fault".

Perhaps some clearer wording might be:

"If a fault is generated, it MUST generate XXX".

There are also a few occasions when this wording should not be used:

In Enumeration:

1)
[Body]/wsen:PullResponse/wsen:EndOfSequence

This optional element indicates that no more elements are available from 
this enumeration. Additionally, once this element is returned in a Pull 
response message, subsequent Pull requests using that enumeration context 
SHOULD generate a wsen:InvalidEnumerationContext fault message; in any 
case, they MUST NOT return a valid PullResponse.

This needs to be left as is until Issue 6956 is resolved.

2)
Section 3.2 at the end.

If the consumer does issue a Pull or Release on an invalid enumeration 
context, the result is undefined: the data source MAY ignore the request 
or MAY return a wsen:InvalidEnumerationContext fault or MAY take some 
other action.

This should be left as is.

--Geoff


-----Original Message-----
From: public-ws-resource-access-notifications-request@w3.org 
[mailto:public-ws-resource-access-notifications-request@w3.org] On Behalf 
Of bugzilla@wiggum.w3.org
Sent: Tuesday, May 26, 2009 1:51 PM
To: public-ws-resource-access-notifications@w3.org
Subject: [Bug 6916] Event and Enum: change MAY generate to MUST generate

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6916





--- Comment #2 from Robert Freund <bob@freunds.com>  2009-05-26 20:51:29 
---
discussed on 2009-05-26, folks requested 1 more week


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.