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

Revised agenda, 2009-11-05/6 face to face

From: Bob Freund <bob.freund@hitachisoftware.com>
Date: Thu, 5 Nov 2009 07:16:54 -0800
Message-Id: <7CA8AB35-DD2A-4A07-835B-5686364AE2CD@hitachisoftware.com>
To: public-ws-resource-access@w3.org
face to face meeting 2009-11-5 and 6
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-05
Location Salon 7
09:00 Scribe assignments, Roll, approval of prior minutes
09:15 Administrivia as below
09:20 Issue Discussion as below
14:00 Joint session with XML security relative to XPath subset  
definition advance reading
Location: Ponderosa, 1st floor, at TPAC (subject to change, confirm at  
registration desk)

Topic: Streaming XPath profile(s)

Bridge:  Zakim Bridge: +1.617.761.6200 conference code 965732#  
('XMLSEC')

IRC Chat: irc.w3.org (port 6665), #xmlsec
Reading: "Subset of XPath for Performance", XML Signature 2.0 FPWD  
(editors draft does not contain all the text, FPWD does)
http://www.w3.org/TR/2009/WD-xmldsig-core2-20091022/#spec-xpath-subset

15:15: Issue Discussion resumes
17:00 meeting recessed

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


Topic: Opening
Roll
Assignment of scribes[1]
Approval of this Agenda
Approval of minutes 2009-10-27[2]

Administrivia
Topic: Logistics January face to face
Host: Fujitsu (Thanks, Dave)
Location: Sunnyvale, CA
Dates: 2010-01-26 through 2010-01-28

N.B. Key:
Due to WG members in the UK, certain issues are marked with "am" to  
indicate that they will be discussed in the mornings.
Due a request by an issue raiser an issue has been market with an "F"  
to indicate that its discussion will not occur until Friday

Topic: New Issue Moratorium
The chair has noticed that many of the new issues received are  
editorial or nearly so. In order to get these specifications  
progressed I suggest the institution of a new issue moratorium except  
for those that may arise from the processing of current issues or  
those that may be extracted from external reviewers comments that are  
substantive in nature.

Topic: New Issues
-Issue-8124 All: policy URIs - what do they reference?  http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124 
  -Davis

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

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
-Issue-8191 serialization of fragment Put input is underspecified http://www.w3.org/Bugs/Public/show_bug.cgi?id=8191 
  -Pilz
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
-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


Topic: Issues with proposals

MEX:
am-Issue-7912 WS-Mex/All: Consider using Dialect Identifier for  
implicit operation WSDL? http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912 
  -Warr
am-Issue-8031 WS-Mex: Distinguishing the 'main' metadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031-Warr
am-Issue-6463 MEX-Attaching Policy to WS-Mex GetMetadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463 
  -Warr (6721)
am-Issue-7728 MEX: Attaching Policy to Indicate MEX/MEX Features  
Supported http://www.w3.org/Bugs/Public/show_bug.cgi?id=7728 -Malhotra  
(6463)

Eventing:
-Issue-7970 Eventing: clarify role of event source http://www.w3.org/Bugs/Public/show_bug.cgi?id=7970 
  -Davis? Antoine?
-Issue-7986 Eventing: supported notification policy http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986 
  -Davis
-Issue-8068 Eventing: Create ED Doc http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068 
  -Davis
-Issue-6435 Eventing needs state table to fully describe protocol http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435 
  -Pilz (LC)
-Issue-8076 Enum and Eventing: Inconsistent Across Protocol and  
Metadata http://www.w3.org/Bugs/Public/show_bug.cgi?id=8076 -Vedamuthu

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

Common:
-Issue-7791 Consistent Policy applied to a set of resources http://www.w3.org/Bugs/Public/show_bug.cgi?id=7791 
  -Fremantle

Enumeration:
-Issue-8069 Enum: intro text needs updating http://www.w3.org/Bugs/Public/show_bug.cgi?id=8069 
  -Davis
-Issue-8070 Enum: ambiguity around new Enum contexts http://www.w3.org/Bugs/Public/show_bug.cgi?id=8070 
  -Davis
-Issue-8071 Enum: Sec 3 intro text isn't accurate w.r.t. EOS http://www.w3.org/Bugs/Public/show_bug.cgi?id=8071 
  -Davis
-Issue-8072 Enum: inconsistency around invalid EnumContext http://www.w3.org/Bugs/Public/show_bug.cgi?id=8072 
  -Davis
-Issue-8075 Enum: MaxTime could be clearer http://www.w3.org/Bugs/Public/show_bug.cgi?id=8075 
  -Davis
-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:
-Issue-7969 Fragment: clarify behavior of optional xml http://www.w3.org/Bugs/Public/show_bug.cgi?id=7969 
  -Davis
===


[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
Received on Thursday, 5 November 2009 15:17:37 GMT

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