Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Registration Procedures for SOIF Template Types (RFC2656)

IP.com Disclosure Number: IPCOM000003245D
Original Publication Date: 1999-Aug-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 6 page(s) / 16K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Hardie: AUTHOR

Abstract

The Summary Object Interchange Format [Ref. 1] 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.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 17% of the total text.

Network Working Group T. Hardie

Request For Comments: 2656 Equinix

Category: Experimental August 1999

Registration Procedures for SOIF Template Types

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.

Abstract

The Summary Object Interchange Format [Ref. 1] 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 uses named template types to indicate the attributes which may

be contained within a particular summary object. Within the context

of a single application, private agreement on the definition of

template types has been adequate. As SOIF objects are moved among

applications, however, the need for standard, well-specified, and

easily identifiable template types increases. This need is

particularly intense in the context of query referral, where

knowledge of an attribute's definition and the allowed data types for

specific values is crucial. For a discussion of this in the context

of the Common Indexing Protocol, see [Ref. 1].

The registration procedure described in this document is specific to

SOIF template types. There is ongoing work within the IETF to

specify a more generic schema registration facility[Ref. 5]. It is

not yet clear whether the results of that work will encompass the

ability to register entities like SOIF template types. If it does

so, the registration of SOIF template types may be shifted to that

method and registry. Should that occur, appropriate pointers will be

created in cooperation with the Registrar to ensure that no

registrations are lost.

1. Registrar

The initial registrar of SOIF template types will be the Internet

Assigned Numbers Authority (IANA).

2. Defining Template Types

Each SOIF object is composed of 3 fundamental components: a template

type IDENTIFIER, a UR...