As per Relevance of the word registration, we have this rfc below:
Network Working Group T.
Request For Comments: 2656
Category: Experimental August 1999
Registration Procedures for SOIF Template
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
The Summary Object Interchange Format [Ref. 1] was first defined
the Harvest Project [Ref 2.] in January 1994. SOIF was derived
a combination of the Internet Anonymous FTP Archives IETF
Group (IAFA) templates [Ref 3.] and the BibTeX bibliography
[Ref 4.]. The combination was originally noted for its advantages
providing a convenient and intuitive way for delimiting
within a stream, and setting apart the URL for easy object access
invocation, while still preserving compatibility with IAFA templates
SOIF uses named template types to indicate the attributes which
be contained within a particular summary object. Within the
of a single application, private agreement on the definition
template types has been adequate. As SOIF objects are moved
applications, however, the need for standard, well-specified,
easily identifiable template types increases. This need
particularly intense in the context of query referral,
knowledge of an attribute's definition and the allowed data types
specific values is crucial. For a discussion of this in the
of the Common Indexing Protocol, see [Ref. 1].
The registration procedure described in this document is specific
SOIF template types. There is ongoing work within the IETF
specify a more generic schema registration facility[Ref. 5]. It
not yet clear whether the results of that work will encompass
ability to register entities like SOIF template types. If it
so, the registration of SOIF template types may be shifted to
method and registry. Should that occur, appropriate pointers will
created in cooperation with the Registrar to ensure that
registrations are lost
Hardie Experimental [Page 1]
RFC 2656 Registration Procedures for SOIF August 1999
1.
The initial registrar of SOIF template types will be the
Assigned Numbers Authority (IANA).
2. Defining Template
Each SOIF object is composed of 3 fundamental components: a
type IDENTIFIER, a URL, and zero or more ATTRIBUTE-VALUE pairs.
[Ref 1.] for the formal grammar of SOIF and a description of
these components interrelate. As part of the registration process
registrants must: propose a template type IDENTIFER; list
ATTRIBUTEs which the template may contain; identify whether
ATTRIBUTE is mandatory or optional; and specifiy the data type
encoding appropriate for the VALUEs associated with each ATTRIBUTE
2.1 The template type
The IDENTIFIER for the template type is assigned at
based on a proposal from the registrant. It is, however, at the
discretion of the registrars to assign specific IDENTIFIERS.
they will normally assign the IDENTIFIERs proposed by registrants
they may choose to modify a proposed IDENTIFIER to avoid
with other existing or proposed template types
Because of the pre-installed base of servers using privately
upon template types, applications using SOIF need to be able
ascertain whether a referenced template type has been registered.
order to accomplish this, all template type IDENTIFIERS for
types registered with the IANA will begin with the ASCII
"IANA-". An IANA-registered template type based on the
specification, for example, might be registered as "IANA-GILS".
Should other registrars emerge over time, similar strings must
established and used to compose template type IDENTIFIERS which
assign
2.2 The
The URL associated with a particular summary object is determined
the application generating the object. Applications must
valid URLs according to the rules of [Ref 6.], but there is
restriction on what sorts of URLs may be associated with
template types. The use of a particular template type indicates
type of information contained in the summary object, not how
inital resource being summarized was accessed. This aspect of
summary objects is therefor not subject to registration
Hardie Experimental [Page 2]
RFC 2656 Registration Procedures for SOIF August 1999
2.3
Where an ATTRIBUTE associated with a proposed template type
matches an ATTRIBUTE previously defined in a registered
type, the proposed ATTRIBUTE should be defined by reference to
existing, registered ATTRIBUTE. This allows query referral meshes
easily map queries against ATTRIBUTEs derived from different
types and provides an easy method for extending or restricting
existing template type to match an application's particular needs
In such cases, the ATTRIBUTE for the newly registered template
will have the same name, description, and allowed values as
ATTRIBUTE in the existing registered template type
Where no existing ATTRIBUTE may be referenced, registrants
specify each ATTRIBUTE's name, description, and allowed values
2.3.1 ATTRIBUTE
To handle multiple VALUEs for the same ATTRIBUTE, SOIF uses a
convention, appending a hyphen and a positive integer to the
ATTRIBUTE name to create a unique ATTRIBUTE IDENTIFIER. For example
the ATTRIBUTE IDENTIFIERs "Publisher-1", "Publisher-2",
"Publisher-3" can be used to associate three VALUEs with
ATTRIBUTE named "Publisher". In order to provide for the
operation of this convention, ATTRIBUTE names may not terminate
a hyphen followed by an integer. ATTRIBUTE names are
restricted only by the grammar defined in [Ref. 1].
In general, registrants will probably wish to propose ATTRIBUTE
which are short, mnemonic, and intuitively associated with
characterstic that the ATTRIBUTE describes. While these may
generally laudable goals, it must be remembered that the
interface need not present the raw ATTRIBUTE name to the end user
indeed, in situations where the end user's language does not use
ASCII character set, the interface must map the ATTRIBUTE name to
appropriate local representation. Since ATTRIBUTE definitions
provided as part of the registration process, registrants
avoid attempting to overload the ATTRIBUTE name with
which belongs in the description
2.3.2 ATTRIBUTE
ATTRIBUTE descriptions for ATTRIBUTEs registered with the IANA
be in English, though mappings to other languages may be proposed
part of the ATTRIBUTE description. ATTRIBUTE descriptions
propose clear criteria for establishing whether an object posseses
particular ATTRIBUTE. Descriptions should also include at least
examples of how each attribute relates to an object being summarized
Hardie Experimental [Page 3]
RFC 2656 Registration Procedures for SOIF August 1999
using, where possible, objects which are broadly available to a
variety of audiences. If several ATTRIBUTEs within a template
inter-relate, the descriptions of each may reference the others;
must be taken, however, that the resulting descriptions are
circular. Where fully realized specifications of the ATTRIBUTEs
been created in other contexts, the salient text from
descriptions should be quoted and appropriate references cited
2.3.3 Required and Optional
Each ATTRIBUTE registered for a template type must be marked
required or optional. Note that marking an ATTRIBUTE required
not imply that it may not have a null value; it implies only that
must appear in all templates of that registered template type
2.4
For each ATTRIBUTE, the registrant must specify the data format and
if appropriate, the language, character set, and encoding.
possible, the registrant should include references to a precise
openly available specification of the format. The registrant
also specify the appropriate matching semantics for the ATTRIBUTE
these are not strictly implied by the data format and encoding.
registrant must also note whether null values are permitted
3.
Creating a revision of a template type is functionally similar
creating a new template type. A Registrant may propose as a name
derivative allowed under the rules of section 4.1 and [Ref. 1] to
new template type. ATTRIBUTEs retained across versions
modification should be referenced as described in section 4.3.
Modified ATTRIBUTEs must be described as if new. A registrant
note a relationship between a proposed template type and an
template type as part of the registration process. The
three relationships are currently defined
Successor: for proposed template types intended to replace
existing template type
Variant: for proposed template types whose ATTRIBUTEs are either
superset or a subset of an existing template type
Alternate: for proposed template types which share a large number
ATTRIBUTEs with an existing template type but whose ATTRIBUTEs do
form a strict superset or subset of an existing template type
Hardie Experimental [Page 4]
RFC 2656 Registration Procedures for SOIF August 1999
Note that there may be relationships between ATTRIBUTEs of
template types without there being a named relationship between
template types themselves
4.
SOIF template types which are intended for applications which
pass summary objects over the global Internet should
authentication ATTRIBUTEs. SOIF summary objects
authentication ATTRIBUTEs must be treated as unreliable indicators
the referenced resource's content and should only be used where
aspects of the environment provide sufficient security to
spoofing. Given, however, that particular template types may
intended for environments with such security, there is no
that registered template types contain authentication ATTRIBUTEs
The application developer must select or propose a template
appropriate for the intended appliation environment; if none
available with suitable authentication ATTRIBUTEs, the provisions
section 4.3 make it easy for the developer to propose an extension
an existing template type with the appropriate
ATTRIBUTEs
5.
[1] Hardie, T., Bowman, M., Hardy, D., Schwartz, M. and D. Wessels
"CIP Index Object Format for SOIF Objects", RFC 2655,
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] IETF Schema Registration Working Group
Applications_Area
[6] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform
Locators (URL)", RFC 1738, December 1994.
Hardie Experimental [Page 5]
RFC 2656 Registration Procedures for SOIF August 1999
6. Author's
Ted
901 Marshall
Redwood City, CA 94063
EMail: hardie@equinix.
Hardie Experimental [Page 6]
RFC 2656 Registration Procedures for SOIF August 1999
Appendix A
An Example Registration
1. Registrant's Name ________________________________________
2. Registrant's Organization ________________________________
3. Registrant's email address _______________________________
4. Registrant's postal address ______________________________
______________________________
______________________________
______________________________
5. Registrant's telephone number ____________________________
6. Proposed Template Type IDENTIFIER: IANA-__________________
7. If this Template Type relates to an existing Template
list the Template Type(s) and the relationship
Template Type ___________________ Relationship ______________
8. For each ATTRIBUTE in this Template type, provide
following information
a) NAME _____________________________________________________
b) Reference Template Type __________________________________
If there is no registered Template Type which has
specified this attribute, provide the following information
c) ATTRIBUTE Description ____________________________________
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________
Hardie Experimental [Page 7]
RFC 2656 Registration Procedures for SOIF August 1999
d) Required [] or Optional []?
e) Data Type and ecoding for this VALUE _____________________
_____________________
_____________________
f) If a specific language and character set are expected,
them here ___________________________________________________
g) Is a null value permitted? Yes [] No []
Hardie Experimental [Page 8]
RFC 2656 Registration Procedures for SOIF August 1999
7. 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 Experimental [Page 9]
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
