ISO/IEC 29362:2008

INTERNATIONAL ISO/IEC
STANDARD 29362
First edition
2008-06-15
Corrected version
2008-10-01
Information technology — Web Services
Interoperability — WS-I Attachments
Profile Version 1.0
Technologies de l'information — Interopérabilité des services
du Web — Profil des fichiers joints 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 . v
1 Scope and introduction.1
1.1 Scope.1
1.2 Relationship to other Profiles .1
1.3 Notational Conventions.1
1.4 Profile Identification and Versioning.3
2 Profile Conformance.3
2.1 Conformance Requirements .3
2.2 Conformance Targets .4
2.3 Conformance Scope .5
2.4 Claiming Conformance .5
3 Attachments Packaging.6
3.1 Root Part .6
3.2 Encoding of Root Part .7
3.3 Media Type of Message .7
3.4 Messages with No Attachments .7
3.5 Dereferencing Attachments.9
3.6 Carrying Additional SOAP Envelopes .9
3.7 Fault Messages with Attachments.9
3.8 Value-space of Content-Id Header.9
3.9 Ordering of MIME Parts.10
3.10 Position of Root Part .11
3.11 Content-Transfer-Encoding .11
© ISO/IEC 2008 – All rights reserved iii

3.12 MIME Boundary String. 12
4 Attachments Description. 12
4.1 Use of MIME Binding Extension . 12
4.2 Unbound portType Element Contents. 13
4.3 Referencing Message Parts. 13
4.4 Referencing Attachments from the SOAP Envelope. 14
4.5 Specifying Root Part . 18
4.6 Specifying SOAP Headers in Root Part. 19
4.7 MIME Binding Schema Fixes. 20
4.8 Specifying Alternate Media Types . 20
4.9 WSDL Parts. 21
4.10 Ordering of Parts . 21
4.11 Sending Fault Messages . 22
4.12 Describing Faults. 22
4.13 Sending Additional Parts Not Described in WSDL. 22
4.14 Conformance of SOAP Messages. 22
4.15 Example Attachment Description Using mime:conent . 22
4.16 Example Attachment Description Using swaRef. 25
Appendix A: Referenced Specifications. 27
Appendix B: Extensibility Points. 28
Appendix C: Normative References. 29
Appendix D: Defined Terms. 30
Appendix E: Acknowledgements . 31

iv © ISO/IEC 2008 – All rights reserved

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 29362 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.
This corrected version of ISO/IEC 29362:2008 includes characters which were missing from the
sample code in 3.1, 3.4 and 4.4 of the original version.

© ISO/IEC 2008 – All rights reserved v

INTERNATIONAL STANDARD ISO/IEC 29362:2008(E)

Information technology — Web Services
Interoperability — WS-I Attachments Profile
Version 1.0
1 Scope and introduction
1.1 Scope
This International Standard defines the WS-I Attachments Profile 1.0 (hereafter,
"Profile"), consisting of a set of non-proprietary Web services specifications, along
with clarifications to and amplifications of those specifications that are intended to
promote interoperability. This profile complements the WS-I Basic Profile 1.1 to
add support for conveying interoperable SOAP Messages with Attachments-based
attachments with SOAP messages.
SOAP Messages with Attachments (SwA) defines a MIME multipart/related
structure for packaging attachments with SOAP messages. This profile
complements the WS-I Basic Profile 1.1 to add support for conveying interoperable
SwA-based attachments with SOAP messages.
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.
1.2 Relationship to other Profiles
This Profile adds support for SOAP with Attachments and MIME bindings, and is
intended to be used in combination with the Basic Profile 1.1.
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 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:
© ISO/IEC 2008 – All rights reserved 1

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 published, the specification that
the requirement is derived from may change; this information is included only as a
convenience to implementers.
Extensibility points in underlying specifications (see "Conformance Scope") are
presented in a similar manner:
EnnnnExtensibility Point Name - Description
where "nnnn" is replaced by a number that is unique among the extensibility points
in the Profile. As with requirement statements, extensibility statements can be
considered namespace-qualified.
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.
• soap - "http://schemas.xmlsoap.org/soap/envelope/"
• xsi - "http://www.w3.org/2001/XMLSchema-instance"
• xsd - "http://www.w3.org/2001/XMLSchema"
• soapenc - "http://schemas.xmlsoap.org/soap/encoding/"
• wsdl - "http://schemas.xmlsoap.org/wsdl/"
• soapbind - "http://schemas.xmlsoap.org/wsdl/soap/"
• mime - "http://schemas.xmlsoap.org/wsdl/mime/"
• uddi - "urn:uddi-org:api_v2"
• wsi - "http://www.ws-i.org/schemas/conformanceClaim"
• ref - "http://ws-i.org/profiles/basic/1.1/xsd"
2 © ISO/IEC 2008 – All rights reserved

1.4 Profile Identification and Versioning
This document is identified by a name (in this case, Attachments 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.
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 i
...