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