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

Re: Agenda, WS-RA 2009-07-28

From: Yves Lafon <ylafon@w3.org>
Date: Mon, 27 Jul 2009 03:45:18 -0400 (EDT)
To: Bob Freund <bob@freunds.com>
cc: public-ws-resource-access@w3.org
Message-ID: <alpine.DEB.1.10.0907270341200.1266@wnl.j3.bet>
On Fri, 24 Jul 2009, Bob Freund wrote:

> Distributed meeting

Regrets, in another f2f.

>
> 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-21 distributed meeting[2]
>
> Topic: Action Item review[4]
>
> Topic: August F2F
> Agenda consideration and preparation, see items marked F2F below
>
> Topic: New Issues
> -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
>
> Topic: Issues with proposals
>
> Common:
> -none-
>
> Enumeration:
> -none-
>
> Transfer:
> F2F-Issue-7015 Transfer: Separation of Verb and Content 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=7015 -Bullen
>
> Resource-Transfer:
> -none-
>
> MEX:
> -Issue-6411 WS-MEX: no way to create metadata 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6411 -Davis
>
> Eventing:
> 2-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)
> 1-Issue-6692 WS-Eventing: Remove Mode from the specification 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6692 -Snelling
> -Issue-6692-a QName vs Compact Policies
> -Issue-6692-b Fault behavior
> -Issue-6692-c extension negotiation behavior
> -Issue-6692-d use of the word "Push"
> 3-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:
> 4-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
> F2F-Issue-6642 WS-Eventing does not describe how to advertise policy for 
> Subscription Manager http://www.w3.org/Bugs/Public/show_bug.cgi?id=6642 -Pilz
> F2F-Issue-6917 WS-Eventing: Performance Flaw 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6917 -Li (Action-66)
>
> MEX:
> -Issue-6406 WS-MEX - define policy 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6406 -Davis
> 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)
> -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
>
> ===
> 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-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-6720 Transfer: Metadata returned by WS-Transfer GET unclear 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6720 -Malhotra (Action-83)
> -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
> -Issue-6403 Enumeration - define policy 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6403 -Davis (Action-60) -Bullen
>
> Resource-Transfer:
> -Issue-6407 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)
> 5-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:
> 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-6700 Eventing: Complete Infoset description 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700 -Wu
>
> MEX:
>
> -Issue-6719 MEX: What does the MEX dialect denote? 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6719 -Malhotra (Action-84)
>
> 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:
> 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-21.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

-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves
Received on Monday, 27 July 2009 07:45:27 GMT

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