public-ws-addressing@w3.org from February 2005 by subject

"transport address" (was Re: Thoughts on TAG issue EndpointsRef47

Action related to i043

Agenda for joint TAG/WS-Addressing Meeting at Feb. 2005 Technical Plenary

Agenda: 2005-02-27 F2F, Boston, MA US

Agenda: 2005-02-27 F2F, Boston, MA US [DRAFT]

Agenda: WS-A telcon 2005-02-07

Agenda: WS-A telcon 2005-02-14

Agenda: WS-A telcon 2005-02-21

detailed proposal for issues i024 and i026

endpoint definition

i004: Security Model

i004: Text for reorganization of security sections

i007 - Issue 7 convo from Melbourne

i014 again

i017 - Purpose of action property

i017b: Action and ONM

i026 Metadata Proposal (amended)

i042: Extensibility Model

i047: Absolute vs relative URIs

i049: Predefined default/anonymous action URIs

i049: We need a 'default default' action for faults

i051: Binding of message addressing properties in the SOAP underlying protocol [i051]

i051: Text about [action]'s relationship to SOAP Action feature

i051: Text for the relationship between [action]'s value and the SOAP Action HTTP header / feature

i052: What is a logical address?

IRI proposal

issue 017, subissue b -- proposal in light of WSD's best practice decision

Issue 7 - processing model for SOAP headers

Issue 7 convo from Melbourne

Issue i001: what and how many things are we identifying?

Issue i018 -- EPR abstract properties and binding to SOAP

Issue i020 -- restate the subissues in issue i020

Issue i020, subissue 3 proposal

Issue i020, subissue iv

Issue i020, subissue iv: resolution proposal

Issue i044: Definition of the rules to reply to a message in Core 3.2

Issue i048 - summary of discussion

Minutes for the 2005-02-14 teleconference

Minutes for the 2005-02-21 teleconference

Minutes of the 2005-01-31 teleconference

Minutes of the 2005-02-07 teleconference

New ed drafts available.

New editors drafts sans 'identify' used in conjunction with EPRs

NEW ISSUE: Binding of message addressing properties in the SOAP underlying protocol

NEW ISSUE: Binding of message addressing properties in the SOAP underlying protocol [i051]

NEW ISSUE: Definition of SOAP 1.2 (and 1.1) modules

NEW ISSUE: Information Model for EndpointReferences -- is it necessary?

NEW ISSUE: Misalignment of treatment of reply messages and fault messages

NEW ISSUE: Misalignment of treatment of reply messages and fault messages [i050]

NEW ISSUE: Schema tweaks

NEW ISSUE: Splitting the WSDL binding into 1.1 and 2.0 (was -- Re: WSDL 1.1 binding and schedule)

New issue: We need a 'default default' action for faults

NEW ISSUE: What is a logical address?

pointer to detailed metadata proposal

Proposed resolution for issues 24 (metadata) and 26 (multiple ports)

Referencing the IRI RFC (was Re: Snapshots of the drafts for review)

Regrets for 2/21 call

Schema now available ( was RE: Agenda: WS-A telcon 2005-02-21)

Section 2.3 in Editors' draft

Security Considerations - Initial Proposal

SOAP binding: Action and Message-Id

SSDL: SOAP Service Description Language

straw-man agenda for WS-A/TAG Joint Meeting

Thoughts on TAG issue EndpointsRef47

W3C Rec track 101

ws-addr overview for joint meeting with TAG slides

WSDL 1.1 binding and schedule

Last message date: Monday, 28 February 2005 23:06:43 UTC