bogus, viral email
Media type encoding parameter?
- Re: Media type encoding parameter?
- Re: Media type encoding parameter?
- Re: Media type encoding parameter?
Re: issue 168 proposal: xsi:type of external references in Encodi ng (fwd)
- Re: issue 168 proposal: xsi:type of external references in Encodi ng (fwd)
- Re: issue 168 proposal: xsi:type of external references in Encodi ng (fwd)
Multicast MEP and multiple body actors
Re: issue 168 proposal: xsi:type of external references in Encodi ng (fwd)
Re: Two issues to be opened relating to my rewrite for Issue 101 (and one more already resolved)
maxOccurs="1" for header and body?
Proposal for resolving 144, 161, 117: array serialization
- Re: Proposal for resolving 144, 161, 117: array serialization
- Re: Proposal for resolving 144, 161, 117: array serialization
- RE: Proposal for resolving 144, 161, 117: array serialization
- RE: Proposal for resolving 144, 161, 117: array serialization
- RE: Proposal for resolving 144, 161, 117: array serialization
Issue #97 closed
Closing issue 171
Minutes of 12 December 2001
RE: issue 168 proposal: xsi:type of external references in Encodi ng (fwd)
- Re: issue 168 proposal: xsi:type of external references in Encodi ng (fwd)
Publication of SOAP Version 1.2 Part 0: Primer, SOAP Version 1.2 Part 1: Messaging Framework, SOAP Version 1.2 Part 2: Adjuncts and XML Protocol Usage Scenarios as W3C Working Drafts
Test Assertion Subgroup 1
RE: issue 168 proposal: xsi:type of external references in Encoding (fwd)
Minutes of 5 dec 2001 teleconference
proposal for issue 164: describing arrays in XML Schema
Multistructs - why not.
NameValue and NameValueList data types
- Re: NameValue and NameValueList data types
- RE: NameValue and NameValueList data types
- RE: NameValue and NameValueList data types
- RE: NameValue and NameValueList data types
- RE: NameValue and NameValueList data types
- Re: NameValue and NameValueList data types
RE: issue 168 proposal: xsi:type of external references in Enco ding
Test cases for SOAP 1.2 Part 2 Section 5
Two issues to be opened relating to my rewrite for Issue 101 (and one more already resolved)
document vs rpc
RE : Issue 171. Revised text to close issue
Feedback on arrays
Feedback
Re: [soapbuilders] FEEDBACK REQUESTED - Issues regarding Array encoding for SOAP 1.2
RE: [SOAP Encoding Issue] Most to least specific encodingStyles,HOW?
RE: [soapbuilders] FEEDBACK REQUESTED - Issues regarding Array encoding for SOAP 1.2
- RE: [soapbuilders] FEEDBACK REQUESTED - Issues regarding Array encoding for SOAP 1.2
- RE: [soapbuilders] FEEDBACK REQUESTED - Issues regarding Array encoding for SOAP 1.2
FW: [soapbuilders] FEEDBACK REQUESTED - Issues regarding Array en coding for SOAP 1.2
Proposed Issue 173 Resolution (Hierarchical Fault Codes)
- Re: Proposed Issue 173 Resolution (Hierarchical Fault Codes)
- RE: Proposed Issue 173 Resolution (Hierarchical Fault Codes)
- RE: Proposed Issue 173 Resolution (Hierarchical Fault Codes)
- RE: Proposed Issue 173 Resolution (Hierarchical Fault Codes)
- RE: Proposed Issue 173 Resolution (Hierarchical Fault Codes)
- RE: Proposed Issue 173 Resolution (Hierarchical Fault Codes)
Last Call XMLP comments to XMLE: expires Friday Dec 14th
issue 59: mandating character encoding - seeking clarification
RE: issue #159 resolution addendum
Re: ETF: Issue 47 (SOAP Data Model)
- Re: ETF: Issue 47 (SOAP Data Model)
- Re: ETF: Issue 47 (SOAP Data Model)
- Re: ETF: Issue 47 (SOAP Data Model)
RE: issue 168 proposal: xsi:type of external references in Encoding (fwd)
- Re: issue 168 proposal: xsi:type of external references in Encoding (fwd)
- RE: issue 168 proposal: xsi:type of external references in Encoding (fwd)
Re: issue #159 resolution addendum
soap-envelope schema
Encoding test case template
Encoding: encodingStyle issues
Encoding: mandate validation of XML Schema simple types?
- RE: Encoding: mandate validation of XML Schema simple types?
- Re: Encoding: mandate validation of XML Schema simple types?
issue 168 proposal: xsi:type of external references in Encoding
- Re: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
- RE: issue 168 proposal: xsi:type of external references in Encoding
Encoding: multistructs, generic compound types
Test collection as part of group 2 efforts on Section 4
XMLE Review: xmlp wg comments to XMLE/Canonicalization WDs
- RE: XMLE Review: xmlp wg comments to XMLE/Canonicalization WDs
- Re: XMLE Review: xmlp wg comments to XMLE/Canonicalization WDs
- RE: XMLE Review: xmlp wg comments to XMLE/Canonicalization WDs
part 2/sec 6
possible new editorial issues
SOAP IANA considerations
Issue on TBTF introductory text
email for proposed closing of issue #21
RE: Proposed text for issue 155
Re: SOAP and dynamic structures
SOAP Message Path & Transport Binding Standard Features - initial list
Re: Proposed text for issue 155
- Re: Proposed text for issue 155
- Re: Proposed text for issue 155
- Re: Proposed text for issue 155
- Re: Proposed text for issue 155
Re: Proposed resolution of issue 101: relationship between headerand body blocks
TBTF pieces for the specs
[Fwd: Business Case for using SOAP]
- Re: [Fwd: Business Case for using SOAP]
- RE: [Fwd: Business Case for using SOAP]
- RE: [Fwd: Business Case for using SOAP]
RE: Proposed Edits to "Framework" spec for header/body distinctio n.
Possible new issue on interpretation of relative URI actors
- RE: Possible new issue on interpretation of relative URI actors
- RE: Possible new issue on interpretation of relative URI actors
- RE: Possible new issue on interpretation of relative URI actors
- RE: Possible new issue on interpretation of relative URI actors
- RE: Possible new issue on interpretation of relative URI actors
- RE: Possible new issue on interpretation of relative URI actors
- RE: Possible new issue on interpretation of relative URI actors
- Re: Possible new issue on interpretation of relative URI actors
- Re: Possible new issue on interpretation of relative URI actors
- RE: Possible new issue on interpretation of relative URI actors
- RE: Possible new issue on interpretation of relative URI actors
- RE: Possible new issue on interpretation of relative URI actors
RE: Comments on Message Exchange Pattern: Single Request-Response document
RE: Proposed Edits to "Framework" spec for header/body distinctio n.
- Re: Proposed Edits to "Framework" spec for header/body distinctio n.
- RE: Proposed Edits to "Framework" spec for header/body distinctio n.
- RE: Proposed Edits to "Framework" spec for header/body distinctio n.
- Re: Proposed Edits to "Framework" spec for header/body distinctio n.
Comments on Message Exchange Pattern: Single Request-Response document
Re: Transport Binding Reviews
Comments on SOAP Protocol Binding Framework
Comments on the HTTP binding
Proposed Edits to "Framework" spec for header/body distinction.
- re: Proposed Edits to "Framework" spec for header/body distinction.
- Re: Proposed Edits to "Framework" spec for header/body distinction.
- Re: Proposed Edits to "Framework" spec for header/body distinction.
- Re: Proposed Edits to "Framework" spec for header/body distinction.
- Re: Proposed Edits to "Framework" spec for header/body distinction.
- Re: Proposed Edits to "Framework" spec for header/body distinction.
Closing issue 138
Section 5 vs Schema
Issue #170 proposal - referencing to missing data
- RE: Issue #170 proposal - referencing to missing data
- RE: Issue #170 proposal - referencing to missing data
- RE: Issue #170 proposal - referencing to missing data
- Re: Issue #170 proposal - referencing to missing data
- Re: Issue #170 proposal - referencing to missing data
- Re: Issue #170 proposal - referencing to missing data
- Re: Issue #170 proposal - referencing to missing data
RE: SOAP 1.2 Part 0: Primer Editor's draft available for review
RE: i154: are roles invariant?
Re: SOAP 1.2 Part 0: Primer Editor's draft available for review
Proposed text for XML Base support in SOAP 1.2
- Re: Proposed text for XML Base support in SOAP 1.2
- RE: Proposed text for XML Base support in SOAP 1.2
- Re: Proposed text for XML Base support in SOAP 1.2
- RE: Proposed text for XML Base support in SOAP 1.2
- RE: Proposed text for XML Base support in SOAP 1.2
Updated SOAP Protocol Binding Framework
- Re: Updated SOAP Protocol Binding Framework
- Re: Updated SOAP Protocol Binding Framework
- RE: Updated SOAP Protocol Binding Framework
Suggestion on application/soap{+xml} media type attribute
- Re: Suggestion on application/soap{+xml} media type attribute
- Re: Suggestion on application/soap{+xml} media type attribute
- RE: Suggestion on application/soap{+xml} media type attribute
- RE: Suggestion on application/soap{+xml} media type attribute
- Re: Suggestion on application/soap{+xml} media type attribute
- Re: Suggestion on application/soap{+xml} media type attribute