ISO IEC 29362:2008 pdfダウンロード

ISO IEC 29362:2008 pdfダウンロード。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:
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