Agenda 2009-11-06 (corrected)

face to face meeting 2009-11-06
Start time each day will be 9:00am Pacific
end time will be 5:00pm pacific
Breaks will be held as deemed necessary each day for comfort and lunch

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

Schedule all times Pacific:

2009-11-06
Location Salon E (note room change)
09:00 Issue Discussion Continues
12:00 Lunch Break
13:00 Issue Discussion continues
17:00 Meeting adjourns


Topic: Opening
confirmation of scribes
confirmation of this agenda

N.B. Key:
a number preceding the issue indicates a suggested order of discussion

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-09

Topic: New Issues
Note that I have distributed a few new issues in the agenda for  
discussion at this face to face

Topic: New Issues that have arrived subsequent to the first version of  
this agenda
These have ben marked as following (at the sole opinion of the chair:
L an issue safely processable during last call
E an editorial issue suggest that they be reviewed en-mass and either  
approved or if not converted into a last call issue
no mark a normal issue, possibly substantive that would make sense to  
process prior to last call
These as well as any that may arrive prior to the moratorium will be  
sorted out for action on 2009-11-17
A few have been placed on the agenda today for either resolution or  
preliminary discussion

L-Issue-8157 Enum: apply 6595 to enum http://www.w3.org/Bugs/Public/show_bug.cgi?id=8157 
  -Davis
E-Issue-8158 Enum: example 3-1 is wrong w.r.t. expires http://www.w3.org/Bugs/Public/show_bug.cgi?id=8158 
  -Davis
L-Issue-8159 Enum: does maxChars include the wsen:Items element? http://www.w3.org/Bugs/Public/show_bug.cgi?id=8159 
  -Davis
E-Issue-8160 All: RFC2119 - "required" keyword http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160 
  -Davis
L-Issue-8161 Enum: en:Code isn't extensible http://www.w3.org/Bugs/Public/show_bug.cgi?id=8161 
  -Davis
L-Issue-8162 Eventing: "event notifications"??? http://www.w3.org/Bugs/Public/show_bug.cgi?id=8162 
  -Davis
E-Issue-8163 Eventing: we send notifications not events http://www.w3.org/Bugs/Public/show_bug.cgi?id=8163 
  -Davis
L-Issue-8164 Eventing: delivery of SubscriptionEnd to non-addressable  
endpoint http://www.w3.org/Bugs/Public/show_bug.cgi?id=8164 -Davis
L-Issue-8165 Eventing: uniqueness of subscriptions http://www.w3.org/Bugs/Public/show_bug.cgi?id=8165 
  -Davis
E-Issue-8166 Eventing: remove "we" http://www.w3.org/Bugs/Public/show_bug.cgi?id=8166 
  -Davis
E-Issue-8167 Eventing: no SHOULD about it http://www.w3.org/Bugs/Public/show_bug.cgi?id=8167 
  -Davis
E-Issue-8168 MEX-Eventing: text about WSA is redundant http://www.w3.org/Bugs/Public/show_bug.cgi?id=8168 
  -Davis
L-Issue-8169 Eventing: dup WSA refP text http://www.w3.org/Bugs/Public/show_bug.cgi?id=8169 
  -Davis
E-Issue-8170 Eventing: (de)marshalling? http://www.w3.org/Bugs/Public/show_bug.cgi?id=8170 
  -Davis
E-Issue-8172 Eventing: ED@name MUST be unique http://www.w3.org/Bugs/Public/show_bug.cgi?id=8172 
  -Davis
L-Issue-8176 Eventing: MAY vs MUST on UnkownSubscription fault http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176 
  -Davis
E-Issue-8177 Transfer: intro is a bit off w.r.t. create http://www.w3.org/Bugs/Public/show_bug.cgi?id=8177 
  -Davis
L-Issue-8178 Transfer: is create optional? http://www.w3.org/Bugs/Public/show_bug.cgi?id=8178 
  -Davis
E-Issue-8179 All: refs to faults http://www.w3.org/Bugs/Public/show_bug.cgi?id=8179 
  -Davis
L-Issue-8180 Transfer: can a resource represenation be empty? http://www.w3.org/Bugs/Public/show_bug.cgi?id=8180 
  -Davis
L-Issue-8181 desription of fragment put is confusing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8181 
  -Pilz
L-Issue-8182 unclear if/when result of a fragment Put is XSD validated http://www.w3.org/Bugs/Public/show_bug.cgi?id=8182 
  -Pilz
L-Issue-8183 Transfer: be clear on fault for bad representation http://www.w3.org/Bugs/Public/show_bug.cgi?id=8183 
  -Davis
E-Issue-8184 Transfer: what does delete actually do? http://www.w3.org/Bugs/Public/show_bug.cgi?id=8184 
  -Davis
L-Issue-8185 fragment Put @Mode="Insert" underspecified http://www.w3.org/Bugs/Public/show_bug.cgi?id=8185 
  -Pilz
E-Issue-8186 Transfer: odd wording for ResourceCreated http://www.w3.org/Bugs/Public/show_bug.cgi?id=8186 
  -Davis
L-Issue-8192 Fragment: when is InvalidFragment fault generated? http://www.w3.org/Bugs/Public/show_bug.cgi?id=8192 
  -Davis
L-Issue-8193 Fragment: Replace mode could be clearer http://www.w3.org/Bugs/Public/show_bug.cgi?id=8193 
  -Davis
L-Issue-8194 Fragment: inconsistency w.r.t multiple nodes http://www.w3.org/Bugs/Public/show_bug.cgi?id=8194 
  -Davis
L-Issue-8195 Fragment: what's a wsf:NodeSet? http://www.w3.org/Bugs/Public/show_bug.cgi?id=8195 
  -Davis
L-Issue-8196 inheriting enveloping namespace prefixes is dangerous http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196 
  -Pilz
E-Issue-8199 MEX: example 2-1 is missing the Get Body wrapper http://www.w3.org/Bugs/Public/show_bug.cgi?id=8199 
  -Davis
-Issue-8200 MEX: remove mex-all from Identifier table http://www.w3.org/Bugs/Public/show_bug.cgi?id=8200 
  -Davis
-Issue-8202 MEX: definition of GetMetata/Dialect is a bit off http://www.w3.org/Bugs/Public/show_bug.cgi?id=8202 
  -Davis
L-Issue-8203 MEX: don't repeat WSA info http://www.w3.org/Bugs/Public/show_bug.cgi?id=8203 
  -Davis
-Issue-8204 MEX: metadata in an EPR is misleading http://www.w3.org/Bugs/Public/show_bug.cgi?id=8204 
  -Davis
-Issue-8205 MEX: can mex appear more than once in an EPR http://www.w3.org/Bugs/Public/show_bug.cgi?id=8205 
  -Davis
L-Issue-8213 Eventing: two minor things...  http://www.w3.org/Bugs/Public/show_bug.cgi?id=8213 
  -Davis
L-Issue-8214 MEX: Typo in mex Content URI parameter http://www.w3.org/Bugs/Public/show_bug.cgi?id=8214 
  -Davis

Topic: Issues with proposals

MEX:
1(status check)-Issue-8031 WS-Mex: Distinguishing the 'main' metadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031-Warr
X-Issue-6463 MEX-Attaching Policy to WS-Mex GetMetadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463 
  -Warr
2-Issue-7728 MEX: Attaching Policy to Indicate MEX/MEX Features  
Supported http://www.w3.org/Bugs/Public/show_bug.cgi?id=7728 -Malhotra
3-Issue-8124 All: policy URIs - what do they reference?  http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124 
  -Davis

Transfer:
4-Issue-7911 mismatching action and body wrapper http://www.w3.org/Bugs/Public/show_bug.cgi?id=7911 
  -Lafon

Eventing:
5-Issue-7970 Eventing: clarify role of event source http://www.w3.org/Bugs/Public/show_bug.cgi?id=7970 
  -Davis? Antoine?
6-Issue-7986 Eventing: supported notification policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986 
  -Davis
7-Issue-8068 Eventing: Create ED Doc http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068 
  -Davis
8-Issue-6435 Eventing needs state table to fully describe protocol http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435 
  -Pilz (LC)
9-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 producehttp://www.w3.org/Bugs/Public/show_bug.cgi?id=8198 -Nixon  
(new)

Common:
10-Issue-7791 Consistent Policy applied to a set of resources http://www.w3.org/Bugs/Public/show_bug.cgi?id=7791 
  -Fremantle
11-Issue-8201 Clarify required and optional operations http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201 
  -Jeyaraman (new)


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

Frag:
12-Issue-7774 @mode in ws-frag is harmful http://www.w3.org/Bugs/Public/show_bug.cgi?id=7774 
  -Lafon
13-Issue-7969 Fragment: clarify behavior of optional xml http://www.w3.org/Bugs/Public/show_bug.cgi?id=7969 
  -Davis
14-Issue-8191 serialization of fragment Put input is underspecified http://www.w3.org/Bugs/Public/show_bug.cgi?id=8191 
  -Pilz (new)
===


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