W3C home > Mailing lists > Public > public-ws-addressing@w3.org > October 2005

Agenda: WS-A telcon 2005-10-31

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Sat, 29 Oct 2005 09:56:53 -0700
Message-Id: <18E71164-F3C5-4FD5-BFAB-217CC53127FA@bea.com>
To: WS-Addressing <public-ws-addressing@w3.org>

W3C Web Services Addressing Working Group - distributed meeting agenda
   Monday, 31 Oct
   21:00-23:00 UTC; 13:00-15:00 US/Pacific; 16:00-18:00 US/Eastern;  
21:00-23:00 UK/London; 22:00-24:00 FR/Paris; 7:00-9:00 (Tuesday) AU/ 
Melbourne; 8:00-9:00 (Tuesday) AU/Brisbane
   Dial-in information on WG Admin page <http://www.w3.org/2002/ws/ 
addr/admin>

1. Roll call, select scribe
(see scribe list below)

2. Agenda review, AOB

3. Call for corrections to the minutes
   - 2005-10-24: <http://www.w3.org/2002/ws/addr/5/10/24-ws-addr- 
minutes.html>

4. Review action items <http://www.w3.org/2002/ws/addr/ 
admin#actionitems>
     2005-10-10: Anish Karmarkar to propose meaningful EPR extensions  
for test 3, Endpoint Reference Extensibility (2.5).  PENDING
     2005-10-24: cr9 - Jonathan Marsh to develop a more detailed  
proposal.  DONE

5. WD Issues <http://www.w3.org/2002/ws/addr/wd-issues/>

* i059 - Support for asynchronous / multi-MEP usage of web services
   Owner: Glen Daniels
   Proposal 1: <http://lists.w3.org/Archives/Public/public-ws- 
addressing/2005Oct/att-0116/ProposalTake3.htm>

6. CR Issues <http://www.w3.org/2002/ws/addr/cr-issues/>

* cr9 - wsa:Action for undefined faults
   ACTION: 2005-10-24: Jonathan Marsh to develop a more detailed  
proposal.  DONE
   Proposal 1: Do nothing / Perhaps note in the spec that such action  
values are explicitly not defined.
   Proposal 2: Reuse http://www.w3.org/@@@@/@@/addressing/fault.
   Proposal 3: Define a new action URI for soap faults (e.g. /soap/ 
fault).
   Proposal 4: <http://www.w3.org/mid/ 
37D0366A39A9044286B2783EB4C3C4E8845EF6@RED- 
MSG-10.redmond.corp.microsoft.com>

* cr10 - TAG Request for Change to WS Addressing Core
   Proposal 1: Add note: Web Architecture dictates that resources  
should be identified with URIs.  Thus, use of the abstract properties  
of an EPR other than wsa:address to identify resources is contrary to  
Web Architecture.  In certain circumstances, use of such additional  
properties may be convenient or beneficial, perhaps due to the  
availability of QName-based tools.  When building systems that  
violate this principle, care must be taken to weigh the tradeoffs  
inherent in deploying resources that are not on the Web.

* cr11 - SOAP Binding and SOAPAction in SOAP 1.1
   Proposal 1: "Use of the SOAPAction HTTP header is required in the  
HTTP Request when using the SOAP 1.1 HTTP binding. The value of the  
SOAPAction HTTP header, if present, MUST either be "[action]" or  
"" (quotes are significant). The latter case supports the ability to  
obscure the wsa:Action header through SOAP-level security mechanisms,  
without requiring otherwise unnecessary transport-level security. A  
SOAPAction value different to "[action]" or "", results in the  
generation of an Action Mismatch fault (see 5.4.1.6 Action Mismatch)."

7. CR Testing report

8. Other Business

-----------------------------------------------------------
Scribe list

A participant from the Member at the top of the list is expected to  
scribe the meeting. If no participant from that Member is able to  
scribe, a participant from the the next Member on the list is  
expected to scribe, and so forth. After one participant from a Member  
scribes, that Member's name goes to the bottom of the list.

Systinet
Datapower
Arjuna
HP
Sun
ERICSSON
Novell
CA
SAP
IBM
IONA
Nortel
TIBCO
webMethods
SeeBeyond
Microsoft
Fujitsu
BEA
BT
Oracle
Sonoa
Sonic
W3C
Nokia
Hitachi


See <http://www.w3.org/2002/ws/addr/minutes.html> for more  
information about taking minutes.
Received on Saturday, 29 October 2005 16:57:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:09 GMT