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

RE: Agenda: WS-RA 2009-12-01

From: Martin Chapman <martin.chapman@oracle.com>
Date: Tue, 1 Dec 2009 19:25:35 -0000
To: "'Bob Freund'" <bob.freund@hitachisoftware.com>, <public-ws-resource-access@w3.org>
Message-ID: <000401ca72bc$0f3ffbb0$2dbff310$@chapman@oracle.com>
Regrets. At an OASIS SCA F2F meeting.

> -----Original Message-----
> From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On
> Behalf Of Bob Freund
> Sent: 01 December 2009 18:22
> To: public-ws-resource-access@w3.org
> Subject: Agenda: WS-RA 2009-12-01
> 
> distributed meeting:
> 
> Dial-in and IRC according to usual practice[5]
> 
> Topic: Opening
> Roll
> Assignment of scribe[1]
> Approval of this Agenda
> Approval of minutes 2009-11-17[2]
> 
> Topic: Review of new snapshots
> When can it be done?
> 
> 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
> 
> 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: New Issues
> We will attempt to disposition these issues into categories:
> L an issue that may be 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
> 
> New: Common
> -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
> 
> New: Frag
> -none-
> 
> New: Eventing
> -Issue-8176 Eventing: MAY vs MUST on UnkownSubscription fault
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176 -Davis
> -Issue-8323 Eventing: context node for XPath filter dialect ambiguous
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8323 -external comment
> 
> New: MEX
> -Issue-8200 MEX: remove mex-all from Identifier table
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8200 -Davis
> L-Issue-8202 MEX: definition of GetMetata/Dialect is a bit off
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8202 -Davis
> E-Issue-8203 MEX: don't repeat WSA info http://www.w3.org/Bugs/Public/show_bug.cgi?id=8203 -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
> -Issue-8227 Mex: Change the Schema to make Content a child rather than a sibling of Dialect
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8227 -Malhotra
> -Issue-8289 MEX: misuse of RFC2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=8289 -Pilz L-
> Issue-8290 MEX: "Requirements" section confusing and unnecessary
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8290 -Pilz
> E-Issue-8291 MEX: editorial: what is an "explicit request for metadata"?
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8291 -Pilz
> E-Issue-8292 MEX: redundant discussions of WS-T/GetMetadata duality
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8292 -Pilz
> L-Issue-8293 MEX: fuzzy definition of a "metadata resource"
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8293 -Pilz
> -Issue-8294 MEX: editorial: description of @Identifier too verbose
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8294 -Pilz
> -Issue-8295 MEX: Dialect IRI's versus "selector IRI's
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8295 -Pilz
> -Issue-8296 MEX: services can't know what metadata a consumer might need
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8296 -Pilz
> L-Issue-8297 MEX: @URI="http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex" returns nothing
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8297 -Pilz
> 
> New: Transfer
> -Issue-8180 Transfer: can a resource represenation be empty?
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8180 -Davis
> -Issue-8183 Transfer: be clear on fault for bad representation
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8183 -Davis
> -Issue-8298 Transfer: misuse of RFC2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=8298 -Pilz
> -Issue-8299 Transfer: possible ambiguity of extensions in PutResponse and CreateResponse
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8299 -Pilz E-Issue-8300 Transfer: unnecessary
> descriptions of extension elements http://www.w3.org/Bugs/Public/show_bug.cgi?id=8300 -Pilz
> -Issue-8301 Transfer: generating the PutDenied fault
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8301 -Pilz
> E-Issue-8302 Transfer: descriptions of PutResponse and CreateResponse contain unclear sections
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8302 -Pilz
> L-Issue-8303 Transfer: extensibility of wst:Create and wst:CreateResponse
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8303 -Pilz
> 
> New: Enumeration
> -Issue-8157 Enum: apply 6595 to enum http://www.w3.org/Bugs/Public/show_bug.cgi?id=8157 -Davis
> -Issue-8159 Enum: does maxChars include the wsen:Items element?
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8159 -Davis
> -Issue-8161 Enum: en:Code isn't extensible http://www.w3.org/Bugs/Public/show_bug.cgi?id=8161 -Davis
> -Issue-8304 Enum: misuse of RFC2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=8304 -Pilz
> -Issue-8305 Enum: Expires - treatment of specific time values lacking time zones underspecified
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8305 -Pilz
> E-Issue-8306 Enum: description of Pull contains unclear sections
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8306 -Pilz
> 
> 
> Topic: Issues with proposals
> 
> MEX:
> 1-Issue-8031 WS-Mex: Distinguishing the 'main' metadata
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031-Warr
> 2-Issue-6463 MEX-Attaching Policy to WS-Mex GetMetadata
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463 -Warr
> 3-Issue-7728 MEX: Attaching Policy to Indicate MEX/MEX Features Supported
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=7728 -Malhotra
> 
> Transfer:
> 4-Issue-7911 mismatching action and body wrapper http://www.w3.org/Bugs/Public/show_bug.cgi?id=7911 -
> Lafon
> 
> Eventing:
> 5-Issue-7986 Eventing: supported notification policy
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986 -Davis
> X-Issue-8068 Eventing: Create ED Doc http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068 -Davis
> X-Issue-6435 Eventing needs state table to fully describe protocol
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435 -Pilz (LC)
> -Issue-8164 Eventing: delivery of SubscriptionEnd to non-addressable endpoint
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8164 -Davis
> -Issue-8271 Eventing: misuse of RFC2119 terms http://www.w3.org/Bugs/Public/show_bug.cgi?id=8271 -Pilz
> X-Issue-8198 Eventing:  A mechanism to relate the portType(s) of an event source Web Service to the
> abstract description of the events it canproducehttp://www.w3.org/Bugs/Public/show_bug.cgi?id=8198 -
> Nixon
> -Issue-8275 Eventing: editorial: description of wse:Filter/@Dialect verbose and unclear
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275 -Pilz
> -Issue-8281 Eventing: RetryAfter extension semantics
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8281 -Pilz
> -Issue-8283 Eventing: fault descriptions/semantics are inconsistent
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283 -Pilz
> -Issue-8286 Eventing: description of Subscription End ambiguous
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286 -Pilz
> -Issue-8288 Eventing: requirements on Notification Bindings for EventDescriptions too lax
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8288 -Pilz
> L-Issue-8165 Eventing: uniqueness of subscriptions http://www.w3.org/Bugs/Public/show_bug.cgi?id=8165
> -Davis
> L-Issue-8287 Eventing: "Implementation Considerations" - expirations and network latency
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8287 -Pilz
> 
> Common:
> X-Issue-7791 Consistent Policy applied to a set of resources
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=7791 -Fremantle
> 6-Issue-8201 Clarify required and optional operations
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201 -Jeyaraman
> L-Issue-8273 : All: "Security Considerations" sections vague and misleading
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8273 -Pilz
> 
> 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:
> 7-Issue-7774 @mode in ws-frag is harmful http://www.w3.org/Bugs/Public/show_bug.cgi?id=7774 -Lafon
> 8-Issue-8191 serialization of fragment Put input is underspecified
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8191 -Pilz
> -Issue-8181 Frag: description of fragment put is confusing
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8181 -Pilz
> -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
> -Issue-8192 Fragment: when is InvalidFragment fault generated?
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8192 -Davis
> -Issue-8194 Fragment: inconsistency w.r.t multiple nodes
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8194 -Davis
> -Issue-8195 Fragment: what's a wsf:NodeSet? http://www.w3.org/Bugs/Public/show_bug.cgi?id=8195 -Davis
> -Issue-8196 Frag: inheriting enveloping namespace prefixes is dangerous
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196 -Pilz-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
> L-Issue-8185 Frag: fragment Put @Mode="Insert" underspecified
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8185 -Pilz
> L-Issue-8193 Fragment: Replace mode could be clearer
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8193 -Davis
> L-Issue-8257 Frag:AttributeNode/@name description unclear
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8257 -Pilz
> L-Issue-8258 Frag: limits to expression languages and the Put operation
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8258 -Pilz ===
> 
> 
> [1] http://www.w3.org/2002/ws/ra/chair-tools/scribelist.html
> [2] http://www.w3.org/2002/ws/ra/9/11/2009-11-17.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 Tuesday, 1 December 2009 19:26:46 GMT

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