RFC 3288:Using the Simple Object Access Protocol (...
RFC-Ref

SOAP


Click on the red underlined text to get to the source

... This memo specifies how SOAP 1.1 envelopes[1] are transmitted using a BEEP profile ...
... BEEP profile[2]. In the W3C, the XMLP effort is evolving SOAP. Accordingly, this memo provides a mechanism for negotiating the use of new features. ...
... of new features. Throughout this memo, the term "envelope" refers to the "SOAP- Env:Envelope" element defined in Section 4 of [1 ...


... The BEEP profile for SOAP is identified as http://iana.org/beep/soap ...
... There are two states in the BEEP profile for SOAP, "boot" and "ready": ...
... o In the "ready" state, either peer begins a SOAP message pattern by sending a "MSG" message containing an envelope. The other peer completes the message pattern either by: ...
... channel bound to the BEEP profile for SOAP provides access to a single resource (a network data object or service ...
... feature negotiation: if new features of SOAP (such as compression) emerge, their use can be negotiated. ...
... feature tokens, each indicating an optional feature of the BEEP profile for SOAP that is being requested for possible use over the channel. ...
... The channel bound to the BEEP profile for SOAP is now in the "ready" state. ...


... SOAP Message Packages ...
... The BEEP profile for SOAP transmits envelopes encoded as UTF-8 using the media type ...
... application/xml <SOAP-ENV:Envelope xmlns:SOAP ...
... SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding ...
... xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP ...
... SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Body> <m:GetLastTradePrice xmlns:m="Some-URI ...
... DIS</symbol> </m:GetLastTradePrice> </SOAP-ENV:Body> </SOAP-ENV:Envelope> ...
... </SOAP-ENV:Body> </SOAP-ENV:Envelope> END ...
... In addition, the BEEP profile for SOAP also allows envelopes to be transmitted as the root part of a "multipart/related"[5 ...
... <?xml version='1.0' ?> <SOAP-ENV:Envelope xmlns:SOAP ...
... SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> ...
... xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> .. <theSignedForm href="cid:claim061400a.tiff@claiming-it.com" /> ...
... <theSignedForm href="cid:claim061400a.tiff@claiming-it.com" /> .. </SOAP-ENV:Body> </SOAP-ENV:Envelope> ...
... </SOAP-ENV:Body> </SOAP-ENV:Envelope> --MIME ...


... SOAP Message Patterns ...
... The BEEP profile for SOAP achieves this using a one-to-many exchange, in which the client sends a "MSG" message containing an envelope, and ...
... The BEEP profile for SOAP achieves this using a one-to-one exchange, in which the client ...
... Finally, the BEEP profile for SOAP does not use the "ERR" message for SOAP ...
... SOAP does not use the "ERR" message for SOAP faults when performing one-to-one exchanges -- whatever response is generated by the server ...
... The BEEP profile for SOAP achieves this using a one-to-many exchange, in which the client sends a "MSG" message containing an envelope, and ...


... soap.beep" and "soap.beeps", which identify the use of SOAP over BEEP over TCP. Note that, at present, a "generic" URL scheme ...
... TCP. Note that, at present, a "generic" URL scheme for SOAP is not defined. ...
... URL scheme indicates the use of the BEEP profile for SOAP running over TCP/IP. ...
... that prior to starting the BEEP profile for SOAP, the BEEP session must be tuned for privacy ...


... SOAP Profile Feature Registration Template ...
... When a feature for the BEEP profile for SOAP is registered, the following information is supplied: ...


... Registration: The SOAP Profile ...
... Messages starting one-to-one exchanges: bootmsg, SOAP-Env:Envelope Messages in positive replies: bootrpy, SOAP ...
... SOAP-Env:Envelope Messages in positive replies: bootrpy, SOAP-Env:Envelope Messages in negative replies: error Messages ...
... Messages in negative replies: error Messages in one-to-many exchanges: SOAP-Env:Envelope Message Syntax: SOAP ...
... SOAP-Env:Envelope Message Syntax: SOAP-Env:Envelope as defined in Section 4 of [1] and [6 ...
... 10] Intended usage: identifies a SOAP resource made available using the BEEP profile for SOAP ...
... SOAP resource made available using the BEEP profile for SOAP Applications using this scheme: c.f., "Intended usage", above ...
... 10] Intended usage: identifies a SOAP resource made available using the BEEP profile for SOAP ...
... SOAP resource made available using the BEEP profile for SOAP after the BEEP session has been tuned for privacy ...
... Registration: The System (Well-Known) TCP port number for SOAP over BEEP ...
... Multicast: none Proposed Name: SOAP over BEEP Short name: soap-beep ...


... Box, D., Ehnebuske, D., Kakivaya, G., Layman, A., Mendelsohn, N., Nielsen, H., Thatte, S. and D. Winer, "Simple Object Access Protocol (SOAP) 1.1", May 2000, <http://www.w3.org/TR/2000/NOTE-SOAP-20000508 >. ...
... http://www.w3.org/TR/2000/NOTE-SOAP-20000508 ...
... Barton, J., Thatte, S. and H. Nielsen, "SOAP Messages with Attachments", December 2000, <http://www.w3.org/TR/2000/NOTE-SOAP-attachments-20001211 >. ...
... http://www.w3.org/TR/2000/NOTE-SOAP-attachments-20001211 ...


... The IANA has also registered "SOAP over BEEP" as a TCP port number, as specified in Section 7.4. ...
... Finally, the IANA maintains a list of SOAP profile features, c.f., Section 6.1. The IESG is responsible for assigning a designated expert ...
... IANA making the assignment. Prior to contacting the IESG, developers of SOAP profile features must use the mailing list beepwg@lists.beepcore.org to ...



Google
Web
RFC-Ref