W3C home > Mailing lists > Public > public-ws-addressing@w3.org > January 2006

Agenda: 2006-01-19 F2F, Vancouver, BC CA

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Fri, 13 Jan 2006 14:56:50 -0800
Message-Id: <36D63D33-32F1-4C37-91D0-AE6E476718AF@bea.com>
To: WS-Addressing <public-ws-addressing@w3.org>

W3C Web Services Addressing Working Group - face-to-face meeting agenda
    19-20 January
    Logistics linked from the WG Admin page <http://www.w3.org/2002/ 
ws/addr/admin#schedule>

Thursday, January 19th
-------------------------------------
09:00-09:15
     - Introductions
     - Roll Call
     - Assign Scribes
     - Agenda Review
     - AOB
     - Action Item Review <http://www.w3.org/2002/ws/addr/ 
admin#actionitems>
       2005-11-28: i059 - Jonathan Marsh to maintain option 3 as a  
separate proposal.  PENDING
       2006-01-09: i067 - David Orchard to propose referencing text  
to external binding documents.  PENDING
       2006-01-09: i068 - David Orchard to summarise SOAP/HTTP one- 
way binding status.  PENDING

     - Approve Minutes
       2006-01-09: <http://www.w3.org/2002/ws/addr/6/01/09-ws-addr- 
minutes.html>

09:15-10:15  Rechartering Discusssion
10:15-10:45  Interop Event Feedback / Summary
10:45-11:00  Morning Break
11:00-12:30  Working Draft Issues <http://www.w3.org/2002/ws/addr/wd- 
issues/>

* i066 - wsaw:UsingAddressing as a policy assertion
   Owner: Jonathan Marsh
   Proposal 1: <http://www.w3.org/mid/ 
37D0366A39A9044286B2783EB4C3C4E8012AABB9@RED- 
MSG-10.redmond.corp.microsoft.com>
   Proposal 2: <http://www.w3.org/mid/ 
37D0366A39A9044286B2783EB4C3C4E8012AABB9@RED- 
MSG-10.redmond.corp.microsoft.com>

* i067 - SOAP 1.2 support for Async
   Owner: ???
   Proposal 1: <http://www.w3.org/mid/438CA309.9070406@tibco.com>

* i068 - One-Way SOAP 1.1 Binding for HTTP
   Owner: ???
   Proposal 1: <http://lists.w3.org/Archives/Public/public-ws- 
addressing/2005Dec/att-0080/ws-addr-wsdlProposedRevision1.62.html>

* i069 - Complications due to wsaw:UsingAddressing and wsaw:Anonymous  
on endpoint
   Owner: Katy Warr
   Proposal 1: Remove the ability to associate the  
wsaw:UsingAddressing and wsaw:Anonymous from the endpoint altogether.

* i070 - New Issue: Allow for runtime override of WSDL address when  
generating [destination] MAP
   Owner: Katy Warr

12:30-01:30  Lunch
01:30-03:00  WD Issues (cont’d)
03:00-03:30  Afternoon Break
03:30-05:00  Candidate Recommendation Issues <http://www.w3.org/2002/ 
ws/addr/cr-issues/>

* 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.
   Proposal 2: The Web Architecture dictates that resources should be  
identified with URIs. Thus, use of the abstract properties of an EPR  
other than [destination] to identify a resource may result in it not  
being on the Web. In certain circumstances, use of such additional  
properties may be convenient or beneficial. When building systems  
that use non-URI identifiers, care must be taken to weigh the  
tradeoffs inherent in deploying resources that are not on the Web.
   Proposal 3: The Web Architecture dictates that resources should be  
identified with URIs. Thus, use of the abstract properties of an EPR  
other than [destination] to identify a resource is out of the scope  
of the Web Architecture. In certain circumstances, use of such  
additional properties may be convenient or beneficial. When building  
systems that use non-URI identifiers, care must be taken to weigh the  
tradeoffs inherent in deploying resources that are not on the Web.
   Proposal 4: The Web Architecture dictates that resources should be  
identified with URIs. Thus, use of the abstract properties of an EPR  
other than [destination] to identify a resource loses core benefits  
of the Web Architecture [AoWWW 2.1]. In certain circumstances, use of  
such additional properties may be convenient or beneficial. When  
building systems that use non-URI identifiers, care must be taken to  
weigh the tradeoffs inherent in deploying resources that are not on  
the Web.
   Proposal 5: The W3C Architecture of the World Wide Web [AoWWW]  
recommends as Best Practice [Section 2.1] the use of URIs to identify  
resources. Following this best practice precludes the use of abstract  
properties of an EPR other than [destination] to identify resources.   
In certain circumstances, such a use of additional properties may be  
convenient or beneficial.  However, when building systems, the  
benefits or convenience of identifying a resource using reference  
parameters should be carefully weighed against the benefits of  
identifying a resource solely by URI.
Proposal 6: <http://www.w3.org/mid/20051205213626.GN3451@w3.org>

* cr13 - Two additional predefined faults

* cr14 - Relation of SOAP Headers to transport-level headers

* cr15 - Exact relationship of anonymous URI to SOAP  request-response
   Proposal 1:
          Replace the first two sentences of the section so that the  
section as a whole reads:
          In the context of a SOAP request-response MEP, sending a  
response message to an EPR whose [address] is "http://www.w3.org/@@@@/ 
@@/addressing/anonymous" means sending it as the response message of  
the MEP.  For instance, the SOAP 1.2 HTTP binding[SOAP 1.2 Part 2:  
Adjuncts] puts the reply message in the HTTP response.

Friday, January 20th
-------------------------------------
09:00-10:45  CR Issues (cont'd)
10:45-11:00  Morning Break
11:00-12:30  CR Issues (cont'd)
12:30-01:30  Lunch

--
Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Friday, 13 January 2006 23:01:40 GMT

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