Network Working Group D. Eastlake
Request for Comments: 3505 Motorola
Category: Informational March 2003
Network Working Group D. Eastlake
Request for Comments: 3505 Motorola
Category: Informational March 2003
Electronic Commerce Modeling Language (ECML): Version 2 Requirements
电子商务建模语言（ECML）：第2版要求
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 (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
Abstract
摘要
This document lists the design principles, scope, and requirements for the Electronic Commerce Modeling Language (ECML) version 2 specification. It includes requirements as they relate to Extensible Markup Language (XML) syntax, data model, format, and payment processing.
本文档列出了电子商务建模语言（ECML）第2版规范的设计原则、范围和要求。它包括与可扩展标记语言（XML）语法、数据模型、格式和支付处理相关的需求。
Table of Contents
目录
1. Introduction.................................................... 2
1.1 Relationship to Other Standards............................. 2
2. Design Principles and Scope..................................... 2
3. Requirements.................................................... 3
3.1 Payment Processing Elements................................. 3
3.2 Payment Processing Types.................................... 3
3.3 XML Data Model and Syntax................................... 4
3.4 Implementation.............................................. 4
3.5 Detailed Requests........................................... 4
4. Security Considerations......................................... 5
5. References...................................................... 5
6. Acknowledgments................................................. 6
7. Authors' Addresses.............................................. 7
8. Full Copyright Statement........................................ 8
1. Introduction.................................................... 2
1.1 Relationship to Other Standards............................. 2
2. Design Principles and Scope..................................... 2
3. Requirements.................................................... 3
3.1 Payment Processing Elements................................. 3
3.2 Payment Processing Types.................................... 3
3.3 XML Data Model and Syntax................................... 4
3.4 Implementation.............................................. 4
3.5 Detailed Requests........................................... 4
4. Security Considerations......................................... 5
5. References...................................................... 5
6. Acknowledgments................................................. 6
7. Authors' Addresses.............................................. 7
8. Full Copyright Statement........................................ 8
ECML Version 2.0 will describe the syntax of a class of data objects called Payment Processing Objects. This will involve the development of a hierarchically organized set of data elements and an XML syntax for payment transaction information for both electronic wallets and Business to Business (B2B) payment types such as credit card, electronic check, line of credit, ACH (Automated Clearing House,) Mobile Phone Payments, and PDA Payments.
ECML版本2.0将描述一类称为支付处理对象的数据对象的语法。这将涉及为电子钱包和企业对企业（B2B）支付类型（如信用卡、电子支票、信用额度、ACH（自动清算所）、移动电话支付和PDA支付）的支付交易信息开发分层组织的数据元素集和XML语法。
This document lists the design principles, scope, and requirements over three things: (1) the scope of work available to the WG, (2) the ECML version 2 specification, and (3) applications that implement the specification. It includes requirements as they relate to the payment element syntax, data model, format, implementation, and external requirements. Those things that are required are designated as "must", those things that are optional are designated by "may", those things that are optional but recommended are designated as "should".
本文件列出了三方面的设计原则、范围和要求：（1）工作组可用的工作范围，（2）ECML第2版规范，以及（3）实施规范的应用程序。它包括与支付元素语法、数据模型、格式、实现和外部需求相关的需求。那些需要的东西被指定为“必须”，那些可选的东西被指定为“可以”，那些可选但推荐的东西被指定为“应该”。
The set of fields documented herein was started by the ECML Alliance [ECML] which developed the North American / HTML form field oriented Versions 1 and 1.1 of ECML [RFC 3106]. Control and development of future versions of the standard has been transferred to the IETF.
本文中记录的字段集由ECML联盟[ECML]启动，该联盟开发了ECML[RFC 3106]的北美/HTML表单面向字段的版本1和1.1。本标准未来版本的控制和开发已移交给IETF。
The ECML Version 1 fields were initially derived from and are consistent with the W3C P3P base data schema [P3P BASE]. Version 2 extends the fields provided to encompass [P3P ECOM] and selected additional fields from [ISO 8583], [JCM], or other sources.
ECML版本1字段最初源自W3C P3P基础数据模式[P3P基础]，并与之一致。版本2扩展了提供的字段，包括[P3P ECOM]和[ISO 8583]、[JCM]或其他来源中选定的其他字段。
ECML Version 2.0 is not a replacement or alternative to TLS [RFC 2246], SET [SET], EMV [EMV], XML [XML], or IOTP [RFC 2801]. These are important standards that provide functionality such as confidentiality, non-repudiated transactions, automatic payment scheme selection, and smart card support.
ECML版本2.0不是TLS[RFC 2246]、SET[SET]、EMV[EMV]、XML[XML]或IOTP[RFC 2801]的替代品或替代品。这些是提供保密性、不可否认交易、自动支付方案选择和智能卡支持等功能的重要标准。
1. The specification must describe the fields necessary to process a payment between a consumer and merchant or between two businesses, describing the XML syntax and content in particular.
1. 规范必须描述处理消费者和商家之间或两个企业之间的支付所需的字段，特别是描述XML语法和内容。
2. Keep the addition of fields beyond those in ECML v1.1 [RFC 3106] to a minimum.
2. 将ECMLV1.1[RFC3106]中字段之外的字段添加量保持在最低限度。
3. Maintain all existing functionality from ECML v1.1. In essence, ECML v2 should be a superset of ECML v1.1.
3. 维护ECMLV1.1中的所有现有功能。本质上，ECMLV2应该是ECMLV1.1的超集。
4. Increase the flexibility of the standard to include other forms of payments. These include ACH, Mobile Phone, PDA, Purchasing Card and electronic check. See [P3P ECOM, JCM], etc.
4. 增加标准的灵活性，以包括其他形式的支付。其中包括ACH、手机、PDA、采购卡和电子支票。参见[P3P ECOM、JCM]等。
5. Allow for use of a common and uniform DTD with back-end payment systems such as Enterprise Resource Provision (ERP), Card Line Item Detail (LID) Level II & Level III, etc.
5. 允许在后端支付系统中使用通用和统一的DTD，如企业资源供应（ERP）、卡行项目详细信息（LID）二级和三级等。
6. Allow for use of the standard with Business to Business (B2B) payment vehicles, such as B2B Wallets, Marketplaces, etc.
6. 允许将标准用于企业对企业（B2B）支付工具，如B2B钱包、市场等。
7. Create a usage/implementation guide section of the specification to cover additional use cases for functionality included.
7. 创建规范的使用/实施指南部分，以涵盖所包含功能的其他用例。
8. ECML version 2 may include the concept of an offer.
8. ECML版本2可能包含报价的概念。
9. ECML version 2 should be developed as part of the broader Web design philosophy of decentralization, URIs, Web data, modularity /layering / extensibility, and assertions as statements about statements. [Berners-Lee, WebData, XML, XML Name] In this context, this standard should take advantage of existing provider (and infrastructure) primitives.
9. ECML第2版应该作为更广泛的Web设计理念的一部分进行开发，即分散、URI、Web数据、模块化/分层/可扩展性，以及作为语句声明的断言。[Berners Lee，WebData，XML，XML名称]在这种情况下，该标准应该利用现有的提供者（和基础设施）原语。
ECML v2 must cover the data types and other requirements enumerated in this section. It should provide for asserting and querying relevant element values.
ECML v2必须涵盖本节列举的数据类型和其他要求。它应该提供断言和查询相关元素值的功能。
1. Cost 2. Receipt 3. Currency 4. Card 5. Payment 6. Bank/Telco
1. 成本2。收据3。货币4。卡片5。付款6。银行/电信
1. All current Processing types for ECML 1.1 [RFC 3106]. 2. Automated Clearing house [ACH] 3. Electronic check [eCheck] 4. Mobile phone payments 5. PDA payments
1. ECML 1.1[RFC 3106]的所有当前处理类型。2.自动结算所[ACH]3。电子支票[电子支票]4。手机支付5。PDA支付
1. A well-formed DTD and possibly schema need to be developed to include new fields in this standard.
1. 需要开发格式良好的DTD和可能的模式，以便在本标准中包括新字段。
2. A W3C Note may be drafted to document changes from [W3C ECOM].
2. 可以起草W3C说明，以记录[W3C ECOM]的变更。
1. The ECML version 2 specification should meet the requirements of the following applications:
1. ECML版本2规范应满足以下应用的要求：
a. Internet Open Trading Protocol v1.0 [IOTP]
a. 互联网开放交易协议v1.0[IOTP]
b. Check against representative ACH, electronic check, and Mobile Phone payment setup.
b. 根据代表ACH、电子支票和手机支付设置进行检查。
2. Test all XML DTDs, schemas and XML examples included the specification to insure that they are well-formed XML.
2. 测试规范中包含的所有XML DTD、模式和XML示例，以确保它们是格式良好的XML。
3. Compare completeness against (in accordance with standard's goals:)
3. 将完整性与（根据标准的目标：）进行比较
1. ECML v1.1 [RFC 3106] 2. Using P3P for E-Commerce [P3P NOTE] 3. Financial transaction card originated messages [ISO 8583] 4. ebXML
1. ECMLV1.1[RFC3106]2。使用P3P进行电子商务[P3P注释]3。金融交易卡原始信息[ISO 8583]4。电子商务扩展标记语言
The following are specific comments received on claimed deficiencies in ECML v1.1 and should all be considered for possible inclusion in ECML v2.
以下是针对ECML v1.1中声称存在的缺陷而收到的具体意见，应考虑将其全部纳入ECML v2中。
1. Increase Last Name field minimum required support to at least 22 characters.
1. 将姓氏字段所需的最小支持增加到至少22个字符。
2. Improved Internationalization support.
2. 改进的国际化支持。
3. Longer minimum supported telephone number and email fields.
3. 更长的最小支持电话号码和电子邮件字段。
4. Provide a "translation field" which would specify a mapping between existing fields and ECML specified fields. The addition of such a field in ECML v2 (which would normally be hidden when presented in HTML) would permit ECML support with no change to existing fields or code. ECML code could fill in existing fields based on the ECML field they map to.
4. 提供一个“翻译字段”，它将指定现有字段和ECML指定字段之间的映射。在ECMLv2中添加这样一个字段（在HTML中显示时通常是隐藏的）将允许ECML支持，而不会更改现有字段或代码。ECML代码可以根据它们映射到的ECML字段填充现有字段。
Many ECML fields contain sensitive private information. ECML is dependent upon:
许多ECML字段包含敏感的私有信息。ECML取决于：
- the security of the transmission infrastructure used to send such private information
- 用于发送此类私人信息的传输基础设施的安全性
- the security of applications which store or release such sensitive information.
- 存储或发布此类敏感信息的应用程序的安全性。
ECML need not add any security mechanisms to this infrastructure or these applications. The ECML v2 specification must include adequate warnings and suggested courses of action to protect this information.
ECML不需要向这个基础设施或这些应用程序添加任何安全机制。ECML v2规范必须包括足够的警告和建议的行动方案，以保护这些信息。
[ACH] Automated Clearing House <http://www.nacha.org>
[ACH] Automated Clearing House <http://www.nacha.org>
[Berners-Lee] "Axioms of Web Architecture: URIs",
<http://www.w3.org/DesignIssues/Axioms.html>, "Web
Architecture from 50,000 feet",
<http://www.w3.org/DesignIssues/Architecture.html>
[Berners-Lee] "Axioms of Web Architecture: URIs",
<http://www.w3.org/DesignIssues/Axioms.html>, "Web
Architecture from 50,000 feet",
<http://www.w3.org/DesignIssues/Architecture.html>
[eCheck] Electronic Check <http://www.echeck.org>
[eCheck] Electronic Check <http://www.echeck.org>
[ECML] Electronic Commerce Modeling Language, The ECML Alliance, <http://www.oasis-open.org/cover/ecml.html>.
[ECML]电子商务建模语言，ECML联盟<http://www.oasis-open.org/cover/ecml.html>.
[HTML] "HTML 3.2 Reference Specification", Hyper Text Markup Language, <http://www.w3.org/TR/REC-html32.html>, D. Raggett, January 1997.
[HTML]“HTML 3.2参考规范”，超文本标记语言<http://www.w3.org/TR/REC-html32.html>，D.Raggett，1997年1月。
[ISO 8583] "Financial transaction card originated messages -- Interchange message specifications", International Standards Organization, 1993.
[ISO 8583]“金融交易卡原始报文——交换报文规范”，国际标准组织，1993年。
[JCM] "Java Commerce Messages", Sun Microsystems, IBM, April 1998.
[JCM]“Java商业信息”，Sun Microsystems，IBM，1998年4月。
[EMV] The EuroCard, MasterCard, Visa chip card protocol
standard. <http://www.emvco.org>
[EMV] The EuroCard, MasterCard, Visa chip card protocol
standard. <http://www.emvco.org>
[RFC 2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC 2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC 2246] Dierks, T. and C. Allen, "The TLS Protocol: Version 1.0", RFC 2246, January 1999.
[RFC 2246]Dierks，T.和C.Allen，“TLS协议：1.0版”，RFC 2246，1999年1月。
[RFC 2801] "Internet Open Trading Protocol - IOTP Version 1.0", D. Burdett, April 2000.
[RFC 2801]“互联网开放交易协议-IOTP 1.0版”，D.Burdett，2000年4月。
[RFC 3106] Eastlake, D. and T. Goldstein, "ECML v1.1: Field Names for E-Commerce", RFC 3106, April 2001.
[RFC 3106]Eastlake，D.和T.Goldstein，“ECML v1.1：电子商务领域名称”，RFC 3106，2001年4月。
[P3P BASE] "The Platform for Privacy Preferences 1.0 (P3P1.0) Specification", L. Cranor, M. Langheinrich, M. Marchiori, M. Presler-Marshall, J. Reagle, December 2000, <http://www.w3.org/TR/WD-P3P/basedata.html>.
[P3P基础]“隐私偏好平台1.0（P3P1.0）规范”，L.Cranor，M.Langheinrich，M.Marchiori，M.Presler Marshall，J.Reagle，2000年12月<http://www.w3.org/TR/WD-P3P/basedata.html>.
[P3P ECOM] "Using P3P for E-Commerce", J. Coco, S. Klein, D. Schutzer, S. Yen, A. Slater, November 1999, <http://www.w3.org/TR/P3P-for-ecommerce>.
[P3P ECOM]“将P3P用于电子商务”，J.Coco，S.Klein，D.Schutzer，S.Yen，A.Slater，1999年11月<http://www.w3.org/TR/P3P-for-ecommerce>.
[SET] "Secure Electronic Transaction", <http://www.setco.org/set_specifications.html>.
[设置]“安全电子交易”<http://www.setco.org/set_specifications.html>.
[WebData] "Web Architecture: Describing and Exchanging Data",
<http://www.w3.org/1999/04/WebData>
[WebData] "Web Architecture: Describing and Exchanging Data",
<http://www.w3.org/1999/04/WebData>
[XML] "Extensible Markup Language (XML) 1.0 (Second Edition)", <http://www.w3.org/TR/REC-xml>, T. Bray, J. Paoli, C. M. Sperberg-McQueen.
[XML]“可扩展标记语言（XML）1.0（第二版）”<http://www.w3.org/TR/REC-xml>，T.Bray，J.Paoli，C.M.Sperberg McQueen。
[XML Name] "Namespaces in XML", Tim Bray, Dave Hollander, Andrew
Layman, 14 January 1999.
<http://www.w3.org/TR/REC-xml-names>
[XML Name] "Namespaces in XML", Tim Bray, Dave Hollander, Andrew
Layman, 14 January 1999.
<http://www.w3.org/TR/REC-xml-names>
Jon W. Parsons and David Shepherd contributed substantially to this document.
Jon W.Parsons和David Shepherd对本文件做出了重大贡献。
Donald E. Eastlake 3rd Motorola 155 Beaver Street Milford, MA 01757 USA
Donald E.Eastlake 3rd Motorola美国马萨诸塞州米尔福德海狸街155号01757
Phone: +1-508-851-8280 (w)
+1-508-634-2066 (h)
EMail: Donald.Eastlake@motorola.com
Phone: +1-508-851-8280 (w)
+1-508-634-2066 (h)
EMail: Donald.Eastlake@motorola.com
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。