Network Working Group M. Baker
Request for Comments: 3902 Independent
Category: Informational M. Nottingham
BEA Systems
September 2004
Network Working Group M. Baker
Request for Comments: 3902 Independent
Category: Informational M. Nottingham
BEA Systems
September 2004
The "application/soap+xml" media type
“应用程序/soap+xml”媒体类型
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.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
Abstract
摘要
This document defines the "application/soap+xml" media type which can be used to describe SOAP 1.2 messages serialized as XML 1.0.
本文档定义了“应用程序/soap+xml”媒体类型，可用于描述序列化为xml 1.0的soap 1.2消息。
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）是一种轻量级协议，用于在分散、分布式环境中的对等方之间交换结构化信息。它定义了一个可扩展的消息传递框架，其中包含一个基于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.
本规范定义了媒体类型“application/soap+xml”，可用于标识已用xml 1.0序列化的soap 1.2消息信封。此类序列化可用作SOAP 1.2协议绑定规范[W3C.REC-soap12-part1-20030624]的“连线格式”基础，或在其他需要对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”媒体类型明确标识了已用xml 1.0序列化的soap 1.2消息信封；具有不同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].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
MIME media type name: application MIME subtype name: soap+xml Required parameters: none Optional parameters:
MIME媒体类型名称：应用程序MIME子类型名称：soap+xml必需参数：无可选参数：
"charset": This parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in RFC 3023 [RFC3023].
“charset”：此参数与RFC 3023[RFC3023]中指定的“application/xml”媒体类型的charset参数具有相同的语义。
"action": 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.
“action”：此可选参数可用于指定标识消息意图的URI。在SOAP1.2中，它的用途与SOAP1.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[RFC2396]定义的绝对URI引用，它必须为非空。SOAP对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.
动作参数的使用是可选的。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[RFC3023]第3.2节中描述的“应用程序/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-
安全注意事项：由于SOAP可以携带应用程序定义的数据，这些数据的语义独立于任何MIME包装（或使用MIME包装的上下文）的语义，因此不能期望仅基于MIME包装的语义就能理解SOAP消息的语义。因此，无论何时使用“application/soap+xml”媒体类型，强烈建议完全理解使用soap消息的上下文的安全含义。安全影响可能涉及到与底层协议的特定SOAP绑定以及应用程序-
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消息中携带的数据的定义语义（尽管在执行此操作时必须小心，如SOAP 1.2第1部分[W3C.REC-soap12-part1-20030624]，绑定到应用程序特定协议一节中所述）。
Also, see SOAP 1.2 Part 1 [W3C.REC-soap12-part1-20030624], the entire section Security Considerations.
另外，请参见SOAP1.2第1部分[W3C.REC-soap12-part1-20030624]，完整一节介绍了安全注意事项。
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[RFC3023]第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参数不是安全机制，不应用于身份验证。如果操作参数用于做出决策（例如，分派、筛选），建议通过检查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].
已发布规范：SOAP 1.2第1部分[W3C.REC-soap12-part1-20030624]和SOAP 1.2第2部分[W3C.REC-soap12-part2-20030624]。
Applications which use this media type: Various SOAP 1.2 conformant toolkits use this media type.
使用此媒体类型的应用程序：各种符合SOAP 1.2的工具包都使用此媒体类型。
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.
附加信息：文件扩展名：SOAP消息不是必需的，也不希望存储为文件。片段标识符：与RFC 3023[RFC3023]第5节中描述的“应用程序/xml”的标识符相同。基本URI：如RFC 3023[RFC3023]第6节所述。另请参见SOAP 1.2第1部分[W3C.REC-soap12-part1-20030624]，SOAP中URI的使用一节。Macintosh文件类型代码：文本联系人和电子邮件地址以获取更多信息：万维网联盟<Web-human@w3.org>预期用途：通用作者/变更控制器：SOAP1.2规范集是万维网联盟XML协议工作组的工作产品。W3C对这些规范具有变更控制权。
See the "Security Considerations" section of the registration template found in Section 2.
请参阅第2节中注册模板的“安全注意事项”部分。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[RFC2396]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，RFC 2396，1998年8月。
[RFC3023] Murata, M., St.Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001.
[RFC3023]Murata，M.，St.Laurent，S.，和D.Kohn，“XML媒体类型”，RFC 3023，2001年1月。
[W3C.REC-soap12-part1-20030624] 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.
[W3C.REC-soap12-part1-20030624]Hadley，M.，Mendelsohn，N.，Moreau，J.，Nielsen，H.，和M.Gudgin，“SOAP版本1.2第1部分：消息传递框架”，W3C REC-soap12-part1-20030624，2003年6月。
[W3C.REC-soap12-part2-20030624] 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.
[W3C.REC-soap12-part2-20030624]莫里奥，J.，尼尔森，H.，古金，M.，哈德利，M.，和N.门德尔松，“SOAP版本1.2第2部分：附件”，W3C REC-soap12-part2-20030624，2003年6月。
Mark A. Baker Independent 37 Charles St. Ottawa, Ontario K1M 1R3 CA
Mark A.Baker Independent 37安大略省渥太华查尔斯街K1M 1R3 CA
EMail: distobj@acm.org
EMail: distobj@acm.org
Mark Nottingham BEA Systems 235 Montgomery St., Level 15 San Francisco, CA 94010 US
标记诺丁汉BEA系统235蒙哥马利圣，15级旧金山，CA 94010美国
EMail: mnot@pobox.com
EMail: mnot@pobox.com
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and at www.rfc-editor.org, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78和www.rfc-editor.org中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、其代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关ISOC文件中权利的ISOC程序信息，请参见BCP 78和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 http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
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-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。