 |
|
Home | SOAP Tools | UDDI Browser | Resources | Source Code | RFCs | News Reader | SOAP Interop | Bookmarks |
|
|
|
Home | SOAP Tools | UDDI Browser | Resources | Source Code | RFCs | News Reader | SOAP Interop | Bookmarks |
|
| SOAP Related RFCs and Standards | |
|---|---|
| This document defines a notation for specifying business process behavior based on Web Services. This notation is called Business Process Execution Language for Web Services (abbreviated to BPEL4WS in the rest of this document). Processes in BPEL4WS export and import functionality by using Web Service interfaces exclusively. This document is a merge of WSFL and XLANG. | |
| This specification (WS-Coordination) describes an extensible framework for providing protocols that coordinate the actions of distributed applications. | |
| This specification describes coordination types that are used with the extensible coordination framework described in the WS-Coordination specification. | |
| WSDL 1.2 is an XML-based language that describes a Web Service - the data exchanged, the protocol to use, and its location on the Web. | |
| For a variety of reasons, it is desirable that some web services, compliant with the SOAP HTTP Binding, can also be accessed via HTTP GET. This requirement mandates that the information necessary to access the resource can be expressed in an HTTUP URI. | |
| This specification defines a new XML Signature transform to facilitate the development of efficient document subsetting technologies that interoperate under similar performance profiles. | |
| WSCL allows the abstract interfaces of Web services, i.e. the business level conversations or public processes supported by a Web service, to be defined. WSCL specifies the XML documents being exchanged, and the allowed sequencing of these document exchanges. | |
| Pipeline is an XML vocabulary for describing the processing relationships between XML resources. A pipeline document specifies the inputs and outputs to XML processes and a pipeline controller uses this document to figure out the chain of processing that must be executed in order to get a particular result. | |
| Existing XML canonicalization algorithms such as Canonical XML and Exclusive XML Canonicalization suffer from several limitations and design artifacts (enumerated herein) which significantly limit their utility in many XML applications, particularly those which validate and process XML data according to the rules of and flexibilities afforded by XML Schema. The Schema Centric Canonicalization algorithm addresses these concerns. (Editor: Be aware the copyright notice at beginning of the document. ) | |
| Web Services for Remote Portals (WSRP) are visual, user-facing web services centric components that plug-n-play with portals or other intermediary web applications that aggregate content or applications from different sources. They are designed to enable businesses to provide content or applications in a form that does not require any manual content- or application-specific adaptation by consuming intermediary applications. | |
| SMTP Binding for SOAP | This document details transporting SOAP messages over the Simple Mail Transport Protocol (SMTP). |
| SOAP Security Extensions: Digital Signature (SOAP-DSIG, See example) | This document specifies the syntax and processing rules of a SOAP header entry to carry digital signature information within a SOAP 1.1 Envelope. |
| WS-Security | WS-Security provides a security language for Web services. WS-Security describes enhancements to SOAP messaging providing three capabilities: credential exchange, message integrity, and message confidentiality. |
| Web Service Inspection Language | The WS-Inspection specification provides an XML format for assisting in the inspection of a site for available services and a set of rules for how inspection related information should be made available for consumption. |
| SOAP Authentication | This memo defines SOAP Extensions which implement a basic access authentication mechanism and a digest access authentication mechanism for use in request/response message exchange patterns. These mechanisms are adaptations of the corresponding mechanisms defined in RFC 2617. |
| Web Services Experience Language | WSXL (Web Services Experience Language) is a Web services centric component model for interactive Web applications. WSXL is designed to achieve two main goals: enable businesses to distribute Web applications through multiple revenue channels, and enable new services or applications to be created by leveraging existing applications across the Web. |
| SOAP 1.2 Specification (12/19/2002) | Part 0 Primer
is a non-normative document intended to provide an easily understandable
tutorial on the features of the SOAP Version 1.2 specifications. Part 1 (Messaging
Framework) describes the SOAP envelope and SOAP transport binding
framework; Part 2 ( Adjuncts)
describes adjuncts to the envelope and binding framework. There are some
nasty legal issues associated with the spec. see IPR. Changes from SOAP 1.1 to SOAP 1.2 are summarized here. |
| SOAP 1.1 Specification | The W3C has acknowledged receipt of a submission request including the Simple Object Access Protocol (SOAP) 1.1. The submission includes the text of the SOAP 1.1 specification |
| SOAP Security Extensions | This document specifies the syntax and processing rules of a SOAP header entry to carry digital signature information within a SOAP 1.1 Envelope. |
| SOAP Routing Protocol | SOAP Routing Protocol (SOAP-RP) is a SOAP-based, stateless protocol for exchanging one-way SOAP messages from an initial sender to the ultimate receiver, potentially via a set of intermediaries. |
| SOAP Envelope Schema | Define the structure and elements of SOAP Envelope. |
| CORBA/SOAP Intenetworking RFP | Link to other SOAP related information. |
| UDDI Initiative | Internet-based Universal Description, Discovery, and Integration (UDDI) specification. |
| BizTalk 2.0 Specification | Microsoft BizTalk Framework 2.0 Draft: Document and Message Specification. |
| SOAP Messages With Attachments | Specification for attaching documents to SOAP messages. |
| Web Service Definition Language | WSDL 1.1 by Ariba, IBM and Microsoft (released 03/15/2001). |
| SOAP RPC | On the use of HTTP as a Substrate for Other Protocols. |
| Secure SOAP | SecureSoap Design Note. |
| XML-RPC | A similar protocol to SOAP. |
| XML Schema | W3C XML Schema related information. |
| XML Schema Part 0 (Primer) | W3C Proposed Recommendation (3/16/2001). |
| XML Schema Part 1 (Structures) | XML Schema: Structures specifies the XML Schema definition language, which offers facilities for describing the structure and constraining the contents of XML 1.0 documents, including those which exploit the XML Namespace facility. |
| XPath | XML Path Language. |
| XSLT | This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents. |
| Namespaces | XML namespaces. |
| XMLP/SOAP 1.1 | Editor's Copy of XMLP/SOAP Specification. |
| XHTML | This specification defines XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. |
| SOAP-RP | SOAP Routing Protocol |
| DIME DIME (revised 07/17/2002) |
Direct Internet Message Encapsulation (DIME) is a lightweight, binary encapsulation format that can be used to encapsulate multiple application defined entities or payloads of arbitrary type and size into a single message construct. There is also a document about how to encapsulate SOAP in DIME. Changes in the 07/17/2002 version is available here. |
| WSDL
Extension for SOAP in DIME
|
The WSDL Extension for SOAP in DIME specification defines XML elements and attributes for use in Web Service Description Language (WSDL) documents to describe the encapsulation of a Simple Object Access Protocol (SOAP) message with base64Binary and/or hexBinary content in a Direct Internet Message Exchange (DIME) message. |
| XLANG | XLANG is the XML business process language used in BizTalk Server. |
| XML
Signature (XML-DSIG, See example) |
This document specifies XML digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere. |
| XML
Encryption (See example) |
This document specifies a process for encrypting data and representing the result in XML. The data may be arbitrary data (including an XML document), an XML element, or XML element content. The result of encrypting data is an XML Encryption element which contains or references the cipher data. |
| Decryption Transform for XML Signature | This document specifies an XML Signature "decryption transform" that enables XML Signature applications to distinguish between those XML Encryption structures that were encrypted before signing (and must not be decrypted) and those that were encrypted after signing (and must be decrypted) for the signature to validate. |
| XML Key Management (XKMS 2.0) | This document specifies protocols for distributing and registering public keys, suitable for use in conjunction with the proposed standard for XML Signature developed by the World Wide Web Consortium (W3C) and the Internet Engineering Task Force (IETF) and an anticipated companion standard for XML encryption |
| Canonical
XML (See example) |
This specification describes a method for generating a physical representation, the canonical form, of an XML document that accounts for the permissible changes. Except for limitations regarding a few unusual cases, if two documents have the same canonical form, then the two documents are logically equivalent within the given application context. |
| Schemas | |
|---|---|
| WSDL Schema | WSDL-http Schema |
| WSDL-mime Schema | WSDL-soap Schema |
| SOAP RPC encoding | SOAP Envelope |
| Copyright © 1997-2011 SQLData System, Inc All rights reserved. |
|
Comments, or suggestions? Send to info2 at sqldata.com |
| This site is powered by SQLData SOAP Server |