Network Working Group J. Slein
Request for Comments: 2291 Xerox Corporation
Category: Informational F. Vitali
University of Bologna
E. Whitehead
U.C. Irvine
D. Durand
Boston University
February 1998
Network Working Group J. Slein
Request for Comments: 2291 Xerox Corporation
Category: Informational F. Vitali
University of Bologna
E. Whitehead
U.C. Irvine
D. Durand
Boston University
February 1998
Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web
万维网分布式创作和版本控制协议的要求
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 (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
Abstract
摘要
Current World Wide Web (WWW or Web) standards provide simple support for applications which allow remote editing of typed data. In practice, the existing capabilities of the WWW have proven inadequate to support efficient, scalable remote editing free of overwriting conflicts. This document presents a list of features in the form of requirements for a Web Distributed Authoring and Versioning protocol which, if implemented, would improve the efficiency of common remote editing operations, provide a locking mechanism to prevent overwrite conflicts, improve link management support between non-HTML data types, provide a simple attribute-value metadata facility, provide for the creation and reading of container data types, and integrate versioning into the WWW.
当前的万维网（WWW或Web）标准为允许远程编辑键入数据的应用程序提供了简单的支持。实际上，WWW的现有功能已被证明不足以支持高效、可扩展的远程编辑，而不存在覆盖冲突。本文档以Web分布式创作和版本控制协议的要求形式列出了一系列功能，如果实施，将提高常见远程编辑操作的效率，提供锁定机制以防止覆盖冲突，改进非HTML数据类型之间的链接管理支持，提供一个简单的属性值元数据工具，提供容器数据类型的创建和读取，并将版本控制集成到WWW中。
This document describes functionality which, if incorporated in an extension to the existing HTTP proposed standard [HTTP], would allow tools for remote loading, editing and saving (publishing) of various media types on the WWW to interoperate with any compliant Web server. As much as possible, this functionality is described without suggesting a proposed implementation, since there are many ways to perform the functionality within the WWW framework. It is also
本文档描述了一些功能，如果将这些功能合并到现有HTTP建议标准[HTTP]的扩展中，将允许用于远程加载、编辑和保存（发布）WWW上各种媒体类型的工具与任何兼容的Web服务器进行互操作。由于在WWW框架中有许多方法可以执行该功能，因此在描述该功能时尽可能不建议拟议的实现。也是
possible that a single mechanism could simultaneously satisfy several requirements.
单个机构可能同时满足多个要求。
This document reflects the consensus of the WWW Distributed Authoring and Versioning working group (WebDAV) as to the functionality that should be standardized to support distributed authoring and versioning on the Web. As with any set of requirements, practical considerations may make it impossible to satisfy them all. It is the intention of the WebDAV working group to come as close as possible to satisfying them in the specifications that make up the WebDAV protocol.
本文档反映了WWW分布式创作和版本控制工作组（WebDAV）就支持Web上的分布式创作和版本控制应标准化的功能达成的共识。与任何一组需求一样，实际的考虑可能使其不可能全部满足。WebDAV工作组的目的是尽可能在构成WebDAV协议的规范中满足这些要求。
Current Web standards contain functionality which enables the editing of Web content at a remote location, without direct access to the storage media via an operating system. This capability is exploited by several existing HTML distributed authoring tools, and by a growing number of mainstream applications (e.g., word processors) which allow users to write (publish) their work to an HTTP server. To date, experience from the HTML authoring tools has shown they are unable to meet their users' needs using the facilities of Web standards. The consequence of this is either postponed introduction of distributed authoring capability, or the addition of nonstandard extensions to the HTTP protocol or other Web standards. These extensions, developed in isolation, are not interoperable.
当前的Web标准包含的功能允许在远程位置编辑Web内容，而无需通过操作系统直接访问存储介质。一些现有的HTML分布式创作工具以及越来越多的主流应用程序（如文字处理器）利用了这一功能，这些应用程序允许用户将其作品写入（发布）HTTP服务器。迄今为止，HTML创作工具的经验表明，使用Web标准的工具无法满足用户的需求。其结果要么是推迟了分布式创作能力的引入，要么是在HTTP协议或其他Web标准中添加了非标准扩展。这些独立开发的扩展不可互操作。
Other authoring applications have wanted to access document repositories or version control systems through Web gateways, and have been similarly frustrated. Where this access is available at all, it is through nonstandard extensions to HTTP or other standards that force clients to use a different interface for each vendor's service.
其他创作应用程序希望通过Web网关访问文档存储库或版本控制系统，但也受到了类似的挫折。如果这种访问是可用的，则是通过对HTTP或其他标准的非标准扩展，强制客户端为每个供应商的服务使用不同的接口。
This document describes requirements for a set of standard extensions to HTTP that would allow distributed Web authoring tools to provide the functionality their users need by means of the same standard syntax across all compliant servers. The broad categories of functionality that need to be standardized are:
本文档描述了对HTTP的一组标准扩展的需求，这些扩展允许分布式Web创作工具通过所有兼容服务器上相同的标准语法提供用户所需的功能。需要标准化的功能大类包括：
Properties Links Locking Reservations Retrieval of Unprocessed Source Partial Write Name Space Manipulation Collections
属性链接锁定保留检索未处理的源部分写入名称空间操作集合
Versioning Variants Security Internationalization
版本控制变体安全国际化
Where there is overlap, usage is intended to be consistent with that in the HTTP 1.1 specification [HTTP].
在有重叠的地方，使用与HTTP 1.1规范[HTTP]一致。
Client A program which issues HTTP requests and accepts responses.
客户端发出HTTP请求并接受响应的程序。
Collection A collection is a resource that contains other resources, either directly or by reference.
集合集合是包含其他资源（直接或通过引用）的资源。
Distributed Authoring Tool A program which can retrieve a source entity via HTTP, allow editing of this entity, and then save/publish this entity to a server using HTTP.
分布式创作工具一种程序，可以通过HTTP检索源实体，允许编辑此实体，然后使用HTTP将此实体保存/发布到服务器。
Entity The information transferred in a request or response.
实体在请求或响应中传输的信息。
Hierarchical Collection A hierarchical organization of resources. A hierarchical collection is a resource that contains other resources, including collections, either directly or by reference.
分级收集资源的分级组织。分层集合是包含其他资源的资源，包括直接或通过引用的集合。
Link A typed connection between two or more resources.
链接两个或多个资源之间的类型化连接。
Lock A mechanism for preventing anyone other than the owner of the lock from accessing a resource.
锁定一种机制，用于防止锁所有者以外的任何人访问资源。
Member of Version Graph A resource that is a node in a version graph, and so is derived from the resources that precede it in the graph, and is the basis of those that succeed it.
版本图成员是版本图中的一个节点，因此它是从图中位于它前面的资源派生出来的，并且是它后面的资源的基础。
Property Named descriptive information about a resource.
属性命名为有关资源的描述性信息。
Reservation A declaration that one intends to edit a resource.
保留一个声明，表示要编辑一个资源。
Resource A network data object or service that can be identified by a URI.
资源可以由URI标识的网络数据对象或服务。
Server A program which receives and responds to HTTP requests.
服务器接收并响应HTTP请求的程序。
User Agent The client that initiates a request.
用户代理发起请求的客户端。
Variant A representation of a resource. A resource may have one or more representations associated with it at any given time.
变量资源的表示形式。在任何给定时间，资源可能有一个或多个与之关联的表示。
Version Graph A directed acyclic graph with resources as its nodes, where each node is derived from its predecessor(s).
版本图以资源为节点的有向无环图，其中每个节点都是从其前身派生的。
Write Lock A lock that prevents anyone except its owner from modifying the resource it applies to.
写锁防止除所有者以外的任何人修改其应用的资源的锁。
This section describes a set of general principles that the WebDAV extensions should follow. These principles cut across categories of functionality.
本节介绍WebDAV扩展应遵循的一组一般原则。这些原则跨越了功能的各个类别。
All WebDAV clients should be able to work with any WebDAV-compliant HTTP server. It is acceptable for some client/server combinations to provide special features that are not universally available, but the protocol should be sufficient that a basic level of functionality will be universal.
所有WebDAV客户端都应该能够与任何符合WebDAV的HTTP服务器一起工作。某些客户机/服务器组合可以提供不通用的特殊功能，但协议应足以使基本功能级别具有通用性。
The WebDAV extensions should be designed to allow client implementations to be simple.
WebDAV扩展的设计应使客户端实现简单。
It should be possible to implement a WebDAV-compliant server in such a way that it can interoperate with non-WebDAV clients. Such a server would be able to understand any valid HTTP 1.1 request from an ordinary Web client without WebDAV extensions, and to provide a valid HTTP 1.1 response that does not require the client to understand the extensions.
应该可以实现一个WebDAV兼容的服务器，使其能够与非WebDAV客户端进行互操作。这样的服务器将能够理解来自普通Web客户机的任何有效HTTP 1.1请求，而不需要WebDAV扩展，并提供不需要客户机理解扩展的有效HTTP 1.1响应。
WebDAV-compliant servers should be able to work with existing resources and URIs [URL]. Special additional information should not become a mandatory part of document formats.
与WebDAV兼容的服务器应该能够使用现有资源和URI[URL]。特殊附加信息不应成为文件格式的强制性部分。
Distribution and replication are at the heart of the Internet. All WebDAV extensions should be designed to allow for distribution and replication. Version trees should be able to be split across multiple servers. Collections may have members on different servers. Any resource may be cached or replicated for mobile computing or other reasons. Consequently, the WebDAV extensions must be able to operate in a distributed, replicated environment.
分发和复制是Internet的核心。所有WebDAV扩展都应设计为允许分发和复制。版本树应该能够在多个服务器之间拆分。集合的成员可能位于不同的服务器上。出于移动计算或其他原因，可以缓存或复制任何资源。因此，WebDAV扩展必须能够在分布式复制环境中运行。
The WebDAV extensions should keep to a minimum the number of interactions between the client and the server needed to perform common functions. For example, publishing a document to the Web will often mean publishing content together with related properties. A client may often need to find out what version graph a particular resource belongs to, or to find out which resource in a version graph is the published one. The extensions should make it possible to do these things efficiently.
WebDAV扩展应将执行常见功能所需的客户端和服务器之间的交互次数保持在最低限度。例如，将文档发布到Web通常意味着将内容和相关属性一起发布。客户机可能经常需要找出特定资源所属的版本图，或者找出版本图中哪个资源是已发布的资源。这些扩展应该能够有效地完成这些事情。
WebDAV adds a number of new types of objects to the Web: properties, collections, version graphs, etc. Existing HTTP methods such as DELETE and PUT will have to operate in well-defined ways in this expanded environment. WebDAV should explicitly address not only new methods, headers, and MIME types, but also any required changes to the existing HTTP methods and headers.
WebDAV向Web添加了许多新类型的对象：属性、集合、版本图等。现有的HTTP方法（如DELETE和PUT）必须在这个扩展的环境中以定义良好的方式运行。WebDAV不仅应该显式地处理新的方法、头和MIME类型，还应该显式地处理对现有HTTP方法和头所需的任何更改。
It may be desirable to transport WebDAV requests and responses by other mechanisms, particularly EMail, in addition to HTTP. The WebDAV protocol specification should not preclude a future body from developing an interoperability specification for disconnected operation via EMail.
除了HTTP之外，还可以通过其他机制（尤其是电子邮件）传输WebDAV请求和响应。WebDAV协议规范不应妨碍未来机构为通过电子邮件断开连接的操作制定互操作性规范。
In the requirement descriptions below, the requirement will be stated, followed by its rationale.
在下面的需求描述中，将说明该需求，然后是其基本原理。
It must be possible to create, modify, read and delete arbitrary properties on resources of any media type.
必须能够在任何媒体类型的资源上创建、修改、读取和删除任意属性。
Properties describe resources of any media type. They may include bibliographic information such as author, title, publisher, and subject, constraints on usage, PICS ratings, etc. These properties have many uses, such as supporting searches on property values, enforcing copyrights, and the creation of catalog entries as placeholders for objects which are not available in electronic form, or which will be available later.
属性描述任何媒体类型的资源。它们可能包括书目信息，如作者、标题、出版商和主题、使用限制、PICS评级等。这些属性有许多用途，例如支持对属性值的搜索、强制版权以及创建目录条目作为电子形式不可用对象的占位符，或者以后会有。
It must be possible to create, modify, read and delete typed links between resources of any media type.
必须能够在任何媒体类型的资源之间创建、修改、读取和删除类型化链接。
One type of link between resources is the hypertext link, which is browsable using a hypertext style point-and-click user interface. Links, whether they are browsable hypertext links, or simply a means of capturing a relationship between resources, have many purposes. Links can support pushbutton printing of a multi-resource document in a prescribed order, jumping to the access control page for a resource, and quick browsing of related information, such as a table
资源之间的链接类型之一是超文本链接，可以使用超文本样式的点击式用户界面进行浏览。链接，无论是可浏览的超文本链接，还是仅仅是捕获资源之间关系的一种手段，都有许多用途。链接可以支持按指定顺序打印多资源文档，跳转到资源的访问控制页面，以及快速浏览相关信息，如表
of contents, an index, a glossary, a bibliographic record, help pages, etc. While link support is provided by the HTML "LINK" element, this is limited only to HTML resources [HTML]. Similar support is needed for bitmap image types, and other non-HTML media types.
内容、索引、词汇表、书目记录、帮助页等。虽然链接支持由HTML“link”元素提供，但这仅限于HTML资源[HTML]。位图图像类型和其他非HTML媒体类型也需要类似的支持。
5.3.1.1. Independence of locks. It must be possible to lock a resource without performing an additional retrieval of the resource, and without committing to editing the resource.
5.3.1.1. 锁的独立性。必须能够锁定资源，而无需执行额外的资源检索，也无需提交对资源的编辑。
5.3.1.2. Multi-Resource Locking. It must be possible to take out a lock on multiple resources residing on the same server in a single action, and this locking operation must be atomic across these resources.
5.3.1.2. 多资源锁定。必须能够在一次操作中锁定驻留在同一服务器上的多个资源，并且此锁定操作必须是跨这些资源的原子操作。
5.3.2.1. Write Locks. It must be possible to restrict modification of a resource to a specific person.
5.3.2.1. 写锁。必须能够将资源的修改限制到特定的人。
5.3.2.2. Lock Query. It must be possible to find out whether a given resource has any active locks, and if so, who holds those locks.
5.3.2.2. 锁定查询。必须能够找出给定资源是否有任何活动锁，如果有，谁持有这些锁。
5.3.2.3. Unlock. It must be possible to remove a lock.
5.3.2.3. 解锁。必须能够卸下锁。
At present, the Web provides limited support for preventing two or more people from overwriting each other's modifications when they save to a given URI. Furthermore, there is no way to discover whether someone else is currently making modifications to a resource. This is known as the "lost update problem," or the "overwrite problem." Since there can be significant cost associated with discovering and repairing lost modifications, preventing this problem is crucial for supporting distributed authoring. A write lock ensures that only one person may modify a resource, preventing overwrites. Furthermore, locking support is a key component of many versioning schemes, a desirable capability for distributed authoring.
目前，Web在防止两个或更多人在保存到给定URI时覆盖彼此的修改方面提供了有限的支持。此外，无法发现是否有其他人正在对资源进行修改。这被称为“丢失的更新问题”或“覆盖问题”。由于发现和修复丢失的修改可能会带来巨大的成本，因此防止此问题对于支持分布式创作至关重要。写锁确保只有一个人可以修改资源，从而防止覆盖。此外，锁定支持是许多版本控制方案的关键组件，是分布式创作的理想功能。
An author may wish to lock an entire web of resources even though he is editing just a single resource, to keep the other resources from changing. In this way, an author can ensure that if a local hypertext web is consistent in his distributed authoring tool, it will then be
作者可能希望锁定整个资源网，即使他只编辑一个资源，以防止其他资源发生变化。通过这种方式，作者可以确保，如果本地超文本web在其分布式创作工具中是一致的，那么它将是一致的
consistent when he writes it to the server. Because of this, it should be possible to take out a lock without also causing transmission of the contents of a resource.
当他将其写入服务器时保持一致。因此，应该能够在不引起资源内容传输的情况下取出锁。
It is often necessary to guarantee that a lock or unlock operation occurs at the same time across multiple resources, a feature which is supported by the multiple-resource locking requirement. This is useful for preventing a collision between two people trying to establish locks on the same set of resources, since with multi-resource locking, one of the two people will get a lock. If this same multiple-resource locking scenario was repeated by using atomic lock operations iterated across the resources, the result would be a splitting of the locks between the two people, based on resource ordering and race conditions.
通常有必要保证在多个资源之间同时发生锁定或解锁操作，这是多资源锁定需求所支持的功能。这对于防止试图在同一组资源上建立锁的两个人之间发生冲突非常有用，因为使用多资源锁定时，两个人中的一个人将获得锁。如果通过使用原子锁操作在资源之间迭代来重复相同的多资源锁场景，那么结果将是基于资源顺序和竞争条件在两个人之间拆分锁。
5.4.1.1. Reserve. It must be possible for a principal to register with the server an intent to edit a given resource, so that other principals can discover who intends to edit the resource.
5.4.1.1. 储备主体必须能够向服务器注册编辑给定资源的意图，以便其他主体能够发现谁想要编辑该资源。
5.4.1.2. Reservation Query. It must be possible to find out whether a given resource has any active reservations, and if so, who currently holds reservations.
5.4.1.2. 预订查询。必须能够查明给定资源是否有任何活动保留，如果有，目前谁持有保留。
5.4.1.3. Release Reservation. It must be possible to release the reservation.
5.4.1.3. 取消预订。必须能够解除预订。
Experience from configuration management systems has shown that people need to know when they are about to enter a parallel editing situation. Once notified, they either decide not to edit in parallel with the other authors, or they use out-of-band communication (face-to-face, telephone, etc.) to coordinate their editing to minimize the difficulty of merging their results. Reservations are separate from locking, since a write lock does not necessarily imply a resource will be edited, and a reservation does not carry with it any access restrictions. This capability supports versioning, since a check-out typically involves taking out a write lock, making a reservation, and getting the resource to be edited.
配置管理系统的经验表明，人们需要知道何时将进入并行编辑环境。一旦接到通知，他们要么决定不与其他作者并行编辑，要么使用带外通信（面对面、电话等）来协调编辑，以最大限度地降低合并结果的难度。保留与锁定是分开的，因为写锁定不一定意味着资源将被编辑，并且保留不附带任何访问限制。此功能支持版本控制，因为签出通常涉及取出写锁、进行保留以及获取要编辑的资源。
The source of any given resource must be retrievable by any principal with authorization to edit the resource.
任何给定资源的源必须可由具有编辑资源授权的任何主体检索。
There are many cases where the source stored on a server does not correspond to the actual entity transmitted in response to an HTTP GET. Current known cases are server side include directives, and Standard Generalized Markup Language (SGML) source which is converted on the fly to HyperText Markup Language (HTML) [HTML] output entities. There are many possible cases, such as automatic conversion of bitmap images into several variant bitmap media types (e.g. GIF, JPEG), and automatic conversion of an application's native media type into HTML. As an example of this last case, a word processor could store its native media type on a server which automatically converts it to HTML. A GET of this resource would retrieve the HTML. Retrieving the source would retrieve the word processor native format.
在许多情况下，存储在服务器上的源与响应HTTP GET传输的实际实体不对应。目前已知的情况包括服务器端include指令和标准通用标记语言（SGML）源代码，它们被动态转换为超文本标记语言（HTML）[HTML]输出实体。有许多可能的情况，例如将位图图像自动转换为多种不同的位图媒体类型（例如GIF、JPEG），以及将应用程序的本机媒体类型自动转换为HTML。作为最后一个例子，字处理器可以将其本机媒体类型存储在服务器上，服务器会自动将其转换为HTML。获取此资源将检索HTML。检索源将检索字处理器本机格式。
5.6. Partial Write.
5.6. 部分写入。
After editing a resource, it must be possible to write only the changes to the resource, rather than retransmitting the entire resource.
编辑资源后，必须能够只写入对资源的更改，而不是重新传输整个资源。
During distributed editing which occurs over wide geographic separations and/or over low bandwidth connections, it is extremely inefficient and frustrating to rewrite a large resource after minor changes, such as a one-character spelling correction. Support is needed for transmitting "insert" (e.g., add this sentence in the middle of a document) and "delete" (e.g. remove this paragraph from the middle of a document) style updates. Support for partial resource updates will make small edits more efficient, and allow distributed authoring tools to scale up for editing large documents.
在分布编辑过程中，在广泛的地理间隔和/或低带宽连接上进行编辑，在微小的更改（例如一个字符的拼写更正）后重写大型资源是非常低效和令人沮丧的。需要支持发送“插入”（例如，在文档的中间添加这个句子）和“删除”（例如从文档中间删除该段落）样式更新。对部分资源更新的支持将使小型编辑更加高效，并允许分布式创作工具扩展以编辑大型文档。
It must be possible to duplicate a resource without a client loading, then resaving the resource. After the copy operation, a modification to either resource must not cause a modification to the other.
必须能够在不加载客户端的情况下复制资源，然后重新保存资源。复制操作后，对任一资源的修改不得导致对另一资源的修改。
There are many reasons why a resource might need to be duplicated, such as changing ownership, preparing for major modifications, or making a backup. Due to network costs associated with loading and saving a resource, it is far preferable to have a server perform a resource copy than a client.
可能需要复制资源的原因有很多，例如更改所有权、准备重大修改或进行备份。由于与加载和保存资源相关的网络成本，让服务器执行资源复制比让客户端执行资源复制更可取。
It must be possible to change the location of a resource without a client loading, then resaving the resource under a different name. After the move operation, it must no longer be possible to access the resource at its original location.
必须能够在不加载客户端的情况下更改资源的位置，然后以其他名称重新保存资源。执行移动操作后，必须不再能够在其原始位置访问资源。
It is often necessary to change the name of a resource, for example due to adoption of a new naming convention, or if a typing error was made entering the name originally. Due to network costs, it is undesirable to perform this operation by loading, then resaving the resource, followed by a delete of the old resource. Similarly, a single rename operation is more efficient than a copy followed by a delete operation. Note that moving a resource is considered the same function as renaming a resource.
通常有必要更改资源的名称，例如，由于采用了新的命名约定，或者最初输入名称时出现键入错误。由于网络成本，不希望通过加载、重新保存资源，然后删除旧资源来执行此操作。类似地，一次重命名操作比一次复制后再执行删除操作更有效。请注意，移动资源与重命名资源的功能相同。
A collection is a resource that is a container for other resources, including other collections. A resource may belong to a collection either directly or by reference. If a resource belongs to a collection directly, name space operations like copy, move, and delete applied to the collection also apply to the resource. If a resource belongs to a collection by reference, name space operations applied to the collection affect only the reference, not the resource itself.
集合是一种资源，它是其他资源（包括其他集合）的容器。资源可以直接或通过引用属于集合。如果资源直接属于某个集合，则应用于该集合的名称空间操作（如复制、移动和删除）也将应用于该资源。如果资源按引用属于某个集合，则应用于该集合的名称空间操作仅影响引用，而不影响资源本身。
5.8.1.1. List Collection. A listing of all resources in a specific collection must be accessible.
5.8.1.1. 列表集合。必须可以访问特定集合中所有资源的列表。
5.8.1.2. Make Collection. It must be possible to create a new collection.
5.8.1.2. 收藏。必须能够创建新集合。
5.8.1.3. Add to Collection. It must be possible to add a resource to a collection directly or by reference.
5.8.1.3. 添加到集合中。必须能够直接或通过引用将资源添加到集合中。
5.8.1.4. Remove from Collection. It must be possible to remove a resource from a collection.
5.8.1.4. 从集合中删除。必须能够从集合中删除资源。
In [URL] it states that, "some URL schemes (such as the ftp, http, and file schemes) contain names that can be considered hierarchical." Especially for HTTP servers which directly map all or part of their URL name space into a filesystem, it is very useful to get a listing of all resources located at a particular hierarchy level. This functionality supports "Save As..." dialog boxes, which provide a listing of the entities at a current hierarchy level, and allow navigation through the hierarchy. It also supports the creation of graphical visualizations (typically as a network) of the hypertext structure among the entities at a hierarchy level, or set of levels. It also supports a tree visualization of the entities and their hierarchy levels.
在[URL]中，它指出，“一些URL方案（如ftp、http和文件方案）包含可被视为分层的名称。”特别是对于直接将其全部或部分URL名称空间映射到文件系统的http服务器，获取位于特定分层级别的所有资源的列表非常有用。此功能支持“另存为…”对话框，该对话框提供当前层次结构级别的实体列表，并允许在层次结构中导航。它还支持在层次级别或一组级别的实体之间创建超文本结构的图形可视化（通常作为网络）。它还支持实体及其层次结构级别的树可视化。
In addition, document management systems may want to make their documents accessible through the Web. They typically allow the organization of documents into collections, and so also want their users to be able to view the collection hierarchy through the Web.
此外，文档管理系统可能希望通过Web访问其文档。它们通常允许将文档组织到集合中，因此也希望其用户能够通过Web查看集合层次结构。
There are many instances where there is not a strong correlation between a URL hierarchy level and the notion of a collection. One example is a server in which the URL hierarchy level maps to a computational process which performs some resolution on the name. In this case, the contents of the URL hierarchy level can vary depending on the input to the computation, and the number of resources accessible via the computation can be very large. It does not make sense to implement a directory feature for such a name space. However, the utility of listing the contents of those URL hierarchy levels which do correspond to collections, such as the large number of HTTP servers which map their name space to a filesystem, argue for the inclusion of this capability, despite not being meaningful in all
在许多情况下，URL层次结构级别与集合概念之间没有很强的相关性。一个例子是服务器，其中URL层次结构级别映射到对名称执行某种解析的计算过程。在这种情况下，URL层次结构级别的内容可能因计算的输入而异，并且通过计算可访问的资源数量可能非常大。为这样的名称空间实现目录功能是没有意义的。然而，列出与集合相对应的那些URL层次结构级别的内容的实用程序，例如大量将其名称空间映射到文件系统的HTTP服务器，主张包含此功能，尽管这在所有方面都没有意义
cases. If listing the contents of a URL hierarchy level does not makes sense for a particular URL, then a "405 Method Not Allowed" status code could be issued.
案例。如果列出URL层次结构级别的内容对特定URL没有意义，则可能会发出“405方法不允许”状态代码。
The ability to create collections to hold related resources supports management of a name space by packaging its members into small, related clusters. The utility of this capability is demonstrated by the broad implementation of directories in recent operating systems. The ability to create a collection also supports the creation of "Save As..." dialog boxes with "New Level/Folder/Directory" capability, common in many applications.
创建集合以保存相关资源的能力支持通过将名称空间的成员打包到小型相关集群来管理名称空间。最近的操作系统中目录的广泛实现证明了此功能的实用性。创建集合的功能还支持创建具有“新级别/文件夹/目录”功能的“另存为…”对话框，这在许多应用程序中很常见。
5.9.1.1. Stability of versions. Most versioning systems are intended to provide an accurate record of the history of evolution of a document. This accuracy is ensured by the fact that a version eventually becomes "frozen" and immutable. Once a version is frozen, further changes will create new versions rather than modifying the original. In order for caching and persistent references to be properly maintained, a client must be able to determine that a version has been frozen. Any successful attempt to retrieve a frozen version of a resource will always retrieve exactly the same content, or return an error if that version (or the resource itself) is no longer available.
5.9.1.1. 版本的稳定性。大多数版本控制系统旨在提供文档演变历史的准确记录。这种准确性是由一个版本最终变得“冻结”和不可变这一事实来保证的。一旦版本被冻结，进一步的更改将创建新版本，而不是修改原始版本。为了正确维护缓存和持久引用，客户端必须能够确定某个版本已被冻结。任何成功检索资源冻结版本的尝试都将始终检索完全相同的内容，或者在该版本（或资源本身）不再可用时返回错误。
5.9.1.2. Operations for Creating New Versions. Version management systems vary greatly in the operations they require, the order of the operations, and how they are combined into atomic functions. In the most complete cases, the logical operations involved are:
5.9.1.2. 创建新版本的操作。版本管理系统在所需的操作、操作顺序以及如何将它们组合成原子功能方面存在很大差异。在最完整的情况下，涉及的逻辑操作包括：
o Reserve existing version o Lock existing version o Retrieve existing version o Request or suggest identifier for new version o Write new version o Release lock o Release reservation
o 保留现有版本o锁定现有版本o检索现有版本o请求或建议新版本的标识符o写入新版本o释放锁定o释放保留
With the exception of requesting a new version identifier, all of these operations have applications outside of versioning and are either already part of HTTP or are discussed in earlier sections of these requirements. Typically, versioning systems combine reservation, locking, and retrieval -- or some subset of these -- into an atomic checkout function. They combine writing, releasing
除了请求一个新的版本标识符之外，所有这些操作都有版本控制之外的应用程序，或者已经是HTTP的一部分，或者在这些需求的前面部分中讨论过。通常，版本控制系统将保留、锁定和检索（或其中的一些子集）组合到一个原子签出函数中。它们结合了写作、写作和写作
the lock, and releasing the reservation -- or some subset of these -- into an atomic checkin function. The new version identifier may be assigned either at checkout or at checkin.
锁，并将保留（或其中的一些子集）释放到原子签入函数中。新版本标识符可以在签出或签入时分配。
The WebDAV extensions must find some balance between allowing versioning servers to adopt whatever policies they wish with regard to these operations and enforcing enough uniformity to keep client implementations simple.
WebDAV扩展必须在允许版本控制服务器对这些操作采用他们想要的任何策略和强制执行足够的一致性以保持客户端实现简单之间找到某种平衡。
5.9.1.3. The Versioning Model. Each version typically stands in a "derived from" relationship to its predecessor(s). It is possible to derive several different versions from a single version (branching), and to derive a single version from several versions (merging). Consequently, the collection of related versions forms a directed acyclic graph. In the following discussion, this graph will be called a "version graph". Each node of this graph is a "version" or "member of the version graph". The arcs of the graph capture the "derived from" relationships.
5.9.1.3. 版本控制模型。每个版本通常与其前一版本存在“派生自”关系。可以从单个版本派生出多个不同的版本（分支），也可以从多个版本派生出单个版本（合并）。因此，相关版本的集合形成一个有向无环图。在下面的讨论中，此图将被称为“版本图”。此图的每个节点都是“版本”或“版本图的成员”。曲线图的圆弧捕捉“派生自”关系。
It is also possible for a single resource to participate in multiple version graphs.
单个资源也可以参与多个版本图。
The WebDAV extensions should support this versioning model, though particular servers may restrict it in various ways.
WebDAV扩展应该支持此版本控制模型，尽管特定服务器可能以各种方式限制它。
5.9.1.4. Versioning Policies. Many writers, including Feiler [CM] and Haake and Hicks [VSE], have discussed the notion of versioning styles (referred to here as versioning policies, to reflect the nature of client/server interaction) as one way to think about the different policies that versioning systems implement. Versioning policies include decisions on the shape of version histories (linear or branched), the granularity of change tracking, locking requirements made by a server, etc. The protocol should clearly identify the policies that it dictates and the policies that are left up to versioning system implementors or administrators.
5.9.1.4. 版本控制策略。包括Feiler[CM]和Haake and Hicks[VSE]在内的许多作者都讨论过版本控制风格的概念（这里称为版本控制策略，以反映客户机/服务器交互的性质），作为思考版本控制系统实现的不同策略的一种方式。版本控制策略包括关于版本历史的形状（线性或分支）、更改跟踪的粒度、服务器的锁定要求等的决策。协议应清楚地标识它指定的策略以及留给版本控制系统实施者或管理员的策略。
5.9.1.5. It is possible to version resources of any media type.
5.9.1.5. 可以对任何媒体类型的资源进行版本设置。
5.9.2.1. Referring to a version graph. There must be a way to refer to a version graph as a whole.
5.9.2.1. 参考版本图。必须有一种方法将版本图作为一个整体引用。
Some queries and operations apply, not to any one member of a version graph, but to the version graph as a whole. For example, a client may request that an entire graph be moved, or may ask for a version history. In these cases, a way to refer to the whole version graph is required.
有些查询和操作不是应用于版本图的任何一个成员，而是应用于整个版本图。例如，客户机可能会要求移动整个图形，或者要求提供版本历史记录。在这些情况下，需要一种引用整个版本图的方法。
5.9.2.2. Referring to a specific member of a version graph. There must be a way to refer to each member of a version graph. This means that each member of the graph is itself a resource.
5.9.2.2. 指版本图的特定成员。必须有一种方法来引用版本图的每个成员。这意味着图的每个成员本身就是一个资源。
Each member of a version graph must be a resource if it is to be possible for a hypertext link to refer to specific version of a page, or for a client to request a specific version of a document for editing.
如果超文本链接可以引用页面的特定版本，或者客户端可以请求编辑文档的特定版本，则版本图的每个成员都必须是资源。
5.9.2.3. A client must be able to determine whether a resource is a version graph, or whether a resource is itself a member of a version graph.
5.9.2.3. 客户机必须能够确定资源是否是版本图，或者资源本身是否是版本图的成员。
A resource may be a simple, non-versioned resource, or it may be a version graph, or it may be a member of a version graph. A client needs to be able to tell which sort of resource it is accessing.
资源可以是简单的、未版本化的资源，也可以是版本图，也可以是版本图的成员。客户机需要能够知道它正在访问哪种资源。
5.9.2.4. There must be a way to refer to a server-defined default member of a version graph.
5.9.2.4. 必须有一种方法来引用版本图的服务器定义的默认成员。
The server should return a default version of a resource for requests that ask for the default version, as well as for requests where no specific version information is provided. This is one of the simplest ways to guarantee non-versioning client compatibility. This does not rule out the possibility of a server returning an error when no sensible default exists.
对于请求默认版本的请求以及未提供特定版本信息的请求，服务器应返回资源的默认版本。这是保证无版本客户端兼容性的最简单方法之一。这并不排除服务器在不存在可感知的默认值时返回错误的可能性。
It may also be desirable to be able to refer to other special members of a version graph. For example, there may be a current version for editing that is different from the default version. For a graph with several branches, it may be useful to be able to request the tip version of any branch.
可能还希望能够引用版本图的其他特殊成员。例如，当前编辑版本可能与默认版本不同。对于具有多个分支的图，能够请求任何分支的tip版本可能很有用。
5.9.2.5. It must be possible, given a reference to a member of a version graph, to find out which version graph(s) that resource belongs to.
5.9.2.5. 给定对版本图成员的引用，必须能够找出资源所属的版本图。
This makes it possible to understand the versioning context of the resource. It makes it possible to retrieve a version history for the graphs to which it belongs, and to browse the version graph. It also supports some comparison operations: It makes it possible to determine whether two references designate members of the same version graph.
这使得理解资源的版本控制上下文成为可能。它可以检索它所属的图的版本历史记录，并浏览版本图。它还支持一些比较操作：它可以确定两个引用是否指定同一版本图的成员。
5.9.2.6. Navigation of a version graph. Given a reference to a member of a version graph, it must be possible to discover and access the following related members of the version graph.
5.9.2.6. 版本图的导航。给定对版本图成员的引用，必须能够发现并访问版本图的以下相关成员。
o root member of the graph o predecessor member(s) o successor member(s) o default member of the graph
o 图的根成员o前导成员o后继成员o图的默认成员
It must be possible in some way for a versioning client to access versions related to a resource currently being examined.
版本控制客户端必须能够以某种方式访问与当前正在检查的资源相关的版本。
5.9.2.7. Version Topology. There must be a way to retrieve the complete version topology for a version graph, including information about all members of the version graph. The format for this information must be standardized so that the basic information can be used by all clients. Other specialized formats should be accommodated, for servers and clients that require information that cannot be included in the standard topology.
5.9.2.7. 版本拓扑。必须有一种方法来检索版本图的完整版本拓扑，包括有关版本图所有成员的信息。此信息的格式必须标准化，以便所有客户都可以使用基本信息。对于需要无法包含在标准拓扑中的信息的服务器和客户端，应采用其他专用格式。
5.9.2.8. A client must be able to propose a version identifier to be used for a new member of a version graph. The server may refuse to use the client's suggested version identifier. The server should tell the client what version identifier it has assigned to the new member of the version graph.
5.9.2.8. 客户机必须能够为版本图的新成员提出一个版本标识符。服务器可能拒绝使用客户端建议的版本标识符。服务器应该告诉客户端它为版本图的新成员分配了什么版本标识符。
5.9.2.9. A version identifier must be unique across a version graph.
5.9.2.9. 版本标识符在版本图中必须是唯一的。
5.9.2.10. A client must be able to supply version-specific properties to be associated with a new member of a version graph. (See Section 5.1 "Properties" above.) At a minimum, it must be possible to associate comments with the new member, explaining what changes were made.
5.9.2.10. 客户端必须能够提供与版本图的新成员关联的特定于版本的属性。（见上文第5.1节“属性”）至少必须能够将评论与新成员联系起来，解释所做的更改。
5.9.2.11. A client must be able to query the server for information about a version tree, including which versions are locked, which are reserved for editing, and by whom (Session Tracking).
5.9.2.11. 客户端必须能够向服务器查询有关版本树的信息，包括哪些版本已锁定、哪些版本保留供编辑以及由谁（会话跟踪）执行。
Versioning in the context of the world-wide web offers a variety of benefits:
万维网环境中的版本控制提供了多种好处：
It provides infrastructure for efficient and controlled management of large evolving web sites. Modern configuration management systems are built on some form of repository that can track the revision history of individual resources, and provide the higher-level tools to manage those saved versions. Basic versioning capabilities are required to support such systems.
它为大型不断发展的网站的高效和受控管理提供了基础设施。现代配置管理系统构建在某种形式的存储库上，可以跟踪单个资源的修订历史，并提供更高级别的工具来管理这些保存的版本。支持此类系统需要基本的版本控制功能。
It allows parallel development and update of single resources. Since versioning systems register change by creating new objects, they enable simultaneous write access by allowing the creation of variant versions. Many also provide merge support to ease the reverse operation.
它允许并行开发和更新单个资源。由于版本控制系统通过创建新对象来注册更改，因此它们通过允许创建变体版本来实现同步写访问。许多还提供了合并支持，以简化反向操作。
It provides a framework for coordinating changes to resources. While specifics vary, most systems provide some method of controlling or tracking access to enable collaborative resource development.
它提供了一个协调资源变化的框架。虽然具体情况各不相同，但大多数系统提供了一些控制或跟踪访问的方法，以支持协作资源开发。
It allows browsing through past and alternative versions of a resource. Frequently the modification and authorship history of a resource is critical information in itself.
它允许浏览资源的过去版本和替代版本。通常，资源的修改和作者历史本身就是关键信息。
It provides stable names that can support externally stored links for annotation and link-server support. Both annotation and link servers frequently need to store stable references to portions of resources that are not under their direct control. By providing stable states of resources, version control systems allow not only stable pointers into those resources, but also well-defined methods to determine the relationships of those states of a resource.
它提供了稳定的名称，可以支持外部存储的链接以支持注释和链接服务器。注释服务器和链接服务器通常都需要存储对不受其直接控制的资源部分的稳定引用。通过提供稳定的资源状态，版本控制系统不仅允许稳定的指向这些资源的指针，还允许定义良好的方法来确定资源状态之间的关系。
It allows explicit semantic representation of single resources with multiple states. A versioning system directly represents the fact that a resource has an explicit history, and a persistent identity across the various states it has had during the course of that history.
它允许具有多个状态的单个资源的显式语义表示。版本控制系统直接表示这样一个事实：资源具有明确的历史记录，并且在该历史记录的过程中，资源在各个状态之间具有持久的标识。
Detailed requirements for variants will be developed in a separate document.
变体的详细要求将在单独的文件中制定。
It must be possible to send variants to the server, describing the relationships between the variants and their parent resource. In addition, it must be possible to write and retrieve variants of property labels, property descriptions, and property values.
必须能够向服务器发送变体，描述变体与其父资源之间的关系。此外，必须能够写入和检索特性标签、特性描述和特性值的变体。
The HTTP working group is addressing problems of content negotiation and retrieval of variants of a resource. To extend this work to an authoring environment, WEBDAV must standardize mechanisms for authors to use when submitting variants to a server. Authors need to be able to provide variants in different file or document formats, for different uses. They need to provide variants optimized for different
HTTP工作组正在解决资源变体的内容协商和检索问题。为了将这项工作扩展到创作环境，WEBDAV必须标准化作者向服务器提交变体时使用的机制。作者需要能够为不同的用途提供不同文件或文档格式的变体。他们需要提供针对不同需求优化的变体
clients and for different output devices. They need to be able to provide variants in different languages in the international environment of the Web. In support of internationalization requirements (See 5.12 below), variants need to be supported not just for the content of resources, but for any information intended for human use, such as property values, labels, and descriptions.
用于不同输出设备的客户端和。他们需要能够在国际网络环境中提供不同语言的变体。为了支持国际化要求（参见下面的5.12），变体不仅需要支持资源的内容，还需要支持任何供人使用的信息，如属性值、标签和描述。
5.11.1. Authentication. The WebDAV specification should state how the WebDAV extensions interoperate with existing authentication schemes, and should make recommendations for using those schemes.
5.11.1. 认证。WebDAV规范应说明WebDAV扩展如何与现有的身份验证方案进行互操作，并应提出使用这些方案的建议。
5.11.2. Access Control. Access control requirements are specified in a separate access control work in progress [AC].
5.11.2. 访问控制。访问控制要求在单独的访问控制在建工程[AC]中规定。
5.11.3. Interoperability with Security Protocols. The WebDAV specification must provide a minimal list of security protocols which any compliant server / client must support. These protocols should insure the authenticity of messages and the privacy and integrity of messages in transit.
5.11.3. 与安全协议的互操作性。WebDAV规范必须提供任何兼容服务器/客户端必须支持的安全协议的最小列表。这些协议应确保消息的真实性以及传输中消息的隐私和完整性。
Since Web distributed authoring occurs in a multi-lingual environment, information intended for user comprehension must conform to the IETF Character Set Policy [CHAR]. This policy addresses character sets and encodings, and language tagging.
由于Web分布式创作发生在多语言环境中，因此用于用户理解的信息必须符合IETF字符集策略[CHAR]。此策略解决字符集和编码以及语言标记问题。
In the international environment of the Internet, it is important to insure that any information intended for user comprehension can be displayed in a writing system and language agreeable to both the client and the server. The information encompassed by this requirement includes not only the content of resources, but also such things as display names and descriptions of properties, property values, and status messages.
在互联网的国际环境中，确保用户理解的任何信息都能以客户机和服务器都能接受的书写系统和语言显示，这一点很重要。此需求包含的信息不仅包括资源的内容，还包括诸如显示名称、属性描述、属性值和状态消息等内容。
Our understanding of these issues has emerged as the result of much thoughtful discussion, email, and assistance by many people, who deserve recognition for their effort.
我们对这些问题的理解是许多人深思熟虑的讨论、电子邮件和帮助的结果，他们的努力值得认可。
Terry Allen, tallen@sonic.net Alan Babich, FileNet, babich@filenet.com Dylan Barrell, Open Text, dbarrell@opentext.ch Barbara Bazemore, PC DOCS, barbarab@pcdocs.com Martin Cagan, Continuus Software, Marty_Cagan@continuus.com Steve Carter, Novell, srcarter@novell.com Dan Connolly, World Wide Web Consortium, connolly@w3.org Jim Cunningham, Netscape, jfc@netscape.com Ron Daniel Jr., Los Alamos National Laboratory, rdaniel@lanl.gov Mark Day, Lotus, Mark_Day@lotus.com Martin J. Duerst, mduerst@ifi.unizh.ch Asad Faizi, Netscape, asad@netscape.com Ron Fein, Microsoft, ronfe@microsoft.com David Fiander, Mortice Kern Systems, davidf@mks.com Roy Fielding, U.C. Irvine, fielding@ics.uci.edu Mark Fisher, Thomson Consumer Electronics, FisherM@indy.tce.com Yaron Y. Goland, Microsoft, yarong@microsoft.com Phill Hallam-Baker, MIT, hallam@ai.mit.edu Dennis Hamilton, Xerox PARC, hamilton@parc.xerox.com Andre van der Hoek, University of Colorado, Boulder, andre@cs.colorado.edu Del Jensen, Novell, dcjensen@novell.com Gail Kaiser, Columbia University, kaiser@cs.columbia.edu Rohit Khare, World Wide Web Consortium, khare@w3.org Ora Lassila, Nokia Research Center, ora.lassila@research.nokia.com Ben Laurie, A.L. Digital, ben@algroup.co.uk Mike Little, Bellcore, little@bellcore.com Dave Long, America Online, dave@sb.aol.com Larry Masinter, Xerox PARC, masinter@parc.xerox.com Murray Maloney, SoftQuad, murray@sq.com Jim Miller, World Wide Web Consortium, jmiller@w3.org Howard S. Modell, Boeing, howard.s.modell@boeing.com Keith Moore, University of Tennessee, Knoxville, moore@cs.utk.edu Henrik Frystyk Nielsen, World Wide Web Consortium, frystyk@w3.org Jon Radoff, NovaLink, jradoff@novalink.com Alan Robertson, alanr@bell-labs.com Henry Sanders, Microsoft, Andrew Schulert, Microsoft, andyschu@microsoft.com Christopher Seiwald, Perforce Software, seiwald@perforce.com Einar Stefferud, stef@nma.com Richard Taylor, U.C. Irvine, taylor@ics.uci.edu Robert Thau, MIT, rst@ai.mit.edu Sankar Virdhagriswaran, sv@hunchuen.crystaliz.com Dan Whelan, FileNet, dan@FILENET.COM Gregory J. Woodhouse, gjw@wnetc.com
特里·艾伦，tallen@sonic.net艾伦·巴比奇，文件网，babich@filenet.com迪伦·巴雷尔，打开文本，dbarrell@opentext.ch芭芭拉·贝泽摩尔，个人电脑文档，barbarab@pcdocs.comMartin Cagan，连续软件公司，Marty_Cagan@continuus.com史蒂夫·卡特，诺维尔，srcarter@novell.comDan Connolly，万维网联盟，connolly@w3.org吉姆·坎宁安，网景公司， jfc@netscape.com罗恩·丹尼尔，洛斯阿拉莫斯国家实验室，rdaniel@lanl.gov马克·戴，莲花，马克_Day@lotus.com马丁·杜尔斯特，mduerst@ifi.unizh.chAsad Faizi，网景公司，asad@netscape.com罗恩·费恩，微软，ronfe@microsoft.comDavid Fiander，Mortice Kern系统公司，davidf@mks.com罗伊·菲尔丁，加州大学欧文分校， fielding@ics.uci.edu马克·费希尔，汤姆森消费电子公司，FisherM@indy.tce.comYaron Y.Goland，微软，yarong@microsoft.comPhill Hallam Baker，麻省理工学院，hallam@ai.mit.edu丹尼斯·汉密尔顿，施乐PARC，hamilton@parc.xerox.com安德烈范德霍克，科罗拉多大学，Boulder，andre@cs.colorado.edu德尔詹森，诺维尔， dcjensen@novell.com盖尔·凯泽，哥伦比亚大学，kaiser@cs.columbia.eduRohit Khare，万维网联盟，khare@w3.orgOra Lassila，诺基亚研究中心，Ora。lassila@research.nokia.comBen Laurie，A.L.Digital，ben@algroup.co.ukMike Little，Bellcore，little@bellcore.com戴夫·朗，美国在线，dave@sb.aol.com拉里·马辛特，施乐PARC，masinter@parc.xerox.comMurray Maloney，SoftQuad，murray@sq.comJim Miller，万维网联盟，jmiller@w3.org霍华德S.莫代尔，波音，霍华德S。modell@boeing.comKeith Moore，田纳西大学，诺克斯维尔，moore@cs.utk.edu万维网联盟Henrik Frystyk Nielsen，frystyk@w3.orgJon Radoff，NovaLink， jradoff@novalink.com艾伦·罗伯逊，alanr@bell-微软公司亨利·桑德斯，微软公司安德鲁·舒勒特，andyschu@microsoft.comChristopher Seiwald，Perforce软件公司，seiwald@perforce.com埃纳·斯特夫拉德，stef@nma.com理查德·泰勒，加州大学欧文分校，taylor@ics.uci.edu麻省理工，rst@ai.mit.eduSankar Virdhagriswaran， sv@hunchuen.crystaliz.comDan Whelan，文件网，dan@FILENET.COM格雷戈里·J·伍德豪斯，gjw@wnetc.com
[AC] J. Radoff, "Requirements for Access Control within Distributed
Authoring and Versioning Environments on the World Wide Web",
unpublished manuscript, <http://lists.w3.org/Archives/Public/w3c-
dist-auth/1997AprJun/0183.html>
[AC] J. Radoff, "Requirements for Access Control within Distributed
Authoring and Versioning Environments on the World Wide Web",
unpublished manuscript, <http://lists.w3.org/Archives/Public/w3c-
dist-auth/1997AprJun/0183.html>
[CHAR] Alvestrand, H., "IETF Policy on Character Sets and Languages", RFC 2277, January 1998.
[CHAR]Alvestrand，H.，“IETF字符集和语言政策”，RFC 2277，1998年1月。
[CM] P. Feiler, "Configuration Management Models in Commercial
Environments", Software Engineering Institute Technical Report
CMU/SEI-91-TR-7,
<http://www.sei.cmu.edu/products/publications/91.reports/91.tr.007.html>
[CM] P. Feiler, "Configuration Management Models in Commercial
Environments", Software Engineering Institute Technical Report
CMU/SEI-91-TR-7,
<http://www.sei.cmu.edu/products/publications/91.reports/91.tr.007.html>
[HTML] Berners-Lee, T., and D. Connolly, "HyperText Markup Language Specification - 2.0", RFC 1866, November 1995.
[HTML]Berners Lee，T.和D.Connolly，“超文本标记语言规范-2.0”，RFC 18661995年11月。
[HTTP] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2068, January 1997.
[HTTP]Fielding，R.，Gettys，J.，Mogul，J.，Frystyk，H.，和T.Berners Lee，“超文本传输协议——HTTP/1.1”，RFC 2068，1997年1月。
[ISO 10646] ISO/IEC 10646-1:1993. "International Standard --
Information Technology -- Universal Multiple-Octet Coded Character
Set (UCS) -- Part 1: Architecture and Basic Multilingual Plane."
[ISO 10646] ISO/IEC 10646-1:1993. "International Standard --
Information Technology -- Universal Multiple-Octet Coded Character
Set (UCS) -- Part 1: Architecture and Basic Multilingual Plane."
[URL] Berners-Lee, T., Masinter, L., and M. McCahill. "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[URL]伯纳斯·李，T.，马辛特，L.，和M·麦卡希尔。“统一资源定位器（URL）”，RFC 17381994年12月。
[VSE] A. Haake, D. Hicks, "VerSE: Towards Hypertext Versioning Styles", Proc. Hypertext'96, The Seventh ACM Conference on Hypertext, 1996, pages 224-234.
[VSE]A.Haake，D.Hicks，“诗歌：走向超文本版本控制风格”，Proc。超文本'96，第七届ACM超文本会议，1996年，第224-234页。
Judith Slein Xerox Corporation 800 Phillips Road 128-29E Webster, NY 14580
朱迪思·斯莱恩施乐公司800菲利普斯路128-29E韦伯斯特，纽约州14580
EMail: slein@wrc.xerox.com
EMail: slein@wrc.xerox.com
Fabio Vitali Department of Computer Science University of Bologna ITALY
意大利波罗尼亚大学计算机科学系法比奥VITALI
EMail: fabio@cs.unibo.it
EMail: fabio@cs.unibo.it
E. James Whitehead, Jr. Department of Information and Computer Science University of California Irvine, CA 92697-3425
E. James Whitehead，小信息与计算机科学系，加利福尼亚大学，欧文，CA92697－325
Fax: 714-824-4056 EMail: ejw@ics.uci.edu
传真：714-824-4056电子邮件：ejw@ics.uci.edu
David G. Durand Department of Computer Science Boston University Boston, MA
David G.Durand麻省波士顿大学计算机科学系
EMail: dgd@cs.bu.edu
EMail: dgd@cs.bu.edu
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。