W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > August 2009

Revised Agenda, 2009-08-04/06 F2F with new issues listed

From: Bob Freund <bob.freund@hitachisoftware.com>
Date: Mon, 3 Aug 2009 14:47:58 -0400
Message-Id: <B925AE25-7D31-4A0B-8A6C-A19779731E2F@hitachisoftware.com>
To: public-ws-resource-access@w3.org
Face to face meeting
Location: Bellevue, WA Hosted by Microsoft
Location Logistics: http://www.w3.org/2002/ws/ra/9/08/F2FInfo.html
Meeting Time:
Each day will begin at 09:00 PDT and will continue to 17:00 PDT (UTC+8)

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

Note that "*" preceding an issue is chair's suggestion of priority  
discussion
"#" ought to be quickly closable (But the chair is often surprised)
Items marked "X" in the chair's opinion need seasoning
a digit leading indicates the chair's proposed order of discussion

Topic: Opening
Roll
Selection of scribe, see scribe list[1] Six premium scribing slots  
available!
Approval of this Agenda
Approval of minutes from the 2009-07-28 distributed meeting[2]

Topic: Action Item review[4]

Topic: Snapshot review
Anybody ready to close incorporated issues?

Topic: Frag spec
I see it but is it soup yet? When?

Topic: Schedule
Since we are well beyond our chartered schedule, we ought to consider  
a new target time-line.
The following is intended to start the discussion.  Note that not all  
specs will necessary follow the same schedule.
Event:
2009-08-04 Bellevue F2F
2009-09-11 Next WGD publication, Frag FPWD, distribution to other  
organizations for comment prior to Last Call
2009-09-30 Hursley F2F
2009-10-12 Last Call Announcement (minimum three week review), begin  
test preparation
2009-11-02 Tech Plenary Santa Clara (F2F) Last call review complete
six week issue resolution?
2009-12-18 Call for implementations, Publication of Candidate  
Recommendation, identification of features "at risk"
ten week test development? (christmas and New Year's weeks discounted
2010-03-19 Publication of Proposed Recommendation, interoperable  
implementation criteria met or exceeded (minimum of four weeks)
2010-04-30 Recommendation Published


Topic: New Issues -Oh My!-
-Issue-7136 Suggested edits/cleanup of wrapped/unwrapped defintions. http://www.w3.org/Bugs/Public/show_bug.cgi?id=7136 
  -Chapman
-Issue-7159 Eventing lies about sending faults http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159 
  -Davis
-Issue-7160 Eventing:check 2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=7160 
  -Davis
-Issue-7191 Transfer: check 2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=7191 
  -Davis
-Issue-7192 Enumeration is confusing on large items http://www.w3.org/Bugs/Public/show_bug.cgi?id=7192 
  -Davis
-Issue-7193 Enumeration: check 2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=7193 
  -Davis
-Issue-7194 MEX: how to compare Dialect URIs http://www.w3.org/Bugs/Public/show_bug.cgi?id=7194 
  -Davis
-Issue-7195 MEX: 2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=7195 
  -Davis
-Issue-7196 RT: check 2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=7196 
  -Davis
-Issue 7197 Frag: check 2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=7197 
  -Davis
-Issue-7204 Eventing: Delivery policy for delivery mode extension  
(6692-a) http://www.w3.org/Bugs/Public/show_bug.cgi?id=7204 -Li
-Issue-7205 Eventing: Fault behavior for delivery element (6692-b) http://www.w3.org/Bugs/Public/show_bug.cgi?id=7205 
  -Li
-Issue-7206 Eventing: Extension negotiation behavior of Delivery (6692- 
c) http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206 -Li
-Issue-7207 Eventing: Use the work of "Push" (6692-d) http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207 
  -Li

Topic: Issues with proposals

Common:
-none-

Enumeration:
-none-

Transfer:
10-Issue-7015 Transfer: Separation of Verb and Content http://www.w3.org/Bugs/Public/show_bug.cgi?id=7015 
  -Bullen
1-Issue-6720 Transfer: Metadata returned by WS-Transfer GET unclear http://www.w3.org/Bugs/Public/show_bug.cgi?id=6720 
  -Malhotra (Action-83)

Resource-Transfer:
-none-

MEX:
6-Issue-6411 MEX: no way to create metadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=6411 
  -Davis
2-Issue-6719 MEX: What does the MEX dialect denote? http://www.w3.org/Bugs/Public/show_bug.cgi?id=6719 
  -Malhotra (Action-84)

Eventing:
3-Issue-6401 WS-Eventing Notifications violates WS-I BP http://www.w3.org/Bugs/Public/show_bug.cgi?id=6401 
  -Davis (Action-76)
4-Issue-6432 Eventing Push delivery mode does not work when the  
subscriber is not addressablehttp://www.w3.org/Bugs/Public/show_bug.cgi?id=6432-Pilz 
  -Davis
5-Issue-6724 Eventing: define resource representation http://www.w3.org/Bugs/Public/show_bug.cgi?id=6724 
  -Davis

===

Topic: Issues for general discussion
All:
-none-

Transfer
-none-

Resource-Transfer:
-Issue-6422 RT - Introduces An Ad Hoc Boxcarring Mechanism http://www.w3.org/Bugs/Public/show_bug.cgi?id=6422 
  -Bullen
-Issue-6575 RT - Fragment Put should allow computed values http://www.w3.org/Bugs/Public/show_bug.cgi?id=6575 
  -Bullen
-Issue-6634 RT - Document algorithm for modify http://www.w3.org/Bugs/Public/show_bug.cgi?id=6634 
  -Bullen
-Issue-6635 RT - Outer resource with individually addressable inner  
resources http://www.w3.org/Bugs/Public/show_bug.cgi?id=6635 -Bullen
-Issue-6636 RT - Add example of resource after the create http://www.w3.org/Bugs/Public/show_bug.cgi?id=6636 
  -Bullen

Eventing:
-Issue-6435 Eventing needs state table to fully describe protocol http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435 
  -Pilz
9-Issue-6642 Eventing does not describe how to advertise policy for  
Subscription Manager http://www.w3.org/Bugs/Public/show_bug.cgi? 
id=6642 -Pilz
7-Issue-6917 Eventing: Performance Flaw http://www.w3.org/Bugs/Public/show_bug.cgi?id=6917 
  -Li (Action-66)
8-Issue-7127 Eventing: Can event information contained in notification  
be bound to soap:headers http://www.w3.org/Bugs/Public/show_bug.cgi?id=7127 
  -Rutt

MEX:

X-Issue-6463 MEX-Attaching Policy to WS-Mex GetMetadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463 
  -Warr (Katy's return)
11-Issue-6679 MEX's stance towards metadata scope and semantics needs  
clarification http://www.w3.org/Bugs/Public/show_bug.cgi?id=6679 -Pilz

Enumeration:
-Issue-6436 WS-Enumeration needs state table to fully describe  
protocol http://www.w3.org/Bugs/Public/show_bug.cgi?id=6436 -Pilz

AOB
Adjourn

===

Issues needing owners
-Issue-6701 Enumeration: Create Infoset description http://www.w3.org/Bugs/Public/show_bug.cgi?id=6701
-Issue-6702 MEX: Create Infoset description http://www.w3.org/Bugs/Public/show_bug.cgi?id=6702
-Issue-6703 RT: Create Infoset description http://www.w3.org/Bugs/Public/show_bug.cgi?id=6703
-Issue-6704 Transfer: Create Infoset description http://www.w3.org/Bugs/Public/show_bug.cgi?id=6704

===

Needing Proposals prior to Discussion:
Transfer:
-Issue-6533 Transfer: Safeness of operations http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533 
  -Lafon (Action-45)
-Issue-6691 WS-T/RT - Reconcile faults http://www.w3.org/Bugs/Public/show_bug.cgi?id=6691 
  -Warr (Action-51)
F2F-Issue-6694 All: Which specifications have implicit operations? http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694 
  -Davis (Action-87)
-Issue-7013 Transfer: Partial PUT and Versioning http://www.w3.org/Bugs/Public/show_bug.cgi?id=7013 
  -Lafon (Action-67)
F2F-Issue-7068 Transfer: what's the schema of the resource http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068 
  -Davis (Action-85)

Enumeration
-none-

Resource-Transfer:
-Issue-6549 RT - Create focused on resource fragments http://www.w3.org/Bugs/Public/show_bug.cgi?id=6549 
  -Bullen
-Issue-6550 RT - Support for XSLT and XQuery in PUT http://www.w3.org/Bugs/Public/show_bug.cgi?id=6550 
  -Bullen (Action-11)
-Issue-6552 RT - Lifecycle metadata for Create http://www.w3.org/Bugs/Public/show_bug.cgi?id=6552 
  -Bullen (Action-12)
-Issue-6576 RT - No Fault Defined for Mismatch between  
ResourceTransfer header and message bodyhttp://www.w3.org/Bugs/Public/show_bug.cgi?id=6576 
  -Bullen (Action-28)
-Issue-6578 RT - SideEffects applies to other faults http://www.w3.org/Bugs/Public/show_bug.cgi?id=6578 
  -Bullen (Action-29)
-Issue-6579 RT - Bad fragment values with Create http://www.w3.org/Bugs/Public/show_bug.cgi?id=6579 
  -Bullen (Action-30)
-Issue-6603 RT - Inconsistencies in CreateResponse message http://www.w3.org/Bugs/Public/show_bug.cgi?id=6603 
  -Bullen (Action-20)
-Issue-6632 RT - Define fault for cases where the GetResult is too  
large http://www.w3.org/Bugs/Public/show_bug.cgi?id=6632 -Bullen  
(Action-31)
-Issue-6633 RT - Namespaces in updates http://www.w3.org/Bugs/Public/show_bug.cgi?id=6633 
  -Bullen (Action-32)

Eventing:
-Issue-6402 WS-Eventing - define policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=6402 
  -Davis (Action-24)
-Issue-6700 Eventing: Complete Infoset description http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700 
  -Wu

MEX:



Frag
-Issue-7088 Transfer: Define the ws-fragment spec http://www.w3.org/Bugs/Public/show_bug.cgi?id=7088 
  -Davis (Action-81)

===

Blocked with dependancy on (issue):

Eventing:
-Issue-6406 WS-MEX - define policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=6406 
  -Davis (6402)
-Issue-6403 Enumeration - define policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=6403 
  -Davis (Action-60) -Bullen (6402)
-Issue-6407 RT - define policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=6407 
  -Davis (Action-25) (6402)
F2F-X-Issue-6430 Eventing-Remove Attribute wse:EventSource http://www.w3.org/Bugs/Public/show_bug.cgi?id=6430 
  -Li (6401)
X-Issue 6721 All: Attaching policy to implicit operations http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721 
  -Warr (6694)

===

[1] http://www.w3.org/2002/ws/ra/chair-tools/scribelist.html
[2] http://www.w3.org/2002/ws/ra/9/07/2009-07-28.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
Received on Monday, 3 August 2009 18:55:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:18:09 GMT