Agenda WS-RA F2F 2010-01-26/28

F2F meeting hosted by Fujitsu:
Logistics at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Dec/0010..html

Dial-in and IRC according to usual practice[5]
Meetings will be held from 9:00 until 5:00 daily

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

Topic: Action Items[4]

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
A and B are secret code markings LOL
E seem to the chair to be editorial
L in the opinion of the chair might be left for last call

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 with proposals

MEX:
3-MOAP--
-Issue-6463 MEX-Attaching Policy to WS-Mex GetMetadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463 -Warr
-Issue-7728 MEX: Attaching Policy to Indicate MEX/MEX Features Supported http://www.w3.org/Bugs/Public/show_bug.cgi?id=7728 -Malhotra
-Issue-8031 WS-Mex: Distinguishing the 'main' metadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031-Warr (7986)

4-Issue-8205 MEX: can mex appear more than once in an EPR http://www.w3.org/Bugs/Public/show_bug.cgi?id=8205 -Davis
5-Issue-8290 MEX: "Requirements" section confusing and unnecessary http://www.w3.org/Bugs/Public/show_bug.cgi?id=8290 -Pilz
6-Issue-8292 MEX: redundant discussions of WS-T/GetMetadata duality http://www.w3.org/Bugs/Public/show_bug.cgi?id=8292 -Pilz
7-Issue-8294 MEX: editorial: description of @Identifier too verbose http://www.w3.org/Bugs/Public/show_bug.cgi?id=8294 -Pilz

Transfer:

Eventing:
1-Issue-6435 Eventing needs state table to fully describe protocol http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435 -Pilz (LC)
8-Issue-7986 Eventing: supported notification policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986 -Davis (8031)
9-Issue-8180 Transfer: can a resource represenation be empty? http://www.w3.org/Bugs/Public/show_bug.cgi?id=8180 -Davis
10-Issue-8198 Eventing:  A mechanism to relate the portType(s) of an event source Web Service to the abstract description of the events it can produce http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198-Nixon
11-Issue-8275 Eventing: editorial: description of wse:Filter/@Dialect verbose and unclear http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275 -Pilz
12-Issue-8288 Eventing: requirements on Notification Bindings for EventDescriptions too lax http://www.w3.org/Bugs/Public/show_bug.cgi?id=8288 -Pilz
13-Issue-8299 Transfer: possible ambiguity of extensions in PutResponse and CreateResponse http://www.w3.org/Bugs/Public/show_bug.cgi?id=8299 -Pilz
14-Issue-8302 Transfer: descriptions of PutResponse and CreateResponse contain unclear sections http://www.w3.org/Bugs/Public/show_bug.cgi?id=8302 -Pilz

Common:
-Issue-7791 Consistent Policy applied to a set of resources http://www.w3.org/Bugs/Public/show_bug.cgi?id=7791 -Fremantle
-Issue-8273 : All: "Security Considerations" sections vague and misleading http://www.w3.org/Bugs/Public/show_bug.cgi?id=8273 -Pilz
15-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

Enumeration:
2-Issue-6436 WS-Enumeration needs state table to fully describe protocol http://www.w3.org/Bugs/Public/show_bug.cgi?id=6436 -Pilz (LC)
16-Issue-8157 Enum: apply 6595 to enum http://www.w3.org/Bugs/Public/show_bug.cgi?id=8157 -Davis
17-Issue-8306 Enum: description of Pull contains unclear sections http://www.w3.org/Bugs/Public/show_bug.cgi?id=8306 -Pilz

Frag:
18-Issue-7774 @mode in ws-frag is harmful http://www.w3.org/Bugs/Public/show_bug.cgi?id=7774 -Lafon
19-Issue-8181 Frag: description of fragment put is confusing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8181 -Pilz
20-Issue-8182 Frag: unclear if/when result of a fragment Put is XSD validated http://www.w3.org/Bugs/Public/show_bug.cgi?id=8182 -Pilz
21-Issue-8191 serialization of fragment Put input is underspecified http://www.w3.org/Bugs/Public/show_bug.cgi?id=8191 -Pilz
22-Issue-8196 Frag: inheriting enveloping namespace prefixes is dangerous http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196 -Pilz
23-Issue-8229 Frag: XPath Level 1's treatment of unqualified element names is dangerous http://www.w3.org/Bugs/Public/show_bug.cgi?id=8229 -Pilz
24-Issue-8185 Frag: fragment Put @Mode="Insert" underspecified http://www.w3.org/Bugs/Public/show_bug.cgi?id=8185 -Pilz
25-Issue-8193 Fragment: Replace mode could be clearer http://www.w3.org/Bugs/Public/show_bug.cgi?id=8193 -Davis
26-Issue-8257 Frag:AttributeNode/@name description unclear http://www.w3.org/Bugs/Public/show_bug.cgi?id=8257 -Pilz
27-Issue-8258 Frag: limits to expression languages and the Put operation http://www.w3.org/Bugs/Public/show_bug.cgi?id=8258 -Pilz

28-Common Xpath dialect

2119: WIll plan for Thursday "on the spot"
-Issue-8160 All: RFC2119 - "required" keyword  http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160 -Davis
-Issue-8271 Eventing: misuse of RFC2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=8271 -Pilz
-Issue-8289 MEX: misuse of RFC2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=8289 -Pilz
-Issue-8298 Transfer: misuse of RFC2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=8298 -Pilz
-Issue-8304 Enum: misuse of RFC2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=8304 -Pilz

===


[1] http://www.w3.org/2002/ws/ra/chair-tools/scribelist.html
[2] http://www.w3.org/2002/ws/ra/10/01/2010-01-19.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