public-ws-desc-comments@w3.org from May 2005 by subject

a WSDL whatsit? (conformance terminology)

Action 2004-11-11 check on operation@style (LC61a) (or REOPEN LC21 Resolution B)

Another part 1 typo

binding/operation/infault|outfault?

Can multiple inline schemas have same targetNamespace?

Clarificatioin for binding fault

Clarification for wsdl:required attribute needed

Clarification needed: Part 3 sec 2.8.1 and 2.8.2: soap fault codes

Clarify whether Parts 2 & 3 MUST be supported

Comments

comments on the wsdl 2.0 working drafts

Component Designators - what's the unique identifier?

Consistency of WSDL Component property names

Contradictions regarding transitivity of wsdl:import

Editorial Comment: wsdl:include

Editorial comments on WSDL 2.0 Part 1

Editorial last call review comments

Editorial: Ambiguous use of the terms "include" and "import"

Editorial: In section 2.15.3, "and" should be "or"

Editorial: Setting Default Values

Editorial: Typos

Extension Components are not Described

Faults that are not described in WSDL?

Feature and Property Composition for Binding Operation Omits Interface Operation

Feature Composition Edge Cases

HTTP Error code for faults (part3, sec 3.7)

HTTP Transfer Coding and 1.0

Idle question

Is schemaLocation Required When Importing Inline Schemas?

Issue: describing the HTTP error text for faults

issues with wsdl:endpoint@address

Last call review comments

LC107 and Inconsistent Component Names

LC84a: Operation Name Mapping Requirement is ambiguous

MEP template

Message Exchange Patterns -- p2c and/or p2e

Message Reference Component is Underspecified

Misc Part1 editorial issues

Mixing Schema Languages

Multiple input and output elements for an operation

mustUnderstand" - ??

New Issue RPC Style (and proposed fix)

New LC issue: XML Schema required (appears twice)

Optional predefined features in Part 2

Part 3, SOAP Binding - Editorial Issues

Pluggability of Schema Languages in WSDL

Property Composition Edge Cases

Proposal for Simplifications to the Component Model

Proposed Changes to the Interface Component, Features and Properties

QA Review on WSDL 2.0 Part 1, Editorial comments

QA Review on WSDL 2.0 Part 1, intro and conformance issues

Raising an ugly issue again

re; Editorial: Typo in Section 3.7.3 Part 2 - HTTP Fault

real players

Resolution of LC89e

The Component Model Does Not Enforce Component Nesting

The Component Model is Underconstrained wrt the WSDL 2.0 Schema

The description of wsdli:wsdlLocation attribute is limiting (Editorial Item)

The WSDL 2.0 XSD for Root Element is Too Loose

typo

URI References for Schema Components

URI Style and SOAP Response Pattern

WSDL 2.0 LC Comments

WSDL 2.0 Part3, Sec. 3.4

WSDL Last Call issue

WSDL2.0 Last Call comments

wsdl:import semantics is different from xs:import

wsdl:include semantics is different from xs:include

XForms comments on (WSDL) Version 2.0 Part 3: Bindings

XML Schema comment "T2" on WSDL 2.0

XML Schema comment on WSDL 2.0

XMLP Review of WSDL 2.0 Part 2 LC WD

{message label} property of Binding Message Reference Component Should be REQUIRED

Last message date: Tuesday, 31 May 2005 14:01:42 UTC