Tuesday, 31 May 2005
- RE: Clarification needed: Part 3 sec 2.8.1 and 2.8.2: soap fault codes
- Re: LC84a: Operation Name Mapping Requirement is ambiguous
Monday, 30 May 2005
Saturday, 28 May 2005
- Re: LC84a: Operation Name Mapping Requirement is ambiguous
- RE: WSDL 2.0 LC Comments
- RE: The description of wsdli:wsdlLocation attribute is limiting (Editorial Item)
- RE: Clarification for wsdl:required attribute needed
- RE: {message label} property of Binding Message Reference Component Should be REQUIRED
- RE: Editorial: Setting Default Values
- RE: wsdl:import semantics is different from xs:import
- RE: Clarification needed: Part 3 sec 2.8.1 and 2.8.2: soap fault codes
- RE: XML Schema comment on WSDL 2.0
- RE: Pluggability of Schema Languages in WSDL
- RE: URI References for Schema Components
- RE: Mixing Schema Languages
Friday, 27 May 2005
Tuesday, 24 May 2005
Monday, 23 May 2005
Saturday, 21 May 2005
Tuesday, 17 May 2005
Saturday, 21 May 2005
- RE: Editorial: In section 2.15.3, "and" should be "or"
- RE: Editorial: Typos
- RE: Another part 1 typo
- RE: Editorial: Ambiguous use of the terms "include" and "import"
- RE: Contradictions regarding transitivity of wsdl:import
- RE: Misc Part1 editorial issues
- RE: a WSDL whatsit? (conformance terminology)
- RE: Raising an ugly issue again
- RE: The WSDL 2.0 XSD for Root Element is Too Loose
- RE: Proposal for Simplifications to the Component Model
- RE: Proposed Changes to the Interface Component, Features and Properties
- RE: Action 2004-11-11 check on operation@style (LC61a) (or REOPEN LC21 Resolution B)
- RE: Multiple input and output elements for an operation
- RE: HTTP Error code for faults (part3, sec 3.7)
- RE: Idle question
- RE: Raising an ugly issue again
- RE: New LC issue: XML Schema required (appears twice)
- RE: Feature and Property Composition for Binding Operation Omits Interface Operation
- RE: Faults that are not described in WSDL?
- RE: Is schemaLocation Required When Importing Inline Schemas?
- RE: Part 3, SOAP Binding - Editorial Issues
- RE: Message Reference Component is Underspecified
- RE: a WSDL whatsit? (conformance terminology)
- RE: New Issue RPC Style (and proposed fix)
- RE: Misc Part1 editorial issues
- RE: Consistency of WSDL Component property names
- RE: Editorial: Ambiguous use of the terms "include" and "import"
- RE: MEP template
- RE: WSDL 2.0 Part3, Sec. 3.4
- RE: Another part 1 typo
- RE: Contradictions regarding transitivity of wsdl:import
- RE: Editorial Comment: wsdl:include
- RE: Editorial: Typos
- RE: LC107 and Inconsistent Component Names
- RE: Editorial: In section 2.15.3, "and" should be "or"
- RE: Component Designators - what's the unique identifier?
- RE: The Component Model Does Not Enforce Component Nesting
- RE: The Component Model is Underconstrained wrt the WSDL 2.0 Schema
- RE: Extension Components are not Described
- RE: Editorial comments on WSDL 2.0 Part 1
- RE: Message Exchange Patterns -- p2c and/or p2e
- RE: WSDL 2.0 LC Comments
Friday, 20 May 2005
Friday, 13 May 2005
- Re: Can multiple inline schemas have same targetNamespace?
- RE: XMLP Review of WSDL 2.0 Part 2 LC WD
- RE: wsdl:include semantics is different from xs:include
- RE: XML Schema comment "T2" on WSDL 2.0
- RE: issues with wsdl:endpoint@address
- RE: comments on the wsdl 2.0 working drafts
- RE: Can multiple inline schemas have same targetNamespace?
Thursday, 12 May 2005
- FW: binding/operation/infault|outfault?
- RE: Clarificatioin for binding fault
- RE: WSDL Last Call issue
- RE: Optional predefined features in Part 2
- RE: Message Exchange Patterns -- p2c and/or p2e
- RE: binding/operation/infault|outfault?
- RE: Editorial last call review comments
- RE: QA Review on WSDL 2.0 Part 1, intro and conformance issues
- RE: QA Review on WSDL 2.0 Part 1, Editorial comments
Wednesday, 11 May 2005
- RE: XForms comments on (WSDL) Version 2.0 Part 3: Bindings
- RE: Last call review comments
- RE: WSDL2.0 Last Call comments
Friday, 6 May 2005
- RE: mustUnderstand" - ??
- RE: URI Style and SOAP Response Pattern
- RE: HTTP Transfer Coding and 1.0
- RE: Property Composition Edge Cases
- RE: Feature Composition Edge Cases
- RE: re; Editorial: Typo in Section 3.7.3 Part 2 - HTTP Fault
Thursday, 5 May 2005
- RE: mustUnderstand" - ??
- RE: URI Style and SOAP Response Pattern
- RE: QA Review on WSDL 2.0 Part 1, intro and conformance issues
- Re: Resolution of LC89e
- Resolution of LC89e