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

Agenda, 2009-07-14 distributed meeting

From: Bob Freund <bob.freund@hitachisoftware.com>
Date: Tue, 14 Jul 2009 07:14:56 +0100
Message-Id: <6C2F7DE6-9273-42CB-9A97-137F0AA5B15F@hitachisoftware.com>
To: public-ws-resource-access@w3.org
Distributed meeting

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
Items marked F2F are reserved for the August face to face
a digit leading indicates the chair's proposed order of discussion

Topic: Opening
Roll
Selection of scribe, see scribe list[1]
Approval of this Agenda
Approval of minutes from the 2009-07-07 distributed meeting[2]

Topic: Team 6401
Status on Use cases and Requirements remaining areas of controversy

Topic: New Issues
-Issue-7088 Transfer: Define the ws-fragment spec http://www.w3.org/Bugs/Public/show_bug.cgi?id=7088 
  -Davis

Topic: Issues with proposals

Common:
-none-

Enumeration:
-none-

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

Resource-Transfer:
2-Issue-6803 RT: Is this functionality required? http://www.w3.org/Bugs/Public/show_bug.cgi?id=6803 
  -Bullen


MEX:
-Issue-6500 MEX: Wrappers around GetMetadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=6500 
  -Bullen
-Issue-6719 MEX: What does the MEX dialect denote? http://www.w3.org/Bugs/Public/show_bug.cgi?id=6719 
  -Malhotra

Eventing:

-Issue-6724 Eventing: define resource representation http://www.w3.org/Bugs/Public/show_bug.cgi?id=6724 
  -Davis
X-Issue-6692 WS-Eventing: Remove Mode from the specification http://www.w3.org/Bugs/Public/show_bug.cgi?id=6692 
  -Snelling
4-Issue-6692-a QName vs Compact Policies
5-Issue-6692-b Fault behavior
6-Issue-6692-c extension negotiation behavior
7-Issue-6692-d use of the work "Push"
3-Issue-6980 Eventing: which came first - the filter or the format? http://www.w3.org/Bugs/Public/show_bug.cgi?id=6980 
  -Davis

===

Topic: Issues for general discussion
All:
-none-

Resource-Transfer:
8-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 WS-Eventing needs state table to fully describe protocol http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435 
  -Pilz
-Issue-6642 WS-Eventing does not describe how to advertise policy for  
Subscription Managerhttp://www.w3.org/Bugs/Public/show_bug.cgi?id=6642  
-Pilz
*-Issue-6917 WS-Eventing: Performance Flaw http://www.w3.org/Bugs/Public/show_bug.cgi?id=6917 
  -Li


MEX:
-Issue-6406 WS-MEX - define policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=6406 
  -Davis
-Issue-6463 MEX-Attaching Policy to WS-Mex GetMetadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463 
  -Warr
-Issue-6679 MEX's stance towards metadata scope and semantics needs  
clarification http://www.w3.org/Bugs/Public/show_bug.cgi?id=6679 -Pilz
-Issue-6680 MEX Section 3.2 has inconsistent properties http://www.w3.org/Bugs/Public/show_bug.cgi?id=6680 
  -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

===
N.B.
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-6551 Transfer - Message processing time exceeded http://www.w3.org/Bugs/Public/show_bug.cgi?id=6551 
  -Bullen (Action-13)
-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-32)
-Issue-6633 RT - Namespaces in updates http://www.w3.org/Bugs/Public/show_bug.cgi?id=6633 
  -Bullen (Action-32)
-Issue-6691 WS-T/RT - Reconcile faults http://www.w3.org/Bugs/Public/show_bug.cgi?id=6691 
  -Warr (Action-51)
-Issue-6694 All: Which specifications have implicit operations? http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694 
  -Davis (Action-66)
-Issue-7013 Transfer: Partial PUT and Versioning http://www.w3.org/Bugs/Public/show_bug.cgi?id=7013 
  -Lafon (Action-67)
-Issue-7068 Transfer: what's the schema of the resource http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068 
  -Davis

Enumeration
-Issue-6403 Enumeration - define policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=6403 
  -Davis (Action-60) -Bullen

Resource-Transfer:
-Issue-6407 WS-RT - define policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=6407 
  -Davis (Action-25)
-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)

Eventing:
F2F-Issue-6401 WS-Eventing Notifications violates WS-I BP http://www.w3.org/Bugs/Public/show_bug.cgi?id=6401 
  -Davis (Action-76)
-Issue-6402 WS-Eventing - define policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=6402 
  -Davis (Action-24)
-Issue-6421 Eventing-Extension point in reply message of Unsubscribe http://www.w3.org/Bugs/Public/show_bug.cgi?id=6421 
  -Bullen (Action-27)
-Issue-6700 Eventing: Complete Infoset description http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700 
  -Wu

MEX:
-Issue-6411 WS-MEX: no way to create metadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=6411 
  -Davis (Action-26)

===

Blocked with dependancy on (issue):

Eventing:
X-Issue-6430 Eventing-Remove Attribute wse:EventSource http://www.w3.org/Bugs/Public/show_bug.cgi?id=6430 
  -Li (6401)
X-Issue-6432 WS-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 (6692)
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-07.html
[3] http://www.w3.org/2002/ws/ra/wiki/Main_Page
[4] this space for rent
[5] http://www.w3.org/2002/ws/ra/admin.html
Received on Tuesday, 14 July 2009 06:15:40 GMT

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