Network Working Goup D. Eastlake
Request for Comments: 2706 IBM
Category: Informational T. Goldstein
Brodia
October 1999
Network Working Goup D. Eastlake
Request for Comments: 2706 IBM
Category: Informational T. Goldstein
Brodia
October 1999
ECML v1: Field Names for E-Commerce
ECMLV1：电子商务的字段名
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 (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
IESG Note
IESG注释
This document is the output of a vendor consortium, and is not the output of an IETF Working Group. Implementors of this specification are warned that this data model is heavily biased toward conventions used in the United States, and the English language. As such it is unlikely to be suitable for international or multilingual use in the global Internet.
本文件是供应商联盟的输出，不是IETF工作组的输出。本规范的实施者受到警告，该数据模型严重偏向于美国和英语中使用的约定。因此，它不太可能适用于全球互联网中的国际或多语言使用。
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.
客户通常需要在互联网商户网站上输入大量信息，以完成购买或其他交易，尤其是第一次去那里时。一组标准的信息字段被定义为电子商务建模语言（ECML）的第一个版本，因此该任务可以更容易地自动化，例如通过可以填充字段的钱包软件。即使对于手动数据输入案例，如果大量客户采用这些标准字段，客户也不会因不同的商户站点而感到困惑。
Acknowledgements
致谢
The following persons, in alphabetic order, contributed substantially to the material herein:
以下人员按字母顺序对本文件中的材料做出了重大贡献：
George Burne, Trintech
乔治·伯恩，Trintech
Joe Coco, Microsoft
乔·科科，微软
Kevin Weller, Visa
凯文·韦勒，维萨
Table of Contents
目录
1. Introduction................................................2
1.1 Background.................................................2
1.2 Relationship to Other Standards............................3
1.3 Areas Deferred to Future Versions..........................4
2. Using The Fields............................................4
2.1 Presentation of the Fields.................................4
2.2 Methods and Flow of Setting the Fields.....................5
2.3 HTML Example...............................................6
3. Field Definitions...........................................7
4. End Notes...................................................9
5. Security Considerations....................................10
References....................................................11
Authors' Addresses............................................12
Full Copyright Statement......................................13
1. Introduction................................................2
1.1 Background.................................................2
1.2 Relationship to Other Standards............................3
1.3 Areas Deferred to Future Versions..........................4
2. Using The Fields............................................4
2.1 Presentation of the Fields.................................4
2.2 Methods and Flow of Setting the Fields.....................5
2.3 HTML Example...............................................6
3. Field Definitions...........................................7
4. End Notes...................................................9
5. Security Considerations....................................10
References....................................................11
Authors' Addresses............................................12
Full Copyright Statement......................................13
Today, numerous merchants are successfully conducting business on the Internet using HTML-based forms. The data formats used in these forms varies 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 complete a merchant's form every time. Digital wallets that fill forms have been successfully built into browsers, 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>) Version 1 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>）第1版为网络商家提供了一套简单的指南，使来自多个供应商的电子钱包能够填写他们的网络表单。最终的结果是，更多的消费者会发现网上购物很容易，也很吸引人。
The set of fields documented herein was developed by the Wallet/Merchant Standards Alliance (www.ecml.org) which now includes, in alphabetic order, the following:
此处记录的字段集由钱包/商户标准联盟（www.ecml.org）开发，现在按字母顺序包括以下内容：
American Express (www.americanexpress.com) AOL (www.aol.com) Brodia (www.brodia.com) Compaq (www.compaq.com) CyberCash (www.cybercash.com) Discover (www.discovercard.com) FSTC (www.fstc.org) IBM (www.ibm.com) Mastercard (www.mastercard.com) Microsoft (www.microsoft.com) Novell (www.novell.com) SETCo (www.setco.org) Sun Microsystems (www.sun.com) Trintech (www.trintech.com) Visa (www.visa.com)
美国运通（www.americanexpress.com）美国在线（www.AOL.com）Brodia（www.Brodia.com）Compaq（www.Compaq.com）CyberCash（www.CyberCash.com）Discover（www.discovercard.com）FSTC（www.FSTC.org）IBM（www.IBM.com）万事达卡（www.Mastercard.com）微软（www.Microsoft.com）Novell（www.Novell.com）SETCo（www.SETCo.org）太阳微系统（www.Sun.com）Trintech（www.Trintech.com）Visa（www.Visa.com）
The fields are derived from and consistent with the W3C P3P base data schema at
这些字段派生自W3C P3P基本数据模式，并与该模式保持一致
<http://www.w3.org/TR/WD-P3P/basedata.html>.
<http://www.w3.org/TR/WD-P3P/basedata.html>.
ECML Version 1 is not a replacement or alternative to SSL/TLS [RFC 2246], SET [SET], XML [XML], or IOTP [IOTP]. These are important standards that provide functionality such as non-repudiatable transactions, automatable payment scheme selection, and smart card support.
ECML版本1不是SSL/TLS[RFC 2246]、SET[SET]、XML[XML]或IOTP[IOTP]的替代品或替代品。这些是提供不可否认交易、自动支付方案选择和智能卡支持等功能的重要标准。
ECML may be used with any payment mechanism. It simply allows a merchant to publish consistent simple web forms.
ECML可与任何支付机制一起使用。它只允许商家发布一致的简单web表单。
Multiple wallets and multiple merchants plan to interoperably support ECML. This is an open standard. ECML is designed to be simple.
多个钱包和多个商家计划互操作支持ECML。这是一个开放的标准。ECML设计得很简单。
Version 1 of the project adds no new technology to the web. A merchant can adopt ECML and gain the support of these multiple Wallets by making very simple changes to the HTML pages that they currently use to support their customers. Use of ECML requires no license.
该项目的第1版没有向web添加新技术。商家可以采用ECML，并通过对当前用于支持其客户的HTML页面进行非常简单的更改来获得这些多钱包的支持。使用ECML不需要许可证。
Standardization of information fields transmitted from the merchant to the consumer, considerations for business purchasing cards, non-card payment mechanisms, wallet activation, privacy related mechanisms, additional payment mechanisms, and any sort of "negotiation" were among the areas deferred to consideration in future versions. Hidden or other special fields were minimized. The primary target was North American consumer to merchant electronic commerce.
从商户向消费者传输的信息字段的标准化、商业购买卡的考虑因素、非卡支付机制、钱包激活、隐私相关机制、附加支付机制以及任何形式的“协商”都属于未来版本中推迟考虑的领域。隐藏字段或其他特殊字段被最小化。主要目标是北美消费者对商家的电子商务。
To conform to this document, the field names shall be as listed in section 3 below. Note: this does not impose any restriction on the user visible labeling of fields, just on their names as used in communication with the merchant.
为符合本文件要求，字段名称应如下文第3节所列。注：这不会对字段的用户可见标签施加任何限制，仅对与商户通信时使用的字段名称施加限制。
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 HTML form on one web page, others may ask for parts of the information at different times on different 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.
对于呈现的顺序或方式没有必要的暗示。有些商家可能希望获得更多信息，有些则希望通过省略字段来获得更少的信息。一些商家可能会在一个网页上以一种HTML格式要求提供他们想要的信息，其他商家可能会在不同的时间在不同的网页上要求提供部分信息。例如，通常会更早地要求提供“收货方”信息，因此可以在支付方式信息之前计算运费。一些商家可能要求提供他们要求的所有信息，而另一些商家则要求提供更多可选信息，等等。
There is no way with version 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无法说明商户认为哪些字段是必填字段。从客户软件的角度来看，所有字段都是可选的。但是，如果商户要求的某个字段未填写，则商户可能会给出错误或重新提交信息请求，正如商户可能会以其认为错误的方式填写某个字段一样。
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 [HTML4.0] form. Other possibilities are to use the W3C P3P protocol or the IOTP Authenticate transaction [IOTP].
客户和商户之间可能存在多种通信方法，商户可以通过这些方法指示消费者可以提供他们想要的字段。对于当前部署的软件，最容易使用的可能是HTML[HTML4.0]表单中的as字段。其他可能性是使用W3C P3P协议或IOTP身份验证事务[IOTP]。
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. It is 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_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 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 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 in HTML 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
<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.0">
<br>
<INPUT type="submit" value="submit"> <INPUT type="reset">
</FORM>
</BODY>
</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
<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.0">
<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_TransactionComplete">
<INPUT type="hidden" name="Ecom_SchemaVersion"
value="http://www.ecml.org/version/1.0">
</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_TransactionComplete">
<INPUT type="hidden" name="Ecom_SchemaVersion"
value="http://www.ecml.org/version/1.0">
</FORM>
</BODY>
</HTML>
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 consumer to merchant transmission mechanisms may use this to request and send aggregates, such as Ecom_Payment_Card_ExpDate to encompass all the date components or Ecom_ShipTo to encompass all the ship to components that the consumer is willing to provide. The marshalling and unmarshalling of the components of such aggregates depends on the data transfer protocol used.
下面列出了字段以及允许的最小数据输入大小。请注意，这些字段是按嵌入的下划线（“389;”）字符所指示的层次结构组织的。适当的消费者到商户传输机制可使用此功能请求和发送聚合，例如，Ecom_支付卡_ExpDate包含所有日期组件，或Ecom_ShipTo包含消费者愿意提供的所有船到组件。此类聚合组件的编组和解编组取决于所使用的数据传输协议。
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”的地区交易的商户显然必须允许更长的数据输入。但是，在某些情况下，有一个最大大小是有意义的，在这种情况下，它会记录在字段的注释中。
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 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)
收货方名称收货方名称收货方名称前缀4（1）收货方名称收货方名称收货方名称前15收货方名称收货方名称收货方名称中15（2）收货方姓氏收货方名称收货方名称后15收货方名称后缀收货方名称收货方名称后4（3）收货方街道1号线收货方街道1号线收货方名称收货方名称后20（4）船舶至街道线路2经济地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理地理位置发送至电话Ecom_发送至电话号码10（8）发送至电子邮件Ecom_发送至电话号码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 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) bill to city Ecom_BillTo_Postal_City 22
账单标题Ecom_bill to Postal_Name_前缀4（1）账单名字Ecom_bill to Postal_Name_前15账单中间名Ecom_bill to Postal_Name_中间名15（2）账单姓氏Ecom_bill to Postal_Name_最后15账单名字后缀Ecom_bill to Postal_Name_后缀4（3）账单街道线1 Ecom_bill to Postal_街道线120（4）账单至街道行2账单至邮政局账单至街道行20（4）账单至街道行3账单至邮政局账单至街道行20（4）账单至城市账单至邮政局账单至城市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)
账单到州/省经济账单到邮政账单到州Prov 2（5）账单到邮政编码经济账单到邮政编码14（6）账单到国家经济账单到邮政编码2（7）账单到电话经济账单到电信电话号码10（8）账单到电子邮件经济账单到在线电子邮件40（9）
receiptTo title Ecom_ReceiptTo_Postal_Name_Prefix 4 ( 1) receiptTo first name Ecom_ReceiptTo_Postal_Name_First 15 receiptTo middle name Ecom_ReceiptTo_Postal_Name_Middle 15 ( 2) receiptTo last name Ecom_ReceiptTo_Postal_Name_Last 15 receiptTo name suffix Ecom_ReceiptTo_Postal_Name_Suffix 4 ( 3) receiptTo street line1 Ecom_ReceiptTo_Postal_Street_Line1 20 ( 4) receiptTo street line2 Ecom_ReceiptTo_Postal_Street_Line2 20 ( 4) receiptTo street line3 Ecom_ReceiptTo_Postal_Street_Line3 20 ( 4) receiptTo city Ecom_ReceiptTo_Postal_City 22 receiptTo state/province Ecom_ReceiptTo_Postal_StateProv 2 ( 5) receiptTo postal code Ecom_ReceiptTo_Postal_PostalCode 14 ( 6) receiptTo country Ecom_ReceiptTo_Postal_CountryCode 2 ( 7) receiptTo phone Ecom_ReceiptTo_Telecom_Phone_Number 10 ( 8) receiptTo email Ecom_ReceiptTo_Online_Email 40 ( 9)
收款人姓名收款人姓名前缀4（1）收款人姓名收款人姓名收款人姓名首15收款人中名收款人姓名收款人中名收款人姓名收款人姓氏收款人姓名收款人姓氏收款人姓氏收款人姓氏收款人姓名后缀4（3）第20（4）条街道第20（4）条街道第2条街道第20（4）条街道第20（4）条街道第3条街道第20（4）条街道第20（4）条街道第20（4）条街道第20（4）条街道第20（4）条街道第20（4）条街道第20（4）条街道第20（4）条街道第20（4）条街道第20（4）条街道第20（4）条街道收件至邮政编码Ecom_收件至邮政编码14（6）收件至国家Ecom_收件至邮政编码2（7）收件至电话Ecom_收件至电信电话号码10（8）收件至电子邮件Ecom_收件至在线电子邮件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)
卡类型Ecom_支付卡类型4（11）卡号Ecom_支付卡编号19（12）卡验证值Ecom_支付卡验证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)
信用卡到期日电子商务支付信用卡到期日第2（14）天信用卡到期日月电子商务支付信用卡到期日第2（15）月信用卡到期日年电子商务支付信用卡到期日第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）
schema version Ecom_SchemaVersion 30 (19)
模式版本Ecom_SchemaVersion 30（19）
end transaction flag Ecom_TransactionComplete - (20)
结束事务标志Ecom_TransactionComplete-（20）
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
重要提示：上表中的“MIN”是允许输入数据的最小数据大小。它不是字段有效内容的最小大小，在大多数情况下，商户软件应准备接收更长或更短的值。处理州/省名称或电话号码等信息的商户
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.
超过下面给出的“最小值”的时间显然必须允许更长的数据输入。但是，在某些情况下，有一个最大大小是有意义的，并记录在该字段的注释中。
( 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, 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 <http://www.din.de/gremien/nas/nabd/iso3166ma/codlstp1.html> for country names.
（7）使用[ISO 3166]标准双字母代码<http://www.din.de/gremien/nas/nabd/iso3166ma/codlstp1.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: American Express=AMER; Diners Club=DINE; Discover=DISC; JCB=JCB; Mastercard=MAST; Visa=VISA.
（11） 使用协会名称的前4个字母：美国运通=美国运通；食客俱乐部=用餐；发现=光盘；JCB=JCB；万事达卡=桅杆；签证=签证。
(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
（14） 一个月的哪一天。数值：1-31
(15) The month of the year. Jan - 1, Feb - 2, March - 3, etc.;
Values: 1-12
(15) The month of the year. Jan - 1, Feb - 2, March - 3, etc.;
Values: 1-12
(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: none, set, & setcert. "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. "None" indicates that automatic field fill is operating but there is no SET wallet or the card is not entered in any SET wallet.
（17） 与指定卡相关的可用协议的空格分隔列表。不区分大小写标记的初始列表：无、集和集证书。“Set”表示可用于Set协议（即，在Set钱包中），但没有Set证书。“Setcert”表示相同，但有一套证书。“无”表示正在运行自动字段填充，但没有设置钱包或卡未输入任何设置钱包。
(18) A unique order ID generated by the consumer software.
（18） 消费者软件生成的唯一订单ID。
(19) URI indicating version of this set of fields. Usually a hidden field. Equal to "http://www.ecml.org/version/1.0" for this version.
（19） 表示这组字段的版本的URI。通常是一个隐藏的字段。等于“http://www.ecml.org/version/1.0“对于此版本。
(20) A flag to indicate that this web-page/aggregate is the final one for this transaction. Usually a hidden field.
（20） 指示此网页/聚合是此事务的最终网页/聚合的标志。通常是一个隐藏的字段。
The information called for by many of these fields is sensitive and should be protected 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 SSL/TLS [RFC 2246] or IPSec [RFC 2411] would be appropriate in many cases.
其中许多领域所要求的信息都是敏感信息，如果通过公共互联网或其他可以观察到的渠道发送，则应予以保护。此处未指定用于此类保护的机制，但在许多情况下，诸如SSL/TLS[RFC 2246]或IPSec[RFC 2411]之类的信道加密将是合适的。
User control over release of such information is needed to protect the user's privacy.
需要用户控制此类信息的发布，以保护用户的隐私。
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
工具书类
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 - Identification card - Identification of issuers - Part 1:
Numbering system
HTTP4.0 - HTML 4.0 Specification, <http://www.w3.org/TR/REC-html40>
HTTP4.0 - HTML 4.0 Specification, <http://www.w3.org/TR/REC-html40>
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月。
IOTP - Internet Open Trading Protocol, being specified in the IETF TRADE working group, D. Burdett
IOTP——互联网开放交易协议，由IETF贸易工作组D.Burdett指定
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,
<http://www.w3.org/TR/1998/REC-xml-19980210>, T. Bray, J.
Paoli, C. M. Sperberg-McQueen
XML - Extensible Markup Language (XML) 1.0,
<http://www.w3.org/TR/1998/REC-xml-19980210>, T. Bray, J.
Paoli, C. M. Sperberg-McQueen
Authors' Addresses
作者地址
Donald E. Eastlake, 3rd IBM, J1-N63 17 Skyline Drive Hawthorne, NY 10532 USA
Donald E.Eastlake，第三IBM，美国纽约州霍桑市天际大道17号J1-N63，邮编10532
Phone: +1-914-784-7913
Fax: +1-914-784-3833
EMail: dee3@us.ibm.com
Phone: +1-914-784-7913
Fax: +1-914-784-3833
EMail: dee3@us.ibm.com
Ted Goldstein Brodia Networks, Inc. 221 Main Street, Suite 1530 San Francisco, CA 94105 USA
Ted Goldstein Brodia网络公司，221大街，套房1530旧金山，CA 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 (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
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编辑功能的资金目前由互联网协会提供。