- From: Mark Nottingham <mark.nottingham@bea.com>
- Date: Sun, 19 Jun 2005 09:13:00 -0700
- To: public-ws-addressing@w3.org
W3C Web Services Addressing Working Group - distributed meeting agenda
Monday, 20 Jun
20:00-22: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; 6:00-8:00 (Tuesday) AU/
Melbourne & 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-06-02: <http://www.w3.org/2002/ws/addr/5/06/02-ws-addr-
minutes.html>
- 2005-06-03: <http://www.w3.org/2002/ws/addr/5/06/03-ws-addr-
minutes.html>
- 2005-06-13: <http://www.w3.org/2002/ws/addr/5/06/13-ws-addr-
minutes.html>
4. Review action items <http://www.w3.org/2002/ws/addr/
admin#actionitems>
2005-06-03: lc87 - Marc Hadley to make concrete proposal. PENDING
2005-06-13: lc76 - David Hull to refine proposal to include
sample fault structures and content. PENDING
2005-06-13: lc75 - Marc Hadley to respond to new proposal. DONE
5. Issues <http://www.w3.org/2002/ws/addr/lc-issues/>
* lc75 - Uniqueness of [message id]
* lc88 - Uniqueness of [message id]
ACTION: 2005-06-13: Marc Hadley to respond to new proposal. DONE
* lc90 - Security implications of [message id] in re-transmissions
* lc101 - How does one extend the abstract properties of an endpoint
reference
* lc104 - XML infoset representation of EPR > Information model
* lc69 - mandatory ReplyTo, handling replies in WS-Addressing
* lc108 - Comment from WSDL group on ReplyTo
* i050 - Misalignment of treatment of reply messages and fault messages
* lc103 - what is a 'request' and what is a 'reply'?
Proposal 1: <http://www.w3.org/mid/1191ECEA-0CEB-47B0-B915-
BA21B2F8D196@Sun.COM>
* lc107 - WS Description WG comments on WS-A
* lc20 - Clarify Anonymous URI and for the case of HTTP responses
6. 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
SAP
ERICSSON
Nortel
Novell
TIBCO
IBM
Datapower
webMethods
SeeBeyond
Fujitsu
IONA
Microsoft
BEA
W3C
CA
BT
Nokia
Arjuna
Oracle
Hitachi
Sonoa
HP
Sonic
Sun
See <http://www.w3.org/2002/ws/addr/minutes.html> for more
information about taking minutes.
--
Mark Nottingham Principal Technologist
Office of the CTO BEA Systems
Received on Sunday, 19 June 2005 16:13:09 UTC