RFC 3902

RFC 3902

The "application/soap+xml" media type

Status of this Memo

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.


This document defines the "application/soap+xml" media type which can be used to describe SOAP 1.2 messages serialized as XML 1.0.

この文書は XML 1.0 で直列化した SOAP 1.2 メッセージを記述するために使用できる application/soap+xml 媒体型を定義します。

1. Introduction

SOAP version 1.2 (SOAP) is a lightweight protocol intended for exchange of structured information between peers in a decentralized, distributed environment. It defines an extensible messaging framework that contains a message construct based on XML technologies that can be exchanged over a variety of underlying protocols.

SOAP 1.2 版 (SOAP) は脱集中分散環境の同輩間の構造化情報の交換のための軽量プロトコルです。 SOAP は様々なプロトコルの上で交換できる XML 技術を基にしたメッセージ構造を含む、拡張可能なメッセージ付けの枠組みを定義しています。

This specification defines the media type "application/soap+xml" which can be used to identify SOAP 1.2 message envelopes that have been serialized with XML 1.0. Such serializations are useful as the basis of "wire formats" for SOAP 1.2 Protocol Binding Specifications [W3C.REC-soap12-part1-20030624], or in other situations where an XML serialization of a SOAP envelope is required.

この仕様書は XML 1.0 で直列化した SOAP 1.2 メッセージ封筒を識別するために使うことができる application/soap+xml 媒体型を定義します。 XML 1.0 直列化形は、 SOAP 1.2 プロトコル束縛仕様書の通信 (wire) の基礎として、 あるいはその他 SOAP 封筒の XML 直列化が必要な状況で有用です。

The "application/soap+xml" media type explicitly identifies SOAP 1.2 message envelopes that have been serialised with XML 1.0; message envelopes with a different SOAP namespace version or using another XML serialisation MUST NOT use it.

application/soap+xml 媒体型は明示的に SOAP 1.2 メッセージ封筒を XML 1.0 で直列化したものを識別します。 異なる SOAP 名前空間版や他の XML 直列化を使ったメッセージ封筒は、 この媒体型を使ってはなりません

The key words "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].

2. Registration

MIME media type name
MIME subtype name
Required parameters
Optional parameters
This parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in RFC 3023 [RFC3023].
This optional parameter can be used to specify the URI that identifies the intent of the message. In SOAP 1.2, it serves a similar purpose as the SOAPAction HTTP header field did in SOAP 1.1. Namely, its value identifies the intent of the message.
RFC 3023 で規定されている application/xml 媒体型の charset 引数と同じ意味を持つ引数です。
メッセージの意図を識別する URI を指定するために使うことができる省略可能な引数です。 SOAP 1.2 では SOAP 1.1 の SOAPAction HTTP 頭欄と同様の目的で使います。つまり、値はメッセージの意図を識別します。

The value of the action parameter is an absolute URI-reference as defined by RFC 2396 [RFC2396], which MUST be non-empty. SOAP places no restrictions on the specificity of the URI or that it is resolvable. Although the purpose of the action parameter is to indicate the intent of the SOAP message there is no mechanism for automatically computing the value based on the SOAP envelope. In other words, the value has to be determined out of band. It is recommended that the same value be used to identify sets of message types that are logically connected in some manner, for example part of the same "service". It is strongly RECOMMENDED that the URI be globally unique and stable over time.

action 引数の値は RFC 2396 で定義された絶対 URI 参照で、空以外でなければなりません。 SOAP はこの URI の特異性やこの URI が解決可能かどうかについて何の制限も課しません。 action 引数の目的は SOAP メッセージの意図を示すことですが、 SOAP 封筒を基にして自動的に値を計算する仕組みはありません。 言い換えれば、この値は外部で決定しなければなりません。ある方法で論理的に接続されたメッセージ型の集合、 例えば同じサービスの一部を識別するために同じ値を使うことを推奨します。 URI は大域的に固有であって、時をこえて安定であることを強く推奨します。

Use of the action parameter is OPTIONAL. SOAP Receivers MAY use it as a hint to optimize processing, but SHOULD NOT require its presence in order to operate.

action 引数の使用は任意選択です。 SOAP 受信者は処理を最適化するヒントとして使っても構いませんが、 処理のためにこの引数が存在していることを必要とするべきではありません

Encoding considerations
Identical to those of "application/xml" as described in RFC 3023 [RFC3023], section 3.2, as applied to the SOAP envelope infoset.

RFC 3023 3.2節で application/xml について説明されていることが SOAP 封筒情報集合にも適用されます。

