Network Working Group K. Fujimura
Request for Comments: 4153 NTT
Category: Informational M. Terada
NTT DoCoMo
D. Eastlake 3rd
Motorola Laboratories
September 2005
Network Working Group K. Fujimura
Request for Comments: 4153 NTT
Category: Informational M. Terada
NTT DoCoMo
D. Eastlake 3rd
Motorola Laboratories
September 2005
XML Voucher: Generic Voucher Language
XML凭证：通用凭证语言
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document specifies rules for defining voucher properties in XML syntax. A voucher is a logical entity that represents a right to claim goods or services. A voucher can be used to transfer a wide range of electronic values, including coupons, tickets, loyalty points, and gift certificates, which often have to be processed in the course of payment and/or delivery transactions.
本文档指定了用XML语法定义凭证属性的规则。凭证是一种逻辑实体，表示索赔商品或服务的权利。凭单可用于传递广泛的电子价值，包括优惠券、门票、积分和礼券，这些通常必须在支付和/或交付交易过程中进行处理。
Table of Contents
目录
1. Introduction ................................................. 2
2. Processing Model ............................................. 2
3. Trust Model .................................................. 4
4. Component Structure .......................................... 4
5. Syntax Overview and Examples ................................. 6
6. Syntax and Semantics ......................................... 8
6.1. <Voucher> ............................................... 8
6.2. <Title> ................................................. 9
6.3. <Description> ........................................... 9
6.4. <Provider> .............................................. 9
6.5. <Issuer> ................................................ 10
6.6. <Holder> ................................................ 10
6.7. <Collector> ............................................. 11
6.8. <Value> ................................................. 11
6.8.1. <Ratio> .......................................... 13
6.8.2. <Fixed> .......................................... 13
1. Introduction ................................................. 2
2. Processing Model ............................................. 2
3. Trust Model .................................................. 4
4. Component Structure .......................................... 4
5. Syntax Overview and Examples ................................. 6
6. Syntax and Semantics ......................................... 8
6.1. <Voucher> ............................................... 8
6.2. <Title> ................................................. 9
6.3. <Description> ........................................... 9
6.4. <Provider> .............................................. 9
6.5. <Issuer> ................................................ 10
6.6. <Holder> ................................................ 10
6.7. <Collector> ............................................. 11
6.8. <Value> ................................................. 11
6.8.1. <Ratio> .......................................... 13
6.8.2. <Fixed> .......................................... 13
6.9. <Merchandise> ........................................... 14
6.10. <ValidPeriod> .......................................... 14
6.11. <Conditions> ........................................... 15
7. IANA Considerations .......................................... 15
8. VTS Schema Example ........................................... 18
9. Security Considerations ...................................... 18
10. Acknowledgements ............................................. 19
11. Normative References ......................................... 19
12. Informative References ....................................... 20
6.9. <Merchandise> ........................................... 14
6.10. <ValidPeriod> .......................................... 14
6.11. <Conditions> ........................................... 15
7. IANA Considerations .......................................... 15
8. VTS Schema Example ........................................... 18
9. Security Considerations ...................................... 18
10. Acknowledgements ............................................. 19
11. Normative References ......................................... 19
12. Informative References ....................................... 20
This document specifies rules for defining voucher properties in XML syntax. The motivation and background of the specification are described in [VTS].
本文档指定了用XML语法定义凭证属性的规则。规范的动机和背景见[VTS]。
A voucher is a logical entity that represents a certain right and that is logically managed by the Voucher Trading System (VTS). A voucher is generated by the issuer, traded among users, and finally collected by the collector using VTS.
凭证是表示特定权利的逻辑实体，由凭证交易系统（VTS）进行逻辑管理。凭证由发行人生成，在用户之间进行交易，最后由收款人使用VTS进行收款。
This document defines the syntax and semantics of the Voucher Component, which defines voucher meaning and processing rules in XML syntax [XML]. A Voucher Component defines the properties that must be satisfied to allow the voucher to be processed by VTS or other trading systems; e.g., a wallet or merchant system. VTS definitions and models are also defined in [VTS].
本文档定义凭证组件的语法和语义，该组件以XML语法[XML]定义凭证含义和处理规则。凭证组件定义了必须满足的属性，以允许VTS或其他交易系统处理凭证；e、 例如，钱包或商户系统。[VTS]中还定义了VTS的定义和型号。
Note: This document uses "voucher" as an "instance of voucher", whose meaning is defined by the Voucher Component. In other words, a Voucher Component is NOT a voucher, and multiple vouchers can be issued and managed by the VTS using the same Voucher Component.
注：本单据使用“凭证”作为“凭证实例”，其含义由凭证组件定义。换句话说，凭证组件不是凭证，VTS可以使用同一凭证组件发布和管理多个凭证。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释
There are several ways of implementing VTS and technologies are continually changing. For discount coupons or event tickets, for example, the smartcard-based offline VTS is often preferred, whereas for bonds or securities, the centralized online VTS is preferred. It is impractical to define standard protocols for issuing, transferring, or redeeming vouchers at this time.
有几种实施VTS的方法，技术也在不断变化。例如，对于折扣券或活动门票，通常首选基于智能卡的离线VTS，而对于债券或证券，则首选集中在线VTS。目前，定义用于发行、转让或兑换凭证的标准协议是不切实际的。
To provide implementation flexibility, this document assumes a modular wallet architecture that allows multiple VTSes to be added as plug-ins. In this architecture, instead of specifying a standard voucher transfer protocol, two specifications, Voucher Component and VTS-API, are standardized (Figure 1).
为提供实施灵活性，本文档采用模块化钱包架构，允许将多个VTSE作为插件添加。在此体系结构中，没有指定标准凭证传输协议，而是标准化了凭证组件和VTS-API这两个规范（图1）。
After the sender and receiver agree on which vouchers are to be traded and which VTS is to be used, the issuing system or wallet system requests the corresponding VTS plug-in to permit the issue, transfer, or redeem transactions to be performed via the VTS API. The VTS then rewrites the ownership of the vouchers using the VTS-specific protocol. Finally, a completion event is sent to the wallet systems or issuing/collecting systems.
在发送方和接收方就要交易的凭证和要使用的VTS达成一致后，发行系统或钱包系统请求相应的VTS插件，以允许通过VTS API执行发行、转账或兑换交易。然后，VTS使用VTS特定协议重写凭证的所有权。最后，完成事件被发送到钱包系统或发卡/收款系统。
This document describes the Voucher Component specification. The VTS-API specification is defined in [VTS-API].
本文档介绍凭证组件规范。VTS-API规范在[VTS-API]中定义。
Sender wallet/Issuing system Receiver wallet/Collecting system
+---------------------------+ +---------------------------+
| | | |
| | Voucher Component | |
| | (Specifies VTS Provider and Promise) | |
| |-------------------------------------------------------->| |
| | | | | |
| | Intention to receive and payment (option) | |
| |<- - - - - - - - - - - - - - - - - - - - - - - - - - - - | |
| | | | | |
| | | | | |
| | Issue/transfer/ VTS | | VTS Register | |
| | redeem request plug-in | plug-in Listener(*1)| |
| |------------------>| | | |<------------------| |
| | (VTS-API) |<- - - - - - - ->| (VTS-API) | |
| | | VTS-specific | | |
| | | protocol if VTS | | |
| | | is distributed | | |
| | Result |<- - - - - - - ->| Notify(*2) | |
| |<------------------| | | |------------------>| |
+---------------------------+ +---------------------------+
Sender wallet/Issuing system Receiver wallet/Collecting system
+---------------------------+ +---------------------------+
| | | |
| | Voucher Component | |
| | (Specifies VTS Provider and Promise) | |
| |-------------------------------------------------------->| |
| | | | | |
| | Intention to receive and payment (option) | |
| |<- - - - - - - - - - - - - - - - - - - - - - - - - - - - | |
| | | | | |
| | | | | |
| | Issue/transfer/ VTS | | VTS Register | |
| | redeem request plug-in | plug-in Listener(*1)| |
| |------------------>| | | |<------------------| |
| | (VTS-API) |<- - - - - - - ->| (VTS-API) | |
| | | VTS-specific | | |
| | | protocol if VTS | | |
| | | is distributed | | |
| | Result |<- - - - - - - ->| Notify(*2) | |
| |<------------------| | | |------------------>| |
+---------------------------+ +---------------------------+
(*1) Registration is optional. Note also that the VTS plug-ins are usually pre-registered when the wallet or collecting system is started.
（*1）注册是可选的。还请注意，VTS插件通常在钱包或收集系统启动时预先注册。
(*2) If a listener is registered.
（*2）如果已注册侦听器。
Figure 1. Wallet architecture with VTS plug-ins
图1。带VTS插件的钱包体系结构
A voucher is trusted if the Issuer and VTS Provider are trusted, as the Issuer is responsible for the contents of the voucher and the VTS Provider is responsible for preventing ownership from being assigned to multiple users.
如果发卡机构和VTS提供商受信任，则凭证受信任，因为发卡机构负责凭证的内容，VTS提供商负责防止将所有权分配给多个用户。
The trust level required for the Issuer and VTS Provider depends on the type (or Promise) of the voucher. To provide the information needed for verification, the conditions of the Issuer and VTS Provider are specified in the Voucher Component and given as input to the verifier; e.g., wallet system or other software. The trust of a voucher is thus verified through the Voucher Component. This model enables trading partners to verify their trust in the voucher regardless of their trust in the partners.
发卡机构和VTS提供商所需的信任级别取决于凭证的类型（或承诺）。为了提供验证所需的信息，在凭证组件中指定了发行人和VTS提供商的条件，并将其作为输入提供给验证人；e、 例如，钱包系统或其他软件。因此，凭证的信任通过凭证组件进行验证。该模型使贸易伙伴能够验证其对凭证的信任，而不考虑其对合作伙伴的信任。
This document assumes that the Voucher Component is the root of trust. If a malicious user could alter the Voucher Component, a forged voucher could be verified as valid.
本文档假定凭证组件是信任的根。如果恶意用户可以更改凭证组件，则可以验证伪造凭证是否有效。
When a Voucher Component is delivered from the trusted VTS Provider, Issuer, or trusted third party, a secure communication channel (e.g., [TLS], [IPSEC], or object security, such as [XMLDSIG]) should be used to prevent alteration during the delivery.
当凭证组件从受信任的VTS提供商、发行人或受信任的第三方交付时，应使用安全通信通道（例如[TLS]、[IPSEC]或对象安全性，例如[XMLDSIG]）来防止在交付过程中发生更改。
Note: The Voucher Component does not have to be sent from the sender of the voucher. Note also that a set of trusted Voucher Components can be downloaded before a transaction is conducted.
注意：凭证组件不必从凭证的发件人处发送。还请注意，在进行交易之前，可以下载一组受信任的凭证组件。
The Voucher Component provides the information needed to identify the monetary value or merchandize rendered when the voucher is redeemed. It includes
凭证组件提供了识别兑换凭证时提供的货币价值或商品所需的信息。它包括
o how much value/items can be claimed in exchange for the voucher, and
o 凭单可以兑换多少价值/物品，以及
o restrictions applied to the voucher
o 适用于凭证的限制
- participants (VTS Provider, Issuer, Holder, and Collector),
- 参与者（VTS提供商、发行人、持有人和收款人），
- objects (merchandise) to be claimed,
- 要索赔的物品（商品），
- time when valid (validity period), and
- 有效时间（有效期），以及
- others.
- 其他的。
The Voucher Component also provides common properties useful for displaying and manipulating the contents of wallet systems. It includes the title and description of each voucher.
凭证组件还提供用于显示和操作钱包系统内容的常用属性。它包括每张凭证的标题和说明。
The Voucher Component contains the following components:
凭证组件包含以下组件：
Title Component
标题部分
Provides the title of the voucher. This is mainly for listing the entities stored in a wallet system.
提供凭证的标题。这主要用于列出存储在钱包系统中的实体。
Description Component
描述组件
Provides a short description of the voucher. This is mainly for listing the entities stored in a wallet system.
提供凭证的简短说明。这主要用于列出存储在钱包系统中的实体。
Provider Component
提供者组件
Provides restrictions on which VTS Provider (or VTS plug-in) can be used for trading the voucher.
提供有关哪些VTS提供商（或VTS插件）可用于凭证交易的限制。
Issuer Component
发行人组成部分
Provides restrictions on the Issuer of the voucher.
提供对凭证发行人的限制。
Holder Component
支架组件
Provides restrictions on the Holder of the voucher.
提供对凭证持有人的限制。
Collector Component
收集器组件
Provides restrictions on the Collector of the voucher.
提供对凭证收款人的限制。
Value Component
价值成分
Provides the value of each voucher. There are two types of values: fixed and ratio values. For a fixed value, the currency and the figure is specified. For a ratio value, the discount ratio of the corresponding merchandize is specified.
提供每个凭证的值。有两种类型的值：固定值和比率值。对于固定值，指定货币和数字。对于比率值，指定相应商品的折扣率。
The Value Component also indicates the number of vouchers to be redeemed for claiming the merchandise or monetary value specified in the Merchandise Component or Value Component. If "n" (>0) is specified, the merchandize or monetary value can be claimed in exchange for "n sheets of" vouchers. If "0" is specified, it can be used repeatedly.
价值构成部分还表示为索赔商品构成部分或价值构成部分中规定的商品或货币价值而兑换的凭证数量。如果指定了“n”（>0），则可以用“n张”凭证兑换商品或货币价值。如果指定了“0”，则可以重复使用。
Merchandise Component
商品成分
Provides restrictions on the object to be claimed. The domain-specific meaning of the voucher (e.g., reference number of the merchandize or seat number for an event ticket) is specified to identify the merchandize rendered when the voucher is redeemed.
提供对要声明的对象的限制。指定凭单的特定领域含义（例如，商品参考号或活动门票的座位号），以识别兑换凭单时提供的商品。
ValidPeriod Component
有效周期分量
Provides restrictions on the validity period of the voucher; i.e., start date and end date.
提供对凭证有效期的限制；i、 开始日期和结束日期。
Condition Component
条件成分
Provides any other applicable restrictions. This is intended to cover contracts between the issuer and holder of the voucher in natural language form.
提供任何其他适用的限制。这旨在涵盖自然语言形式的凭证发行人和持有人之间的合同。
Using the above Components, semantics for diverse types of vouchers can be defined as shown in Table 1.
使用上述组件，可以定义不同类型凭证的语义，如表1所示。
+----------------+--------------------------------+---------------+
| | Value | Restrictions |
| +-----+---------------+----------+---------------+
| Examples |Ratio| Fixed |Number | Merchandise |
| | +------+--------+needed for| |
| | |Amount|Currency|redemption| |
+----------------+-----+------+--------+----------+---------------+
|Gift certificate| | 25 | USD | 1 |(Not specified)|
|Loyalty point | | 1 | AUD | 10 |(Not specified)|
|Member card | 20%| | | 0 |(Not specified)|
|Coupon | 30%| | | 1 |Beef 500g |
|Event ticket | 100%| | | 1 |Hall A, S ,K23 |
|Exchange ticket | 100%| | | 1 |ISBN:0071355014|
+----------------+-----+------+--------+----------+---------------+
+----------------+--------------------------------+---------------+
| | Value | Restrictions |
| +-----+---------------+----------+---------------+
| Examples |Ratio| Fixed |Number | Merchandise |
| | +------+--------+needed for| |
| | |Amount|Currency|redemption| |
+----------------+-----+------+--------+----------+---------------+
|Gift certificate| | 25 | USD | 1 |(Not specified)|
|Loyalty point | | 1 | AUD | 10 |(Not specified)|
|Member card | 20%| | | 0 |(Not specified)|
|Coupon | 30%| | | 1 |Beef 500g |
|Event ticket | 100%| | | 1 |Hall A, S ,K23 |
|Exchange ticket | 100%| | | 1 |ISBN:0071355014|
+----------------+-----+------+--------+----------+---------------+
Table 1. Examples of vouchers and their properties
表1。凭证及其属性示例
This section provides an overview and examples of Voucher Components. The formal syntax and semantics are found in Sections 6 and 7.
本节提供凭证组件的概述和示例。形式语法和语义见第6节和第7节。
Voucher Components are represented by the <Voucher> element, which has the following structure (where "?" denotes zero or one occurrence):
凭证组件由<凭证>元素表示，该元素具有以下结构（其中“？”表示零次或一次出现）：
<Voucher> (Title) (Description)? (Provider) (Issuer)? (Holder)? (Collector)? (Value) (Merchandise)? (ValidPeriod)? (Conditions)? </Voucher>
<凭证>（标题）（说明）？（提供者）（发行人）？（持有人）？（收藏家）？（价值）（商品）？（有效期）？（条件）</凭单>
An example of a Voucher Component is described below. This is an example of a five-dollar discount coupon for specific merchandize, a book with ISBN number 0071355014. The coupon is valid from April 1, 2001, to March 31, 2002. To claim this offer, one voucher must be spent.
凭证组件的示例如下所述。这是特定商品的五美元折扣券的一个例子，这是一本ISBN编号为0071355014的书。优惠券的有效期为二○○一年四月一日至二○○二年三月三十一日。要申请此优惠，必须使用一张优惠券。
<?xml version="1.0" encoding="UTF-8"?>
<Voucher xmlns="urn:ietf:params:xml:ns:vts-lang"
xmlns:vts="http://www.example.com/vts">
<Title>IOTP Book Coupon</Title>
<Description>$5 off IOTP Book</Description>
<Provider name="Voucher Exchanger 2002">
<vts:Version>VE2.31</vts:Version>
</Provider>
<Issuer name="Alice Book Center, Ltd.">
<vts:KeyInfo>
1DA8DFCF95521014BBB7171B95545E8D61AE803F
</vts:KeyInfo>
</Issuer>
<Collector name="Alice Book Center, Ltd."/>
<Value type="discount" spend="1">
<Fixed amount="5" currency="USD"/>
</Value>
<Merchandise>
<bk:Book xmlns:bk="http://www.example.com/bk"
bk:isbn="0071355014"/>
</Merchandise>
<ValidPeriod start="2002-04-01" end="2003-03-31"/>
<Conditions>
The value of this coupon is subject to tax.
</Conditions>
</Voucher>
<?xml version="1.0" encoding="UTF-8"?>
<Voucher xmlns="urn:ietf:params:xml:ns:vts-lang"
xmlns:vts="http://www.example.com/vts">
<Title>IOTP Book Coupon</Title>
<Description>$5 off IOTP Book</Description>
<Provider name="Voucher Exchanger 2002">
<vts:Version>VE2.31</vts:Version>
</Provider>
<Issuer name="Alice Book Center, Ltd.">
<vts:KeyInfo>
1DA8DFCF95521014BBB7171B95545E8D61AE803F
</vts:KeyInfo>
</Issuer>
<Collector name="Alice Book Center, Ltd."/>
<Value type="discount" spend="1">
<Fixed amount="5" currency="USD"/>
</Value>
<Merchandise>
<bk:Book xmlns:bk="http://www.example.com/bk"
bk:isbn="0071355014"/>
</Merchandise>
<ValidPeriod start="2002-04-01" end="2003-03-31"/>
<Conditions>
The value of this coupon is subject to tax.
</Conditions>
</Voucher>
The general structure of an XML Voucher Component is described in Section 4. This section details the Voucher Component features. Features described in this section MUST be implemented unless otherwise indicated. The syntax is defined via [XML-Schema-1] [XML-Schema-2]. For clarity, unqualified elements in schema definitions are in the XML schema namespace:
第4节描述了XML凭证组件的一般结构。本节详细介绍凭证组件功能。除非另有说明，否则必须实现本节中描述的功能。语法是通过[XML-Schema-1][XML-Schema-2]定义的。为清楚起见，架构定义中的非限定元素位于XML架构命名空间中：
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.w3.org/2001/XMLSchema"
References to XML Voucher schema defined herein use the prefix "gvl" and are in the namespace:
此处定义的对XML凭证模式的引用使用前缀“gvl”，并位于命名空间中：
xmlns:gvl="urn:ietf:params:xml:ns:vts-lang"
xmlns:gvl="urn:ietf:params:xml:ns:vts-lang"
This namespace URI for elements defined by this document is a URN [URN] that uses the namespace identifier 'ietf', defined by [URN-NS-IETF] and extended by [XML-Registry].
本文档定义的元素的名称空间URI是一个URN[URN]，它使用名称空间标识符“ietf”，由[URN-NS-ietf]定义，并由[XML注册表]扩展。
This namespace is also used for unqualified elements in voucher examples.
此命名空间还用于凭证示例中的非限定元素。
The <Voucher> element contains <Title>, <Provider>, and <Value> elements and optionally contains <Description>, <Issuer>, <Holder>, <Collector>, <ValidPeriod>, and <Condition> elements. These sub-elements are defined in the following sections.
“凭证”元素包含<Title>、<Provider>和<Value>元素，还可以选择包含<Description>、<Issuer>、<Holder>、<Collector>、<ValidPeriod>和<Condition>元素。这些子元素在以下章节中定义。
The <Voucher> element is defined by the following schema:
元素由以下架构定义：
<element name="Voucher" type="gvl:VoucherType"/>
<complexType name="VoucherType">
<sequence>
<element ref="gvl:Title"/>
<element ref="gvl:Description" minOccurs="0"/>
<element ref="gvl:Provider"/>
<element ref="gvl:Issuer" minOccurs="0"/>
<element ref="gvl:Holder" minOccurs="0"/>
<element ref="gvl:Collector" minOccurs="0"/>
<element ref="gvl:Value"/>
<element ref="gvl:Merchandise" minOccurs="0"/>
<element ref="gvl:ValidPeriod" minOccurs="0"/>
<element ref="gvl:Conditions" minOccurs="0"/>
</sequence>
</complexType>
<element name="Voucher" type="gvl:VoucherType"/>
<complexType name="VoucherType">
<sequence>
<element ref="gvl:Title"/>
<element ref="gvl:Description" minOccurs="0"/>
<element ref="gvl:Provider"/>
<element ref="gvl:Issuer" minOccurs="0"/>
<element ref="gvl:Holder" minOccurs="0"/>
<element ref="gvl:Collector" minOccurs="0"/>
<element ref="gvl:Value"/>
<element ref="gvl:Merchandise" minOccurs="0"/>
<element ref="gvl:ValidPeriod" minOccurs="0"/>
<element ref="gvl:Conditions" minOccurs="0"/>
</sequence>
</complexType>
The <Title> element contains a simpletext title of the voucher. This is mainly for listing the entities stored in a wallet system.
<Title>元素包含凭证的simpletext标题。这主要用于列出存储在钱包系统中的实体。
The <Title> element has no attribute.
<Title>元素没有属性。
The <Title> element is defined by the following schema:
<Title>元素由以下架构定义：
<element name="Title" type="string"/>
<element name="Title" type="string"/>
The <Description> element contains a simpletext description of the voucher. This is mainly for listing the entities stored in a wallet system.
<Description>元素包含凭证的simpletext描述。这主要用于列出存储在钱包系统中的实体。
The <Description> element has no attribute.
<Description>元素没有属性。
The <Description> element is defined by the following schema:
<Description>元素由以下架构定义：
<element name="Description" type="string"/>
<element name="Description" type="string"/>
The <Provider> element may contain any element that is used to specify or restrict the VTS Provider of the voucher. The sub-elements contained in this element depend on the implementation of the VTS.
<Provider>元素可以包含用于指定或限制凭证的VTS提供者的任何元素。此元素中包含的子元素取决于VTS的实施。
An implementation of a wallet system may use this information to identify and/or authenticate the VTS Provider when the VTS plug-in is registered (see Section 7 of [VTS-API]). These implementation-specific elements of the VTS can be extended using [XML-ns]. An example of such a schema definition is described in Section 8.
当注册VTS插件时，钱包系统的实现可以使用该信息来识别和/或认证VTS提供商（参见[VTS-API]第7节）。VTS的这些特定于实现的元素可以使用[XML ns]进行扩展。第8节描述了此类模式定义的示例。
The <Provider> element has a string-type "name" attribute that is used to specify the name of the VTS Provider.
<Provider>元素有一个字符串类型的“name”属性，用于指定VTS提供程序的名称。
The <Provider> element is defined by the following schema:
<Provider>元素由以下架构定义：
<element name="Provider" type="gvl:RoleType"/>
<complexType name="RoleType" mixed="true">
<sequence>
<any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<attribute name="name" type="string"/>
</complexType>
<element name="Provider" type="gvl:RoleType"/>
<complexType name="RoleType" mixed="true">
<sequence>
<any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<attribute name="name" type="string"/>
</complexType>
The <Issuer> element may contain any element that is used to specify or restrict the Issuer of the voucher.
<Issuer>元素可以包含用于指定或限制凭证发行人的任何元素。
The Issuer of the voucher is generally managed by the VTS [VTS-API]. There is no need to specify the Issuer of the voucher using this element if there are no restrictions on the Issuer.
凭证的发行人通常由VTS[VTS-API]管理。如果对凭证的发行人没有限制，则无需使用此元素指定凭证的发行人。
An implementation of a VTS may use this element to describe the authentication data and/or qualification information of the Issuer. This implementation-specific information can be extended through sub-elements using [XML-ns]. An example of such a schema definition is described in Section 8.
VTS的实现可以使用该元素来描述颁发者的认证数据和/或资格信息。此特定于实现的信息可以使用[XML ns]通过子元素进行扩展。第8节描述了此类模式定义的示例。
The <Issuer> element has a string-type "name" attribute that is used to specify the name of the Issuer.
元素有一个字符串类型的“name”属性，用于指定颁发者的名称。
The <Issuer> element is defined by the following schema:
<Issuer>元素由以下架构定义：
<element name="Issuer" type="gvl:RoleType"/>
<element name="Issuer" type="gvl:RoleType"/>
The <RoleType> element type is defined in Section 6.4.
第6.4节定义了<RoleType>元素类型。
If the <Issuer> element is omitted, it MUST be interpreted that there are no restrictions on the Issuer.
如果省略<Issuer>元素，则必须解释为对发行人没有任何限制。
The <Holder> element may contain any element that is used to specify or restrict the Holder of the voucher.
<Holder>元素可以包含用于指定或限制凭证持有人的任何元素。
The Holder of the voucher is generally managed by the VTS [VTS-API]. There is no need to specify the Holder of the voucher using this element if there are no restrictions on the Holder.
凭证持有人通常由VTS[VTS-API]管理。如果对凭证持有人没有任何限制，则无需使用此元素指定凭证持有人。
An implementation of a VTS may use this element to describe the authentication data and/or qualification information of the Holder. This implementation-specific information can be extended through sub-elements using [XML-ns].
VTS的实现可以使用该元素来描述持有者的认证数据和/或资格信息。此特定于实现的信息可以使用[XML ns]通过子元素进行扩展。
The <Holder> element has a string-type "name" attribute that is used to specify the name of the Holder.
元素有一个字符串类型的“name”属性，用于指定持有者的名称。
The <Holder> element is defined by the following schema:
<Holder>元素由以下架构定义：
<element name="Holder" type="gvl:RoleType"/>
<element name="Holder" type="gvl:RoleType"/>
The <RoleType> element type is defined in Section 6.4.
第6.4节定义了<RoleType>元素类型。
If the <Holder> element is omitted, it MUST be interpreted that there are no restrictions on the Holder.
如果省略了<Holder>元素，则必须解释为对Holder没有任何限制。
The <Collector> element may contain any element that is used to specify or restrict the Collector of the voucher.
<Collector>元素可以包含用于指定或限制凭证收款人的任何元素。
There is no need to specify the Collector of the voucher using this element if there are no restrictions on the Collector.
如果收款人没有限制，则无需使用此元素指定凭证的收款人。
An implementation of a VTS may use this element to describe the authentication data and/or qualification information of the Collector. This implementation-specific information can be extended through sub-elements using [XML-ns].
VTS的实现可以使用该元素来描述收集器的认证数据和/或资格信息。此特定于实现的信息可以使用[XML ns]通过子元素进行扩展。
The <Collector> element has a string-type "name" attribute that is used to specify the name of the Collector.
元素有一个字符串类型的“name”属性，用于指定收集器的名称。
The <Collector> element is defined by the following schema:
<Collector>元素由以下架构定义：
<element name="Collector" type="gvl:RoleType"/>
<element name="Collector" type="gvl:RoleType"/>
The <RoleType> element type is defined in Section 6.4.
第6.4节定义了<RoleType>元素类型。
If the <Collector> element is omitted, it MUST be interpreted that there are no restrictions on the Collector.
如果省略<Collector>元素，则必须解释为对收集器没有任何限制。
The <Value> element optionally contains a <Fixed> or <Ratio> element but not both. These sub-elements are defined in the following sections.
<Value>元素可以选择包含<Fixed>或<Ratio>元素，但不能同时包含这两个元素。这些子元素在以下章节中定义。
The <Value> element has a "type" attribute that is used to specify the value process type. This attribute is provided to calculate the amount paid when the vouchers are redeemed at Merchant site, etc.
<Value>元素有一个“type”属性，用于指定值处理类型。此属性用于计算在商户网站等处兑换凭证时支付的金额。
The following identifiers are defined for the "type" attribute.
为“type”属性定义了以下标识符。
Exchange: Items specified in the <Merchandise> element can be claimed in exchange for the voucher. If this type is selected, neither the <Ratio> nor the <Fixed> element MUST be specified. Note that this value process type has the same meaning as:
交换：<Merchance>元素中指定的项目可以用凭证交换。如果选择此类型，则不必指定<Ratio>或<Fixed>元素。请注意，此值处理类型的含义与：
<Value type="discount"><Ratio percentage="100"/></Value>
<Value type="discount"><Ratio percentage="100"/></Value>
Discount: Items specified in the <Merchandise> element can be purchased at the discount price calculated by the <Ratio> or <Fixed> element.
折扣：可以按照<Ratio>或<Fixed>元素计算的折扣价格购买<merchance>元素中指定的项目。
Monetary: Items specified in the <Merchandise> element can be purchased using the value of the voucher. (Note: if the <Merchandise> element is not specified, the voucher can be used for any purchase.) If this type is selected, the <Fixed> element MUST be specified.
货币：可以使用凭证的价值购买<商品>元素中指定的项目。（注意：如果未指定<商品>元素，则凭证可用于任何购买。）如果选择此类型，则必须指定<固定>元素。
The <Value> element also has a "spend" attribute that is used to specify the number of vouchers to be redeemed for claiming the goods, services, or monetary value specified. For example, if "n" (>0) is specified, goods can be claimed in exchange for "n sheets of" vouchers. (Note: Multiple vouchers for the same Voucher Component must exist in this case.) If "0" is specified, it can be used repeatedly.
<Value>元素还有一个“spend”属性，用于指定要兑换的凭单数量，以声明指定的商品、服务或货币价值。例如，如果指定了“n”（>0），则可以用“n张”凭证交换货物。（注意：在这种情况下，同一凭证组件必须存在多个凭证。）如果指定“0”，则可以重复使用。
If the "spend" attribute or the whole element is omitted, it MUST be interpreted that "1" is specified for the "spend" attribute.
如果省略了“spend”属性或整个元素，则必须解释为“spend”属性指定了“1”。
The <Value> element is defined by the following schema:
<Value>元素由以下架构定义：
<element name="Value" type="gvl:ValueType"/>
<complexType name="ValueType">
<sequence minOccurs="0">
<choice>
<element name="Ratio" type="gvl:RatioValueType"/>
<element name="Fixed" type="gvl:FixedValueType"/>
</choice>
</sequence>
<attribute name="type" type="gvl:ValueProcessType"
use="required"/>
<attribute name="spend" type="nonNegativeInteger"
default="1"/>
</complexType>
<element name="Value" type="gvl:ValueType"/>
<complexType name="ValueType">
<sequence minOccurs="0">
<choice>
<element name="Ratio" type="gvl:RatioValueType"/>
<element name="Fixed" type="gvl:FixedValueType"/>
</choice>
</sequence>
<attribute name="type" type="gvl:ValueProcessType"
use="required"/>
<attribute name="spend" type="nonNegativeInteger"
default="1"/>
</complexType>
The <ValueProcessType> element type is defined by the following schema:
<ValueProcessType>元素类型由以下架构定义：
<simpleType name="ValueProcessType">
<restriction base="string">
<enumeration value="exchange"/>
<enumeration value="discount"/>
<enumeration value="monetary"/>
</restriction>
</simpleType>
<simpleType name="ValueProcessType">
<restriction base="string">
<enumeration value="exchange"/>
<enumeration value="discount"/>
<enumeration value="monetary"/>
</restriction>
</simpleType>
The <Ratio> element does not contain any contents.
<Ratio>元素不包含任何内容。
The <Ratio> element has a "percentage" attribute that is used to specify the discount ratio of the price of the corresponding merchandize in percentage.
<Ratio>元素有一个“百分比”属性，用于指定相应商品价格的折扣率（百分比）。
The <RatioValueType> element type is defined by the following schema:
<RatioValueType>元素类型由以下架构定义：
<complexType name="RatioValueType">
<attribute name="percentage" use="required">
<simpleType>
<restriction base="float">
<maxInclusive value="100"/>
</restriction>
</simpleType>
</attribute>
</complexType>
<complexType name="RatioValueType">
<attribute name="percentage" use="required">
<simpleType>
<restriction base="float">
<maxInclusive value="100"/>
</restriction>
</simpleType>
</attribute>
</complexType>
The <Fixed> element does not contain any contents.
<Fixed>元素不包含任何内容。
The <Fixed> element has "currency" and "amount" attributes and optionally a "decimalPower" attribute as follows:
<Fixed>元素具有“currency”和“amount”属性，还可以选择“decimalPower”属性，如下所示：
Currency: Provides the unit of the monetary value in the three letter ISO currency code [ISO4217]. For example, US dollars is "USD".
货币：以三个字母的ISO货币代码[ISO4217]提供货币值的单位。例如，美元是“USD”。
Amount: Provides the amount of the monetary value per voucher.
金额：提供每张凭证的货币价值金额。
DecimalPower: Provides the number of decimal digits from the decimal point applied to the base for the "amount" attribute above. If the "decimalPower" attribute is omitted, it MUST be interpreted that "0" is specified for the "decimalPower" attribute.
DecimalPower：提供从小数点到上述“金额”属性基数的小数位数。如果省略了“decimalPower”属性，则必须解释为“decimalPower”属性指定了“0”。
For example, with a dollar currency denominated in cents, "1" is specified for the "amount" attribute, and "-2" is specified for the "decimalPower" attribute. Alternately, "0.01" is specified for the "amount" attribute, and the "decimalPower" attribute is omitted.
例如，对于以美分计价的美元货币，“金额”属性指定为“1”，而“分力”属性指定为“-2”。或者，为“amount”属性指定“0.01”，并省略“decimalPower”属性。
The <FixedValueType> type is defined follows:
<FixedValueType>类型定义如下：
<complexType name="FixedValueType">
<attribute name="currency" type="string" use="required"/>
<attribute name="amount" type="float" use="required"/>
<attribute name="decimalPower" type="short" default="0"/>
</complexType>
<complexType name="FixedValueType">
<attribute name="currency" type="string" use="required"/>
<attribute name="amount" type="float" use="required"/>
<attribute name="decimalPower" type="short" default="0"/>
</complexType>
The <Merchandise> element may contain any element used to specify or restrict the goods or services rendered when the voucher is redeemed. The sub-elements contained in this element depend on the application of the voucher and are left to the other domain-specific specifications. Domain-specific elements can be extended as sub-elements using [XML-ns].
<商品>元素可以包含用于指定或限制兑换凭单时提供的商品或服务的任何元素。此元素中包含的子元素取决于凭证的应用程序，并由其他特定于域的规范决定。可以使用[XML ns]将特定于域的元素扩展为子元素。
This element is intended to be interpreted by a collecting system. An implementation of a wallet system does not have to use this element. Any restrictions applied should also be described in the <Description> element or the <Conditions> elements in natural language form to enable users to check the restrictions.
该元素旨在由采集系统进行解释。钱包系统的实现不必使用此元素。还应在<Description>元素或<Conditions>元素中以自然语言形式描述应用的任何限制，以便用户检查限制。
The <Merchandise> element does not have any attribute.
<Merchance>元素没有任何属性。
The <Merchandise> element is defined by the following schema:
<Merchance>元素由以下架构定义：
<element name="Merchandise" type="gvl:MerchandiseType"/>
<complexType name="MerchandiseType" mixed="true">
<sequence>
<any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
<element name="Merchandise" type="gvl:MerchandiseType"/>
<complexType name="MerchandiseType" mixed="true">
<sequence>
<any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
The <ValidPeriod> element does not contain any contents.
<ValidPeriod>元素不包含任何内容。
The <ValidPeriod> element has dateTime-type "start" and "end" attributes that are used to place limits on the validity of the voucher.
元素具有日期时间类型“开始”和“结束”属性，用于限制凭证的有效性。
The <ValidPeriod> element is defined by the following schema:
<ValidPeriod>元素由以下架构定义：
<element name="ValidPeriod" type="gvl:ValidPeriodType"/>
<complexType name="ValidPeriodType">
<attribute name="start" type="dateTime"/>
<attribute name="end" type="dateTime"/>
</complexType>
<element name="ValidPeriod" type="gvl:ValidPeriodType"/>
<complexType name="ValidPeriodType">
<attribute name="start" type="dateTime"/>
<attribute name="end" type="dateTime"/>
</complexType>
If the "start" attribute is omitted, it MUST be interpreted that the voucher is valid on any date up to that specified by the end attribute (inclusive). If the "end" attribute is omitted, it MUST be interpreted that the voucher is valid from the start attribute with no expiry. If neither attribute is specified or the whole element is omitted, it MUST be interpreted that the voucher is valid at any time.
如果省略了“开始”属性，则必须解释凭证在结束属性（包括）指定日期之前的任何日期都有效。如果省略了“结束”属性，则必须解释凭证从“开始”属性起是有效的，没有到期日。如果未指定任何属性或省略了整个元素，则必须解释凭证在任何时候都是有效的。
The <Conditions> element contains any other restrictions or conditions applied. This is intended to cover contracts between the issuer and the holder of the voucher in natural language form.
<Conditions>元素包含应用的任何其他限制或条件。这旨在涵盖自然语言形式的凭证发行人和持有人之间的合同。
An implementation of a wallet system SHOULD provide a means of displaying the text in this element.
钱包系统的实现应提供在此元素中显示文本的方法。
The <Conditions> element has no attribute.
<Conditions>元素没有属性。
The <Conditions> element is defined by the following schema:
<Conditions>元素由以下架构定义：
<element name="Conditions" type="string"/>
<element name="Conditions" type="string"/>
This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [XML-Registry]. IANA has registered two URI assignments.
本文档使用URN来描述符合[XML注册表]中所述注册表机制的XML名称空间和XML模式。IANA注册了两个URI分配。
Registration request for the vts-lang namespace:
vts lang命名空间的注册请求：
URI: urn:ietf:params:xml:ns:vts-lang
URI: urn:ietf:params:xml:ns:vts-lang
Registrant Contact: See the "Authors' Addresses" section of this document.
注册人联系人：请参阅本文件的“作者地址”部分。
XML: None. Namespace URIs do not represent an XML specification.
XML：没有。命名空间URI不表示XML规范。
Registration request for the vts-lang XML schema:
vts lang XML架构的注册请求：
URI: urn:ietf:params:xml:schema:vts-lang
URI: urn:ietf:params:xml:schema:vts-lang
Registrant Contact: See the "Authors' Addresses" section of this document.
注册人联系人：请参阅本文件的“作者地址”部分。
XML:
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
XML:
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema
targetNamespace="urn:ietf:params:xml:ns:vts-lang"
xmlns:gvl="urn:ietf:params:xml:ns:vts-lang"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<schema
targetNamespace="urn:ietf:params:xml:ns:vts-lang"
xmlns:gvl="urn:ietf:params:xml:ns:vts-lang"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<element name="Voucher" type="gvl:VoucherType"/>
<complexType name="VoucherType">
<sequence>
<element ref="gvl:Title"/>
<element ref="gvl:Description" minOccurs="0"/>
<element ref="gvl:Provider"/>
<element ref="gvl:Issuer" minOccurs="0"/>
<element ref="gvl:Holder" minOccurs="0"/>
<element ref="gvl:Collector" minOccurs="0"/>
<element ref="gvl:Value"/>
<element ref="gvl:Merchandise" minOccurs="0"/>
<element ref="gvl:ValidPeriod" minOccurs="0"/>
<element ref="gvl:Conditions" minOccurs="0"/>
</sequence>
</complexType>
<element name="Voucher" type="gvl:VoucherType"/>
<complexType name="VoucherType">
<sequence>
<element ref="gvl:Title"/>
<element ref="gvl:Description" minOccurs="0"/>
<element ref="gvl:Provider"/>
<element ref="gvl:Issuer" minOccurs="0"/>
<element ref="gvl:Holder" minOccurs="0"/>
<element ref="gvl:Collector" minOccurs="0"/>
<element ref="gvl:Value"/>
<element ref="gvl:Merchandise" minOccurs="0"/>
<element ref="gvl:ValidPeriod" minOccurs="0"/>
<element ref="gvl:Conditions" minOccurs="0"/>
</sequence>
</complexType>
<element name="Title" type="string"/>
<element name="Title" type="string"/>
<element name="Description" type="string"/>
<element name="Description" type="string"/>
<element name="Provider" type="gvl:RoleType"/>
<element name="Issuer" type="gvl:RoleType"/>
<element name="Holder" type="gvl:RoleType"/>
<element name="Collector" type="gvl:RoleType"/>
<complexType name="RoleType" mixed="true">
<sequence>
<any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<attribute name="name" type="string"/>
</complexType>
<element name="Provider" type="gvl:RoleType"/>
<element name="Issuer" type="gvl:RoleType"/>
<element name="Holder" type="gvl:RoleType"/>
<element name="Collector" type="gvl:RoleType"/>
<complexType name="RoleType" mixed="true">
<sequence>
<any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<attribute name="name" type="string"/>
</complexType>
<element name="Value" type="gvl:ValueType"/>
<complexType name="ValueType">
<sequence minOccurs="0">
<choice>
<element name="Ratio" type="gvl:RatioValueType"/>
<element name="Fixed" type="gvl:FixedValueType"/>
</choice>
</sequence>
<attribute name="type" type="gvl:ValueProcessType"
use="required"/>
<attribute name="spend" type="nonNegativeInteger"
default="1"/>
</complexType>
<element name="Value" type="gvl:ValueType"/>
<complexType name="ValueType">
<sequence minOccurs="0">
<choice>
<element name="Ratio" type="gvl:RatioValueType"/>
<element name="Fixed" type="gvl:FixedValueType"/>
</choice>
</sequence>
<attribute name="type" type="gvl:ValueProcessType"
use="required"/>
<attribute name="spend" type="nonNegativeInteger"
default="1"/>
</complexType>
<simpleType name="ValueProcessType">
<restriction base="string">
<enumeration value="exchange"/>
<enumeration value="discount"/>
<enumeration value="monetary"/>
</restriction>
</simpleType>
<simpleType name="ValueProcessType">
<restriction base="string">
<enumeration value="exchange"/>
<enumeration value="discount"/>
<enumeration value="monetary"/>
</restriction>
</simpleType>
<complexType name="RatioValueType">
<attribute name="percentage" use="required">
<simpleType>
<restriction base="float">
<maxInclusive value="100"/>
</restriction>
</simpleType>
</attribute>
</complexType>
<complexType name="RatioValueType">
<attribute name="percentage" use="required">
<simpleType>
<restriction base="float">
<maxInclusive value="100"/>
</restriction>
</simpleType>
</attribute>
</complexType>
<complexType name="FixedValueType">
<attribute name="currency" type="string" use="required"/>
<attribute name="amount" type="float" use="required"/>
<attribute name="decimalPower" type="short" default="0"/>
</complexType>
<complexType name="FixedValueType">
<attribute name="currency" type="string" use="required"/>
<attribute name="amount" type="float" use="required"/>
<attribute name="decimalPower" type="short" default="0"/>
</complexType>
<element name="Merchandise" type="gvl:MerchandiseType"/>
<complexType name="MerchandiseType" mixed="true">
<sequence>
<any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
<element name="Merchandise" type="gvl:MerchandiseType"/>
<complexType name="MerchandiseType" mixed="true">
<sequence>
<any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
<element name="ValidPeriod" type="gvl:ValidPeriodType"/>
<complexType name="ValidPeriodType">
<attribute name="start" type="dateTime"/>
<element name="ValidPeriod" type="gvl:ValidPeriodType"/>
<complexType name="ValidPeriodType">
<attribute name="start" type="dateTime"/>
<attribute name="end" type="dateTime"/>
</complexType>
<attribute name="end" type="dateTime"/>
</complexType>
<element name="Conditions" type="string"/>
</schema>
END
<element name="Conditions" type="string"/>
</schema>
END
An example of the schema definition for a VTS implementation is described below.
VTS实现的模式定义示例如下所述。
<?xml version="1.0"?>
<?xml version="1.0"?>
<schema
targetNamespace="http://www.example.com/vts"
xmlns:vts="http://www.example.com/vts"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<schema
targetNamespace="http://www.example.com/vts"
xmlns:vts="http://www.example.com/vts"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<element name="Version" type="string"/>
<element name="KeyInfo" type="hexBinary"/>
</schema>
<element name="Version" type="string"/>
<element name="KeyInfo" type="hexBinary"/>
</schema>
Using this schema definition, the <vts:Version> can be used for specifying the VTS version number, and the <vts:KeyInfo> element can be used for specifying the Issuer in the Voucher Component, as shown in Section 5.
使用此架构定义，<vts:Version>可用于指定vts版本号，<vts:KeyInfo>元素可用于指定凭证组件中的发行人，如第5节所示。
The VTS must provide a means to prevent forgery, alteration, duplicate-redemption, reproduction of a voucher, and non-repudiation of transactions, as described in Section 3.2 of [VTS]. This will commonly require the presence of a unique serial number or the like in each Voucher instance, usually outside the Voucher Component. These security requirements, however, mainly follow the VTS plug-ins and their protocols. This document assumes that the VTS plug-ins are trusted and are installed by some means; e.g., manually checked as are other download applications.
悉尼威立雅运输公司必须提供防止伪造、更改、重复赎回、凭证复制和交易不可抵赖的手段，如[VTS]第3.2节所述。这通常需要在每个凭证实例中（通常在凭证组件之外）存在唯一的序列号等。然而，这些安全需求主要遵循VTS插件及其协议。本文档假定VTS插件是可信的，并通过某种方式安装；e、 例如，手动检查其他下载应用程序。
The Voucher Component, however, defines restrictions on the VTS Provider (or VTS plug-in), and, if this information is altered, incorrect VTS plug-ins not accepted by the issuer could be used, allowing a forged voucher to be verified as if it were valid. To prevent this situation, the Voucher Component should be stored and
但是，凭证组件定义了对VTS提供程序（或VTS插件）的限制，如果此信息被更改，则可能会使用发卡机构不接受的不正确VTS插件，从而允许验证伪造凭证，就好像它是有效的一样。为防止出现这种情况，应存储凭证组件并
acquired securely; e.g., downloaded from a trusted party using a secure communication channel, such as [TLS] or [IPSEC], or secured by the digital signature of a trusted party [XMLDSIG].
安全获得；e、 例如，使用安全通信通道（如[TLS]或[IPSEC]）从受信任方下载，或由受信任方的数字签名[XMLDSIG]保护。
The following persons, in alphabetic order, contributed substantially to the material herein:
以下人员按字母顺序对本文件中的材料做出了重大贡献：
Ian Grigg Renato Iannella Yoshiaki Nakajima
伊恩·格里格·雷纳托·伊安内拉·吉崎中岛
[ISO4217] "Codes for the representation of currencies and funds", ISO 4217, 1995.
[ISO4217]“货币和资金表示代码”，ISO 42171995。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[URN] Moats, R., "URN Syntax", RFC 2141, May 1997.
[瓮]护城河，右，“瓮语法”，RFC 21411997年5月。
[URN-NS-IETF] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, August 1999.
[URN-NS-IETF]Moats，R.，“IETF文档的URN名称空间”，RFC 26481999年8月。
[XML] "Extensible Mark Up Language (XML) 1.0 (Second Edition)", A W3C Recommendation, <http://www.w3.org/TR/REC-xml>, October 2000.
[XML]“可扩展标记语言（XML）1.0（第二版）”，W3C建议<http://www.w3.org/TR/REC-xml>，2000年10月。
[XML-ns] "Namespaces in XML", A W3C Recommendation, <http://www.w3.org/TR/REC-xml-names>, January 1999.
[XML ns]“XML中的名称空间”，W3C建议<http://www.w3.org/TR/REC-xml-names>，1999年1月。
[XML-Registry] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[XML注册表]Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[XML-Schema-1] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, "XML Schema Part 1: Structures W3C Recommendation.", <http://www.w3.org/TR/xmlschema-1/>, May 2001.
[XML-Schema-1]Thompson，H.，Beech，D.，Maloney，M.，和N.Mendelsohn，“XML模式第1部分：结构W3C建议”<http://www.w3.org/TR/xmlschema-1/>，2001年5月。
[XML-Schema-2] Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes W3C Recommendation.", <http://www.w3.org/TR/xmlschema-2/>, May 2001.
[XML-Schema-2]Biron，P.和A.Malhotra，“XML模式第2部分：数据类型W3C建议”<http://www.w3.org/TR/xmlschema-2/>，2001年5月。
[VTS] Fujimura, K. and D. Eastlake, "Requirements and Design for Voucher Trading System (VTS)", RFC 3506, March 2003.
[VTS]Fujimura，K.和D.Eastlake，“凭证交易系统（VTS）的要求和设计”，RFC 3506，2003年3月。
[IPSEC] Thayer, R., Doraswamy, N., and R. Glenn, "IP Security Document Roadmap", RFC 2411, November 1998.
[IPSEC]Thayer，R.，Doraswamy，N.，和R.Glenn，“IP安全文档路线图”，RFC 24111998年11月。
[TLS] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC 2246, January 1999.
[TLS]Dierks，T.和C.Allen，“TLS协议版本1.0”，RFC 2246，1999年1月。
[VTS-API] Terada, M. and K. Fujimura, "Voucher Trading System Application Programming Interface (VTS-API)", RFC 4154, September 2005.
[VTS-API]Terada，M.和K.Fujimura，“凭证交易系统应用程序编程接口（VTS-API）”，RFC 4154，2005年9月。
[XMLDSIG] Eastlake 3rd, D., Reagle, J., and D. Solo, "(Extensible Markup Language) XML-Signature Syntax and Processing", RFC 3275, March 2002.
[XMLDSIG]Eastlake 3rd，D.，Reagle，J.，和D.Solo，“（可扩展标记语言）XML签名语法和处理”，RFC 3275，2002年3月。
Authors' Addresses
作者地址
Ko Fujimura NTT Corporation 1-1 Hikari-no-oka, Yokosuka-shi, Kanagawa, 239-0847 JAPAN
日本神奈川横须贺市Hikari no oka 1-1藤村NTT公司，邮编：239-0847
Phone: +81-(0)46-859-3053
Fax: +81-(0)46-855-1730
EMail: fujimura.ko@lab.ntt.co.jp
Phone: +81-(0)46-859-3053
Fax: +81-(0)46-855-1730
EMail: fujimura.ko@lab.ntt.co.jp
Masayuki Terada NTT DoCoMo, Inc. 3-5 Hikari-no-oka, Yokosuka-shi, Kanagawa, 239-8536 JAPAN
日本神奈川横须贺市Hikari no oka 3-5号田田田正行公司，邮编：239-8536
Phone: +81-(0)46-840-3809
Fax: +81-(0)46-840-3705
EMail: te@rex.yrp.nttdocomo.co.jp
Phone: +81-(0)46-840-3809
Fax: +81-(0)46-840-3705
EMail: te@rex.yrp.nttdocomo.co.jp
Donald E. Eastlake 3rd Motorola Laboratories 155 Beaver Street Milford, MA 01757 USA
Donald E.Eastlake 3rd Motorola Laboratories美国马萨诸塞州米尔福德市海狸街155号，邮编01757
Phone: 1-508-786-7554 (work) 1-508-634-2066 (home) EMail: Donald.Eastlake@motorola.com
电话：1-508-786-7554（工作）1-508-634-2066（家）电子邮件：Donald。Eastlake@motorola.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。