RE: Agenda: WS-RA 2010-03-16

Ø  The next F2F is confirmed during May 4-6, 2010 hosted by Microsoft in Redmond, WA. I will send out the logistics by end of this month.

Correction: The next F2F is during May 11-13th, 2010.

From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On Behalf Of Ram Jeyaraman
Sent: Tuesday, March 16, 2010 10:41 AM
To: Bob Freund; public-ws-resource-access@w3.org
Subject: RE: Agenda: WS-RA 2010-03-16


Ø  2119:
P-Issue-8289 MEX: misuse of RFC2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=8289 -Pilz

Ready to resolve this issue.


Ø  Topic: Last call progression

Ready for LC progression.


Ø  Redmond/Bellevue 2010-04-13 through 2010-04-15 tentative

The next F2F is confirmed during May 4-6, 2010 hosted by Microsoft in Redmond, WA. I will send out the logistics by end of this month.

Other issues and topics: I am willing to discuss them today but NOT ready  to resolve. I need more time.

Thanks.

From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On Behalf Of Bob Freund
Sent: Tuesday, March 16, 2010 10:10 AM
To: public-ws-resource-access@w3.org
Subject: Agenda: WS-RA 2010-03-16

Distributed Meeting

Dial-in and IRC according to usual practice[5]

Topic: Opening
Roll
Assignment of scribe[1]
Approval of this Agenda
Approval of minutes of 2010-03-09[2]

Topic: Action Items[4]

Topic: Face to face schedule
Redmond/Bellevue 2010-04-13 through 2010-04-15 tentative
Sophia 2010-06-15 through 2010-06-17 location and dates tentative

N.B. Key:
a number preceding the issue indicates a suggested order of discussion
Items marked "X" in the chair's opinion need seasoning or at least a proposal
L have been reviewd and determined that they MAY be resolved after last call, or have arrived after the last call issue moratorium
P are waiting proposals

Topic: New Issue Moratorium
The working group decided on 2009-11-05 to impose a new issue moratorium effective end of business on 2009-11-13

Topic: Issues

The following substantive issues MUST be resolved prior to last call.
It is the chairs intention to spend the time it takes to resolve them on the call.

MEX:

Transfer:

Eventing:

Common:

Enumeration:

Frag:

2119:
P-Issue-8289 MEX: misuse of RFC2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=8289 -Pilz
Topic: Closure of incorporated issues

Topic: Last call progression

Topic: Release of issue Moratorium

Topic: New Issues: (arrived during issue moratorium)
P-Issue-8832 Eventing: spec unclear on sink/subscriber behavior in face of expected subscription expirationhttp://www.w3.org/Bugs/Public/show_bug.cgi?id=8832 -Pilz
-Issue-8900 WS-Evd unnecessarily references WSDL http://www.w3.org/Bugs/Public/show_bug.cgi?id=8900 -Freund
-Issue-9031 MEX: Dialect is problematic http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031-Davis
P-Issue-9087 Transfer: What is a "resource"  http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087 -Freund
-Issue-9095 WS-Enumeration - Calling Pull or Release operations after EndOfSequence has been issuedhttp://www.w3.org/Bugs/Public/show_bug.cgi?id=9095Jeyayaman

Topic: Issue discussion
Common:
LP-Issue-8273 : All: "Security Considerations" sections vague and misleading http://www.w3.org/Bugs/Public/show_bug.cgi?id=8273 -Pilz
L-Issue-8284 All: references to WSDL 1.1 should be to BP-corrected version http://www.w3.org/Bugs/Public/show_bug.cgi?id=8284 -Pilz (BP 1.2 and 2.0 status)
L-Issue-8886 Eventing/Enum - is expiration cause for xxxEnd msg http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886 -Davis


-Common Xpath dialect
===


[1] http://www.w3.org/2002/ws/ra/chair-tools/scribelist.html
[2] http://www.w3.org/2002/ws/ra/10/03/2010-03-09.html
[3] http://www.w3.org/2002/ws/ra/wiki/Main_Page
[4] http://www.w3.org/2002/ws/ra/tracker/actions/open
[5] http://www.w3.org/2002/ws/ra/admin.html