As per Relevance of the word resource, we have this rfc below:
Network Working Group T.
Request for Comments: 2655
Category: Experimental M.
D.
M.
Affinia, Inc
D.
August 1999
CIP Index Object Format for SOIF
Status of this
This memo defines an Experimental Protocol for the
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
Copyright (C) The Internet Society (1999). All Rights Reserved
1.
The Common Indexing Protocol (CIP) allows servers to form a
mesh for query handling by defining a mechanism by which
servers exchange hints about the searchable indices they maintain
The structure and transport of CIP are described in (Ref. 1), as
general rules for the definition of index object types.
document describes SOIF, the Summary Object Interchange Format, as
index object type in the context of the CIP framework. SOIF is
machine-readable syntax for transmitting structured summary objects
currently used primarily in the context of the World Wide Web
Query referral has often been dismissed as an ineffective
for handling searches of Web resources, and Web resources
present challenges not present in structured directory services
Rwhois. In situations where a keyword-based free text search
desired, query referral is not likely to be effective because
query will probably be routed to every server participating in
referral mesh. Where a search can be limited by reference to
specific resource attribute, however, query referral is an
tool. SOIF can be used to create such a known-attribute query
because it provides a method for associating attributes with net
addressable resources
Hardie, et al. Experimental [Page 1]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
1.1
SOIF was first defined by the Harvest project [Ref 2.] in
1994. SOIF was derived from a combination of the Internet
FTP Archives IETF Working Group (IAFA) templates [Ref 3.] and
BibTeX bibliography format [Ref 4.]. The combination was
noted for its advantages of providing a convenient and intuitive
for delimiting objects within a stream, and setting apart the URL
easy object access or invocation, while still
compatibility with IAFA templates
Mic Bowman, Darren Hardy, Mike Schwartz, and Duane Wessels
contributed to the creation of the SOIF format as part of the
Project; later work took place as part of the FIND working group
2.
The index object described below will have the MIME type
application/index.obj.HARVEST-SOIF-1.
3. Payload
Each summary object has 3 fundamental components: a template type,
URL, and zero or more ATTRIBUTE-VALUE pairs. Because the VALUEs
the ATTRIBUTE-VALUE pairs may contain arbitrary data (cf.
3.5), SOIF objects should be encoded in Base64 unless the
type unambiguously establishes that the VALUEs do not contain
data
3.1 Template
The Template type is used to identify the set of ATTRIBUTEs
within a particular SOIF object. SOIF does not define the
types themselves; it only provides a way to associate the
object with a predefined template type name. Template types may
registered or unregistered. Unregistered template types provide
indication of available ATTRIBUTE-VALUE pairs, but these may
both according to the original resource and the method by which
summary object was generated. Registered template types must
to a formally specified description of all mandatory and
ATTRIBUTE-VALUE pairs available for that type. See [10] for
description of the process of registering template types with
IANA
Historically, the template types used by SOIF were derived from
template types (Ref. 3). SOIF objects generated by the Harvest
have a "FILE" template type; in current practice this is the
common template type. The "FILE" template type is a generic
Hardie, et al. Experimental [Page 2]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
type meant to handle a large variety of web-based resources.
formal specification of it is available, though a list of ATTRIBUTE
VALUE pairs common to the "FILE" template type is found in
A. "DOCUMENT" and "OBJECT" are other generic template-types
The use of unregistered template types obviously presents
problems to the correct operation of query referral. Two
have been mounted to allow peer-to-peer agreement on the
of template types with specific attribute sets: Netscape's RDM (Ref
6) and the STARTS project (Ref. 7). Initially, CIP meshes based
systems which use unregisterested template types may need to
these or similar methods to associate template types with
attribute sets
Mesh operators are strongly encouraged, however, to migrate
registered template types as soon as is practical.
template types allow CIP meshes to derive the definitions
attributes, which enables multiple-language interfaces to the
attributes. In addition, registered template types allow CIP
and other users of SOIF to establish the permitted data types
encodings of the VALUEs associated with each ATTRIBUTE. This
deriving the appropriate matching semantics for a particular
much more straightforward and eliminates the limitations of
default octet-by-octet matching (cf. Section 4.).
3.2
Uniform Resource Locators (URLs) (Ref 5.) are used by SOIF as
IDENTIFIERs. SOIF associates its summary objects with net
addressable resources by using the URL by which the resource
addressed as the initial field of the object body. See section 3.4
for the formal grammar associated with SOIF objects
This association allows the same resource to have multiple
objects, differentiated only by the URL by which the resource
accessed. This possibility does not, however, impact the
of the URL as an object IDENTIFIER. Furthermore, since it can
argued that the net address is a salient part of the metadata,
may be compensating benefits to using the URL as an
IDENTIFIER
As noted in Appendix A, the Harvest project used several
identity attributes ("Gatherer-Name", "Gatherer-Host", "Gatherer
Port" and "Gatherer-Version") to further identify the provenance of
particular object. Within the context of CIP, it may be useful
identify the base sources of particular index objects; see Appendix
for one example of how a SOIF-based CIP hint could use the
source URL
Hardie, et al. Experimental [Page 3]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
3.3 ATTRIBUTE-VALUE pairs
Each summary object has zero or more ATTRIBUTE-VALUE pairs,
contain metadata about the net-addressable resource referenced by
URL. Pairs are composed of an ATTRIBUTE IDENTIFIER, the length
the VALUE, a delimeter, and the VALUE. It should be stressed
ATTRIBUTE VALUE pairs are not CR/LF terminated, but parsed
to grammar set out in section 3.4. In the examples in Section 3.6
and in many other representations of SOIF objects, ATTRIBUTE-
pairs are represented on individual lines to enhance readability
VALUEs may contain CR/LF, however, and implementors must be
to parse the full VALUE. Implementors of SOIF parsers MUST
,,,, or other whitespace found between the
of an ATTRIBUTE-VALUE pair and the ATTRIBUTE-IDENTIFIER of
subsequent pair
The SOIF syntax does not explicitly allow for a single ATTRIBUTE
have multiple VALUEs. To handle multiple VALUEs for the
ATTRIBUTE, SOIF uses an ATTRIBUTE naming convention; a hyphen
positive integer are appended to the ATTRIBUTE name to create
ATTRIBUTE IDENTIFIER VALUE associated with a specific ATTRIBUTE.
example, the ATTRIBUTE IDENTIFIERs "Author-1", "Author-2",
"Author-3" can be used to represent three VALUEs associated with
ATTRIBUTE "Author" where a specific resource has three authors.
section 4 for the implications of this strategy on
semantics
3.4 SOIF
The SOIF syntax is defined by the following grammar
SOIF ::= OBJECT SOIF |
OBJECT ::= @ TEMPLATE-TYPE { URL ATTRIBUTE-LIST }
TEMPLATE-TYPE ::=
ATTRIBUTE-LIST ::= ATTRIBUTE ATTRIBUTE-LIST |
ATTRIBUTE |
ATTRIBUTE ::= IDENTIFIER {VALUE-SIZE} DELIMITER
URL ::= RFC1738-URL-Syntax | "-"
IDENTIFIER ::= ALPHA-NUMERIC-
VALUE ::= ARBITRARY-
VALUE-SIZE ::= NUMERIC-
DELIMITER ::= ":"
Hardie, et al. Experimental [Page 4]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
3.5 Grammar
a Uniform Resource Locator encoded in the syntax defined by
1738 [3]. If the summary object has no URL associated with it
then a Latin-1 hyphen (octal \055) is used instead
an ASCII character string that only contains
characters and hyphens or underscores. IDENTIFIERs should
including hyphens followed by positive integers except
constructing multiple-VALUE ATTRIBUTE IDENTIFIERs
a buffer of VALUE-SIZE octets containing the VALUE. The VALUE
contain data in arbitrary formats or encodings, which
recognize based on Template-Type
VALUE-
a non-negative integer encoded as an ASCII character string.
integer indicates how many octets the VALUE occupies after
DELIMITER
a two octet delimiter which is a Latin-1 colon (:) and a tab (\t),
(octal \072\011).
{ } the Latin-1 curly braces (octal \173 and \175) are used to
the VALUE-SIZE (no spaces) as well as the URL and ATTRIBUTE-
combination
@TEMPLATE-
the Latin-1 @ (octal \100) and TEMPLATE-TYPE (no space
them) is used to mark the beginning of the SOIF object
NUMERIC-
Zero or more ASCII numerals
ALPHA-NUMERIC-
Zero or more ASCII letters or numerals, plus hyphens
underscore. [a-z,A-Z,0-9,- and _].
ARBITRARY-
Octets of data in arbitrary formats or encodings
Hardie, et al. Experimental [Page 5]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
4. Matching
As was discussed in Section 1, query referral of SOIF objects will
most effective when a query identifies a particular ATTRIBUTE or
of ATTRIBUTEs as the target of the query match. A query-
ATTRIBUTE should be considered to match a SOIF ATTRIBUTE when
case-insentive character-by-character comparison matches that
of the ATTRIBUTE IDENTIFIER prior to any hyphen-integer suffix.
example, a query which asks for a match on the ATTRIBUTE "author
should match the IDENTIFIERs "author", "Author", "AUTHOR",
"Author-1". [10] discourages the registration of template
containing ATTRIBUTEs which have previously been registered
substantially different definitions. This will help eliminate mis
referral, but a CIP mesh may nonetheless need to maintain a
matching ATTRIBUTEs from particular template-types to those of other
especially unregistered, template-types
The matching semantics appropriate for a particular VALUE are
from its data type and encoding. For VALUEs associated
ATTRIBUTEs which are part of a registered template type, the
type and encoding are readily available. For VALUEs associated
ATTRIBUTES associated with unregistered template-types, an octet-by
octet comparison is the default. In cases where previous
has demonstrated that a particular ATTRIBUTE contains string data,
case-insensitive substring match may be used. For example, in
query against the "AUTHOR" ATTRIBUTE of the generic "DOCUMENT
template type, the query VALUE "Garcia" should match the SOIF
"Garcia", "GARCIA", and "Jose Garcia y Montes".
Over time, there may well emerge an understanding of which
tend to produce correct query referrals within a mesh. As
understandings emerge, mesh maintainers may wish to define
particular SOIF TEMPLATE-TYPE which restricts included ATTRIBUTES
those likely to foster correct referrals
5.
The internationalization of SOIF depends on the registration
template-types. Since TEMPLATE-TYPEs and ATTRIBUTE IDENTIFIERs
be in ASCII characters, only languages which use the ASCII
set are fully supported for unregistered TEMPLATE-TYPEs.
registered template types, in contrast, the specification of
ATTRIBUTE's definition will allow UI designers to present a native
language mapping of the ATTRIBUTE to the end user. Further,
inclusion of data type and encoding information in the description
VALUEs means that any language encoding or character set required
a particular application may be supported. For unregistered
types, the ability of peer servers to pass schema definitions
Hardie, et al. Experimental [Page 6]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
provide a form of "private registration" which could provide some
the facilities for internationalization available to
template types. (See above, section 3.1 and Refs. 6 and 7.)
6. Example Summary
The appendices contain example summary objects encoded using
template types. The following are some example summary objects
the generic "DOCUMENT" SOIF template-type
@DOCUMENT { http://home.netscape.com:80/
Title{19}: Welcome to
Content-Type{9}: text/
Content-Length{5}: 33262
}
@DOCUMENT { http://home.netscape.com/eng/ssl3/ssl-toc.
Title{19}: SSL Protocol V. 3.0
Content-Type{9}: text/
Content-Length{5}: 5870
Author-1{14}: Alan O.
Author-2{14}: Philip
Author-3{14}: Paul C.
Abstract{318}: This document specifies Version 3.0 of
Secure Sockets Layer (SSL V3.0) protocol, a
protocol that provides communications privacy over the Internet
The protocol allows client/server applications to communicate
a way that is designed to prevent eavesdropping, tampering,
message forgery
}
@DOCUMENT { http://www.nissanmotors.com/1996/300ZX/pictures/300zx.
Content-Type{10}: image/
Content-Length{5}: 25940
Last-Modified{31}: Tuesday, 11-Jun-96 19:18:44
Thumbnail{259}: ..................
}
7.
Please see (Ref. 1) for a general discussion of Security concerns
the CIP framework
SOIF currently contains no requirement that any template type
an authentication ATTRIBUTE. SOIF summary objects
authentication ATTRIBUTEs must, therefore, be treated as
indicators of the referenced resource's content. A hostile
could create a summary object which significantly misrepresented
Hardie, et al. Experimental [Page 7]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
resource's content. As part of a CIP mesh, this data could
channel a large number of requestors to a resource (
resulting in a denial of service) or away from a resource (
resulting in a loss of appropriate visibility).
8.
[1] Allen, J. and M. Mealling, "The Architecture of the
Indexing Protocol (CIP)", RFC 2651, August 1999.
[2] The Harvest Information Discovery and Access System
.
[3] D. Beckett, IAFA Templates in Use as Internet Metadata, 4
Int'l WWW Conference, December 1995,
[4] L. Lamport, LaTeX: A Document Preparation System, Addison
Wesley, Reading, Mass., 1986.
[5] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform
Locators (URL)", RFC 1738, December 1994.
[6] D. Hardey, Resource Description Messages (RDM), W3C Note-rdm
960724, July 24, 1996,
rdm.html
[7] L. Gravano, K. Chang, H. Garcia-Molina, C. Lagoze, A. Paepcke
STARTS: Stanford Protocol Proposal for Internet Retrieval
Search, January 1997,
db.stanford.edu/~gravano/starts.html
[8] S. Weibel, J. Kunze, C. Lagoze, Dublin Core Metadata for
Resource Description, Work in Progress
[9] E. Miller, Dublin Core Element Set Crosswalk, January 1997,
[10] Hardie, T., "Registration Procedures for SOIF Template Types",
RFC 2656, August 1999.
Hardie, et al. Experimental [Page 8]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
9. Authors'
Ted
901 Marshall
Redwood City, CA 94063
EMail: hardie@equinix.
Mic
Transarc
The Gulf
707 Grant
Pittsburgh, PA 15219
Phone: +1 412 338 4400
EMail: mic@transarc.
Darren
Netscape Communications Corp
685 E. Middlefield
Mountain View, CA 94043
Phone: +1 415 937 2555
EMail: dhardy@netscape.
Mike
Affinia, Inc
621 17th Street, Suite 1700
Denver, CO 80293
Phone: +1 (303) 292-4818
E-mail: mfs@affinia.
Duane
National Laboratory for Applied Network
Phone: +1 303 497 1822
EMail: wessels@nlanr.
Hardie, et al. Experimental [Page 9]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
Appendix A
Common Attributes for "FILE" Template-type Summary Objects created
Harvest
Brief abstract about the object
Author(s) of the object
Brief description about the object
File-
Number of bytes in the object
Full-
Entire contents of the object
Gatherer-
Host on which the Gatherer ran to extract information from
object
Gatherer-
Name of the Gatherer that extracted information from the object
(eg. Full-Text, Selected-Text, or Terse).
Gatherer-
Port number on the Gatherer-Host that serves the Gatherer'
information
Gatherer-
Version number of the Gatherer
Update-
The time that Gatherer updated the content summary for the object
Searchable keywords extracted from the object
Last-Modification-
The time that the object was last modified
MD
MD5 16-byte checksum of the object
Hardie, et al. Experimental [Page 10]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
Refresh-
The number of seconds after Update-Time when the summary object
to be re-generated. Defaults to 1 month
Time-to-
The number of seconds after Update-Time when the summary object
no longer valid. Defaults to 6 months
Title of the object
Type The object's type. Some example types are
Internet-
Hardie, et al. Experimental [Page 11]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
Update-
The time that the summary object was last updated.
field, no default
URL-
Any URL references present within HTML objects
Appendix B
Proposed Attributes for a "CIP-HINT" Template
Attribute-Identifier-
A comma-delimited list whose entries take the form Template
Type:Attribute . This list identifies the attributes
which queries are supported. Because of the current limitation
Identifiers, this list must be in ASCII
The URI of the service which created some or all of the
objects to which this hint applies. Note that this service may
and often is distinct from the server which provides query
to those objects
Total-Object-
The total number of index objects in the collection for which
Hint applies. This should be a positive integer
Weightlist-[Attribute-Identifier
This construction allows the HINT to contain a weighted list
values for a specific Attribute-Identifier. There may be as
Weightlist entries as there Attribute-Identifiers in
Attribute-Identifier-List. Each Weightlist entry takes the
of Value;Object-Count, where the object count is a
integer representing the number of objects within the
which contain that value. Weightlists are comma- delimited
Hardie, et al. Experimental [Page 12]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
Should a Value contain a comma, it should be escaped
incorporated into the weightlist
Threshold-[Attribute-Identifier
If a server wishes not to report infrequently occurring Values
a specific Weightlist, it may declare a threshold under which
will not report Values
Certification-
The type of Certification used for this
The Value of the Certification
The Date at which the hint was
Example
@CIP-HINT{ http://nic.nasa.gov:80/Harvest/brokers/NASA
Attribute-Identifier-list{49}:
DOCUMENT:Author, DOCUMENT:Keywords, IMAGE:
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-
Certification{51}: mQCNAzFNm5QAAEEALUBOolOWKpby+=
Date{29}: Sun, 05 Jan 1997 08:33:33
Appendix C
A "Dublin-Core" Template Type [Ref. 8,9]
The name given to the resource by the CREATOR or PUBLISHER
The person(s) or organization(s) primarily responsible for
intellectual content of the resource. For example, authors in
case of written documents, artists, photographers, or
in the case of visual resources
Hardie, et al. Experimental [Page 13]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
The topic of the resource, or keywords or phrases that
the subject or content of the resource. The intent of
specification of this element is to promote the use of
vocabularies and keywords. This element might well
scheme-qualified classification data (for example, Library
Congress Classification Numbers or Dewey Decimal numbers)
scheme-qualified controlled vocabularies (such as Medical
Headings or Art and Architecture Thesaurus descriptors) as well
A textual description of the content of the resource,
abstracts in the case of document-like objects or
descriptions in the case of visual resources. Future
collections might well include computational content
(spectral analysis of a visual resource, for example) that may
be embeddable in current network systems. In such a case
field might contain a link to such a description rather than
description itself
The entity responsible for making the resource available in
present form, such as a publisher, a university department, or
corporate entity. The intent of specifying this field is
identify the entity that provides access to the resource
Person(s) or organization(s) in addition to those specified in
CREATOR element who have made significant
contributions to the resource but whose contribution is
to the individuals or entities specifed in the CREATOR
(for example, editors, transcribers, illustrators, and convenors).
The date the resource was made available in its present form.
recommended best practice is an 8 digit number in the
YYYYMMDD as defined by ANSI X3.30-1985. In this scheme, the
element for the day this is written would be 19961203, or
3, 1996. Many other schema are possible, but if used, they
be identified in an unambiguous manner
The category of the resource, such as home page, novel, poem
working paper, technical report, essay, dictionary. It
expected that RESOURCE TYPE will be chosen from an enumerated
of types
Hardie, et al. Experimental [Page 14]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
The data representation of the resource, such as text/html, ASCII
Postscript file, executable application, or JPEG image.
intent of specifying this element is to provide
necessary to allow people or machines to make decisions about
usability of the encoded data (what hardware and software might
required to display or execute it, for example). As with
TYPE, FORMAT will be assigned from enumerated lists such
registered Internet Media Types (MIME types). In principal
formats can include physical media such as books, serials,
other non-electronic media
String or number used to uniquely identify the resource.
for networked resources include URLs and URNs (when implemented).
Other globally-unique identifiers,such as International
Book Numbers (ISBN) or other formal names would also be
for this element
The work, either print or electronic, from which this resource
derived, if applicable. For example, an html encoding of
Shakespearean sonnet might identify the paper version of
sonnet from which the electronic version was transcribed
Language(s) of the intellectual content of the resource.
practical, the content of this field should coincide with the
Z39.53 three character codes for written languages
Relationship to other resources. The intent of specifying
element is to provide a means to express relationships
resources that have formal relationships to others, but exist
discrete resources themselves. For example, images in a document
chapters in a book, or items in a collection. A
specification of RELATION is currently under development.
and developers should understand that use of this element
be currently considered experimental
The spatial locations and temporal durations characteristic of
resource. Formal specification of COVERAGE is currently
development. Users and developers should understand that use
this element should be currently considered experimental
Hardie, et al. Experimental [Page 15]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
The content of this element is intended to be a link (a URL
other suitable URI as appropriate) to a copyright notice,
rights-management statement, or perhaps a server that
provide such information in a dynamic way. The intent
specifying this field is to allow providers a means to
terms and conditions or copyright statements with a resource
collection of resources. No assumptions should be made by
if such a field is empty or not present
Example
@Dublin-Core-1 { ftp://ds.internic.net/internet-drafts
draft-kunze-dc-00.
TITLE{52}: Dublin Core Metadata for Simple Resource
CREATOR-1{9}: S.
CREATOR-2{8}: J.
CREATOR-3{9}: C.
SUBJECT{44}: The Dublin Core Set of Elements for
DESCRIPTION{46}: Reference description of Dublin Core elements
PUBLISHER{31}: Internet Engineering Task
CONTRIBUTOR-1{11}: Nick
CONTRIBUTOR-2{15}: Eliot
CONTRIBUTOR-3{14}: Martijn
CONTRIBUTOR-4{18}: Christian
CONTRIBUTOR-5{14}: Timothy
CONTRIBUTOR-6{11}: Andrew
CONTRIBUTOR-7{10}: Mic
CONTRIBUTOR-8{11}: Dan
CONTRIBUTOR-9{15}: Michael
CONTRIBUTOR-10{12}: Wick
DATE{16}: February 9, 1997
TYPE{14}: Internet
FORMAT{4}:
IDENTIFIER:{21} draft-kunze-dc-00.
SOURCE{41}: http://purl.oclc.org/metadata/dublin_
LANGUAGE{3}:
RELATION{24}: Draft Reference
COVERAGE{22}: Expires August 8, 1997
RIGHTS{58}: Unlimited Distribution
readers must not cite as standard
Hardie, et al. Experimental [Page 16]
RFC 2655 CIP Index Object Format for SOIF Objects August 1999
11. Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Hardie, et al. Experimental [Page 17]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
