Tuesday, 30 April 2002
- RE: Position on issue 194
- Re: Position on issue 194
- Re: Position on issue 194
- Re: Position on issue 194
- Re: Position on issue 194
- AXIS beta 2 release is available
- RE: Position on issue 194
- Position on issue 194
- Position on issue 195
Monday, 29 April 2002
Saturday, 27 April 2002
Friday, 26 April 2002
- Re: SOAP Encoding Schema broken
- Re: SOAP Encoding Schema broken
- Re: SOAP Encoding Schema broken
- Re: SOAP Encoding Schema broken
- Re: issue #196 closed
Thursday, 25 April 2002
- SOAP Encoding Schema broken
- Encryption: Onward and Upward -- Your Response Needed
- Modules and Features and URIs, oh my!
- Re: Fwd: Moving exc-c14n forward: your response is needed!
- Re: issue #196 closed
- Re: Issue 195: slightly updated simple proposal
- Re: Issue 195: slightly updated simple proposal
- Re: issue #196 closed
- Re: Proposal for dealing with root
- Re: Proposal for dealing with root
- Re: issue #196 closed
Wednesday, 24 April 2002
Thursday, 25 April 2002
- Re: Proposal for dealing with root
- Re: XMLP Issue 193 Closed
- Re: Issue 195: slightly updated simple proposal
- Re: Issue 195: slightly updated simple proposal
Wednesday, 24 April 2002
- Re: Issue 195: slightly updated simple proposal
- Re: Issue 195: slightly updated simple proposal
- Re: Issue 195: slightly updated simple proposal
- RE: Fwd: Moving exc-c14n forward: your response is needed!
- RE: Fwd: Moving exc-c14n forward: your response is needed!
- Re: Issue 195: slightly updated simple proposal
- Re: Issue 195: slightly updated simple proposal
- [xml-dist-app] <none>
- Re: Summary of Issue 194 - encodingStyle
- Re: Issue 195: slightly updated simple proposal
- Re: Fwd: Moving exc-c14n forward: your response is needed!
- Re: Fwd: Moving exc-c14n forward: your response is needed!
- Re: Fwd: Moving exc-c14n forward: your response is needed!
- RE: Providing a short name for single-request-response MEP
- Re: Providing a short name for single-request-response MEP
- Re: Proposal for dealing with root
- Re: Providing a short name for single-request-response MEP
- Re: Issue 195: slightly updated simple proposal
- Re: Proposal for dealing with root
- RE: Providing a short name for single-request-response MEP
- Re: Proposal for dealing with root
- Re: Providing a short name for single-request-response MEP
- Re: Possible issue on definition of Intermediaries
- Re: Providing a short name for single-request-response MEP
- Re: mime type for SOAP Encoding XML format
- Re: Issue 195: slightly updated simple proposal
- RE: Providing a short name for single-request-response MEP
- Re: Proposal for dealing with root
- Re: mime type for SOAP Encoding XML format
- Join us in Orlando!
- Re: Providing a short name for single-request-response MEP
- Re: Summary of Issue 194 - encodingStyle
- Re: Providing a short name for single-request-response MEP
- Re: Proposal for dealing with root
Tuesday, 23 April 2002
Wednesday, 24 April 2002
- Re: Summary of Issue 194 - encodingStyle
- Re: mime type for SOAP Encoding XML format
- mime type for SOAP Encoding XML format
Tuesday, 23 April 2002
- RE: Possible issue on definition of Intermediaries
- Re: Issue 195: slightly updated simple proposal
- RE: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- [TBTF] Proposal on streaming of messages and request/responses
- Re: Summary of Issue 194 - encodingStyle
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Re: Providing a short name for single-request-response MEP
- Re: Summary of Issue 194 - encodingStyle
- Re: Proposal for closing issue 201
- Re: Proposal for dealing with root
- Re: Proposal for dealing with root
- RE: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Re: Proposal for dealing with root
- RE: Providing a short name for single-request-response MEP
- Proposal for dealing with root
- Re: Proposal for closing issue 201
- Re: Issue #203 : First draft text
- Re: Possible issue on definition of Intermediaries
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- RE: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Re: Providing a short name for single-request-response MEP
- RE: Providing a short name for single-request-response MEP
- Re: Summary of Issue 194 - encodingStyle
Monday, 22 April 2002
- Re: Summary of Issue 194 - encodingStyle
- RE: Issue #203 : First draft text
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- RE: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- RE: Summary of Issue 194 - encodingStyle
- Re: Are QNames in Attribute Values Permitted as Identifiers?
- Re: Summary of Issue 194 - encodingStyle
- Re: Summary of Issue 194 - encodingStyle
- Re: Proposal for closing issue 201
- RE: Possible issue on definition of Intermediaries
- RE: Fwd: Moving exc-c14n forward: your response is needed!
- RE: Proposal for dealing with issue 200: SOAPAction header vs. ac tion parameter
- RE: Proposal for closing issue 201
- Re: Summary of Issue 194 - encodingStyle
- Re: Proposal for closing issue 201
- Re: Proposal for closing issue 201
- RE: Providing a short name for single-request-response MEP
- RE: Completing the tables SRR MEP description.
- Proposal for closing issue 201
- Re: Proposal for closing editorial issue 193
- Re: attributes using soap encoding/RPC
Friday, 19 April 2002
Monday, 22 April 2002
Sunday, 21 April 2002
Saturday, 20 April 2002
- Re: [Fwd: RE: [soapbuilders] Question about root (was Re: PEAR SOAP)]
- Please remove from list
- Re: [Issue, March 20th 2002] Serializer vs. De-serializer
Friday, 19 April 2002
- Re: Fwd: Moving exc-c14n forward: your response is needed!
- Resolution of Issue 61
- Please remove from list
- Re: Providing a short name for single-request-response MEP
- Re: [Fwd: RE: [soapbuilders] Question about root (was Re: PEAR SOAP)]
- RE: Providing a short name for single-request-response MEP
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- RE: FW: draft findings on Unsafe Methods (whenToUseGet-7)
Thursday, 18 April 2002
- [Fwd: RE: [soapbuilders] Question about root (was Re: PEAR SOAP)]
- Re: Providing a short name for single-request-response MEP
- Providing a short name for single-request-response MEP
- RE: Proposal for dealing with issue 200: SOAPAction header vs. ac tion parameter
- Re: Proposal for dealing with issue 200: SOAPAction header vs. ac tion parameter
- Re: Proposal for dealing with issue 200: SOAPAction header vs. ac tion parameter
- RE: [Issue, March 20th 2002] Locally vs. Globally Scoped
- RE: [Issue, March 20th 2002] Does EII represent an edge or node?
- RE: Proposal for dealing with issue 200: SOAPAction header vs. ac tion parameter
- Re: Proposal for dealing with issue 200: SOAPAction header vs. ac tion parameter
- Re: TBTF: DRAFT: revisions to MEP descriptions to address overlapping request response.
- RE: Proposal for dealing with issue 200: SOAPAction header vs. ac tion parameter
- Re: [Issue, March 20th 2002] Does EII represent an edge or node?
- Re: Proposal for dealing with issue 200: SOAPAction header vs. action parameter
- Re: [Issue, March 20th 2002] Does EII represent an edge or node?
- Re: [Issue, March 20th 2002] Does EII represent an edge or node?
Wednesday, 17 April 2002
- Fwd: Moving exc-c14n forward: your response is needed!
- Re: [Issue, March 20th 2002] Locally vs. Globally Scoped
- Re: Issue 36: Clarify nature of conformance
- RE: Issue 36: Clarify nature of conformance
- RE: Issue 36: Clarify nature of conformance
- RE: Issue 36: Clarify nature of conformance
- TBTF: DRAFT: revisions to MEP descriptions to address overlapping request response.
- ICE, RSS, SOAP
- SOAP based NMS applications products information
Tuesday, 16 April 2002
- Re: Issue 195: slightly updated simple proposal
- Re: Issue 195: why not only specify the local name
- RE: Proposal for dealing with issue 200: SOAPAction header vs. action parameter
- Re: Proposal for dealing with issue 200: SOAPAction header vs. action parameter
- RE: Proposal for dealing with issue 200: SOAPAction header vs. action parameter
- Re: Proposal for dealing with issue 200: SOAPAction header vs. action parameter
- Re: Updated proposal for issue 192
- RE: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- RE: Updated proposal for issue 192
- Proposal for dealing with issue 200: SOAPAction header vs. action parameter
- RE: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Issue 195: slightly updated simple proposal
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Re: Proposal for cleanup of RPC section (issue 195)
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Re: [Issue, March 20th 2002] Does EII represent an edge or node?
- RE: Proposal for cleanup of RPC section (issue 195)
- Re: Issue 195: why not only specify the local name
- Re: Issue 195: why not only specify the local name
- Re: Proposal for cleanup of RPC section (issue 195)
- [Issue, March 20th 2002] Does EII represent an edge or node?
- Issue 195: why not only specify the local name
- [Issue, March 20th 2002] Locally vs. Globally Scoped
- Re: Updated proposal for issue 192
- RE: Completing the tables SRR MEP description.
- [Issue, March 20th 2002] Serializer vs. De-serializer
- Re: Proposal for cleanup of RPC section (issue 195)
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- RE: Completing the tables SRR MEP description.
- RE: Proposal for cleanup of RPC section (issue 195)
- Re: Summary of Issue 194 - encodingStyle
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
Thursday, 1 January 1970
Tuesday, 16 April 2002
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Re: FW: draft findings on Unsafe Methods (whenToUseGet-7)
- Issue List Closure
Monday, 15 April 2002
- RE: Proposal for cleanup of RPC section (issue 195)
- FW: draft findings on Unsafe Methods (whenToUseGet-7)
- RE: Summary of Issue 194 - encodingStyle
- new to xml
- "A priori" and the default HTTP binding
- RE: Updated proposal for issue 192
- RE: Issue 192 & R803
- Re: Issue 192 & R803
- RE: Issue 192 & R803
- Re: Proposal for closing editorial issue 193
- RE: Completing the tables SRR MEP description.
- Re: Issue 192 & R803
- RE: Completing the tables SRR MEP description.
- Exclusive Anna Kournikova Photos
- Re: Proposal for closing editorial issue 193
- RE: Issue 36: Clarify nature of conformance
- RE: Issue 192 & R803
Sunday, 14 April 2002
- Re: Completing the tables SRR MEP description.
- Re: Proposal for closing editorial issue 193
- Re: Proposal for cleanup of RPC section (issue 195)
Friday, 12 April 2002
- Re: Proposal for closing editorial issue 193
- Proposal for closing editorial issue 193
- Completing the tables SRR MEP description.
- Re: Issue 36: Clarify nature of conformance
- Re: Proposal for allowing xml:lang on faultstring
- Re: Proposal for allowing xml:lang on faultstring
- RE: Proposal for allowing xml:lang on faultstring
- Re: Misunderstanding of SOAP 1.1 element spec
- Misunderstanding of SOAP 1.1 element spec
- RE: Issue 36: Clarify nature of conformance
- RE: Issue 36: Clarify nature of conformance
- RE: Issue 82 : Proposed resolution
- RE: Issue 36: Clarify nature of conformance
Thursday, 11 April 2002
- Re: Issue: HTTP transcoding [ was: What is W3C's position on RFC 3205? ]
- Re: Issue: HTTP transcoding [ was: What is W3C's position on RFC 3205? ]
- Re: Issue #203 : First draft text
- Issue: HTTP transcoding [ was: What is W3C's position on RFC 3205? ]
- Re: Qualification of Fault children (was RE: Updated proposal for iss ue 192)
- RE: Qualification of Fault children (was RE: Updated proposal for issue 192)
- RE: Qualification of Fault children (was RE: Updated proposal for issue 192)
- Re: Qualification of Fault children (was RE: Updated proposal for iss ue 192)
- Re: Qualification of Fault children (was RE: Updated proposal for iss ue 192)
- Re: Proposal for allowing xml:lang on faultstring
- Re: Qualification of Fault children (was RE: Updated proposal for iss ue 192)
- Re: Issue #203 : First draft text
- Re: Issue #203 : First draft text
- Re: Proposal for allowing xml:lang on faultstring
- Re: Summary of Issue 194 - encodingStyle
- [Fwd: attributes using soap encoding/RPC]
- Re: Qualification of Fault children (was RE: Updated proposal for iss ue 192)
Wednesday, 10 April 2002
Thursday, 11 April 2002
- Issue #203 : First draft text
- Re: Qualification of Fault children (was RE: Updated proposal for iss ue 192)
- Re: Summary of Issue 194 - encodingStyle
- Re: Proposal for allowing xml:lang on faultstring
- Re: Updated proposal for issue 192
Wednesday, 10 April 2002
- Re: Proposal for allowing xml:lang on faultstring
- Proposal for allowing xml:lang on faultstring
- Re: Qualification of Fault children (was RE: Updated proposal for iss ue 192)
- Summary of Issue 194 - encodingStyle
- Qualification of Fault children (was RE: Updated proposal for iss ue 192)
- Re: Remove TOC for Pt2 from Pt1 and Vice Versa ?
- Re: Updated proposal for issue 192
- RE: Updated proposal for issue 192
- Re: Remove TOC for Pt2 from Pt1 and Vice Versa ?
- RE: Updated proposal for issue 192
- Re: Comments on a read through of part 2
- Re: Proposal for cleanup of RPC section (issue 195)
- Re: Comments on a read through of part 2
- New issues?
- Re: Updated proposal for issue 192
- Re: Comments on a read through of part 2
- Re: Updated proposal for issue 192
- Re: Updated proposal for issue 192
- Re: Updated proposal for issue 192
- Comments on a read through of part 2
Tuesday, 9 April 2002
- Email Binding Status
- Re: Updated proposal for issue 192
- Updated proposal for issue 192
- Re: Proposal for cleanup of RPC section (issue 195)
- Proposed resolution for issue 29
- Re: Proposal for cleanup of RPC section (issue 195)
- Re: Proposal for cleanup of RPC section (issue 195)
- Re: Proposal for cleanup of RPC section (issue 195)
- Re: Comments on SOAP 1.2 part 2
- Re: Proposal for cleanup of RPC section (issue 195)
- Re: Comments on SOAP 1.2 part 2
Monday, 8 April 2002
- Re: Proposal for cleanup of RPC section (issue 195)
- Re: Comments on SOAP 1.2 part 2
- Re: Proposal for cleanup of RPC section (issue 195)
- Re: Possible issue on definition of Intermediaries
- Re: Issue 190: closed (default values)
- Re: Proposal for cleanup of RPC section (issue 195)
- Re: Proposal for cleanup of RPC section (issue 195)
- Comments on SOAP 1.2 part 2
- Re: Issue 195: soap-rpc:result
- Proposal for cleanup of RPC section (issue 195)
- Re: Issue 195: soap-rpc:result
- Re: Issue 195: soap-rpc:result
- Re: Comments from a Read-Through of Part 1
- Re: Issue 190: closed (default values)
Sunday, 7 April 2002
Friday, 5 April 2002
- Re: Issue 195: soap-rpc:result
- Re: Comments from a Read-Through of Part 1
- Re: Comments from a Read-Through of Part 1
- Re: Comments from a Read-Through of Part 1
- Re: WSDL question
- WSDL question
- Re: New issues (was: Comments from a Read-Through of Part 1)
- Re: Comments from a Read-Through of Part 1
- Re: Comments from a Read-Through of Part 1
- New issues (was: Comments from a Read-Through of Part 1)
- Re: Comments from a Read-Through of Part 1
- Re: Comments from a Read-Through of Part 1
- Comments from a Read-Through of Part 1
Thursday, 4 April 2002
- Re: HTTP vs. SOAP intermediaries
- RE: Is it possible?
- Is it possible?
- log of 4/4/02 TBTF call IRC minutes
- "Chameleon"
- Re: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- Re: HTTP vs. SOAP intermediaries
- HTTP vs. SOAP intermediaries
- Re: FW: TBTF: Proposal for issue 196
- Re: Issue 192 & R803
- Re: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- RE: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- RE: sender/receiver ids transmitted within xml documents...
Wednesday, 3 April 2002
- Re: Possible issue on definition of Intermediaries
- Re: Summarizing the last 192 discussion
- Re: Issue 192 & R803
- Re: Summarizing the last 192 discussion
- Re: Issue 192 & R803
- RE: [TBTF] proposed edits for incorporating conneg feature for HTTP binding
- RE: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- RE: more Re: Issue 192 & R803
- RE: Issue 192 & R803
- Re: SOAP headers for xmldsig and xenc
- SOAP headers for xmldsig and xenc
- RE: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- Re: FW: TBTF: Proposal for issue 196
- Re: [TBTF] proposed edits for incorporating conneg feature for HTTP binding
- Re: Issue 195: soap-rpc:result
- Re: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- New topic for XML forum
- Re: Issue 192 & R803
- Re: Faultactor or faultnode?
- Re: more Re: Issue 192 & R803
- Re: Issue 192 & R803
- more Re: Issue 192 & R803
- Re: Issue 192 & R803
- RE: Issue 192 & R803
- Re: Issue 192 & R803
- Re: Issue 192 & R803
- Re: Issue 192 & R803
- Re: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- RE: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- Re: Issue 192 & R803
- Re: Issue 195: soap-rpc:result
- Re: Possible issue on definition of Intermediaries
- Re: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- Re: Faultactor or faultnode?
- Re: faultactor
- RE: Faultactor or faultnode?
- RE: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- Possible issue on definition of Intermediaries
- Re: Issue 192 & R803
- Re: Faultactor or faultnode?
- Re: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- Re: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- Re: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- Re: Faultactor or faultnode?
- Re: Faultactor or faultnode?
- Re: Faultactor or faultnode?
- Faultactor or faultnode?
- Re: Issue 195: soap-rpc:result
- RE: [TBTF] proposed edits for incorporating conneg feature for HT TP binding
- Re: New (?) issue : SOAP module specifications
- Re: Summarizing the last 192 discussion
- Re: Summarizing the last 192 discussion
- RE: Summarizing the last 192 discussion
- RE: Summarizing the last 192 discussion
- FW: TBTF: Proposal for issue 196
- Resolution of Issue 191
- Re: Summarizing the last 192 discussion
- Re: using xsi:type with the SOAP encoding rules
- Second Workshop on Industrial Experiences with Systems Software (WIESS '02)
- Re: [TBTF] proposed edits for incorporating conneg feature for HTTP binding
- RE: Issues 12 & 192 (long)
Tuesday, 2 April 2002
- RE: Summarizing the last 192 discussion
- Re: Summarizing the last 192 discussion
- RE: Summarizing the last 192 discussion
- Re: New (?) issue : SOAP module specifications
- Re: IP, TCP/UDP as XML App
- Re: New (?) issue : SOAP module specifications
- IP, TCP/UDP as XML App
- RE: Issue 189: closed
- SOAPAction header vs. action parameter
Monday, 1 April 2002
- RE: T is for Transfer
- RE: T is for Transfer
- Re: T is for Transfer
- RE: T is for Transfer
- [TBTF] proposed edits for incorporating conneg feature for HTTP binding
- RE: T is for Transfer
- Re: Summarizing the last 192 discussion
- RE: Summarizing the last 192 discussion
- Re: Summarizing the last 192 discussion
- Re: Summarizing the last 192 discussion
- RE: T is for Transfer