Security considerations
Because SOAP can carry application defined data whose semantics is independent from that of any MIME wrapper (or context within which the MIME wrapper is used), one should not expect to be able to understand the semantics of the SOAP message based on the semantics of the MIME wrapper alone. Therefore, whenever using the "application/soap+xml" media type, it is strongly RECOMMENDED that the security implications of the context within which the SOAP message is used is fully understood. The security implications are likely to involve both the specific SOAP binding to an underlying protocol as well as the application-defined semantics of the data carried in the SOAP message (though one must be careful when doing this, as discussed in SOAP 1.2 Part 1 [W3C.REC-soap12-part1-20030624], section Binding to Application-Specific Protocols).

SOAP はその意味が MIME 覆い子 (wrapper) のもの (や MIME 覆い子が使用されている文脈) から独立した応用定義のデータを伝達できますから、 MIME 覆い子だけの意味に基づいて SOAP メッセージの意味を理解できると期待するべきではありません。 従って、 application/soap+xml 媒体型を使う時は常に SOAP メッセージが使われている文脈による安全性への影響を完全に理解することを強く推奨します。 安全性への影響は特定の下位プロトコルへの束縛にも、 SOAP メッセージで伝達されるデータの意味にも関わります。

Also, see SOAP 1.2 Part 1 [W3C.REC-soap12-part1-20030624], the entire section Security Considerations.

また、 SOAP 1.2 第1部の安全性に関してもご覧下さい。

In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in RFC 3023 [RFC3023], section 10.

加えて、この媒体型は +xml 記法を使っていますから、 RFC 3023 10章で説明されている安全性についての考察も該当します。

The action parameter is not a security mechanism, and SHOULD NOT be used for authentication. If the action parameter is used to make decisions (e.g., dispatch, filtering), it is RECOMMENDED that the basis for such decisions should be confirmed by examining the SOAP Envelope.

action 引数は安全のための仕組みではなく、 認証のために使用するべきではありません。決定 (例えば発射、濾過) のために action 引数を使う場合は、その決定の基礎は SOAP 封筒の検査によって確認することを推奨します。

Interoperability considerations
There are no known interoperability issues.
Published specification
SOAP 1.2 Part 1 [W3C.REC-soap12-part1-20030624] and SOAP 1.2 Part 2 [W3C.REC-soap12-part2-20030624].
Applications which use this media type
Various SOAP 1.2 conformant toolkits use this media type.
Additional information
   File extension: SOAP messages are not required or expected to be
      stored as files.
   Fragment identifiers: Identical to that of "application/xml" as
      described in RFC 3023 [RFC3023], section 5.
   Base URI: As specified in RFC 3023 [RFC3023], section 6.  Also see
      SOAP 1.2 Part 1 [W3C.REC-soap12-part1-20030624], section Use of
      URIs in SOAP.
   Macintosh File Type code: TEXT
   Person and email address to contact for further information:
      World Wide Web Consortium <web-human@w3.org>
   Intended usage: COMMON
   Author/Change controller: The SOAP 1.2 specification set is a work
      product of the World Wide Web Consortium's XML Protocol Working
      Group.  The W3C has change control over these specifications.

3. Security Considerations

See the "Security Considerations" section of the registration template found in Section 2.

4. Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.
   [RFC2396]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifiers (URI): Generic Syntax", RFC 2396,
              August 1998.
   [RFC3023]  Murata, M., St.Laurent, S., and D. Kohn, "XML Media
              Types", RFC 3023, January 2001.
              Hadley, M., Mendelsohn, N., Moreau, J., Nielsen, H., and
              M.  Gudgin, "SOAP Version 1.2 Part 1: Messaging
              Framework", W3C REC REC-soap12-part1-20030624, June 2003.
              Moreau, J., Nielsen, H., Gudgin, M., Hadley, M., and N.
              Mendelsohn, "SOAP Version 1.2 Part 2: Adjuncts", W3C REC
              REC-soap12-part2-20030624, June 2003.

5. Authors' Addresses

   Mark A. Baker
   37 Charles St.
   Ottawa, Ontario  K1M 1R3
   EMail: distobj@acm.org
   Mark Nottingham
   BEA Systems
   235 Montgomery St., Level 15
   San Francisco, CA  94010
   EMail: mnot@pobox.com

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the ISOC's procedures with respect to rights in ISOC Documents can
   be found in BCP 78 and BCP 79.
   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at ietf-


   Funding for the RFC Editor function is currently provided by the
   Internet Society.