1、 Reference number ISO/IEC 29362:2008(E) ISO/IEC 2008INTERNATIONAL STANDARD ISO/IEC 29362 First edition 2008-06-15 Information technology Web Services Interoperability WS-I Attachments Profile Version 1.0 Technologies de linformation Interoprabilit des services du Web Profil des fichiers joints WS-I,
2、 version 1.0 ISO/IEC 29362: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 performing the
3、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 PDF file can
4、 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
5、 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 in writing
6、 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 reservedISO/IEC 2
7、9362:2008(E) ISO/IEC 2008 All rights reserved iiiContents Foreword v 1 Scope and introduction.1 1.1 Scope1 1.2 Relationship to other Profiles 1 1.3 Notational Conventions.1 1.4 Profile Identification and Versioning3 2 Profile Conformance.3 2.1 Conformance Requirements .3 2.2 Conformance Targets .4 2
8、.3 Conformance Scope .5 2.4 Claiming Conformance .5 3 Attachments Packaging6 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.
9、8 Value-space of Content-Id Header9 3.9 Ordering of MIME Parts.10 3.10 Position of Root Part .11 3.11 Content-Transfer-Encoding .11 ISO/IEC 29362:2008(E) iv ISO/IEC 2008 All rights reserved3.12 MIME Boundary String 12 4 Attachments Description 12 4.1 Use of MIME Binding Extension . 12 4.2 Unbound po
10、rtType 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 Pa
11、rts 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 Specificati
12、ons. 27 Appendix B: Extensibility Points. 28 Appendix C: Normative References. 29 Appendix D: Defined Terms. 30 Appendix E: Acknowledgements . 31 ISO/IEC 29362:2008(E) ISO/IEC 2008 All rights reserved vForeword ISO (the International Organization for Standardization) and IEC (the International Elect
13、rotechnical 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 techni
14、cal 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 technic
15、al 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 circ
16、ulated 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
17、 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 bodi
18、es of ISO and IEC. INTERNATIONAL STANDARD ISO/IEC 29362:2008(E) ISO/IEC 2008 All rights reserved 1Information 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 (hereaft
19、er, “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 SO
20、AP 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 at
21、tachments 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 over
22、view 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 c
23、ombination 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
24、(i.e., those impacting conformance, as outlined in “Conformance Requirements“) are presented in the following manner: ISO/IEC 29362:2008(E) 2 ISO/IEC 2008 All rights reservedRnnnnStatement text here. where “nnnn“ is replaced by a number that is unique among the requirements in the Profile, thereby f
25、orming 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 requirements identifier (e.g., “R9999“ as opposed to “bp10:R9999“), it shou
26、ld 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
27、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
28、 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
29、 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 requirem
30、ent 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
31、.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
32、/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“ ISO/IEC 29362:2008(E) ISO/IEC 2008 All rights reserved 31.4 Profile Identification and Versioning This document is identified by a name (in this case, Attachments Pr
33、ofile) 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 majo
34、r 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
35、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 i
36、nstances 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 impl
37、ies 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
38、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 normati
39、ve, 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 Profiles requirements take precedence for purposes of Profile conforman
40、ce. 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. ISO/IEC 29362:2008(E) 4 ISO/I
41、EC 2008 All rights reservedThis 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 rea
42、sons 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“). The conformance target keyword appears in bold text (
43、e.g. “MESSAGE“). Other conformance targets appearing in non-bold text are being used strictly for their definition and NOT as a conformance target. Additional text may be included to illuminate a requirement or group of requirements (e.g., rationale and examples); however, prose surrounding requirem
44、ent 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 abilit
45、y 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.,
46、 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
47、 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: MESSAGE - protocol elements that transport the EN
48、VELOPE (e.g., SOAP/HTTP messages) (from ISO/IEC 29361) ENVELOPE - the serialization of the soap:Envelope element and its content (from ISO/IEC 29361) DESCRIPTION - descriptions of types, messages, interfaces and their concrete protocol and data format bindings, and the network access points associat
49、ed with Web services (e.g., WSDL descriptions) (from ISO/IEC 29361) ISO/IEC 29362:2008(E) ISO/IEC 2008 All rights reserved 5 INSTANCE - software that implements a wsdl:port or a uddi:bindingTemplate (from ISO/IEC 29361) CONSUMER - software that invokes an INSTANCE (from ISO/IEC 29361) SENDER - software that generates a message according to the protocol(s) associated with it (from ISO/IEC 29361) RECEIVER - software that consumes a message according to the protocol(s) associated with it (e.g.
