ISO/IEC 29363:2008
(Main)Information technology — Web Services Interoperability — WS-I Simple SOAP Binding Profile Version 1.0
Information technology — Web Services Interoperability — WS-I Simple SOAP Binding Profile Version 1.0
ISO/IEC 29363:2008 defines the WS-I Simple SOAP Binding Profile 1.0, consisting of a set of non-proprietary Web services specifications, along with clarifications and amendments to those specifications which promote interoperability.
Technologies de l'information — Interopérabilité des services du Web — Profil de liaison SOAP simple WS-I, version 1.0
Informacijska tehnologija - Osnovni povezovalni profil SOAP, različica 1.0
General Information
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 29363
First edition
2008-06-15
Corrected version
2008-10-01
Information technology — Web Services
Interoperability — WS-I Simple SOAP
Binding Profile Version 1.0
Technologies de l'information — Interopérabilité des services
du Web — Profil de liaison SOAP simple WS-I, version 1.0
Reference number
©
ISO/IEC 2008
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's 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 performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's 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 PDF 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 Secretariat at the address given below.
© 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 in writing from either ISO at the address below or
ISO's 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2008 – All rights reserved
Contents
Foreword . iv
1 Scope and introduction.1
1.1 Scope.1
1.2 Relationships to Other Profiles .1
1.3 Notational Conventions.1
1.4 Profile Identification and Versioning.2
2 Profile Conformance.3
2.1 Conformance Requirements .3
2.2 Conformance Targets .4
2.3 Conformance Scope .4
2.4 Claiming Conformance .5
3 Messaging.5
3.1 Message Serialization.5
4 Description .7
4.1 Bindings.7
Appendix A: Referenced Specifications.9
Appendix B: Extensibility Points .10
Appendix C: Normative References .11
Appendix D: Acknowledgements.12
© ISO/IEC 2008 – All rights reserved iii
Foreword
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 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 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 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.
Attention 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, 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.
In this corrected version of ISO/IEC 29363:2008, the full stop in the last paragraph of 2.3 has been
moved from before “Appendix B” to the end of the sentence.
iv © ISO/IEC 2008 – All rights reserved
INTERNATIONAL STANDARD ISO/IEC 29363:2008(E)
Information technology — Web Services
Interoperability — WS-I Simple 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 specifications
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 parts: 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 specifications.
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 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 Profile 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 2008 – All rights reserved 1
Normative statements 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 requirement 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 requirement's identifier (e.g., "R9999" as opposed
to "bp10:R9999"), it should be interpreted as 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
additional 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: 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 implementers.
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/"
• 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 portion, 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.
2 © ISO/IEC 2008 – All rights reserved
Instances 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 information 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 Profile 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 by 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 refer
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") should likewise be considered
normative. When requirements in the Profile and its referenced specifications
contradict each other, the Profile's requirements take precedence for purposes of
Profile conformance.
Requirement levels, using RFC2119 language (e.g., MUST, MAY, SHOULD)
indicate the nature of 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 upon 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 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 2008 – All rights reserved 3
rationale and examples); however, prose surrounding requirement 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 ability 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.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 behavior 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:Envelope 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 - d
...
INTERNATIONAL ISO/IEC
STANDARD 29363
First edition
2008-06-15
Corrected version
2008-10-01
Information technology — Web Services
Interoperability — WS-I Simple SOAP
Binding Profile Version 1.0
Technologies de l'information — Interopérabilité des services
du Web — Profil de liaison SOAP simple WS-I, version 1.0
Reference number
©
ISO/IEC 2008
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's 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 performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's 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 PDF 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 Secretariat at the address given below.
© 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 in writing from either ISO at the address below or
ISO's 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2008 – All rights reserved
Contents
Foreword . iv
1 Scope and introduction.1
1.1 Scope.1
1.2 Relationships to Other Profiles .1
1.3 Notational Conventions.1
1.4 Profile Identification and Versioning.2
2 Profile Conformance.3
2.1 Conformance Requirements .3
2.2 Conformance Targets .4
2.3 Conformance Scope .4
2.4 Claiming Conformance .5
3 Messaging.5
3.1 Message Serialization.5
4 Description .7
4.1 Bindings.7
Appendix A: Referenced Specifications.9
Appendix B: Extensibility Points .10
Appendix C: Normative References .11
Appendix D: Acknowledgements.12
© ISO/IEC 2008 – All rights reserved iii
Foreword
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 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 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 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.
Attention 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, 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.
In this corrected version of ISO/IEC 29363:2008, the full stop in the last paragraph of 2.3 has been
moved from before “Appendix B” to the end of the sentence.
iv © ISO/IEC 2008 – All rights reserved
INTERNATIONAL STANDARD ISO/IEC 29363:2008(E)
Information technology — Web Services
Interoperability — WS-I Simple 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 specifications
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 parts: 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 specifications.
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 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 Profile 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 2008 – All rights reserved 1
Normative statements 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 requirement 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 requirement's identifier (e.g., "R9999" as opposed
to "bp10:R9999"), it should be interpreted as 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
additional 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: 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 implementers.
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/"
• 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 portion, 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.
2 © ISO/IEC 2008 – All rights reserved
Instances 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 information 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 Profile 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 by 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 refer
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") should likewise be considered
normative. When requirements in the Profile and its referenced specifications
contradict each other, the Profile's requirements take precedence for purposes of
Profile conformance.
Requirement levels, using RFC2119 language (e.g., MUST, MAY, SHOULD)
indicate the nature of 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 upon 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 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 2008 – All rights reserved 3
rationale and examples); however, prose surrounding requirement 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 ability 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.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 behavior 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:Envelope 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 - d
...
SLOVENSKI STANDARD
01-julij-2007
,QIRUPDFLMVNDWHKQRORJLMD±2VQRYQLSRYH]RYDOQLSURILO62$3UD]OLþLFD
Information technology — Simple SOAP Binding Profile Version 1.0
Technologies de l'information — Version 1.0 de profil de liaison SOAP simple
Ta slovenski standard je istoveten z:
ICS:
35.100.05 9HþVORMQHXSRUDEQLãNH Multilayer applications
UHãLWYH
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
DRAFT INTERNATIONAL STANDARD ISO/IEC 29363
Attributed to ISO/IEC JTC 1 by the Central Secretariat (see page iii)
Voting begins on Voting terminates on
2006-12-18 2007-06-18
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОММИСИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE
PUBLICLY AVAILABLE SPECIFICATION PROCEDURE
Information technology — Simple SOAP Binding Profile
Version 1.0
Technologies de l'information — Version 1.0 de profil de liaison SOAP simple
ICS 35.100.05
In accordance with the provisions of Council Resolution 21/1986 this DIS is circulated in the
English language only.
Conformément aux dispositions de la Résolution du Conseil 21/1986, ce DIS est distribué en
version anglaise seulement.
This Publicly Available Specification (PAS) is being submitted for Fast-track processing in
accordance with the provisions of ISO/IEC JTC 1 Directives.
THIS DOCUMENT IS A DRAFT CIRCULATED FOR COMMENT AND APPROVAL. IT IS THEREFORE SUBJECT TO CHANGE AND MAY NOT BE
REFERRED TO AS AN INTERNATIONAL STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS BEING ACCEPTABLE FOR INDUSTRIAL, TECHNOLOGICAL, COMMERCIAL AND USER PURPOSES,
DRAFT INTERNATIONAL STANDARDS MAY ON OCCASION HAVE TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL TO BECOME
STANDARDS TO WHICH REFERENCE MAY BE MADE IN NATIONAL REGULATIONS.
International Organization for Standardization, 2006
©
International Electrotechnical Commission, 2006
ISO/IEC DIS 29363
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's 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 performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's 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 PDF 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 Secretariat at the address given below.
Copyright notice
This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted
under the applicable laws of the user's country, neither this ISO draft nor any extract from it may be
reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic,
photocopying, recording or otherwise, without prior written permission being secured.
Requests for permission to reproduce should be addressed to either ISO at the address below or ISO's
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 copyright@iso.org
Web www.iso.org
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
ii © ISO/IEC 2006 — All rights reserved
ISO/IEC DIS 29363
NOTE FROM ITTF
This draft International Standard is submitted for JTC 1 national body vote under the Fast-Track Procedure.
In accordance with Resolution 30 of the JTC 1 Berlin Plenary 1993, the proposer of this document recommends
assignment of ISO/IEC 29363 to JTC 1.
See also explanatory report.
“FAST-TRACK” PROCEDURE
1 Any P-member and any Category A liaison organization of ISO/IEC JTC 1 may propose that an existing
standard from any source be submitted directly for vote as a DIS. The criteria for proposing an existing
standard for the fast-track procedure are a matter for each proposer to decide.
2 The proposal shall be received by the ITTF which will take the following actions.
2.1 To settle the copyright and/or trade mark situation with the proposer, so that the proposed text can be
freely copied and distributed within JTC 1 without restriction.
2.2 To assess in consultation with the JTC 1 secretariat which SC is competent for the subject covered by
the proposed standard and to ascertain that there is no evident contradiction with other International
Standards.
2.3 To distribute the text of the proposed standard as a DIS. In case of particularly bulky documents the ITTF
may demand the necessary number of copies from the proposer.
3 The period for combined DIS voting shall be six months. In order to be accepted the DIS must be
supported by 75 % of the votes cast (abstention is not counted as a vote) and by two-thirds of the P-members
voting of JTC 1.
4 At the end of the voting period, the comments received, whether editorial only or technical, will be dealt
with by a working group appointed by the secretariat of the relevant SC.
5 If, after the deliberations of this WG, the requirements of 3 above are met, the amended text shall be sent
to the ITTF by the secretariat of the relevant SC for publication as an International Standard.
If it is impossible to agree to a text meeting the above requirements, the proposal has failed and the procedure
is terminated.
In either case the WG shall prepare a full report which will be circulated by the ITTF.
6 If the proposed standard is accepted and published, its maintenance will be handled by JTC 1.
© ISO/IEC 2006 — All rights reserved iii
Simple SOAP Binding Profile - Version 1.0 (Final) http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0-2004-08-24.
Simple SOAP Binding Profile Version 1.0
Final Material
2004-08-24
This version:
http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0-2004-08-24.html
Latest version:
http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0.html
Errata for this Version:
http://www.ws-i.org/Profiles/Basic/2003-08/SimpleSoapBindingProfile-1.0-errata.html
Editors:
Mark Nottingham, BEA Systems
Administrative contact:
secretary@ws-i.org
Certain of its Members. All Rights Reserved.
Abstract
This document defines the WS-I Simple SOAP Binding Profile 1.0, consisting of a set of
non-proprietary Web services specifications, along with clarifications and amendments to
those specifications which promote interoperability.
Status of this Document
This is a final specification. Please refer to the errata, which may include normative
corrections to it.
Notice
The material contained herein is not a license, either expressly or impliedly, to any
intellectual property owned or controlled by any of the authors or developers of this material
or WS-I. The material contained herein is provided on an "AS IS" basis and to the maximum
extent permitted by applicable law, this material is provided AS IS AND WITH ALL FAULTS,
1 of 11 7/10/2006 10:24 PM
Simple SOAP Binding Profile - Version 1.0 (Final) http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0-2004-08-24.
and the authors and developers of this material and WS-I hereby disclaim all other
warranties and conditions, either express, implied or statutory, including, but not limited to,
any (if any) implied warranties, duties or conditions of merchantability, of fitness for a
particular purpose, of accuracy or completeness of responses, of results, of workmanlike
effort, of lack of viruses, and of lack of negligence. ALSO, THERE IS NO WARRANTY OR
CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION,
CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO
THIS MATERIAL.
IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR WS-I BE
LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE
GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY
INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES
WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN
ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS MATERIAL,
WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF
SUCH DAMAGES.
Feedback
If there are areas in this specification that could be clearer, or if errors or omissions are
identified, WS-I would like to be notified in order to provide the best possible interoperability
guidance.
By sending email, or otherwise communicating with WS-I, you (on behalf of yourself if you
are an individual, and your company if you are providing Feedback on behalf of the
company) will be deemed to have granted to WS-I, the members of WS-I, and other parties
that have access to your Feedback, a non-exclusive, non-transferable, worldwide, perpetual,
irrevocable, royalty-free license to use, disclose, copy, license, modify, sublicense or
otherwise distribute and exploit in any manner whatsoever the Feedback you provide
regarding the work. You acknowledge that you have no expectation of confidentiality with
respect to any Feedback you provide. You represent and warrant that you have rights to
provide this Feedback, and if you are providing Feedback on behalf of a company, you
represent and warrant that you have the rights to provide Feedback on behalf of your
company. You also acknowledge that WS-I is not required to review, discuss, use, consider
or in any way incorporate your Feedback into future versions of its work. If WS-I does
incorporate some or all of your Feedback in a future version of the work, it may, but is not
obligated to include your name (or, if you are identified as acting on behalf of your company,
the name of your company) on a list of contributors to the work. If the foregoing is not
acceptable to you and any company on whose behalf you are acting, please do not provide
any Feedback.
Feedback on this document should be directed to wsbasic_comment@ws-i.org.
Table of Contents
1. Introduction
1.1. Relationships to Other Profiles
1.2. Notational Conventions
1.3. Profile Identification and Versioning
2 of 11 7/10/2006 10:24 PM
Simple SOAP Binding Profile - Version 1.0 (Final) http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0-2004-08-24.
2. Profile Conformance
2.1. Conformance Requirements
2.2. Conformance Targets
2.3. Conformance Scope
2.4. Claiming Conformance
3. Messaging
3.1. Message Serialization
3.1.1. XML Envelope Serialization
3.1.2. XML Namespace declarations
3.1.3. Unicode BOMs
3.1.4. XML Declarations
3.1.5. Character Encodings
4. Description
4.1. Bindings
4.1.1. SOAP Binding Extensions
4.1.2. Unbound portType Element Contents
Appendix A: Referenced Specifications
Appendix B: Extensibility Points
Appendix C: Acknowledgements
1. Introduction
This document 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 specifications 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 parts;
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 document and those in the referenced
specifications.
1.1 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 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 supercedes the Basic Profile 1.0.
1.2 Notational Conventions
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
3 of 11 7/10/2006 10:24 PM
Simple SOAP Binding Profile - Version 1.0 (Final) http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0-2004-08-24.
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in RFC2119.
Normative statements of requirements in the Profile (i.e., those impacting conformance, as
outlined in "Conformance Requirements") are presented in the following manner:
Rnnnn Statement text here.
where "nnnn" is replaced by a number that is unique among the requirements in the Profile,
thereby forming a unique requirement 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 requirement's identifier (e.g., "R9999" as opposed to "bp10:R9999"), it should be
interpreted as 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 additional
constraints upon implementations. For convenience, clarifications are annotated in the
C
following manner:
Some requirements are derived from ongoing standardization work on the referenced
specification(s). For convenience, such forward-derived statements are annotated in the
xxxx
following manner: , 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 specif
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.