1、 Reference number ISO/IEC 29363:2008(E) ISO/IEC 2008INTERNATIONAL STANDARD ISO/IEC 29363 First edition 2008-06-15 Information technology Web Services Interoperability WS-I Simple SOAP Binding Profile Version 1.0 Technologies de linformation Interoprabilit des services du Web Profil de liaison SOAP s
2、imple WS-I, version 1.0 ISO/IEC 29363:2008(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer perf
3、orming the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this P
4、DF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central
5、Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2008 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission
6、 in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2008 All rights reserv
7、edISO/IEC 29363:2008(E) ISO/IEC 2008 All rights reserved iiiContents Foreword . iv 1 Scope and introduction.1 1.1 Scope1 1.2 Relationships to Other Profiles .1 1.3 Notational Conventions.1 1.4 Profile Identification and Versioning2 2 Profile Conformance.3 2.1 Conformance Requirements .3 2.2 Conforma
8、nce Targets .4 2.3 Conformance Scope .4 2.4 Claiming Conformance .5 3 Messaging5 3.1 Message Serialization.5 4 Description .7 4.1 Bindings7 Appendix A: Referenced Specifications9 Appendix B: Extensibility Points .10 Appendix C: Normative References .11 Appendix D: Acknowledgements12 ISO/IEC 29363:20
9、08(E) iv ISO/IEC 2008 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development
10、of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in
11、 liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint
12、 technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attentio
13、n is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 29363 was prepared by the Web Services Interoperability Organization (WS-I) and was adopted,
14、under the PAS procedure, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of ISO and IEC. ISO/IEC 2008 All rights reserved 1INTERNATIONAL STANDARD ISO/IEC 29363:2008(E)Information technology Web Services Interoperability WS-I Simple
15、 SOAP Binding Profile Version 1.0 1 Scope and introduction 1.1 Scope This International Standard defines the WS-I Simple SOAP Binding Profile 1.0 (hereafter, “Profile“), consisting of a set of non-proprietary Web services specifications, along with clarifications to and amplifications of those speci
16、fications which promote interoperability. Section 1 introduces the Profile, and explains its relationships to other profiles. Section 2, “Profile Conformance“, explains what it means to be conformant to the Profile. Each subsequent section addresses a component of the Profile, and consists of two pa
17、rts: an overview detailing the component specifications and their extensibility points, followed by subsections that address individual parts of the component specifications. Note that there is no relationship between the section numbers in this International Standard and those in the referenced spe
18、cifications. 1.2 Relationships to Other Profiles This Profile is derived from those Basic Profile 1.0 requirements related to the serialization of the envelope and its representation in the message, incorporating any errata to date. These requirements have been factored out of the Basic Profile 1.1
19、to enable other Profiles to be composable with it. A combined claim of conformance to both the Basic Profile 1.1 and the Simple SOAP Binding Profile 1.0 is roughly equivalent to a claim of conformance to the Basic Profile 1.0. This Profile composed with the Basic Profile 1.1 supersedes the Basic Pro
20、file 1.0. 1.3 Notational Conventions The keywords “MUST“, “MUST NOT“, “REQUIRED“, “SHALL“, “SHALL NOT“, “SHOULD“, “SHOULD NOT“, “RECOMMENDED“, “MAY“, and “OPTIONAL“ in this document are to be interpreted as described in RFC2119. ISO/IEC 29363:2008(E) 2 ISO/IEC 2008 All rights reservedNormative state
21、ments of requirements in the Profile (i.e., those impacting conformance, as outlined in “Conformance Requirements“) are presented in the following manner: RnnnnStatement text here. where “nnnn“ is replaced by a number that is unique among the requirements in the Profile, thereby forming a unique req
22、uirement identifier. Requirement identifiers can be considered to be namespace qualified, in such a way as to be compatible with QNames from Namespaces in XML. If there is no explicit namespace prefix on a requirements identifier (e.g., “R9999“ as opposed to “bp10:R9999“), it should be interpreted a
23、s being in the namespace identified by the conformance URI of the document section it occurs in. If it is qualified, the prefix should be interpreted according to the namespace mappings in effect, as documented below. Some requirements clarify the referenced specification(s), but do not place additi
24、onal constraints upon implementations. For convenience, clarifications are annotated in the following manner: C Some requirements are derived from ongoing standardization work on the referenced specification(s). For convenience, such forward-derived statements are annotated in the following manner:
25、xxxx, where “xxxx“ is an identifier for the specification (e.g., “WSDL20“ for WSDL Version 2.0). Note that because such work was not complete when this document was publiished, the specification that the requirement is derived from may change; this information is included only as a convenience to im
26、plementers. This specification uses a number of namespace prefixes throughout; their associated URIs are listed below. Note that the choice of any namespace prefix is arbitrary and not semantically significant. wsdl - “http:/schemas.xmlsoap.org/wsdl/“ soapbind - “http:/schemas.xmlsoap.org/wsdl/soap/
27、“ uddi - “urn:uddi-org:api_v2“ 1.4 Profile Identification and Versioning This document is identified by a name (in this case, Simple SOAP Binding Profile) and a version number (here, 1.0). Together, they identify a particular profile instance. Version numbers are composed of a major and minor portio
28、n, in the form “major.minor“. They can be used to determine the precedence of a profile instance; a higher version number (considering both the major and minor components) indicates that an instance is more recent, and therefore supersedes earlier instances. ISO/IEC 29363:2008(E) ISO/IEC 2008 All ri
29、ghts reserved 3Instances of profiles with the same name (e.g., “Example Profile 1.1“ and “Example Profile 5.0“) address interoperability problems in the same general scope (although some developments may require the exact scope of a profile to change between instances). One can also use this informa
30、tion to determine whether two instances of a profile are backwards-compatible; that is, whether one can assume that conformance to an earlier profile instance implies conformance to a later one. Profile instances with the same name and major version number (e.g., “Example Profile 1.0“ and “Example P
31、rofile 1.1“) MAY be considered compatible. Note that this does not imply anything about compatibility in the other direction; that is, one cannot assume that conformance with a later profile instance implies conformance to an earlier one. 2 Profile Conformance Conformance to the Profile is defined b
32、y adherence to the set of requirements defined for a specific target, within the scope of the Profile. This section explains these terms and describes how conformance is defined and used. 2.1 Conformance Requirements Requirements state the criteria for conformance to the Profile. They typically refe
33、r to an existing specification and embody refinements, amplifications, interpretations and clarifications to it in order to improve interoperability. All requirements in the Profile are considered normative, and those in the specifications it references that are in-scope (see “Conformance Scope“) sh
34、ould likewise be considered normative. When requirements in the Profile and its referenced specifications contradict each other, the Profiles requirements take precedence for purposes of Profile conformance. Requirement levels, using RFC2119 language (e.g., MUST, MAY, SHOULD) indicate the nature of
35、the requirement and its impact on conformance. Each requirement is individually identified (e.g., R9999) for convenience. For example; R9999 WIDGETs SHOULD be round in shape. This requirement is identified by “R9999“, applies to the target WIDGET (see below), and places a conditional requirement upo
36、n widgets; i.e., although this requirement must be met to maintain conformance in most cases, there are some situations where there may be valid reasons for it not being met (which are explained in the requirement itself, or in its accompanying text). Each requirement statement contains exactly one
37、requirement level keyword (e.g., “MUST“) and one conformance target keyword (e.g., “MESSAGE“). Additional text may be included to illuminate a requirement or group of requirements (e.g., ISO/IEC 29363:2008(E) 4 ISO/IEC 2008 All rights reservedrationale and examples); however, prose surrounding requi
38、rement statements must not be considered in determining conformance. Definitions of terms in the Profile are considered authoritative for the purposes of determining conformance. None of the requirements in the Profile, regardless of their conformance level, should be interpreted as limiting the abi
39、lity of an otherwise conforming implementation to apply security countermeasures in response to a real or perceived threat (e.g., a denial of service attack). 2.2 Conformance Targets Conformance targets identify what artifacts (e.g., SOAP message, WSDL description, UDDI registry data) or parties (e.
40、g., SOAP processor, end user) requirements apply to. This allows for the definition of conformance in different contexts, to assure unambiguous interpretation of the applicability of requirements, and to allow conformance testing of artifacts (e.g., SOAP messages and WSDL descriptions) and the behav
41、ior of various parties to a Web service (e.g., clients and service instances). Requirements conformance targets are physical artifacts wherever possible, to simplify testing and avoid ambiguity. The following conformance targets are used in the Profile: ENVELOPE - the serialization of the soap:Envel
42、ope element and its content (from ISO/IEC 29361) MESSAGE - protocol elements that transport the ENVELOPE (e.g., SOAP/HTTP messages) (from ISO/IEC 29361) DESCRIPTION - descriptions of types, messages, interfaces and their concrete protocol and data format bindings, and the network access points assoc
43、iated with Web services (e.g., WSDL descriptions) (from ISO/IEC 29361) INSTANCE - software that implements a wsdl:port or a uddi:bindingTemplate (from ISO/IEC 29361) RECEIVER - software that consumes a message according to the protocol(s) associated with it (e.g., SOAP processors) (from ISO/IEC 2936
44、1) 2.3 Conformance Scope The scope of the Profile delineates the technologies that it addresses; in other words, the Profile only attempts to improve interoperability within its own scope. Generally, the Profiles scope is bounded by the specifications referenced by it. ISO/IEC 29363:2008(E) ISO/IEC
45、2008 All rights reserved 5The Profiles scope is further refined by extensibility points. Referenced specifications often provide extension mechanisms and unspecified or open-ended configuration parameters; when identified in the Profile as an extensibility point, such a mechanism or parameter is out
46、side the scope of the Profile, and its use or non-use is not relevant to conformance. Note that the Profile may still place requirements on the use of an extensibility point. Also, specific uses of extensibility points may be further restricted by other profiles, to improve interoperability when use
47、d in conjunction with the Profile. Because the use of extensibility points may impair interoperability, their use should be negotiated or documented in some fashion by the parties to a Web service; for example, this could take the form of an out-of-band agreement. The Profiles scope is defined by th
48、e referenced specifications in Appendix A, as refined by the extensibility points in .Appendix B 2.4 Claiming Conformance Claims of conformance to the Profile can be made using the following mechanisms, as described in Conformance Claim Attachment Mechanisms, when the applicable Profile requirements
49、 associated with the listed targets have been met: WSDL 1.1 Claim Attachment Mechanism for Web Services Instances - MESSAGE DESCRIPTION INSTANCE RECEIVER WSDL 1.1 Claim Attachment Mechanism for Description Constructs - DESCRIPTION UDDI Claim Attachment Mechanism for Web Services Instances - MESSAGE DESCRIPTION INSTANCE RECEIVER The conformance claim URI for this Profile is “http:/wsi.org/Profiles/SimpleSoapBinding/1.0“. 3 Messaging This section of the Profile incorporates the following specifications by ref
