{
  "id": "soap-004096-73aafe99b9ac7c2e",
  "slug": "soap",
  "title": "soap",
  "qid": "Q34396",
  "lead": ", a typical ingredient found in bar soaps action of soap on oil Soap is a salt of a fatty acid (sometimes other carboxylic acids) used for cleaning and lubricating products as well as other applications. In a domestic setting, soaps, specifically \"toilet soaps\", are surfactants typically used for washing, bathing, and other types of housekeeping. In industrial settings, soaps are used as thickeners, components of some lubricants, emulsifiers, and catalysts. Soaps are often produced by mixing fats and oils with a base. Humans have used soap for millennia, and evidence exists for the production of soap-like materials in ancient Babylon around 2800 BC.",
  "body": "SOAP (originally an acronym for Simple Object Access Protocol) is a messaging protocol specification for exchanging structured information in the implementation of web services in computer networks. It uses XML Information Set for its message format, and relies on application layer protocols, most often Hypertext Transfer Protocol (HTTP), although some legacy systems communicate over Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission. ==Characteristics== SOAP provides the Messaging Protocol layer of a web services protocol stack for web services. It is an XML-based protocol consisting of three parts: an envelope, which defines the message structure and how to process it a set of encoding rules for expressing instances of application-defined datatypes a convention for representing procedure calls and responses SOAP has three major characteristics: extensibility (security and WS-Addressing are among the extensions under development) neutrality (SOAP can operate over any protocol such as HTTP, SMTP, TCP, UDP) independence (SOAP allows for any programming model) As an example of what SOAP procedures can do, an application can send a SOAP request to a server that has web services enabled—such as a real-estate price database—with the parameters for a search. The server then returns a SOAP response (an XML-formatted document) with the resulting data, e.g., prices, location, features. Since the generated data comes in a standardized machine-parsable format, the requesting application can then integrate it directly. The SOAP architecture consists of several layers of specifications for: message format Message Exchange Patterns (MEP) underlying transport protocol bindings message processing models protocol extensibility SOAP evolved as a successor of XML-RPC, though it borrows its transport and interaction neutrality from Web Service Addressing and the envelope/header/body from elsewhere (probably from WDDX). ==History== SOAP was designed as an object-access protocol and released as XML-RPC in June 1998 as part of Frontier 5.1 by Dave Winer, Don Box, Bob Atkinson, and Mohsen Al-Ghosein for Microsoft, where Atkinson and Al-Ghosein were working. The specification was not made available until it was submitted to IETF 13 September 1999. According to Don Box, this was due to politics within Microsoft. Because of Microsoft's hesitation, Dave Winer shipped XML-RPC in 1998. The submitted Internet Draft did not reach RFC status and is therefore not considered a \"web standard\" as such. Version 1.1 of the specification was published as a W3C Note on 8 May 2000. Since version 1.1 did not reach W3C Recommendation status, it can not be considered a \"web standard\" either. Version 1.2 of the specification, however, became a W3C recommendation on June 24, 2003. SOAP originally stood for \"Simple Object Access Protocol\" but version 1.2 of the standard dropped this acronym. The SOAP specification was maintained by the XML Protocol Working Group of the World Wide Web Consortium until the group was closed 10 July 2009. After SOAP was first introduced, it became the underlying layer of a more complex set of web services, based on WSDL, XSD and UDDI. These different services, especially UDDI, have proved to be of far less interest, but an appreciation of them gives a complete understanding of the expected role of SOAP compared to how web services have actually evolved. ==Specification== The SOAP specification defines the messaging framework, which consists of: The SOAP processing model, defining the rules for processing a SOAP message The SOAP extensibility model defining the concepts of SOAP features and SOAP modules The SOAP underlying protocol binding framework describing the rules for defining a binding to an underlying protocol that can be used for exchanging SOAP messages between SOAP nodes The SOAP message construct defining the structure of a SOAP message ==SOAP building blocks== A SOAP message is an ordinary XML document containing the following elements: ==Transport methods== Both SMTP and HTTP are valid application layer protocols used as transport for SOAP, but HTTP has gained wider acceptance as it works well with today's internet infrastructure; specifically, HTTP works well with network firewalls. SOAP may also be used over HTTPS (which is the same protocol as HTTP at the application level, but uses an encrypted transport protocol underneath) with either simple or mutual authentication; this is the advocated WS-I method to provide web service security as stated in the WS-I Basic Profile 1.1. This is a major advantage over other distributed protocols like GIOP/IIOP or DCOM, which are normally filtered by firewalls. SOAP over AMQP is yet another possibility that some implementations support. SOAP also has an advantage over DCOM that it is unaffected by security rights configured on the machines that require knowledge of both transmitting and receiving nodes. This lets SOAP be loosely coupled in a way that is not possible with DCOM. There is also the SOAP-over-UDP OASIS standard. POST /InStock HTTP/1.1 Host: www.example.org Content-Type: application/soap+xml; charset=utf-8 Content-Length: 299 SOAPAction: \"http://www.w3.org/2003/05/soap-envelope\" T ===Disadvantages=== When using standard implementation and the default SOAP/HTTP binding, the XML infoset is serialized as XML. To improve performance for the special case of XML with embedded binary objects, the Message Transmission Optimization Mechanism was introduced. When relying on HTTP as a transport protocol and not using Web Services Addressing or an Enterprise Service Bus, the roles of the interacting parties are fixed. Only one party (the client) can use the services of the other. SOAP is less \"simple\" than the name would suggest. The verbosity of the protocol, low parsing speed of XML, and lack of a standardized interaction model led to the dominance of services using the HTTP protocol more directly. See, for example, REST. Being protocol-agnostic, SOAP is unable to take advantage of protocol-specific features and optimizations such as REST's Uniform Interface or caching – instead having to reimplement them (as with WS-Addressing). ==See also== SOAP with Attachments SOAP with Attachments API for Java SOAP-over-UDP List of web service protocols Message Transmission Optimization Mechanism (MTOM) XML-binary Optimized Packaging (XOP) Extensible User Interface Protocol (XUP) a SOAP-based UI protocol WebSocket Web Services Security WS-Security based products and services ==Further reading==",
  "categories": [
    "10639794",
    "106902159",
    "107141658",
    "20354702",
    "22175909",
    "22900965",
    "22904412",
    "23118434",
    "23603337",
    "23758858",
    "23890325",
    "24549072",
    "24623845",
    "24745122",
    "27206937",
    "29815558",
    "29815561",
    "37717757",
    "37717758",
    "44852951",
    "47548643",
    "48128016",
    "49505187",
    "60213782",
    "68384674"
  ],
  "license": "CC BY-SA 4.0",
  "source_uri": "https://en.wikipedia.org/w/index.php?oldid=1376458225",
  "content_hash": "73aafe99b9ac7c2edef95d516b5beefa4a0c0026bbd917a64cd13416d67d930e",
  "created_at": 1792308366.2863991,
  "updated_at": 1790225602.0,
  "claims": [
    {
      "id": 31541608,
      "subject_qid": "",
      "subject_slug": "soap",
      "predicate": "publication date",
      "object_text": "2000-05-08",
      "object_num": 20000508.0,
      "object_unit": null,
      "polarity": 1,
      "qualifier": "",
      "source_uri": "https://en.wikipedia.org/w/index.php?oldid=1368816634",
      "source_name": "Wikipedia",
      "source_tier": 3,
      "retrieved_at": 1792507234.371869,
      "confidence": 0.95,
      "article_slug": "soap",
      "span_start": 37,
      "span_end": 75
    },
    {
      "id": 31541607,
      "subject_qid": "",
      "subject_slug": "soap",
      "predicate": "release date",
      "object_text": "1998",
      "object_num": 19980000.0,
      "object_unit": null,
      "polarity": 1,
      "qualifier": "",
      "source_uri": "https://en.wikipedia.org/w/index.php?oldid=1368816634",
      "source_name": "Wikipedia",
      "source_tier": 3,
      "retrieved_at": 1792507234.3718684,
      "confidence": 0.95,
      "article_slug": "soap",
      "span_start": 63,
      "span_end": 111
    }
  ],
  "contradictions": [],
  "confidence": 0.95,
  "csl": {
    "id": "soap-004096-73aafe99b9ac7c2e",
    "type": "webpage",
    "title": "soap",
    "author": [
      {
        "family": "Anticloud FZ LLE",
        "literal": "Anticloud FZ LLE"
      }
    ],
    "container-title": "encyclopegia.org",
    "publisher": "Anticloud FZ LLE",
    "publisher-place": "Dubai, United Arab Emirates",
    "URL": "https://encyclopegia.org/a/soap",
    "issued": {
      "date-parts": [
        [
          2026,
          10,
          18
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          11,
          21
        ]
      ]
    },
    "license": "CC BY-SA 4.0",
    "DOI": "eo1:soap-004096-73aafe99b9ac7c2e",
    "isBasedOn": "https://en.wikipedia.org/w/index.php?oldid=1376458225",
    "note": "Immutable snapshot soap-004096-73aafe99b9ac7c2e, content root 73aafe99b9ac7c2e…"
  }
}