public-ws-addressing@w3.org from November 2004 by subject

(no subject)

[public-ws-addressing] <none>

Action and scope (was: WS-Addr issues)

Action item: embedded policy requirements/use case

Action optionality (was: WS-Addr issues)

ACTION: Rich to begin work on schema

Addresses, identifiers, and cookie semantics

Agenda: 2004-12-07 F2F, Redmond, WA US [DRAFT]

Agenda: WS-A telcon 2004-11-08

Agenda: WS-A telcon 2004-11-15

Agenda: WS-A telcon 2004-11-22

Agenda: WS-A telcon 2004-11-29

Agenda: WS-A WG telcon 2004-11-03

AI: why Service QName is required if client has WSDL + engaged in conversation?

Cardinality / Optionality issues

Composibility problems with refps

EPRs and URIs prezo at F2F

foo wsa:action (was WS-Addr issues)

get metadata (was RE: WS-Addr issues

i0001: EPRs as identifiers

i0001: EPRs as identifiers (implementation model)

i0001: EPRs as identifiers (why XML?)

i0016: Distinguishing RefProperty headers

i0018: Protocol-specific markup in RefP's

i001: EPRs as identifiers: Use cases for RefProps/Params

i0031: Making wsa:Action Optional

i003: WSDL 1.1/2.0 MEPs. Initial proposal (long)

i009 Cardinality of properties and their values

i017: Purpose of Action property

i023 status

i023: Requried properties in EPR -- email to kick off the discussion

i026: Supporting Multiple Ports in EPRs: Initial proposal

i028: Implications of the presence of ReplyTo

i028: Implications of the presence of ReplyTo (and also i003: )

i028: RE: i028: Implications of the presence of ReplyTo

i029 Disallowing Faults

i034: computing default Action value for WSDL 2.0

I034: Re: Issue 019: WSDL Version Neutrality

i034: scope of action defaults

i038: Scope of message addressing properties [i038]

Implication of the publication of the first public Working Draft with regards to the Patent Policy

IOR Questions

Issue #1: Proposed text and resolution

Issue 0001: Use cases for Reference Properties?

Issue 011

Issue 012: EPR Lifetime

Issue 012: Recapitulation and proposal draft 1

Issue 019: WSDL Version Neutrality

Issue 019: WSDL Version Neutrality [i034]

Issue 021: WSDL Extension for Addressing

Issue 6 (Message Property Optionality)

ISSUE 8 : "Clarity and Safety"

Issue i021 detailed proposal (was Re: Issue 021: WSDL Extension for Addressing)

Issue numbers

Issues and e-mail discussion

Issues i034: Action defaults (was Re: Issue 019: WSDL Version Neutrality)

Mandator wsa:Action (was Re: WS-Addr issues)

Minutes of the 2004-11-03 teleconference

Minutes of the 2004-11-08 teleconference

Minutes of the 2004-11-15 teleconference

Minutes of the 2004-11-22 teleconference

Minutes of the NYC F2F

NEW ISSUE

NEW Issue - Reference to WSDL definition in an EPR

NEW Issue - Reference to WSDL definition in an EPR [i033]

NEW ISSUE: Fixed action URI for faults

NEW ISSUE: Fixed action URI for faults [i035]

NEW ISSUE: making wsa:Action optional

NEW ISSUE: Marking RefProps/RefParams using attributes

NEW ISSUE: Replace QName's with anyURI

NEW ISSUE: Replace QName's with anyURI [i037]

NEW ISSUE: Scope of message addressing properties

NEW ISSUE: Scope of message addressing properties [i038]

NEW ISSUE: Securing EPRs

NEW ISSUE: Spec name versioning (editorial)

NEW ISSUE: Spec name versioning (editorial) [i039]

New Issue: use XSD to describe the syntax

New Issue: use XSD to describe the syntax [i032]

NEW ISSUE: WS-Addressing MIME Media Type

NEW ISSUE: WS-Addressing MIME Media Type [i036]

Raising issues

Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!)

schema / component model for addressing structures?

Security and self-description (was Re: Composibility problems with refps

URIs vs EPRs

Using attributes to mark RefProp's and RefParam's

WD CHANGE

WD CHANGE: Mention schema, XML 1.0 decisions

Why FaultTo?

why Service QName is required if client has WSDL + engaged in conversation?

WS-A Issue 27 - Reference to WSDL definition in an EPR

WS-A Issue 28 - Multiple ports

WS-A Issue 28 - Multiple ports needed in an EPR

WS-Addr issues

WS-Addressing presentation from the NYC F2F

WS-Reliability specification submitted for OASIS Standard

Last message date: Tuesday, 30 November 2004 22:43:19 UTC