Network Working Group D. Eastlake
Request for Comments: 3106 Motorola
Obsoletes: 2706 T. Goldstein
Category: Informational Brodia
April 2001
Network Working Group D. Eastlake
Request for Comments: 3106 Motorola
Obsoletes: 2706 T. Goldstein
Category: Informational Brodia
April 2001
ECML v1.1: Field Specifications for E-Commerce
ECMLV1.1：电子商务的字段规范
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 (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
IESG Note:
IESG注：
This document specifies version 1.1 of ECML and obsoletes RFC 2706 which specifies version 1.0 of ECML. Both version 1.0 and 1.1 of ECML are products of the ECML alliance which is described in section 1.1 of this document. The reader should note that version 2.0 of ECML is under development (as of the publication of this RFC) in the IETF in the TRADE Working Group.
本文件规定了ECML的1.1版，并废除了RFC 2706，RFC 2706规定了ECML的1.0版。ECML的1.0版和1.1版都是ECML联盟的产品，本文件第1.1节对此进行了描述。读者应注意，ECML的2.0版正在贸易工作组的IETF中开发（截至本RFC发布之日）。
Abstract
摘要
Customers are frequently required to enter substantial amounts of information at an Internet merchant site in order to complete a purchase or other transaction, especially the first time they go there. A standard set of information fields is defined as the first version of an Electronic Commerce Modeling Language (ECML) so that this task can be more easily automated, for example by wallet software that could fill in fields. Even for the manual data entry case, customers will be less confused by varying merchant sites if a substantial number adopt these standard fields. In addition, some fields are defined for merchant to consumer communication.
客户通常需要在互联网商户网站上输入大量信息，以完成购买或其他交易，尤其是第一次去那里时。一组标准的信息字段被定义为电子商务建模语言（ECML）的第一个版本，因此该任务可以更容易地自动化，例如通过可以填充字段的钱包软件。即使对于手动数据输入案例，如果大量客户采用这些标准字段，客户也不会因不同的商户站点而感到困惑。此外，还为商户对消费者通信定义了一些字段。
Acknowledgements
致谢
The following persons, in alphabetic order, contributed substantially to the material herein:
以下人员按字母顺序对本文件中的材料做出了重大贡献：
George Burne Joe Coco Jon Parsons James Salsman David Shepherd Kevin Weller
乔治·伯恩、乔·可可、乔恩·帕森斯、詹姆斯·萨尔斯曼、大卫·谢泼德、凯文·韦勒
Table of Contents
目录
1. Introduction.................................................. 2
1.1 The ECML Alliance............................................ 3
1.2 Relationship to Other Standards.............................. 4
1.3 Areas Deferred to Future Versions............................ 4
2. Field Definitions and DTD..................................... 4
2.1 Field List and Descriptions.................................. 4
2.1.1 Field List................................................. 5
2.1.2 Field Foot Notes........................................... 7
2.2 Use in HTML.................................................. 10
2.3 An ECML 1.1 XML DTD.......................................... 11
3. Using The Fields.............................................. 13
3.1 Presentation of the Fields................................... 13
3.2 Methods and Flow of Setting the Fields....................... 14
3.3 HTML Example................................................ 14
4. Security and Privacy Considerations........................... 16
References....................................................... 16
Appendix: Changes from ECML 1.0.................................. 18
Authors' Addresses............................................... 19
Full Copyright Statement......................................... 20
1. Introduction.................................................. 2
1.1 The ECML Alliance............................................ 3
1.2 Relationship to Other Standards.............................. 4
1.3 Areas Deferred to Future Versions............................ 4
2. Field Definitions and DTD..................................... 4
2.1 Field List and Descriptions.................................. 4
2.1.1 Field List................................................. 5
2.1.2 Field Foot Notes........................................... 7
2.2 Use in HTML.................................................. 10
2.3 An ECML 1.1 XML DTD.......................................... 11
3. Using The Fields.............................................. 13
3.1 Presentation of the Fields................................... 13
3.2 Methods and Flow of Setting the Fields....................... 14
3.3 HTML Example................................................ 14
4. Security and Privacy Considerations........................... 16
References....................................................... 16
Appendix: Changes from ECML 1.0.................................. 18
Authors' Addresses............................................... 19
Full Copyright Statement......................................... 20
Today, numerous merchants are successfully conducting business on the Internet using HTML-based forms. The data formats used in these forms vary considerably from one merchant to another. End-users find the diversity confusing and the process of manually filling in these forms to be tedious. The result is that many merchant forms, reportedly around two thirds, are abandoned during the fill in process.
今天，许多商家正在使用基于HTML的表单在互联网上成功地开展业务。这些表格中使用的数据格式因商户而异。最终用户发现多样性令人困惑，手动填写这些表格的过程非常繁琐。结果是，许多商户表格（据报道约占三分之二）在填写过程中被废弃。
Software tools called electronic wallets can help this situation. A digital wallet is an application or service that assists consumers in conducting online transactions by allowing them to store billing, shipping, payment, and preference information and to use this
称为电子钱包的软件工具可以帮助解决这种情况。数字钱包是一种应用程序或服务，它通过允许消费者存储账单、发货、付款和偏好信息并使用这些信息来帮助消费者进行在线交易
information to automatically complete merchant interactions. This greatly simplifies the check-out process and minimizes the need for a consumer to think about and complete a merchant's form every time. Digital wallets that fill forms have been successfully built into browsers, as proxy servers, as helper applications to browsers, as stand-alone applications, as browser plug-ins, and as server-based applications. But the proliferation of electronic wallets has been hampered by the lack of standards.
自动完成商户交互的信息。这大大简化了结账流程，并最大限度地减少了消费者每次考虑和填写商户表格的需要。填充表单的数字钱包已成功构建到浏览器中，作为代理服务器、浏览器的辅助应用程序、独立应用程序、浏览器插件和基于服务器的应用程序。但由于缺乏标准，电子钱包的普及受到了阻碍。
ECML (Electronic Commerce Modeling Language, <www.ecml.org>) provides a set of simple guidelines for web merchants that will enable electronic wallets from multiple vendors to fill in their web forms. The end-result is that more consumers will find shopping on the web to be easy and compelling.
ECML（Electronic Commerce Modeling Language，<www.ECML.org>）为网络商家提供了一套简单的指南，使来自多个供应商的电子钱包能够填写他们的网络表单。最终的结果是，更多的消费者会发现网上购物很容易，也很吸引人。
Version 1.1 has been enhanced over Version 1.0 [RFC 2706] as described in the appendix to this document. These enhancements include support for communication from the merchant to the wallet. This information can be used by the wallet to present transaction information and possibly signed receipts. The format of the signatures for receipts is not specified in this document.
如本文件附录所述，1.1版已比1.0版[RFC 2706]增强。这些增强功能包括支持从商户到钱包的通信。钱包可以使用此信息来显示交易信息和可能已签名的收据。本文件未规定收据签名的格式。
Multiple wallets and multiple merchants interoperably support ECML. This is an open standard. ECML is designed to be simple. Neither Version 1.0 nor Version 1.1 of the project add new technology to the web. A merchant can adopt ECML and gain the support of these multiple Wallets by making very simple changes to their site. Use of ECML requires no license.
多个钱包和多个商家可互操作地支持ECML。这是一个开放的标准。ECML设计得很简单。项目的1.0版和1.1版都没有向web添加新技术。商家可以采用ECML，并通过对其站点进行非常简单的更改来获得这些多钱包的支持。使用ECML不需要许可证。
The set of fields documented herein was developed by the ECML Alliance (www.ecml.org) which now includes, in alphabetic order, the fifteen Steering Committee members listed below and numerous General Members some of whom are listed on the ECML web site.
本文中记录的一组字段是由ECML联盟（www.ECML.org）开发的，该联盟现在按字母顺序包括以下列出的15名指导委员会成员和许多普通成员，其中一些成员在ECML网站上列出。
1. American Express (www.americanexpress.com> 2. AOL (www.aol.com) 3. Brodia (www.brodia.com) 4. Compaq (www.compaq.com) 5. CyberCash (www.cybercash.com) 6. Discover (www.discovercard.com) 7. FSTC (www.fstc.org) 8. IBM (www.ibm.com) 9. Mastercard (www.mastercard.com) 10. Microsoft (www.microsoft.com) 11. Novell (www.novell.com> 12. SETCo (www.setco.org)
1.美国运通（www.americanexpress.com>2.AOL（www.AOL.com）3.Brodia（www.Brodia.com）4.Compaq（www.Compaq.com）5.CyberCash（www.CyberCash.com）6.Discover（www.discovercard.com）7.FSTC（www.FSTC.org）8.IBM（www.IBM.com）9.Mastercard（www.Mastercard.com）10.Microsoft（www.Microsoft.com）11.Novell（www.Novell.com>12.SETCo（www.setco.org）
13. Sun Microsystems (www.sun.com) 14. Trintech (www.trintech.com> 15. Visa International (www.visa.com)
13. 太阳微系统公司（www.Sun.com）14。Trintech（www.Trintech.com>15.Visa国际（www.Visa.com）
The ECML fields were initially derived from and are consistent with the W3C P3P base data schema at
ECML字段最初来源于W3C P3P基本数据模式，并与之一致
<http://www.w3.org/TR/WD-P3P/basedata.html>.
<http://www.w3.org/TR/WD-P3P/basedata.html>.
ECML Version 1.1 is not a replacement or alternative to SSL/TLS [RFC 2246], SET [SET], XML [XML], or IOTP [RFC 2801]. These are important standards that provide functionality such as non-repudiatable transactions, automatable payment scheme selection, and smart card support.
ECML版本1.1不是SSL/TLS[RFC 2246]、SET[SET]、XML[XML]或IOTP[RFC 2801]的替代品或替代品。这些是提供不可否认交易、自动支付方案选择和智能卡支持等功能的重要标准。
ECML may be used with any payment mechanism. It simply allows a merchant to publish consistent simple web forms. Information on the use of the ECML fields with W3C P3P protocol is available at <http://www.w3.org/TR/P3P-for-ecommerce> which also includes some proposed extension fields. These extension fields may be included in a future version of ECML.
ECML可与任何支付机制一起使用。它只允许商家发布一致的简单web表单。有关在W3C P3P协议中使用ECML字段的信息，请访问<http://www.w3.org/TR/P3P-for-ecommerce>其中还包括一些建议的扩展字段。这些扩展字段可能包含在ECML的未来版本中。
Considerations for business purchasing cards, non-card payment mechanisms, wallet activation, privacy related mechanisms, additional payment mechanisms, currency exchange, and any sort of "negotiation" were among the areas deferred to consideration in future versions. Hidden or other special fields were minimized.
商业购买卡、非卡支付机制、钱包激活、隐私相关机制、附加支付机制、货币兑换和任何形式的“谈判”等方面的考虑因素都将推迟到未来版本中考虑。隐藏字段或其他特殊字段被最小化。
The ECML Standard is primarily the definition and naming of fields. These fields can be encoded in a variety of syntaxes and protocols.
ECML标准主要是字段的定义和命名。这些字段可以用各种语法和协议进行编码。
Section 2.1 below lists and describes the fields, Section 2.2 gives additional notes on HTML usage of the fields, and Section 2.3 provides an XML DTD for use with the fields.
下面的第2.1节列出并描述了字段，第2.2节给出了关于字段HTML用法的附加说明，第2.3节提供了用于字段的XML DTD。
The fields are listed below along with the minimum data entry size to allow. Note that these fields are hierarchically organized as indicated by the embedded underscore ("_") characters. Appropriate data transmission mechanisms may use this to request and send aggregates, such as Ecom_Payment_Card_ExpDate to encompass all the
下面列出了字段以及允许的最小数据输入大小。请注意，这些字段是按嵌入的下划线（“389;”）字符所指示的层次结构组织的。适当的数据传输机制可以使用此来请求和发送聚合，例如Ecom_Payment_Card_ExpDate，以包含所有
date components or Ecom_ShipTo to encompass all the ship to components that the consumer is willing to provide. The labeling, marshalling, unmarshalling of the components of such aggregates depends on the data transfer protocol used.
日期组件或Ecom_ShipTo包含消费者愿意提供的所有ship-to组件。此类聚合组件的标记、编组和解编取决于所使用的数据传输协议。
IMPORTANT NOTE: "MIN" in the table below is the MINIMUM DATA SIZE TO ALLOW FOR ON DATA ENTRY. It is NOT the minimum size for valid contents of the field and merchant software should, in most cases, be prepared to receive a longer or shorter value. Merchant dealing with areas where, for example, the state/province name or phone number is longer than the "Min" given below must obviously permit longer data entry. In some cases, however, there is a maximum size that makes sense and where this is the case, it is documented in a Note for the field.
重要提示：下表中的“MIN”是允许输入数据的最小数据大小。它不是字段有效内容的最小大小，在大多数情况下，商户软件应准备接收更长或更短的值。例如，在州/省名称或电话号码长于下面给出的“Min”的地区交易的商户显然必须允许更长的数据输入。但是，在某些情况下，有一个最大大小是有意义的，在这种情况下，它会记录在字段的注释中。
The following fields are used to communicate from the customer to the merchant:
以下字段用于客户与商户之间的通信：
FIELD NAME Min Notes
字段名Min Notes
ship to title Ecom_ShipTo_Postal_Name_Prefix 4 ( 1) ship to first name Ecom_ShipTo_Postal_Name_First 15 ship to middle name Ecom_ShipTo_Postal_Name_Middle 15 ( 2) ship to last name Ecom_ShipTo_Postal_Name_Last 15 ship to name suffix Ecom_ShipTo_Postal_Name_Suffix 4 ( 3) ship to company name Ecom_ShipTo_Postal_Company 20 ship to street line1 Ecom_ShipTo_Postal_Street_Line1 20 ( 4) ship to street line2 Ecom_ShipTo_Postal_Street_Line2 20 ( 4) ship to street line3 Ecom_ShipTo_Postal_Street_Line3 20 ( 4) ship to city Ecom_ShipTo_Postal_City 22 ship to state/province Ecom_ShipTo_Postal_StateProv 2 ( 5) ship to zip/postal code Ecom_ShipTo_Postal_PostalCode 14 ( 6) ship to country Ecom_ShipTo_Postal_CountryCode 2 ( 7) ship to phone Ecom_ShipTo_Telecom_Phone_Number 10 ( 8) ship to email Ecom_ShipTo_Online_Email 40 ( 9)
发货至名称Ecom_ShipTo_Postal_Name_前缀4（1）发货至名Ecom_ShipTo_Postal_Name_前15发货至中名Ecom_ShipTo_Postal_Name_中15（2）发货至姓Ecom_ShipTo_Postal_Name_last 15发货至名后缀Ecom_ShipTo_Postal_Name_后缀4（3）船到公司名称Ecom_船到邮政_公司20船到街道1号线Ecom_船到邮政_街道1号线20（4）船到街道2号线Ecom_船到邮政_街道2号线20（4）船到街道3号线Ecom_船到邮政_街道3号线20（4）船到城市Ecom_船到邮政_城市22船到州/省Ecom_船到邮政_州2（5）发货至邮政编码Ecom\u发货至\u邮政编码14（6）发货至国家Ecom\u发货至\u邮政编码2（7）发货至电话Ecom\u发货至\u电信\u电话号码10（8）发货至电子邮件Ecom\u发货至\u在线\u电子邮件40（9）
bill to title Ecom_BillTo_Postal_Name_Prefix 4 ( 1) bill to first name Ecom_BillTo_Postal_Name_First 15 bill to middle name Ecom_BillTo_Postal_Name_Middle 15 ( 2) bill to last name Ecom_BillTo_Postal_Name_Last 15 bill to name suffix Ecom_BillTo_Postal_Name_Suffix 4 ( 3) bill to company name Ecom_BillTo_Postal_Company 20 bill to street line1 Ecom_BillTo_Postal_Street_Line1 20 ( 4) bill to street line2 Ecom_BillTo_Postal_Street_Line2 20 ( 4) bill to street line3 Ecom_BillTo_Postal_Street_Line3 20 ( 4)
汇票到标题Ecom_bill到邮政名称前缀4（1）汇票到名字Ecom_bill到邮政名称前15张汇票到中间名Ecom_bill到邮政名称中15（2）汇票到姓氏Ecom_bill到邮政名称最后15张汇票到名字后缀Ecom_bill到邮政名称后缀4（3）账单到公司名称Ecom_bill到邮政公司20账单到街道行1 Ecom_bill到邮政街行1 20（4）账单到街道行2 Ecom_bill到邮政街行2 20（4）账单到街道行3 Ecom_bill到邮政街行3 20（4）
bill to city Ecom_BillTo_Postal_City 22 bill to state/province Ecom_BillTo_Postal_StateProv 2 ( 5) bill to zip/postal code Ecom_BillTo_Postal_PostalCode 14 ( 6) bill to country Ecom_BillTo_Postal_CountryCode 2 ( 7) bill to phone Ecom_BillTo_Telecom_Phone_Number 10 ( 8) bill to email Ecom_BillTo_Online_Email 40 ( 9)
账单至城市经济账单至城市22账单至州/省经济账单至邮政州2（5）账单至邮政编码经济账单至邮政编码14（6）账单至国家经济账单至邮政编码2（7）账单至电话经济账单至电信电话号码10（8）账单至电子邮件经济账单至在线电子邮件40（9）
receipt to (32) receipt to title Ecom_ReceiptTo_Postal_Name_Prefix 4 ( 1) receipt to first name Ecom_ReceiptTo_Postal_Name_First 15 receipt to middle name Ecom_ReceiptTo_Postal_Name_Middle 15 ( 2) receipt to last name Ecom_ReceiptTo_Postal_Name_Last 15 receipt to name suffix Ecom_ReceiptTo_Postal_Name_Suffix 4 ( 3) receipt to company name Ecom_ReceiptTo_Postal_Company 20 receipt to street line1 Ecom_ReceiptTo_Postal_Street_Line1 20 ( 4) receipt to street line2 Ecom_ReceiptTo_Postal_Street_Line2 20 ( 4) receipt to street line3 Ecom_ReceiptTo_Postal_Street_Line3 20 ( 4) receipt to city Ecom_ReceiptTo_Postal_City 22 receipt to state/province Ecom_ReceiptTo_Postal_StateProv 2 ( 5) receipt to postal code Ecom_ReceiptTo_Postal_PostalCode 14 ( 6) receipt to country Ecom_ReceiptTo_Postal_CountryCode 2 ( 7) receipt to phone Ecom_ReceiptTo_Telecom_Phone_Number 10 ( 8) receipt to email Ecom_ReceiptTo_Online_Email 40 ( 9)
收货至（32）收货至标题收货至邮政名称前缀4（1）收货至姓名收货至邮政名称前15收货至中间名收货至邮政名称中15（2）收货至姓氏收货至邮政名称后15收货至姓名后缀收货至邮政名称后4（3）收据至公司名称Ecom_收据至邮政_公司20收据至街道1号线Ecom_收据至邮政_街道1号线20（4）收据至街道2号线Ecom_收据至邮政_街道2号线20（4）收据至街道3号线Ecom_收据至邮政_街道3号线20（4）回执至城市经济区回执至邮政城市22回执至州/省经济区回执至邮政州2（5）回执至邮政编码经济区回执至邮政编码14（6）回执至国家经济区回执至邮政编码2（7）回执至电话经济区回执至电信电话号码10（8）回执至电子邮件经济区回执至在线电子邮件40（9）
name on card Ecom_Payment_Card_Name 30 (10)
卡上姓名Ecom_支付_卡上姓名30（10）
card type Ecom_Payment_Card_Type 4 (11) card number Ecom_Payment_Card_Number 19 (12) card verification value Ecom_Payment_Card_Verification 4 (13) card expire date day Ecom_Payment_Card_ExpDate_Day 2 (14) card expire date month Ecom_Payment_Card_ExpDate_Month 2 (15) card expire date year Ecom_Payment_Card_ExpDate_Year 4 (16)
卡类型Ecom_支付卡类型4（11）卡号Ecom_支付卡编号19（12）卡验证值Ecom_支付卡验证4（13）卡到期日Ecom_支付卡到期日第2（14）天卡到期日月Ecom_支付卡到期日第2（15）个月卡到期日年Ecom_支付卡到期日第4（16）年
card protocols Ecom_Payment_Card_Protocol 20 (17)
卡协议Ecom_支付卡协议20（17）
consumer order ID Ecom_ConsumerOrderID 20 (18)
消费者订单ID Ecom_ConsumerOrderID 20（18）
user ID Ecom_User_ID 40 (19) user password Ecom_User_Password 20 (19)
用户ID Ecom_用户ID 40（19）用户密码Ecom_用户密码20（19）
schema version Ecom_SchemaVersion 30 (20)
模式版本Ecom_SchemaVersion 30（20）
wallet id Ecom_WalletID 40 (21)
钱包id Ecom_WalletID 40（21）
end transaction flag Ecom_TransactionComplete - (22)
结束事务标志Ecom_TransactionComplete-（22）
The following fields are used to communicate from the merchant to the consumer:
以下字段用于商户与消费者之间的通信：
FIELD NAME Min Notes
字段名Min Notes
merchant home domain Ecom_Merchant 128 (23) processor home domain Ecom_Processor 128 (24) transaction identifier Ecom_Transaction_ID 128 (25) transaction URL inquiry Ecom_Transaction_Inquiry 500 (26) transaction amount Ecom_Transaction_Amount 128 (27) transaction currency Ecom_Transaction_CurrencyCode 3 (28) transaction date Ecom_Transaction_Date 80 (29) transaction type Ecom_Transaction_Type 40 (30) transaction signature Ecom_Transaction_Signature 160 (31)
商户主域Ecom_商户128（23）处理器主域Ecom_处理器128（24）交易标识符Ecom_交易ID 128（25）交易URL查询Ecom_交易查询500（26）交易金额Ecom_交易金额128（27）交易货币Ecom_交易代码3（28）交易日期Ecom_交易日期80（29）交易类型Ecom_交易类型40（30）交易签名Ecom_交易签名160（31）
end transaction flag Ecom_TransactionComplete - (22)
结束事务标志Ecom_TransactionComplete-（22）
FIELD NAME Min Notes
字段名Min Notes
IMPORTANT NOTE: "MIN" in the table above is the MINIMUM DATA SIZE TO ALLOW FOR ON DATA ENTRY. It is NOT the minimum size for valid contents of the field and merchant software should, in most cases, be prepared to receive a longer or shorter value. Merchant dealing with areas where, for example, the state/province name or phone number is longer than the "Min" given below must obviously permit longer data entry. In some cases, however, there is a maximum size that makes sense and this is documented in a Note for the field.
重要提示：上表中的“MIN”是允许输入数据的最小数据大小。它不是字段有效内容的最小大小，在大多数情况下，商户软件应准备接收更长或更短的值。例如，在州/省名称或电话号码长于下面给出的“Min”的地区交易的商户显然必须允许更长的数据输入。但是，在某些情况下，有一个最大大小是有意义的，并记录在该字段的注释中。
( 1) For example: Mr., Mrs., Ms., Dr. This field is commonly not used.
（1）例如：先生、夫人、女士、博士。此字段通常不使用。
( 2) May also be used for middle initial.
（2）也可用于中间首字母。
( 3) For example: Ph.D., Jr. (Junior), 3rd, Esq. (Esquire). This field is commonly not used.
（3）例如：小博士（初级），第三，绅士（绅士）。此字段通常不使用。
( 4) Address lines must be filled in the order line1, then line2, and last line3.
（4）必须在订单第1行、第2行和最后一行3中填写地址行。
( 5) 2 characters are the minimum for the US and Canada, other countries may require longer fields. For the US use 2 character US Postal state abbreviation.
（5）美国和加拿大至少需要2个字符，其他国家可能需要更长的字段。对于美国，使用2个字符的美国邮政州缩写。
( 6) Minimum field lengths for Postal Code will vary based on international market served. Use 5 character or 5+4 ZIP for the US and 6 character postal code for Canada. The size given, 14, is believed to be the maximum required anywhere in the world.
（6）邮政编码的最小字段长度将根据所服务的国际市场而有所不同。美国使用5个字符或5+4个邮政编码，加拿大使用6个字符的邮政编码。给出的尺寸为14，据信是世界上任何地方所需的最大尺寸。
( 7) Use [ISO 3166] standard two letter codes. See <http://www.din.de/gremien/nas/nabd/iso3166ma/index.html> for country names.
（7）使用[ISO 3166]标准双字母代码。看<http://www.din.de/gremien/nas/nabd/iso3166ma/index.html>国家名称。
( 8) 10 digits are the minimum for numbers local to the North American Numbering Plan (<http://www.nanpa.com>: US, Canada and a number of smaller Caribbean and Pacific nations (but not Cuba)), other countries may require longer fields. Telephone numbers are complicated by differing international access codes, variant punctuation of area/city codes within countries, confusion caused by the fact that the international access code in the NANP region is usually the same as the "country code" for that area (1), etc. It will probably be necessary to use heuristics or human examination based on the telephone number and addresses given to figure out how to actually call a customer. It is recommend that an "x" be placed before extension numbers.
（8）北美编号计划本地编号的最小位数为10位(<http://www.nanpa.com>：美国、加拿大和一些较小的加勒比和太平洋国家（但不是古巴），其他国家可能需要更长的油田。不同的国际接入码、不同国家/地区/城市代码的标点符号、NANP地区的国际接入码通常与该地区的“国家代码”相同（1）这一事实造成的混乱使电话号码变得复杂，等。可能有必要根据给定的电话号码和地址使用启发式或人工检查，以确定如何实际呼叫客户。建议在分机号码前加上“x”。
( 9) For example: jsmith@example.com
（9）例如：jsmith@example.com
(10) The name of the cardholder.
（10） 持卡人的姓名。
(11) Use the first 4 letters of the association name:
（11） 使用协会名称的前4个字母：
AMER American Express BANK Bankcard (Australia) DC DC (Japan) DINE Diners Club DISC Discover JCB JCB MAST Mastercard NIKO Nikos (Japan) SAIS Saison (Japan) UC UC (Japan) UCAR UCard (Taiwan) VISA Visa
美国运通银行银行卡（澳大利亚）DC DC DC（日本）DINE Diners Club DISC DISC Discover JCB JCB MAST Mastercard NIKO NIKO Nikos（日本）SAIS Saison（日本）UC UC UC（日本）UCAR UCard（台湾）VISA
(12) Includes the check digit at end but no spaces or hyphens [ISO 7812]. The Min given, 19, is the longest number permitted under the ISO standard.
（12） 在末尾包含校验位，但不包含空格或连字符[ISO 7812]。给出的最小值19是ISO标准允许的最长数字。
(13) An additional cardholder verification number printed on the card (but not embossed or recorded on the magnetic stripe) such as American Express' CIV, MasterCard's CVC2, and Visa's CVV2 values.
（13） 打印在卡上的额外持卡人验证号（但不浮雕或记录在磁条上），如美国运通的CIV、万事达卡的CVC2和Visa的CVV2值。
(14) The day of the month. Values: 1-31. A leading zero is ignored so, for example, 07 is valid for the seventh day of the month.
（14） 一个月的哪一天。数值：1-31。前导零将被忽略，因此，例如，07在一个月的第七天有效。
(15) The month of the year. Jan - 1, Feb - 2, March - 3, etc.; Values: 1-12. A leading zero is ignored so, for example, 07 is valid for July.
（15） 一年中的月份。1月1日、2月2日、3月3日等。；数值：1-12。前导零被忽略，因此，例如，07在7月份有效。
(16) The value in the wallet cell is always four digits, e.g., 1999, 2000, 2001, ...
（16） 钱包单元格中的值始终为四位数字，例如，1999、2000、2001。。。
(17) A space separated list of protocols available in connection with the specified card. Initial list of case insensitive tokens:
（17） 与指定卡相关的可用协议的空格分隔列表。不区分大小写令牌的初始列表：
none set setcert iotp echeck simcard phoneid
无设置setcert iotp echeck simcard phoneid
"Set" indicates usable with SET protocol (i.e., is in a SET wallet) but does not have a SET certificate. "Setcert" indicates same but does have a set certificate. "iotp" indicates the IOTP protocol [RFC 2801] is supported at the customer. "echeck" indicates that the eCheck protocol [eCheck] is supported at the customer. "simcard" indicates use the transaction instrument built into a Cellphone subscriber for identification. "phoneid" indicates use the transaction instrument of a phone bill instrument. "None" indicates that automatic field fill is operating but there is no SET wallet or the card is not entered in any SET wallet.
“Set”表示可用于Set协议（即，在Set钱包中），但没有Set证书。“Setcert”表示相同，但有一套证书。“iotp”表示客户支持iotp协议[RFC 2801]。“echeck”表示客户支持echeck协议[echeck]。“simcard”表示使用手机用户内置的交易工具进行识别。“phoneid”表示使用电话账单工具的交易工具。“无”表示正在运行自动字段填充，但没有设置钱包或卡未输入任何设置钱包。
(18) A unique order ID generated by the consumer software.
（18） 消费者软件生成的唯一订单ID。
(19) The user ID and password fields are used in cases where the user has a pre-established account with the merchant.
（19） 用户ID和密码字段用于用户与商户预先建立帐户的情况。
(20) URI indicating version of this set of fields. Usually a hidden field. Equal to "http://www.ecml.org/version/1.1" for this version.
（20） 表示这组字段的版本的URI。通常是一个隐藏的字段。等于“http://www.ecml.org/version/1.1“对于此版本。
(21) A string to identify the source and version of the form fill software that is acting on behalf of the user. Should contain company and/or product name and version. Example "Wallets Inc., SuperFill, v42.7". Usually a hidden field.
（21）一个字符串，用于标识代表用户运行的表单填写软件的源和版本。应包含公司和/或产品名称和版本。示例“钱包公司，SuperFill，v42.7”。通常是一个隐藏的字段。
(22) A flag to indicate that this web-page/aggregate is the final one for this transaction. Usually a hidden field.
（22）一个标志，指示此网页/聚合是此交易的最终网页/聚合。通常是一个隐藏的字段。
(23) Merchant domain name such as www.merchant.example. This is usually a hidden field.
（23）商户域名，如www.Merchant.example。这通常是一个隐藏字段。
(24) Gateway transaction processor who is actually accepting the payment on behalf of the merchant in home domain such as www.processor.example. This is usually a hidden field.
（24）网关交易处理者，代表商户在主域（如www.processor.example）中实际接受付款。这通常是一个隐藏字段。
(25) A Transaction identification string whose format is specific to the processor. This is usually a hidden field.
（25）一种事务标识字符串，其格式特定于处理器。这通常是一个隐藏字段。
(26) A URL that can be invoke to inquire about the transaction. This is usually a hidden field.
（26）可以调用以查询交易的URL。这通常是一个隐藏字段。
(27) The amount of the transaction in ISO currency format. This is two integer numbers with a period in between but no other currency marks (such as a $ dollar sign). This is usually a hidden field.
（27）ISO货币格式的交易金额。这是两个整数，中间有一个句点，但没有其他货币标记（如美元符号）。这通常是一个隐藏字段。
(28) This is the three letter ISO currency code. For example, for US dollars it is USD. This is usually a hidden field.
（28）这是三个字母的ISO货币代码。例如，美元是美元。这通常是一个隐藏字段。
(29) ISO Transaction date. This is usually a hidden field.
（29）ISO交易日期。这通常是一个隐藏字段。
(30) The type of the transaction (either debit or credit) if known. This is usually a hidden field.
（30）交易类型（借方或贷方），如已知。这通常是一个隐藏字段。
(31) The signature of the encoded certificate. This is usually a hidden field.
（31）编码证书的签名。这通常是一个隐藏字段。
(32) The Receipt To fields are used when the Bill To entity, location, or address and the Receipto entity, location, or address are different. For example, when using some forms of Corporate Purchasing Cards or Agent Purchasing Cards, the individual card holder would be in the Receipt To fields and the corporate or other owner would be in the Bill To fields.
（32）当收票人实体、地点或地址与收票人实体、地点或地址不同时，使用收票人字段。例如，当使用某些形式的公司采购卡或代理采购卡时，个人卡持有人将在“收货到”字段中，公司或其他所有者将在“帐单到”字段中。
The normal use of ECML in HTML is as a form with input field names identical to those given in section 2.1 above. In general, <INPUT> tags with type text, hidden, and password must be supported as must <SELECT> tags.
在HTML中，ECML的正常使用是作为一种表单，其输入字段名称与上面第2.1节中给出的名称相同。通常，必须支持带有类型文本、隐藏和密码的<INPUT>标记，就像必须<SELECT>标记一样。
Internationalization in HTML is limited. The information available with the HTML form Method as to character set and language SHOULD be used.
HTML的国际化是有限的。应使用HTML表单方法提供的有关字符集和语言的信息。
Below is an XML DTD that can be used for the XML encoding of ECML v1.1 Fields.
下面是一个XML DTD，可用于ECMLV1.1字段的XML编码。
For internationalization of [XML] ECML, use the general XML character encoding provisions, which mandate support of UTF-8 and UTF-16 and permit support of other character sets, and the xml:lang attribute which may be used to specify language information.
对于[XML]ECML的国际化，请使用通用XML字符编码规定（强制支持UTF-8和UTF-16并允许支持其他字符集）和XML:lang属性（可用于指定语言信息）。
<!-- Electronic Commerce Modeling Language 1.1 -->
<!-- Electronic Commerce Modeling Language 1.1 -->
<!ELEMENT Ecom ( #PCDATA | ShipTo | BillTo | ReceiptTo | Payment |
User | Transaction | TransactionComplete )* >
<!ATTLIST Ecom
id ID #IMPLIED
ConsumerOrderID CDATA #IMPLIED
Merchant CDATA #IMPLIED
Processor CDATA #IMPLIED
SchemaVersion ( "http://www.ecml.org/version/1.0" |
"http://www.ecml.org/version/1.1" )
#IMPLIED
WalletID CDATA #IMPLIED >
<!ELEMENT Ecom ( #PCDATA | ShipTo | BillTo | ReceiptTo | Payment |
User | Transaction | TransactionComplete )* >
<!ATTLIST Ecom
id ID #IMPLIED
ConsumerOrderID CDATA #IMPLIED
Merchant CDATA #IMPLIED
Processor CDATA #IMPLIED
SchemaVersion ( "http://www.ecml.org/version/1.0" |
"http://www.ecml.org/version/1.1" )
#IMPLIED
WalletID CDATA #IMPLIED >
<!ELEMENT ShipTo ( #PCDATA | Postal | Telecom | Online )* >
<!ATTLIST ShipTo
id ID #IMPLIED >
<!ELEMENT ShipTo ( #PCDATA | Postal | Telecom | Online )* >
<!ATTLIST ShipTo
id ID #IMPLIED >
<!ELEMENT BillTo ( #PCDATA | Postal | Telecom | Online )* >
<!ATTLIST BillTo
id ID #IMPLIED >
<!ELEMENT BillTo ( #PCDATA | Postal | Telecom | Online )* >
<!ATTLIST BillTo
id ID #IMPLIED >
<!ELEMENT ReceiptTo ( #PCDATA | Postal | Telecom | Online )* >
<!ATTLIST ReceiptTo
id ID #IMPLIED >
<!ELEMENT ReceiptTo ( #PCDATA | Postal | Telecom | Online )* >
<!ATTLIST ReceiptTo
id ID #IMPLIED >
<!ELEMENT Postal ( #PCDATA | Name | Company |
Street | City | StateProv )* >
<!ATTLIST Postal
id ID #IMPLIED
PostalCode NMTOKEN #IMPLIED
CountryCode NMTOKEN #IMPLIED >
<!ELEMENT Postal ( #PCDATA | Name | Company |
Street | City | StateProv )* >
<!ATTLIST Postal
id ID #IMPLIED
PostalCode NMTOKEN #IMPLIED
CountryCode NMTOKEN #IMPLIED >
<!ELEMENT Name EMPTY >
<!ATTLIST Name
id ID #IMPLIED
Prefix NMTOKEN #IMPLIED
First NMTOKEN #IMPLIED
<!ELEMENT Name EMPTY >
<!ATTLIST Name
id ID #IMPLIED
Prefix NMTOKEN #IMPLIED
First NMTOKEN #IMPLIED
Middle NMTOKEN #IMPLIED Last NMTOKEN #IMPLIED Suffix NMTOKEN #IMPLIED >
中间NMTOKEN#隐含最后NMTOKEN#隐含后缀NMTOKEN#隐含>
<!ELEMENT Street EMPTY >
<!ATTLIST Street
id ID #IMPLIED
Line1 CDATA #REQUIRED
Line2 CDATA #IMPLIED
Line3 CDATA #IMPLIED >
<!ELEMENT Street EMPTY >
<!ATTLIST Street
id ID #IMPLIED
Line1 CDATA #REQUIRED
Line2 CDATA #IMPLIED
Line3 CDATA #IMPLIED >
<!ELEMENT Company #PCDATA >
<!ELEMENT Company #PCDATA >
<!ELEMENT City #PCDATA >
<!ELEMENT City #PCDATA >
<!ELEMENT StateProv #PCDATA >
<!ELEMENT StateProv #PCDATA >
<!ELEMENT Telecom ( #PCDATA | Phone )* >
<!ELEMENT Telecom ( #PCDATA | Phone )* >
<!ELEMENT Phone EMPTY >
<!ATTLIST Phone
id ID #IMPLIED
Number CDATA #REQUIRED >
<!ELEMENT Phone EMPTY >
<!ATTLIST Phone
id ID #IMPLIED
Number CDATA #REQUIRED >
<!ELEMENT Online ( #PCDATA | Email )* >
<!ELEMENT Online ( #PCDATA | Email )* >
<!ELEMENT Email EMPTY >
<!ATTLIST Email
id ID #IMPLIED
Address CDATA #REQUIRED >
<!ELEMENT Email EMPTY >
<!ATTLIST Email
id ID #IMPLIED
Address CDATA #REQUIRED >
<!ELEMENT Payment Card>
<!ELEMENT Payment Card>
<!ELEMENT Card ExpDate >
<!ATTLIST Card
id ID #IMPLIED
Name CDATA #IMPLIED
Type NMTOKEN #IMPLIED
Number NMTOKEN #REQUIRED
Protocols NMTOKENS #IMPLIED
Verification NMTOKEN #IMPLIED >
<!ELEMENT Card ExpDate >
<!ATTLIST Card
id ID #IMPLIED
Name CDATA #IMPLIED
Type NMTOKEN #IMPLIED
Number NMTOKEN #REQUIRED
Protocols NMTOKENS #IMPLIED
Verification NMTOKEN #IMPLIED >
<!ELEMENT ExpDate EMPTY >
<!ATTLIST ExpDate
id ID #IMPLIED
Day NMTOKEN #IMPLIED
Month NMTOKEN #REQUIRED
Year NMTOKEN #REQUIRED >
<!ELEMENT ExpDate EMPTY >
<!ATTLIST ExpDate
id ID #IMPLIED
Day NMTOKEN #IMPLIED
Month NMTOKEN #REQUIRED
Year NMTOKEN #REQUIRED >
<!ELEMENT User ( #PCDATA | UserID | Password )* >
<!ATTLIST User
id ID #IMPLIED >
<!ELEMENT User ( #PCDATA | UserID | Password )* >
<!ATTLIST User
id ID #IMPLIED >
<!ELEMENT UserID #PCDATA >
<!ELEMENT UserID #PCDATA >
<!ELEMENT Password #PCDATA >
<!ELEMENT Password #PCDATA >
<!ELEMENT Transaction ( #PCDATA | TransactionID | Inquiry |
TransDate | Signature )* >
<!ATTLIST Transaction
id ID #IMPLIED
Amount CDATA #IMPLIED
Currency NMTOKEN #IMPLIED
Type NMTOKEN #IMPLIED >
<!ELEMENT Transaction ( #PCDATA | TransactionID | Inquiry |
TransDate | Signature )* >
<!ATTLIST Transaction
id ID #IMPLIED
Amount CDATA #IMPLIED
Currency NMTOKEN #IMPLIED
Type NMTOKEN #IMPLIED >
<!ELEMENT TransactionComplete EMPTY>
<!ELEMENT TransactionComplete EMPTY>
To conform to this document, the field names must be structured and named as close to the structure and naming listed in Section 2 above as permitted by the transaction protocol in use. Note: this does not impose any restriction on the user visible labeling of fields, just on their names as used in communication.
为符合本文件的要求，字段名称的结构和名称必须与上文第2节中所列的结构和名称接近，并符合所用交易协议的要求。注意：这不会对字段的用户可见标签施加任何限制，只对通信中使用的字段名称施加任何限制。
There is no necessary implication as to the order or manner of presentation. Some merchants may wish to ask for more information, some less by omitting fields. Some merchants may ask for the information they want in one interaction or web page, others may ask for parts of the information at different times in multiple interactions or different web pages. For example, it is common to ask for "ship to" information earlier, so shipping cost can be computed, before the payment method information. Some merchants may require that all the information they request be provided while other make much information optional. Etc.
对于呈现的顺序或方式没有必要的暗示。有些商家可能希望获得更多信息，有些则希望通过省略字段来获得更少的信息。一些商家可能会在一个互动或网页中要求提供他们想要的信息，其他商家可能会在多个互动或不同网页的不同时间要求提供部分信息。例如，通常会更早地要求提供“收货方”信息，因此可以在支付方式信息之前计算运费。一些商家可能要求提供他们要求的所有信息，而另一些商家则要求提供更多可选信息。等
There is no way with Version 1.0 or 1.1 of ECML to indicate what fields the merchant considers mandatory. From the point of view of customer software, all fields are optional to complete. However, the merchant may give an error or re-present a request for information if some field it requires is not completed, just as it may if a field is completed in a manner it considers erroneous.
ECML版本1.0或1.1无法说明商户认为哪些字段是必填字段。从客户软件的角度来看，所有字段都是可选的。但是，如果商户要求的某个字段未填写，则商户可能会给出错误或重新提交信息请求，正如商户可能会以其认为错误的方式填写某个字段一样。
It is entirely up to the merchant when and which, if any, of the merchant to consumer fields it presents.
这完全取决于商户何时以及在何种情况下呈现商户对消费者字段（如有）。
There are a variety of methods of communication possible between the customer and the merchant by which the merchant can indicate what fields they want that the consumer can provide. Probably the easiest to use for currently deployed software is as fields in an [HTML] form (see section 2.2). Other possibilities are to use the IOTP Authenticate transaction [RFC 2801], an [XML] exchange, or proprietary protocols.
客户和商户之间可能存在多种通信方法，商户可以通过这些方法指示消费者可以提供他们想要的字段。对于当前部署的软件，最容易使用的可能是[HTML]表单中的as字段（参见第2.2节）。其他可能性是使用IOTP身份验证事务[RFC 2801]、[XML]交换或专有协议。
User action or the appearance of the Ecom_SchemaVersion field are examples of triggers that could be used to initiate a facility capable of filling in fields. Because some wallets may require user activation, there should be at least one user visible Ecom field on every page with any Ecom fields present that are to be filled in. It is also REQUIRED that the Ecom_SchemaVersion field, which is usually a hidden field, be included on every web page that has any Ecom fields.
用户操作或Ecom_SchemaVersion字段的出现是可以用来启动能够填充字段的工具的触发器的示例。由于某些钱包可能需要用户激活，因此每个页面上至少应有一个用户可见的Ecom字段，其中包含要填写的任何Ecom字段。还需要在每个包含任何Ecom字段的网页上包含Ecom_SchemaVersion字段，该字段通常是一个隐藏字段。
Because web pages can load very slowly, it may not be clear to an automated field fill-in function when it is finished filling in fields on a web page. For this reason, it is recommended that the Ecom_SchemaVersion field be the last Ecom field on a web page.
由于网页的加载速度可能非常慢，因此在完成填写网页上的字段时，自动字段填写功能可能不清楚。因此，建议将Ecom_SchemaVersion字段作为网页上的最后一个Ecom字段。
Merchant requests for information can extend over several interactions or web pages. Without further provision, a facility could either require re-starting on each page or possibly violate or appear to violate privacy by continuing to fill in fields for pages beyond with end of the transaction with a particular merchant. For this reason the Ecom_TransactionComplete field, which is normally hidden, is provided. It is recommended that it appear on the last interaction or web page involved in a transaction, just before an Ecom_SchemaVersion field, so that multi-web-page automated field fill in logic could know when to stop if it chooses to check for this field.
商户对信息的请求可以扩展到多个交互或网页。在没有进一步规定的情况下，设施可能需要在每个页面上重新启动，或者可能违反或似乎违反隐私，在与特定商户的交易结束后继续填写页面字段。因此，提供了通常隐藏的Ecom_TransactionComplete字段。建议它出现在事务中涉及的最后一次交互或网页上，就在Ecom_SchemaVersion字段之前，这样多网页自动字段填充逻辑就可以知道如果选择检查此字段，何时停止。
An example HTML form might be as follows:
示例HTML表单可能如下所示：
<HTML>
<HEAD>
<title> eCom Fields Example </title>
</HEAD>
<BODY>
<FORM action="http://ecom.example.com" method="POST">
Please enter card information:
<p>Your name on the card
<HTML>
<HEAD>
<title> eCom Fields Example </title>
</HEAD>
<BODY>
<FORM action="http://ecom.example.com" method="POST">
Please enter card information:
<p>Your name on the card
<INPUT type="text" name="Ecom_Payment_Card_Name" SIZE=40>
<br>The card number
<INPUT type="text" name="Ecom_Payment_Card_Number" SIZE=19>
<br>Expiration date (MM YY)
<INPUT type="text" name="Ecom_Payment_Card_ExpDate_Month" SIZE=2>
<INPUT type="text" name="Ecom_Payment_Card_ExpDate_Year" SIZE=4>
<INPUT type="hidden" name="Ecom_Payment_Card_Protocol">
<INPUT type="hidden" name="Ecom_SchemaVersion"
value="http://www.ecml.org/version/1.1">
<br>
<INPUT type="submit" value="submit"> <INPUT type="reset">
</FORM>
</BODY>
</HTML>
<INPUT type="text" name="Ecom_Payment_Card_Name" SIZE=40>
<br>The card number
<INPUT type="text" name="Ecom_Payment_Card_Number" SIZE=19>
<br>Expiration date (MM YY)
<INPUT type="text" name="Ecom_Payment_Card_ExpDate_Month" SIZE=2>
<INPUT type="text" name="Ecom_Payment_Card_ExpDate_Year" SIZE=4>
<INPUT type="hidden" name="Ecom_Payment_Card_Protocol">
<INPUT type="hidden" name="Ecom_SchemaVersion"
value="http://www.ecml.org/version/1.1">
<br>
<INPUT type="submit" value="submit"> <INPUT type="reset">
</FORM>
</BODY>
</HTML>
After all of the pages are submitted, the merchant will reply with a confirmation page informing both the user and the wallet that the transaction is complete.
提交所有页面后，商户将回复确认页面，通知用户和钱包交易已完成。
<HTML>
<HEAD>
<title> eCom Transaction Complete Example </title>
</HEAD>
<BODY>
<FORM>
Thank you for your order. It will be shipped in several days.
<INPUT type="hidden" name="Ecom_Merchant" value="www.merchant.example">
<INPUT type="hidden" name ="Ecom_Processor"
value="www.processor.example">
<INPUT type="hidden" name="Ecom_Transaction_ID" value="EF123456">
<INPUT type="hidden" name="Ecom_Transaction_Inquiry"
value="http://www.merchant.example/cgi-bin/inquire?ID=EF123456">
<INPUT type="hidden" name="Ecom_Transaction_Amount" value="789.00">
<INPUT type="hidden" name="Ecom_Transaction_Currency" value="USD">
<INPUT type="hidden" name="Ecom_Transaction_Date" value="July 14 2000">
<INPUT type="hidden" name="Ecom_Transaction_Type" value="credit">
<INPUT type="hidden" name="Ecom_Transaction_Signature"
value="ig6rh4;;20dfna00s34hj10s--s-45j30-22z92l-frwds-85">
<INPUT type="hidden" name="Ecom_TransactionComplete">
<INPUT type="hidden" name="Ecom_SchemaVersion"
value="http://www.ecml.org/version/1.1">
</FORM>
</BODY>
</HTML>
<HTML>
<HEAD>
<title> eCom Transaction Complete Example </title>
</HEAD>
<BODY>
<FORM>
Thank you for your order. It will be shipped in several days.
<INPUT type="hidden" name="Ecom_Merchant" value="www.merchant.example">
<INPUT type="hidden" name ="Ecom_Processor"
value="www.processor.example">
<INPUT type="hidden" name="Ecom_Transaction_ID" value="EF123456">
<INPUT type="hidden" name="Ecom_Transaction_Inquiry"
value="http://www.merchant.example/cgi-bin/inquire?ID=EF123456">
<INPUT type="hidden" name="Ecom_Transaction_Amount" value="789.00">
<INPUT type="hidden" name="Ecom_Transaction_Currency" value="USD">
<INPUT type="hidden" name="Ecom_Transaction_Date" value="July 14 2000">
<INPUT type="hidden" name="Ecom_Transaction_Type" value="credit">
<INPUT type="hidden" name="Ecom_Transaction_Signature"
value="ig6rh4;;20dfna00s34hj10s--s-45j30-22z92l-frwds-85">
<INPUT type="hidden" name="Ecom_TransactionComplete">
<INPUT type="hidden" name="Ecom_SchemaVersion"
value="http://www.ecml.org/version/1.1">
</FORM>
</BODY>
</HTML>
The information called for by many of these fields is sensitive and should be secured if being sent over the public Internet or through other channels where it can be observed. Mechanisms for such protection are not specified herein but channel encryption such as TLS/SSL [RFC 2246] or IPSec [RFC 2411] would be appropriate in many cases.
其中许多领域所要求的信息都是敏感的，如果通过公共互联网或其他可以观察到的渠道发送，则应加以保护。本文未指定用于此类保护的机制，但诸如TLS/SSL[RFC 2246]或IPSec[RFC 2411]之类的信道加密在许多情况下是合适的。
User control over release of such information is needed to protect the user's privacy.
需要用户控制此类信息的发布，以保护用户的隐私。
A wallet that is installed on a shared or public terminal should be configurable such that the ECML memory of address and other contact information is fully disabled. This is vital to protect the privacy of library patrons, students, and customers using public terminals, and children who might, for example, use a form on a public terminal without realizing that their information is being stored.
安装在共享或公共终端上的钱包应可配置为完全禁用地址和其他联系信息的ECML存储器。这对于保护使用公共终端的图书馆用户、学生和客户以及可能（例如）在公共终端上使用表单而未意识到其信息正在存储的儿童的隐私至关重要。
When contact information is stored, the operator should have an option to protect the information with a password, without which the information might be unavailable, even to someone who has access to the file(s) in which it is being stored. This would also allow for a convenient method for multiple people to use their own ECML information from the same browser.
存储联系信息时，操作员应选择使用密码保护信息，没有密码，信息可能不可用，即使是对存储该信息的文件具有访问权限的人。这也为多人使用同一浏览器中自己的ECML信息提供了一种方便的方法。
Any multi-web-page or other multi-aggregate field fill in or data provision mechanism should check for the Ecom_TransactionComplete field and cease automated fill when it is encountered until fill is further authorized.
任何多网页或其他多聚合字段填写或数据提供机制应检查Ecom_TransactionComplete字段，并在遇到自动填写时停止自动填写，直到进一步授权填写。
References
工具书类
[eCheck] <http://www.echeck.org>
[eCheck] <http://www.echeck.org>
[HTML] HTML 3.2 Reference Specification <http://www.w3.org/TR/REC-html32.html>, D. Raggett, January 1997.
[HTML]HTML3.2参考规范<http://www.w3.org/TR/REC-html32.html>，D.Raggett，1997年1月。
[IANA] Internet Assigned Numbers Authority, Official Names for Character Sets, ed. Keld Simonsen et al. <ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets>.
[IANA]互联网分配号码管理局，字符集的官方名称，ed.Keld Simonsen等人<ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets>.
[ISO 3166] Codes for the representation of names of countries,
<http://www.din.de/gremien/nas/nabd/iso3166ma>
[ISO 3166] Codes for the representation of names of countries,
<http://www.din.de/gremien/nas/nabd/iso3166ma>
[ISO 7812] "Identification card - Identification of issuers - Part 1: Numbering system".
[ISO 7812]“识别卡-发卡机构识别-第1部分：编号系统”。
[RFC 1766] Alvestrand, H., "Tags for the Identification of Languages", BCP 47, RFC 3066, January 2001.
[RFC 1766]Alvestrand，H.，“语言识别标签”，BCP 47，RFC 3066，2001年1月。
[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 2411] Thayer, R., Doraswany, N. and R. Glenn, "IP Security: Document Roadmap", RFC 2411, November 1998.
[RFC 2411]Thayer，R.，Doraswany，N.和R.Glenn，“IP安全：文档路线图”，RFC 2411，1998年11月。
[RFC 2706] Eastlake, D. and T. Goldstein, "ECML v1: Field Names for E-Commerce", RFC 2706, September 1999.
[RFC 2706]Eastlake，D.和T.Goldstein，“ECML v1：电子商务的字段名”，RFC 2706，1999年9月。
[RFC 2801] Burdett, D., "Internet Open Trading Protocol - IOTP Version 1.0", RFC 2801, April 2000.
[RFC 2801]Burdett，D.，“互联网开放交易协议-IOTP版本1.0”，RFC 2801，2000年4月。
[SET] Secure Electronic Transaction,
<http://www.setco.org/set_specifications.html>
[SET] Secure Electronic Transaction,
<http://www.setco.org/set_specifications.html>
[XML] Extensible Markup Language (XML) 1.0 (Second Edition), <http://www.w3.org/TR/REC-xml>, T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler.
[XML]可扩展标记语言（XML）1.0（第二版）<http://www.w3.org/TR/REC-xml>，T.Bray，J.Paoli，C.M.Sperberg McQueen，E.Maler。
Appendix: Changes from ECML 1.0
附录：ECML 1.0的变更
ECML 1.0 is documented in [RFC 2706].
[RFC 2706]中记录了ECML 1.0。
(1) Fields added for consumer to merchant transmission as listed below. * indicated multiple values. Adding fields is a backward compatible change.
(1) 为用户到商户传输添加的字段如下所示。*指示多个值。添加字段是向后兼容的更改。
Ecom_*_Postal_Company Ecom_User_ID Ecom_User_Password Ecom_WalletID
Ecom\uU*\ u邮政\u公司Ecom\u用户\u ID Ecom\u用户\u密码Ecom\u WalletID
(2) Change Ecom_SchemaVersion field value to "http://www.ecml.org/version/1.1".
(2) 将Ecom_SchemaVersion字段值更改为“http://www.ecml.org/version/1.1".
(3) Addition of XML DTD.
(3) 添加XML DTD。
(4) Add "iotp", "echeck", "simcard", and "phoneid" as allowed tokens in Ecom_Payment_Card_Protocol.
(4) 添加“iotp”、“echeck”、“simcard”和“phoneid”作为Ecom_支付卡协议中允许的令牌。
(5) Specify that a leading zero is permitted in day and month number fields.
(5) 指定允许在日数和月数字段中使用前导零。
(6) Change "Security Considerations" section to "Security and Privacy Considerations" and add material.
(6) 将“安全注意事项”部分更改为“安全和隐私注意事项”，并添加材料。
(7) Add internationalization material to HTML and XML subsections of Section 2.
(7) 在第2节的HTML和XML小节中添加国际化材料。
(8) Enumerate HTML form elements that must be supported (Section 2.2) including SELECT.
(8) 枚举必须支持的HTML表单元素（第2.2节），包括SELECT。
(9) Add more credit card brand codes.
(9) 添加更多信用卡品牌代码。
(10) Add fields for merchant to consumer transmissions as follows:
（10） 添加商户到消费者传输字段，如下所示：
Ecom_Merchant Ecom_Processor Ecom_Transaction_*
Ecom_商户Ecom_处理器Ecom_交易_*
Authors' Addresses
作者地址
Donald E. Eastlake, 3rd Motorola, M2-450 20 Cabot Boulevard Mansfield, MA 02048
Donald E.Eastlake，第三摩托罗拉，马萨诸塞州曼斯菲尔德卡博特大道20号M2-450 02048
Phone: +1-508-261-5434
Fax: +1-508-261-4447
EMail: Donald.Eastlake@motorola.com
Phone: +1-508-261-5434
Fax: +1-508-261-4447
EMail: Donald.Eastlake@motorola.com
Ted Goldstein Brodia 221 Main Street, Suite 1530 San Francisco, CA 94105 USA
Ted Goldstein Brodia大街221号，CA旧金山1530套房94105美国
Phone: +1 415-495-3100 x222
Fax: +1 415-495-3177
EMail: tgoldstein@brodia.com
Phone: +1 415-495-3100 x222
Fax: +1 415-495-3177
EMail: tgoldstein@brodia.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
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编辑功能的资金目前由互联网协会提供。