Network Working Group T. Hardie
Request for Comments: 2655 Equinix
Category: Experimental M. Bowman
Transarc
D. Hardy
Netscape
M. Schwartz
Affinia, Inc.
D. Wessels
NLANR
August 1999
Network Working Group T. Hardie
Request for Comments: 2655 Equinix
Category: Experimental M. Bowman
Transarc
D. Hardy
Netscape
M. Schwartz
Affinia, Inc.
D. Wessels
NLANR
August 1999
CIP Index Object Format for SOIF Objects
SOIF对象的CIP索引对象格式
Status of this Memo
本备忘录的状况
This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.
这份备忘录为互联网社区定义了一个实验性协议。它没有规定任何类型的互联网标准。要求进行讨论并提出改进建议。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
The Common Indexing Protocol (CIP) allows servers to form a referral mesh for query handling by defining a mechanism by which cooperating servers exchange hints about the searchable indices they maintain. The structure and transport of CIP are described in (Ref. 1), as are general rules for the definition of index object types. This document describes SOIF, the Summary Object Interchange Format, as an index object type in the context of the CIP framework. SOIF is a machine-readable syntax for transmitting structured summary objects, currently used primarily in the context of the World Wide Web.
公共索引协议（CIP）允许服务器通过定义一种机制来形成查询处理的引用网格，协作服务器通过该机制交换有关其维护的可搜索索引的提示。CIP的结构和传输如（参考文献1）所述，索引对象类型定义的一般规则也是如此。本文档将SOIF（摘要对象交换格式）描述为CIP框架上下文中的索引对象类型。SOIF是用于传输结构化摘要对象的机器可读语法，目前主要用于万维网环境。
Query referral has often been dismissed as an ineffective strategy for handling searches of Web resources, and Web resources certainly present challenges not present in structured directory services like Rwhois. In situations where a keyword-based free text search is desired, query referral is not likely to be effective because the query will probably be routed to every server participating in the referral mesh. Where a search can be limited by reference to a specific resource attribute, however, query referral is an effective tool. SOIF can be used to create such a known-attribute query mesh because it provides a method for associating attributes with net-addressable resources.
查询引用通常被认为是处理Web资源搜索的一种无效策略，而Web资源无疑带来了Rwhois等结构化目录服务所不具备的挑战。在需要基于关键字的自由文本搜索的情况下，查询引用不太可能有效，因为查询可能会路由到参与引用网格的每个服务器。但是，如果可以通过引用特定的资源属性来限制搜索，那么查询引用是一种有效的工具。SOIF可用于创建此类已知属性查询网格，因为它提供了一种将属性与网络可寻址资源关联的方法。
SOIF was first defined by the Harvest project [Ref 2.] in January 1994. SOIF was derived from a combination of the Internet Anonymous FTP Archives IETF Working Group (IAFA) templates [Ref 3.] and the BibTeX bibliography format [Ref 4.]. The combination was originally noted for its advantages of providing a convenient and intuitive way for delimiting objects within a stream, and setting apart the URL for easy object access or invocation, while still preserving compatibility with IAFA templates.
SOIF于1994年1月由Harvest项目[Ref 2]首次定义。SOIF源自互联网匿名FTP档案IETF工作组（IAFA）模板[Ref 3.]和BibTeX书目格式[Ref 4.]的组合。这种组合最初的优点是提供了一种方便直观的方式来划分流中的对象，并设置了URL以便于对象访问或调用，同时仍然保持了与IAFA模板的兼容性。
Mic Bowman, Darren Hardy, Mike Schwartz, and Duane Wessels each contributed to the creation of the SOIF format as part of the Harvest Project; later work took place as part of the FIND working group.
Mic Bowman、Darren Hardy、Mike Schwartz和Duane Wessels都参与了SOIF格式的创建，作为Harvest项目的一部分；后来的工作是作为FIND工作组的一部分进行的。
The index object described below will have the MIME type of application/index.obj.HARVEST-SOIF-1.
下面描述的索引对象的MIME类型为application/index.obj.HARVEST-SOIF-1。
Each summary object has 3 fundamental components: a template type, a URL, and zero or more ATTRIBUTE-VALUE pairs. Because the VALUEs in the ATTRIBUTE-VALUE pairs may contain arbitrary data (cf. Section 3.5), SOIF objects should be encoded in Base64 unless the template type unambiguously establishes that the VALUEs do not contain binary data.
每个摘要对象有3个基本组件：模板类型、URL和零个或多个属性值对。由于属性-值对中的值可能包含任意数据（参见第3.5节），因此SOIF对象应以Base64编码，除非模板类型明确确定值不包含二进制数据。
The Template type is used to identify the set of ATTRIBUTEs contained within a particular SOIF object. SOIF does not define the template types themselves; it only provides a way to associate the summary object with a predefined template type name. Template types may be registered or unregistered. Unregistered template types provide an indication of available ATTRIBUTE-VALUE pairs, but these may vary both according to the original resource and the method by which the summary object was generated. Registered template types must refer to a formally specified description of all mandatory and optional ATTRIBUTE-VALUE pairs available for that type. See [10] for a description of the process of registering template types with the IANA.
模板类型用于标识特定SOIF对象中包含的属性集。SOIF不定义模板类型本身；它仅提供将摘要对象与预定义模板类型名称关联的方法。模板类型可以是已注册的或未注册的。未注册的模板类型提供可用属性-值对的指示，但这些属性-值对可能根据原始资源和生成摘要对象的方法而有所不同。注册的模板类型必须引用该类型可用的所有强制和可选属性-值对的正式指定描述。有关向IANA注册模板类型的过程的描述，请参见[10]。
Historically, the template types used by SOIF were derived from IAFA template types (Ref. 3). SOIF objects generated by the Harvest system have a "FILE" template type; in current practice this is the most common template type. The "FILE" template type is a generic template
从历史上看，SOIF使用的模板类型源自IAFA模板类型（参考文献3）。收割系统生成的SOIF对象具有“文件”模板类型；在当前实践中，这是最常见的模板类型。“文件”模板类型是通用模板
type meant to handle a large variety of web-based resources. No formal specification of it is available, though a list of ATTRIBUTE-VALUE pairs common to the "FILE" template type is found in Appendix A. "DOCUMENT" and "OBJECT" are other generic template-types.
类型用于处理大量基于web的资源。虽然附录a中列出了“文件”模板类型共有的属性-值对列表，“文档”和“对象”是其他通用模板类型，但没有可用的正式规范。
The use of unregistered template types obviously presents some problems to the correct operation of query referral. Two efforts have been mounted to allow peer-to-peer agreement on the association of template types with specific attribute sets: Netscape's RDM (Ref. 6) and the STARTS project (Ref. 7). Initially, CIP meshes based on systems which use unregisterested template types may need to use these or similar methods to associate template types with specific attribute sets.
使用未注册的模板类型显然会给查询引用的正确操作带来一些问题。为了允许在模板类型与特定属性集的关联上达成对等协议，已经进行了两项工作：Netscape的RDM（参考文献6）和STARTS项目（参考文献7）。最初，基于使用未注册模板类型的系统的CIP网格可能需要使用这些或类似方法将模板类型与特定属性集关联。
Mesh operators are strongly encouraged, however, to migrate to registered template types as soon as is practical. Registered template types allow CIP meshes to derive the definitions of attributes, which enables multiple-language interfaces to the base attributes. In addition, registered template types allow CIP meshes and other users of SOIF to establish the permitted data types and encodings of the VALUEs associated with each ATTRIBUTE. This makes deriving the appropriate matching semantics for a particular VALUE much more straightforward and eliminates the limitations of the default octet-by-octet matching (cf. Section 4.).
但是，强烈建议网格操作符在可行的情况下尽快迁移到已注册的模板类型。注册的模板类型允许CIP网格派生属性的定义，从而支持基本属性的多语言接口。此外，注册的模板类型允许CIP Mesh和SOIF的其他用户建立与每个属性关联的值的允许数据类型和编码。这使得为特定值导出适当的匹配语义更加简单，并且消除了默认的八位字节逐八位字节匹配的限制（参见第4节）。
Uniform Resource Locators (URLs) (Ref 5.) are used by SOIF as object IDENTIFIERs. SOIF associates its summary objects with net-addressable resources by using the URL by which the resource was addressed as the initial field of the object body. See section 3.4 for the formal grammar associated with SOIF objects.
SOIF使用统一资源定位器（URL）（参考5.）作为对象标识符。SOIF将其摘要对象与净可寻址资源相关联，方法是使用URL作为对象体的初始字段来寻址资源。有关SOIF对象的形式语法，请参见第3.4节。
This association allows the same resource to have multiple summary objects, differentiated only by the URL by which the resource was accessed. This possibility does not, however, impact the usability of the URL as an object IDENTIFIER. Furthermore, since it can be argued that the net address is a salient part of the metadata, there may be compensating benefits to using the URL as an object IDENTIFIER.
此关联允许同一资源具有多个摘要对象，仅通过访问资源的URL进行区分。然而，这种可能性并不影响URL作为对象标识符的可用性。此外，由于可以认为网络地址是元数据的一个重要部分，因此使用URL作为对象标识符可能会带来一些好处。
As noted in Appendix A, the Harvest project used several additional identity attributes ("Gatherer-Name", "Gatherer-Host", "Gatherer-Port" and "Gatherer-Version") to further identify the provenance of a particular object. Within the context of CIP, it may be useful to identify the base sources of particular index objects; see Appendix B for one example of how a SOIF-based CIP hint could use the base source URL.
如附录A所述，Harvest项目使用了几个额外的身份属性（“Gatherer名称”、“Gatherer主机”、“Gatherer端口”和“Gatherer版本”），以进一步识别特定对象的来源。在CIP的上下文中，识别特定索引对象的基本源可能是有用的；有关基于SOIF的CIP提示如何使用基本源URL的示例，请参见附录B。
3.3 ATTRIBUTE-VALUE pairs.
3.3 属性值对。
Each summary object has zero or more ATTRIBUTE-VALUE pairs, which contain metadata about the net-addressable resource referenced by the URL. Pairs are composed of an ATTRIBUTE IDENTIFIER, the length of the VALUE, a delimeter, and the VALUE. It should be stressed that ATTRIBUTE VALUE pairs are not CR/LF terminated, but parsed according to grammar set out in section 3.4. In the examples in Section 3.6 and in many other representations of SOIF objects, ATTRIBUTE-VALUE pairs are represented on individual lines to enhance readability. VALUEs may contain CR/LF, however, and implementors must be careful to parse the full VALUE. Implementors of SOIF parsers MUST ignore <CR>,<LF>,<TAB>,<SPACE>, or other whitespace found between the VALUE of an ATTRIBUTE-VALUE pair and the ATTRIBUTE-IDENTIFIER of the subsequent pair.
每个摘要对象都有零个或多个属性值对，这些属性值对包含URL引用的可寻址资源的元数据。对由属性标识符、值的长度、delimeter和值组成。应该强调的是，属性值对不是以CR/LF结尾的，而是根据第3.4节规定的语法进行解析。在第3.6节的示例和SOIF对象的许多其他表示中，属性值对表示在单独的行上，以增强可读性。然而，值可能包含CR/LF，实现者必须小心地解析完整值。SOIF解析器的实现者必须忽略<CR>、<LF>、<TAB>、<SPACE>，或在属性值对的值和后续对的属性标识符之间找到的其他空白。
The SOIF syntax does not explicitly allow for a single ATTRIBUTE to have multiple VALUEs. To handle multiple VALUEs for the same ATTRIBUTE, SOIF uses an ATTRIBUTE naming convention; a hyphen and positive integer are appended to the ATTRIBUTE name to create an ATTRIBUTE IDENTIFIER VALUE associated with a specific ATTRIBUTE. For example, the ATTRIBUTE IDENTIFIERs "Author-1", "Author-2", and "Author-3" can be used to represent three VALUEs associated with the ATTRIBUTE "Author" where a specific resource has three authors. See section 4 for the implications of this strategy on matching semantics.
SOIF语法不明确允许单个属性具有多个值。为了处理同一属性的多个值，SOIF使用属性命名约定；将连字符和正整数附加到属性名称，以创建与特定属性关联的属性标识符值。例如，属性标识符“Author-1”、“Author-2”和“Author-3”可用于表示与属性“Author”关联的三个值，其中特定资源有三个作者。有关此策略对匹配语义的影响，请参见第4节。
The SOIF syntax is defined by the following grammar:
SOIF语法由以下语法定义：
SOIF ::= OBJECT SOIF |
OBJECT
OBJECT ::= @ TEMPLATE-TYPE { URL ATTRIBUTE-LIST }
TEMPLATE-TYPE ::= IDENTIFIER
ATTRIBUTE-LIST ::= ATTRIBUTE ATTRIBUTE-LIST |
ATTRIBUTE |
NULL
ATTRIBUTE ::= IDENTIFIER {VALUE-SIZE} DELIMITER VALUE
URL ::= RFC1738-URL-Syntax | "-"
IDENTIFIER ::= ALPHA-NUMERIC-STRING
VALUE ::= ARBITRARY-DATA
VALUE-SIZE ::= NUMERIC-STRING
DELIMITER ::= ":<TAB>"
SOIF ::= OBJECT SOIF |
OBJECT
OBJECT ::= @ TEMPLATE-TYPE { URL ATTRIBUTE-LIST }
TEMPLATE-TYPE ::= IDENTIFIER
ATTRIBUTE-LIST ::= ATTRIBUTE ATTRIBUTE-LIST |
ATTRIBUTE |
NULL
ATTRIBUTE ::= IDENTIFIER {VALUE-SIZE} DELIMITER VALUE
URL ::= RFC1738-URL-Syntax | "-"
IDENTIFIER ::= ALPHA-NUMERIC-STRING
VALUE ::= ARBITRARY-DATA
VALUE-SIZE ::= NUMERIC-STRING
DELIMITER ::= ":<TAB>"
URL a Uniform Resource Locator encoded in the syntax defined by RFC 1738 [3]. If the summary object has no URL associated with it, then a Latin-1 hyphen (octal \055) is used instead.
URL以RFC 1738[3]定义的语法编码的统一资源定位器。如果摘要对象没有与之关联的URL，则使用拉丁字母-1连字符（octal\055）。
IDENTIFIER an ASCII character string that only contains alphanumeric characters and hyphens or underscores. IDENTIFIERs should avoid including hyphens followed by positive integers except when constructing multiple-VALUE ATTRIBUTE IDENTIFIERs.
标识符仅包含字母数字字符和连字符或下划线的ASCII字符串。标识符应避免包含后跟正整数的连字符，除非在构造多值属性标识符时。
VALUE a buffer of VALUE-SIZE octets containing the VALUE. The VALUE may contain data in arbitrary formats or encodings, which recipients recognize based on Template-Type.
值包含该值的值大小八位字节的缓冲区。该值可以包含任意格式或编码的数据，收件人可以根据模板类型识别这些格式或编码。
VALUE-SIZE a non-negative integer encoded as an ASCII character string. The integer indicates how many octets the VALUE occupies after the DELIMITER.
VALUE-SIZE编码为ASCII字符串的非负整数。整数表示该值在分隔符后占用的八位字节数。
DELIMITER a two octet delimiter which is a Latin-1 colon (:) and a tab (\t), (octal \072\011).
分隔符两个八位组的分隔符，它是一个拉丁文1冒号（：）和一个制表符（\t），（八进制\072\011）。
{ } the Latin-1 curly braces (octal \173 and \175) are used to wrap the VALUE-SIZE (no spaces) as well as the URL and ATTRIBUTE-LIST combination.
{}拉丁-1大括号（八进制\173和\175）用于包装值大小（无空格）以及URL和属性列表组合。
@TEMPLATE-TYPE the Latin-1 @ (octal \100) and TEMPLATE-TYPE (no space between them) is used to mark the beginning of the SOIF object.
@TEMPLATE-TYPE拉丁语-1@（八进制\100）和TEMPLATE-TYPE（它们之间没有空格）用于标记SOIF对象的开头。
NUMERIC-STRING Zero or more ASCII numerals.
数字字符串零个或多个ASCII数字。
ALPHA-NUMERIC-STRING Zero or more ASCII letters or numerals, plus hyphens or underscore. [a-z,A-Z,0-9,- and _].
字母数字字符串零个或多个ASCII字母或数字，加连字符或下划线。[a-z，a-z，0-9，-和u]。
ARBITRARY-DATA Octets of data in arbitrary formats or encodings.
任意格式或编码的数据的任意八位字节。
As was discussed in Section 1, query referral of SOIF objects will be most effective when a query identifies a particular ATTRIBUTE or set of ATTRIBUTEs as the target of the query match. A query-identified ATTRIBUTE should be considered to match a SOIF ATTRIBUTE when a case-insentive character-by-character comparison matches that portion of the ATTRIBUTE IDENTIFIER prior to any hyphen-integer suffix. For example, a query which asks for a match on the ATTRIBUTE "author" should match the IDENTIFIERs "author", "Author", "AUTHOR", and "Author-1". [10] discourages the registration of template types containing ATTRIBUTEs which have previously been registered with substantially different definitions. This will help eliminate mis-referral, but a CIP mesh may nonetheless need to maintain a thesaurus matching ATTRIBUTEs from particular template-types to those of other, especially unregistered, template-types.
如第1节所述，当查询将特定属性或属性集识别为查询匹配的目标时，SOIF对象的查询引用将最有效。当不区分大小写的逐字符比较匹配任何连字符整数后缀之前的属性标识符部分时，应将查询标识的属性视为匹配SOIF属性。例如，要求匹配属性“author”的查询应匹配标识符“author”、“author”、“author”和“author-1”。[10] 不鼓励注册包含属性的模板类型，这些属性以前已使用完全不同的定义注册。这将有助于消除错误引用，但CIP网格可能仍然需要维护一个同义词库，将特定模板类型的属性与其他（尤其是未注册的）模板类型的属性进行匹配。
The matching semantics appropriate for a particular VALUE are derived from its data type and encoding. For VALUEs associated with ATTRIBUTEs which are part of a registered template type, the data type and encoding are readily available. For VALUEs associated with ATTRIBUTES associated with unregistered template-types, an octet-by-octet comparison is the default. In cases where previous experience has demonstrated that a particular ATTRIBUTE contains string data, a case-insensitive substring match may be used. For example, in a query against the "AUTHOR" ATTRIBUTE of the generic "DOCUMENT" template type, the query VALUE "Garcia" should match the SOIF VALUEs "Garcia", "GARCIA", and "Jose Garcia y Montes".
适合于特定值的匹配语义是从其数据类型和编码派生的。对于与作为注册模板类型一部分的属性相关联的值，数据类型和编码很容易获得。对于与未注册模板类型关联的属性关联的值，默认情况下会进行八位字节对八位字节的比较。在以前的经验表明特定属性包含字符串数据的情况下，可以使用不区分大小写的子字符串匹配。例如，在针对通用“文档”模板类型的“作者”属性的查询中，查询值“Garcia”应与SOIF值“Garcia”、“Garcia”和“Jose Garcia y Montes”匹配。
Over time, there may well emerge an understanding of which attributes tend to produce correct query referrals within a mesh. As such understandings emerge, mesh maintainers may wish to define a particular SOIF TEMPLATE-TYPE which restricts included ATTRIBUTES to those likely to foster correct referrals.
随着时间的推移，人们很可能会理解哪些属性倾向于在网格中生成正确的查询引用。随着这些理解的出现，网格维护人员可能希望定义一个特定的SOIF模板类型，该模板类型将包含的属性限制为那些可能促进正确引用的属性。
The internationalization of SOIF depends on the registration of template-types. Since TEMPLATE-TYPEs and ATTRIBUTE IDENTIFIERs must be in ASCII characters, only languages which use the ASCII character set are fully supported for unregistered TEMPLATE-TYPEs. For registered template types, in contrast, the specification of an ATTRIBUTE's definition will allow UI designers to present a native-language mapping of the ATTRIBUTE to the end user. Further, the inclusion of data type and encoding information in the description of VALUEs means that any language encoding or character set required by a particular application may be supported. For unregistered template types, the ability of peer servers to pass schema definitions may
SOIF的国际化取决于模板类型的注册。由于模板类型和属性标识符必须使用ASCII字符，因此只有使用ASCII字符集的语言才能完全支持未注册的模板类型。相反，对于已注册的模板类型，属性定义的规范将允许UI设计者向最终用户呈现属性的本机语言映射。此外，在值的描述中包括数据类型和编码信息意味着可以支持特定应用所需的任何语言编码或字符集。对于未注册的模板类型，对等服务器传递架构定义的能力可能会受到影响
provide a form of "private registration" which could provide some of the facilities for internationalization available to registered template types. (See above, section 3.1 and Refs. 6 and 7.)
提供一种“私人注册”形式，可以为注册的模板类型提供一些国际化工具。（见上文第3.1节和参考文献6和7。）
The appendices contain example summary objects encoded using specific template types. The following are some example summary objects using the generic "DOCUMENT" SOIF template-type:
附录包含使用特定模板类型编码的示例摘要对象。以下是一些使用通用“文档”SOIF模板类型的摘要对象示例：
@DOCUMENT { http://home.netscape.com:80/
Title{19}: Welcome to Netscape
Content-Type{9}: text/html
Content-Length{5}: 33262
}
@DOCUMENT { http://home.netscape.com:80/
Title{19}: Welcome to Netscape
Content-Type{9}: text/html
Content-Length{5}: 33262
}
@DOCUMENT { http://home.netscape.com/eng/ssl3/ssl-toc.html
Title{19}: SSL Protocol V. 3.0
Content-Type{9}: text/html
Content-Length{5}: 5870
Author-1{14}: Alan O. Freier
Author-2{14}: Philip Karlton
Author-3{14}: Paul C. Kocher
Abstract{318}: This document specifies Version 3.0 of the
<B>Secure Sockets Layer (SSL V3.0)</B> protocol, a security
protocol that provides communications privacy over the Internet.
The protocol allows client/server applications to communicate in
a way that is designed to prevent eavesdropping, tampering, or
message forgery.
}
@DOCUMENT { http://home.netscape.com/eng/ssl3/ssl-toc.html
Title{19}: SSL Protocol V. 3.0
Content-Type{9}: text/html
Content-Length{5}: 5870
Author-1{14}: Alan O. Freier
Author-2{14}: Philip Karlton
Author-3{14}: Paul C. Kocher
Abstract{318}: This document specifies Version 3.0 of the
<B>Secure Sockets Layer (SSL V3.0)</B> protocol, a security
protocol that provides communications privacy over the Internet.
The protocol allows client/server applications to communicate in
a way that is designed to prevent eavesdropping, tampering, or
message forgery.
}
@DOCUMENT { http://www.nissanmotors.com/1996/300ZX/pictures/300zx.jpg
Content-Type{10}: image/jpeg
Content-Length{5}: 25940
Last-Modified{31}: Tuesday, 11-Jun-96 19:18:44 GMT
Thumbnail{259}: ..................
}
@DOCUMENT { http://www.nissanmotors.com/1996/300ZX/pictures/300zx.jpg
Content-Type{10}: image/jpeg
Content-Length{5}: 25940
Last-Modified{31}: Tuesday, 11-Jun-96 19:18:44 GMT
Thumbnail{259}: ..................
}
Please see (Ref. 1) for a general discussion of Security concerns for the CIP framework.
关于CIP框架安全问题的一般性讨论，请参见（参考文献1）。
SOIF currently contains no requirement that any template type contain an authentication ATTRIBUTE. SOIF summary objects lacking authentication ATTRIBUTEs must, therefore, be treated as unreliable indicators of the referenced resource's content. A hostile party could create a summary object which significantly misrepresented a
SOIF目前不要求任何模板类型包含身份验证属性。因此，缺少身份验证属性的SOIF摘要对象必须被视为引用资源内容的不可靠指标。敌对方可以创建一个摘要对象，该对象严重歪曲了
resource's content. As part of a CIP mesh, this data could either channel a large number of requestors to a resource (possibly resulting in a denial of service) or away from a resource (possibly resulting in a loss of appropriate visibility).
资源的内容。作为CIP网格的一部分，该数据可以将大量请求者引导到资源（可能导致拒绝服务）或远离资源（可能导致适当可见性的丧失）。
[1] Allen, J. and M. Mealling, "The Architecture of the Common Indexing Protocol (CIP)", RFC 2651, August 1999.
[1] Allen，J.和M.Melling，“公共索引协议（CIP）的体系结构”，RFC 26511999年8月。
[2] The Harvest Information Discovery and Access System: <URL:http://harvest.transarc.com/>.
[2] 收获信息发现和访问系统：<URL:http://harvest.transarc.com/>.
[3] D. Beckett, IAFA Templates in Use as Internet Metadata, 4th
Int'l WWW Conference, December 1995,
<URL:http://www.hensa.ac.uk/tools/www/iafatools/>
[3] D. Beckett, IAFA Templates in Use as Internet Metadata, 4th
Int'l WWW Conference, December 1995,
<URL:http://www.hensa.ac.uk/tools/www/iafatools/>
[4] L. Lamport, LaTeX: A Document Preparation System, Addison-Wesley, Reading, Mass., 1986.
[4] 兰波特，《乳胶：文件准备系统》，艾迪生·韦斯利，马萨诸塞州雷丁，1986年。
[5] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[5] Berners Lee，T.，Masinter，L.和M.McCahill，“统一资源定位器（URL）”，RFC 17381994年12月。
[6] D. Hardey, Resource Description Messages (RDM), W3C Note-rdm-
960724, July 24, 1996, <URL:http://www.w3.org/pub/WWW/TR/NOTE-
rdm.html>
[6] D. Hardey, Resource Description Messages (RDM), W3C Note-rdm-
960724, July 24, 1996, <URL:http://www.w3.org/pub/WWW/TR/NOTE-
rdm.html>
[7] L. Gravano, K. Chang, H. Garcia-Molina, C. Lagoze, A. Paepcke,
STARTS: Stanford Protocol Proposal for Internet Retrieval and
Search, January 1997, <URL:http://www-
db.stanford.edu/~gravano/starts.html>
[7] L. Gravano, K. Chang, H. Garcia-Molina, C. Lagoze, A. Paepcke,
STARTS: Stanford Protocol Proposal for Internet Retrieval and
Search, January 1997, <URL:http://www-
db.stanford.edu/~gravano/starts.html>
[8] S. Weibel, J. Kunze, C. Lagoze, Dublin Core Metadata for Simple Resource Description, Work in Progress.
[8] S.Weibel，J.Kunze，C.Lagoze，都柏林核心元数据，用于简单资源描述，正在进行的工作。
[9] E. Miller, Dublin Core Element Set Crosswalk, January 1997,
<URL:http://www.oclc.org:5046/~emiller/DC/crosswalk.html>
[9] E. Miller, Dublin Core Element Set Crosswalk, January 1997,
<URL:http://www.oclc.org:5046/~emiller/DC/crosswalk.html>
[10] Hardie, T., "Registration Procedures for SOIF Template Types", RFC 2656, August 1999.
[10] Hardie，T.，“SOIF模板类型的注册程序”，RFC 2656，1999年8月。
Ted Hardie Equinix 901 Marshall Street Redwood City, CA 94063 USA
美国加利福尼亚州红木市马歇尔街901号Ted Hardie Equinix 94063
EMail: hardie@equinix.com
EMail: hardie@equinix.com
Mic Bowman Transarc Corporation The Gulf Tower 707 Grant Street Pittsburgh, PA 15219 USA
美国宾夕法尼亚州匹兹堡格兰特街707号海湾大厦Mic Bowman Transarc Corporation，邮编15219
Phone: +1 412 338 4400
EMail: mic@transarc.com
Phone: +1 412 338 4400
EMail: mic@transarc.com
Darren Hardy Netscape Communications Corp. 685 E. Middlefield Road Mountain View, CA 94043 USA
达伦哈代网景通信公司，美国加利福尼亚州米德尔菲尔德路东685号山景城，邮编94043
Phone: +1 415 937 2555
EMail: dhardy@netscape.com
Phone: +1 415 937 2555
EMail: dhardy@netscape.com
Mike Schwartz Affinia, Inc. 621 17th Street, Suite 1700 Denver, CO 80293
迈克·施瓦茨·阿菲尼亚公司，美国科罗拉多州丹佛市第17街621号1700室，邮编80293
Phone: +1 (303) 292-4818
E-mail: mfs@affinia.net
Phone: +1 (303) 292-4818
E-mail: mfs@affinia.net
Duane Wessels National Laboratory for Applied Network Research
Duane Wessels国家应用网络研究实验室
Phone: +1 303 497 1822
EMail: wessels@nlanr.net
Phone: +1 303 497 1822
EMail: wessels@nlanr.net
Appendix A.
附录A。
Common Attributes for "FILE" Template-type Summary Objects created by Harvest:
Harvest创建的“文件”模板类型摘要对象的通用属性：
Abstract Brief abstract about the object.
关于对象的简短摘要。
Author Author(s) of the object.
对象的作者。
Description Brief description about the object.
描述关于对象的简要描述。
File-Size Number of bytes in the object.
文件大小对象中的字节数。
Full-Text Entire contents of the object.
全文对象的全部内容。
Gatherer-Host Host on which the Gatherer ran to extract information from the object.
Gatherer运行Gatherer以从对象提取信息的主机。
Gatherer-Name Name of the Gatherer that extracted information from the object. (eg. Full-Text, Selected-Text, or Terse).
Gatherer名称从对象提取信息的Gatherer的名称。（如全文、精选文本或简明扼要）。
Gatherer-Port Port number on the Gatherer-Host that serves the Gatherer's information.
Gatherer主机上提供Gatherer信息的Gatherer端口号。
Gatherer-Version Version number of the Gatherer.
Gatherer的Gatherer版本号。
Update-Time The time that Gatherer updated the content summary for the object.
Update Time Gatherer更新对象内容摘要的时间。
Keywords Searchable keywords extracted from the object.
关键字从对象中提取的可搜索关键字。
Last-Modification-Time The time that the object was last modified.
上次修改时间上次修改对象的时间。
MD5 MD5 16-byte checksum of the object.
MD5 MD5对象的16字节校验和。
Refresh-Rate The number of seconds after Update-Time when the summary object is to be re-generated. Defaults to 1 month.
Refresh Rate更新时间后重新生成摘要对象的秒数。默认为1个月。
Time-to-Live The number of seconds after Update-Time when the summary object is no longer valid. Defaults to 6 months.
生存时间当摘要对象不再有效时，更新时间后的秒数。默认为6个月。
Title Title of the object.
对象的标题。
Type The object's type. Some example types are:
键入对象的类型。一些示例类型包括：
Archive Audio Awk Backup Binary C CHeader Command Compressed CompressedTar Configuration Data Directory DotFile Dvi FAQ FYI Font FormattedText GDBM GNUCompressed GNUCompressedTar HTML Image Internet-Draft MacCompressed Mail Makefile ManPage Object OtherCode PCCompressed Patch Perl PostScript
归档音频Awk备份二进制C CHeader命令压缩压缩的压缩tar配置数据目录点文件Dvi FAQ FYI字体格式文本GDBM GNUCompressed GNUCompressed GNUCompressedTar HTML图像Internet草稿MacCompressed Mail Makefile ManPage对象其他代码PCCompressed Patch Perl PostScript
RCS README RFC SCCS ShellArchive Tar Tcl Tex Text Troff Uuencoded WaisSource
RCS自述RFC SCCS ShellArchive Tar Tcl Tex文本Troff Uuencoded WaisSource
Update-Time The time that the summary object was last updated. REQUIRED field, no default.
更新时间上次更新摘要对象的时间。必填字段，无默认值。
URL-References Any URL references present within HTML objects.
URL引用HTML对象中存在的任何URL引用。
Appendix B.
附录B。
Proposed Attributes for a "CIP-HINT" Template Type
“CIP-HINT”模板类型的建议属性
Attribute-Identifier-List A comma-delimited list whose entries take the form Template-Type:Attribute . This list identifies the attributes against which queries are supported. Because of the current limitation on Identifiers, this list must be in ASCII.
属性标识符列表以逗号分隔的列表，其条目的格式为模板类型：Attribute。此列表标识支持查询的属性。由于当前对标识符的限制，此列表必须采用ASCII格式。
Source The URI of the service which created some or all of the index objects to which this hint applies. Note that this service may be and often is distinct from the server which provides query access to those objects.
Source创建此提示适用的部分或全部索引对象的服务的URI。请注意，此服务可能并且通常不同于提供对这些对象的查询访问的服务器。
Total-Object-Count The total number of index objects in the collection for which the Hint applies. This should be a positive integer.
Total Object Count应用提示的集合中索引对象的总数。这应该是一个正整数。
Weightlist-[Attribute-Identifier] This construction allows the HINT to contain a weighted list of values for a specific Attribute-Identifier. There may be as many Weightlist entries as there Attribute-Identifiers in the Attribute-Identifier-List. Each Weightlist entry takes the form of Value;Object-Count, where the object count is a positive integer representing the number of objects within the collection which contain that value. Weightlists are comma- delimited.
Weightlist-[Attribute Identifier]此结构允许提示包含特定属性标识符的加权值列表。权重列表项的数量可能与属性标识符列表中的属性标识符的数量相同。每个权重列表条目采用值的形式；对象计数，其中对象计数是一个正整数，表示集合中包含该值的对象数。权重列表以逗号分隔。
Should a Value contain a comma, it should be escaped when incorporated into the weightlist.
如果某个值包含逗号，则在将其合并到权重列表中时应将其转义。
Threshold-[Attribute-Identifier] If a server wishes not to report infrequently occurring Values in a specific Weightlist, it may declare a threshold under which it will not report Values.
阈值-[Attribute Identifier]如果服务器不希望报告特定权重列表中不经常出现的值，它可以声明一个阈值，在该阈值下它不会报告值。
Certification-Type The type of Certification used for this object
证书类型用于此对象的证书类型
Certification The Value of the Certification.
认证——认证的价值。
Date The Date at which the hint was generated
日期生成提示的日期
Example:
例子：
@CIP-HINT{ http://nic.nasa.gov:80/Harvest/brokers/NASA/
Attribute-Identifier-list{49}:
DOCUMENT:Author, DOCUMENT:Keywords, IMAGE:Subject
Source-1{45}: http://nic.nasa.gov/Harvest/gatherers/Eureka/
Source-2{46}: http://techreports.larc.nasa.gov/cgi-bin/NTRS/
Total-Object-Count{5}: 10000
Weightlist-[IMAGE:Subject]{40}:
Shuttle;100, Planet;227, Moon;15, Sun;33
Threshold-[IMAGE:Subject]{2}: 10
Weightlist-[DOCUMENT:Author]{49}:
Grizzard;12, Aldrin\, Buzz;15, Aldrin\, James;45,
Threshold-[DOCMENT:Author]{1}: 5
Certification-Type{13}: PGP-Signature
Certification{51}: mQCNAzFNm5QAAEEALUBOolOWKpby+=YtmtBxUZWQgSGFyZGllID
Date{29}: Sun, 05 Jan 1997 08:33:33 GMT
}
@CIP-HINT{ http://nic.nasa.gov:80/Harvest/brokers/NASA/
Attribute-Identifier-list{49}:
DOCUMENT:Author, DOCUMENT:Keywords, IMAGE:Subject
Source-1{45}: http://nic.nasa.gov/Harvest/gatherers/Eureka/
Source-2{46}: http://techreports.larc.nasa.gov/cgi-bin/NTRS/
Total-Object-Count{5}: 10000
Weightlist-[IMAGE:Subject]{40}:
Shuttle;100, Planet;227, Moon;15, Sun;33
Threshold-[IMAGE:Subject]{2}: 10
Weightlist-[DOCUMENT:Author]{49}:
Grizzard;12, Aldrin\, Buzz;15, Aldrin\, James;45,
Threshold-[DOCMENT:Author]{1}: 5
Certification-Type{13}: PGP-Signature
Certification{51}: mQCNAzFNm5QAAEEALUBOolOWKpby+=YtmtBxUZWQgSGFyZGllID
Date{29}: Sun, 05 Jan 1997 08:33:33 GMT
}
Appendix C.
附录C。
A "Dublin-Core" Template Type [Ref. 8,9]
“都柏林核心”模板类型[参考文献8,9]
TITLE The name given to the resource by the CREATOR or PUBLISHER.
TITLE创建者或发布者为资源指定的名称。
CREATOR The person(s) or organization(s) primarily responsible for the intellectual content of the resource. For example, authors in the case of written documents, artists, photographers, or illustrators in the case of visual resources.
创建者主要负责资源知识内容的人员或组织。例如，书面文档中的作者、视觉资源中的艺术家、摄影师或插图画家。
SUBJECT The topic of the resource, or keywords or phrases that describe the subject or content of the resource. The intent of the specification of this element is to promote the use of controlled vocabularies and keywords. This element might well include scheme-qualified classification data (for example, Library of Congress Classification Numbers or Dewey Decimal numbers) or scheme-qualified controlled vocabularies (such as Medical Subject Headings or Art and Architecture Thesaurus descriptors) as well.
主题资源的主题，或描述资源主题或内容的关键字或短语。该元素规范的目的是促进受控词汇和关键字的使用。该元素可能还包括符合方案的分类数据（例如，国会图书馆分类号或杜威十进制数）或符合方案的受控词汇表（例如，医学主题标题或艺术和建筑叙词表描述符）。
DESCRIPTION A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources. Future metadata collections might well include computational content description (spectral analysis of a visual resource, for example) that may not be embeddable in current network systems. In such a case this field might contain a link to such a description rather than the description itself.
描述资源内容的文本描述，包括文档类对象的摘要或视觉资源的内容描述。未来的元数据集合很可能包括计算内容描述（例如，视觉资源的光谱分析），这些内容可能无法嵌入当前的网络系统中。在这种情况下，此字段可能包含指向此类描述的链接，而不是描述本身。
PUBLISHER The entity responsible for making the resource available in its present form, such as a publisher, a university department, or a corporate entity. The intent of specifying this field is to identify the entity that provides access to the resource.
出版商：负责以当前形式提供资源的实体，如出版商、大学系或公司实体。指定此字段的目的是标识提供资源访问权限的实体。
CONTRIBUTOR Person(s) or organization(s) in addition to those specified in the CREATOR element who have made significant intellectual contributions to the resource but whose contribution is secondary to the individuals or entities specifed in the CREATOR element (for example, editors, transcribers, illustrators, and convenors).
除创建者元素中指定的人员外，对资源做出重大智力贡献但贡献仅次于创建者元素中指定的个人或实体（例如，编辑、转录员、插图画家和召集人）的贡献者人员或组织。
DATE The date the resource was made available in its present form. The recommended best practice is an 8 digit number in the form YYYYMMDD as defined by ANSI X3.30-1985. In this scheme, the date element for the day this is written would be 19961203, or December 3, 1996. Many other schema are possible, but if used, they should be identified in an unambiguous manner.
日期资源以当前形式提供的日期。建议的最佳做法是采用ANSI X3.30-1985定义的YYYYMMDD格式的8位数字。在该方案中，写入日期的日期元素为19961203或1996年12月3日。许多其他模式是可能的，但如果使用，则应以明确的方式标识它们。
TYPE The category of the resource, such as home page, novel, poem, working paper, technical report, essay, dictionary. It is expected that RESOURCE TYPE will be chosen from an enumerated list of types.
键入资源的类别，如主页、小说、诗歌、工作论文、技术报告、文章、词典。预计将从枚举的类型列表中选择资源类型。
FORMAT The data representation of the resource, such as text/html, ASCII, Postscript file, executable application, or JPEG image. The intent of specifying this element is to provide information necessary to allow people or machines to make decisions about the usability of the encoded data (what hardware and software might be required to display or execute it, for example). As with RESOURCE TYPE, FORMAT will be assigned from enumerated lists such as registered Internet Media Types (MIME types). In principal, formats can include physical media such as books, serials, or other non-electronic media.
格式化资源的数据表示形式，例如文本/html、ASCII、Postscript文件、可执行应用程序或JPEG图像。指定此元素的目的是提供必要的信息，以允许人员或机器决定编码数据的可用性（例如，显示或执行数据可能需要哪些硬件和软件）。与资源类型一样，格式将从枚举列表中分配，例如注册的Internet媒体类型（MIME类型）。原则上，格式可以包括物理媒体，如书籍、连载或其他非电子媒体。
IDENTIFIER String or number used to uniquely identify the resource. Examples for networked resources include URLs and URNs (when implemented). Other globally-unique identifiers,such as International Standard Book Numbers (ISBN) or other formal names would also be candidates for this element.
用于唯一标识资源的标识符字符串或数字。网络资源的示例包括URL和URN（实施时）。其他全球唯一标识符，如国际标准书号（ISBN）或其他正式名称也将是该元素的候选项。
SOURCE The work, either print or electronic, from which this resource is derived, if applicable. For example, an html encoding of a Shakespearean sonnet might identify the paper version of the sonnet from which the electronic version was transcribed.
如果适用，从中获取此资源的工作来源，无论是打印的还是电子的。例如，一首莎士比亚十四行诗的html编码可能会识别该十四行诗的纸质版本，而电子版本是从该版本转录而来的。
LANGUAGE Language(s) of the intellectual content of the resource. Where practical, the content of this field should coincide with the NISO Z39.53 three character codes for written languages.
资源智力内容的语言。如果可行，该字段的内容应与书面语言的NISO Z39.53三字符代码一致。
RELATION Relationship to other resources. The intent of specifying this element is to provide a means to express relationships among resources that have formal relationships to others, but exist as discrete resources themselves. For example, images in a document, chapters in a book, or items in a collection. A formal specification of RELATION is currently under development. Users and developers should understand that use of this element should be currently considered experimental.
与其他资源的关系。指定此元素的目的是提供一种表示资源之间关系的方法，这些资源与其他资源具有正式关系，但它们本身作为离散资源存在。例如，文档中的图像、书籍中的章节或集合中的项目。目前正在制定正式的关系规范。用户和开发人员应该理解，当前应该将此元素的使用视为实验性的。
COVERAGE The spatial locations and temporal durations characteristic of the resource. Formal specification of COVERAGE is currently under development. Users and developers should understand that use of this element should be currently considered experimental.
覆盖率资源的空间位置和时间持续时间特征。目前正在制定覆盖范围的正式规范。用户和开发人员应该理解，当前应该将此元素的使用视为实验性的。
RIGHTS The content of this element is intended to be a link (a URL or other suitable URI as appropriate) to a copyright notice, a rights-management statement, or perhaps a server that would provide such information in a dynamic way. The intent of specifying this field is to allow providers a means to associate terms and conditions or copyright statements with a resource or collection of resources. No assumptions should be made by users if such a field is empty or not present.
权限此元素的内容旨在成为指向版权声明、权限管理声明的链接（URL或其他合适的URI，视情况而定），或者可能是以动态方式提供此类信息的服务器。指定此字段的目的是允许提供商将条款和条件或版权声明与资源或资源集合相关联。如果此类字段为空或不存在，则用户不应做出任何假设。
Example:
例子：
@Dublin-Core-1 { ftp://ds.internic.net/internet-drafts/
draft-kunze-dc-00.txt
TITLE{52}: Dublin Core Metadata for Simple Resource Description
CREATOR-1{9}: S. Weibel
CREATOR-2{8}: J. Kunze
CREATOR-3{9}: C. Lagoze
SUBJECT{44}: The Dublin Core Set of Elements for Metadata
DESCRIPTION{46}: Reference description of Dublin Core elements.
PUBLISHER{31}: Internet Engineering Task Force
CONTRIBUTOR-1{11}: Nick Arnett
CONTRIBUTOR-2{15}: Eliot Christian
CONTRIBUTOR-3{14}: Martijn Koster
CONTRIBUTOR-4{18}: Christian Mogensen
CONTRIBUTOR-5{14}: Timothy Niesen
CONTRIBUTOR-6{11}: Andrew Wood
CONTRIBUTOR-7{10}: Mic Bowman
CONTRIBUTOR-8{11}: Dan Connoly
CONTRIBUTOR-9{15}: Michael Mauldin
CONTRIBUTOR-10{12}: Wick Nichols
DATE{16}: February 9, 1997
TYPE{14}: Internet draft
FORMAT{4}: Text
IDENTIFIER:{21} draft-kunze-dc-00.txt
SOURCE{41}: http://purl.oclc.org/metadata/dublin_core
LANGUAGE{3}: eng
RELATION{24}: Draft Reference Standard
COVERAGE{22}: Expires August 8, 1997
RIGHTS{58}: Unlimited Distribution;
readers must not cite as standard.
}
@Dublin-Core-1 { ftp://ds.internic.net/internet-drafts/
draft-kunze-dc-00.txt
TITLE{52}: Dublin Core Metadata for Simple Resource Description
CREATOR-1{9}: S. Weibel
CREATOR-2{8}: J. Kunze
CREATOR-3{9}: C. Lagoze
SUBJECT{44}: The Dublin Core Set of Elements for Metadata
DESCRIPTION{46}: Reference description of Dublin Core elements.
PUBLISHER{31}: Internet Engineering Task Force
CONTRIBUTOR-1{11}: Nick Arnett
CONTRIBUTOR-2{15}: Eliot Christian
CONTRIBUTOR-3{14}: Martijn Koster
CONTRIBUTOR-4{18}: Christian Mogensen
CONTRIBUTOR-5{14}: Timothy Niesen
CONTRIBUTOR-6{11}: Andrew Wood
CONTRIBUTOR-7{10}: Mic Bowman
CONTRIBUTOR-8{11}: Dan Connoly
CONTRIBUTOR-9{15}: Michael Mauldin
CONTRIBUTOR-10{12}: Wick Nichols
DATE{16}: February 9, 1997
TYPE{14}: Internet draft
FORMAT{4}: Text
IDENTIFIER:{21} draft-kunze-dc-00.txt
SOURCE{41}: http://purl.oclc.org/metadata/dublin_core
LANGUAGE{3}: eng
RELATION{24}: Draft Reference Standard
COVERAGE{22}: Expires August 8, 1997
RIGHTS{58}: Unlimited Distribution;
readers must not cite as standard.
}
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。