1179 lines
No EOL
61 KiB
HTML
1179 lines
No EOL
61 KiB
HTML
<!DOCTYPE html>
|
|
<!-- saved from url=(0045)https://datatracker.ietf.org/doc/html/rfc4452 -->
|
|
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
|
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
|
<title>
|
|
|
|
rfc4452
|
|
|
|
</title>
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<style>
|
|
|
|
@media only screen
|
|
and (min-width: 992px)
|
|
and (max-width: 1199px) {
|
|
body { font-size: 14pt; }
|
|
div.content { width: 96ex; margin: 0 auto; }
|
|
}
|
|
@media only screen
|
|
and (min-width: 768px)
|
|
and (max-width: 991px) {
|
|
body { font-size: 14pt; }
|
|
div.content { width: 96ex; margin: 0 auto; }
|
|
}
|
|
@media only screen
|
|
and (min-width: 480px)
|
|
and (max-width: 767px) {
|
|
body { font-size: 11pt; }
|
|
div.content { width: 96ex; margin: 0 auto; }
|
|
}
|
|
@media only screen
|
|
and (max-width: 479px) {
|
|
body { font-size: 8pt; }
|
|
div.content { width: 96ex; margin: 0 auto; }
|
|
}
|
|
@media only screen
|
|
and (min-device-width : 375px)
|
|
and (max-device-width : 667px) {
|
|
body { font-size: 9.5pt; }
|
|
div.content { width: 96ex; margin: 0; }
|
|
}
|
|
@media only screen
|
|
and (min-device-width: 1200px) {
|
|
body { font-size: 10pt; margin: 0 4em; }
|
|
div.content { width: 96ex; margin: 0; }
|
|
}
|
|
h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6 {
|
|
font-weight: bold;
|
|
/* line-height: 0pt; */
|
|
display: inline;
|
|
white-space: pre;
|
|
font-family: monospace;
|
|
font-size: 1em;
|
|
font-weight: bold;
|
|
}
|
|
pre {
|
|
font-size: 1em;
|
|
margin-top: 0px;
|
|
margin-bottom: 0px;
|
|
}
|
|
.pre {
|
|
white-space: pre;
|
|
font-family: monospace;
|
|
}
|
|
.header{
|
|
font-weight: bold;
|
|
}
|
|
.newpage {
|
|
page-break-before: always;
|
|
}
|
|
.invisible {
|
|
text-decoration: none;
|
|
color: white;
|
|
}
|
|
@media print {
|
|
body {
|
|
margin-top: 5em;
|
|
font-family: monospace;
|
|
font-size: 10.5pt;
|
|
}
|
|
h1, h2, h3, h4, h5, h6 {
|
|
font-size: 1em;
|
|
}
|
|
|
|
a:link, a:visited {
|
|
color: inherit;
|
|
text-decoration: none;
|
|
}
|
|
.noprint {
|
|
display: none;
|
|
}
|
|
}
|
|
@media screen {
|
|
.grey, .grey a:link, .grey a:visited {
|
|
color: #777;
|
|
}
|
|
.meta-info {
|
|
background-color: #EEE;
|
|
}
|
|
.top {
|
|
border-top: 7px solid #EEE;
|
|
}
|
|
.pad {
|
|
padding-top: 7px;
|
|
line-height: 24px;
|
|
padding-bottom: 4px;
|
|
}
|
|
.bgwhite { background-color: white; }
|
|
.bgred { background-color: #F44; }
|
|
.bggrey { background-color: #666; }
|
|
.bgbrown { background-color: #840; }
|
|
.bgorange { background-color: #FA0; }
|
|
.bgyellow { background-color: #EE0; }
|
|
.bgmagenta{ background-color: #F4F; }
|
|
.bgblue { background-color: #66F; }
|
|
.bgcyan { background-color: #4DD; }
|
|
.bggreen { background-color: #4F4; }
|
|
|
|
.legend { font-size: 90%; }
|
|
.cplate { font-size: 70%; border: solid grey 1px; }
|
|
}
|
|
|
|
|
|
|
|
.bgwhite { background-color: white; }
|
|
.bgred { background-color: #F44; }
|
|
.bggrey { background-color: #666; }
|
|
.bgbrown { background-color: #840; }
|
|
.bgorange { background-color: #FA0; }
|
|
.bgyellow { background-color: #EE0; }
|
|
.bgmagenta{ background-color: #F4F; }
|
|
.bgblue { background-color: #66F; }
|
|
.bgcyan { background-color: #4DD; }
|
|
.bggreen { background-color: #4F4; }
|
|
|
|
.draftcontent { margin-top:0px !important;}
|
|
|
|
|
|
</style>
|
|
|
|
<!--[if lt IE 9]>
|
|
<script src="https://www.ietf.org/lib/dt/7.36.0/html5shiv/html5shiv.min.js"></script>
|
|
<script src="https://www.ietf.org/lib/dt/7.36.0/respond/dest/respond.min.js"></script>
|
|
<![endif]-->
|
|
|
|
<link rel="alternate" type="application/atom+xml" title="Document changes" href="https://datatracker.ietf.org/feed/document-changes/draft-vandesompel-info-uri/">
|
|
<meta name="description" content="The "info" URI Scheme for Information Assets with Identifiers in Public Namespaces (RFC )">
|
|
<script src="./rfc4452_files/d3.min.js.download"></script>
|
|
<script src="./rfc4452_files/jquery.min.js.download"></script>
|
|
|
|
|
|
|
|
<link rel="shortcut icon" href="https://www.ietf.org/lib/dt/7.36.0/ietf/images/ietf-icon-blue3.png">
|
|
|
|
<link rel="apple-touch-icon" href="https://www.ietf.org/lib/dt/7.36.0/ietf/images/apple-touch-icon.png">
|
|
</head>
|
|
|
|
<body style="padding-top: 0;">
|
|
|
|
<div class="content" id="content">
|
|
|
|
<!-- template: /a/www/ietf-datatracker/web/ietf/templates/doc/document_html.html -->
|
|
|
|
<div class="rfcmarkup">
|
|
<div class="noprint" style="height: 6px;">
|
|
<div onmouseover="this.style.cursor='pointer';" onclick="showLegend();" onmouseout="hideLegend()" style="height: 6px; min-height: 6px; width: 96ex; position: absolute; margin-top:0; " class="meta-info bgorange" title="Click for colour legend."> </div>
|
|
<div id="legend" class="meta-info noprint pre legend" style="position:absolute; top: 4px; left: 4ex; visibility:hidden; background-color: white; padding: 4px 9px 5px 7px; border: solid #345 1px; " onmouseover="showLegend();" onmouseout="hideLegend();">
|
|
</div>
|
|
</div>
|
|
|
|
|
|
<div class="noprint">
|
|
<pre class="pre meta-info">[<a href="https://datatracker.ietf.org/" title="Document search and retrieval page">Search</a>] [<a href="https://www.rfc-editor.org/rfc/rfc4452.txt" title="Plaintext version of this document">txt</a>|<a href="https://www.rfc-editor.org/rfc/rfc4452.html" title="HTML version of this document, from XML2RFC">html</a>|<a href="https://www.rfc-editor.org/rfc/pdfrfc/rfc4452.txt.pdf" title="PDF version of this document">pdf</a>|<a href="https://datatracker.ietf.org/doc/rfc4452/bibtex" title="BibTex entry for this document">bibtex</a>] [<a href="https://datatracker.ietf.org/doc/rfc4452/" title="Datatracker information for this document">Tracker</a>] [<a href="https://datatracker.ietf.org/group/app/" title="The working group handling this document">WG</a>] [<a href="mailto:draft-vandesompel-info-uri@ietf.org?subject=draft-vandesompel-info-uri" title="Send email to the document authors">Email</a>] [<a href="https://www.ietf.org/rfcdiff?difftype=--hwdiff&url2=draft-vandesompel-info-uri-04.txt" title="Inline diff (wdiff)">Diff1</a>] [<a href="https://www.ietf.org/rfcdiff?url2=draft-vandesompel-info-uri-04.txt" title="Side-by-side diff">Diff2</a>] [<a href="https://www.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-vandesompel-info-uri-04.txt" title="Run an idnits check of this document">Nits</a>]
|
|
|
|
From: <a href="https://datatracker.ietf.org/doc/html/draft-vandesompel-info-uri-04">draft-vandesompel-info-uri-04</a> Informational
|
|
<a class="text-warning" href="https://www.rfc-editor.org/errata_search.php?rfc=4452&rec_status=0">Errata exist</a></pre>
|
|
</div>
|
|
|
|
|
|
<div class="draftcontent">
|
|
<pre>Network Working Group H. Van de Sompel
|
|
Request for Comments: 4452 LANL
|
|
Category: Informational T. Hammond
|
|
NPG
|
|
E. Neylon
|
|
Manifest Solutions
|
|
S. Weibel
|
|
OCLC
|
|
April 2006
|
|
|
|
|
|
<span class="h1">The "info" URI Scheme</span>
|
|
<span class="h1">for Information Assets with Identifiers in Public Namespaces</span>
|
|
|
|
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 (2006).
|
|
|
|
Abstract
|
|
|
|
This document defines the "info" Uniform Resource Identifier (URI)
|
|
scheme for information assets with identifiers in public namespaces.
|
|
Namespaces participating in the "info" URI scheme are regulated by an
|
|
"info" Registry mechanism.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 1]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-2"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
Table of Contents
|
|
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-1">1</a>. Introduction ....................................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-3">3</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-1.1">1.1</a>. Terminology ................................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-3">3</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-1.2">1.2</a>. Information Assets .........................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-3">3</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-2">2</a>. Application of the "info" URI Scheme ............................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-4">4</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-3">3</a>. The "info" Registry .............................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-5">5</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-3.1">3.1</a>. Management Characteristics of the "info" Registry ..........<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-5">5</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-3.2">3.2</a>. Functional Characteristics of the "info" Registry ..........<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-5">5</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-3.3">3.3</a>. Maintenance of the "info" Registry .........................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-6">6</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-4">4</a>. The "info" URI Scheme ...........................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-6">6</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-4.1">4.1</a>. Definition of "info" URI Syntax ............................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-6">6</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-4.2">4.2</a>. Allowed Characters Under the "info" URI Scheme .............<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-8">8</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-4.3">4.3</a>. Examples of "info" URIs ....................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-9">9</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-5">5</a>. Normalization and Comparison of "info" URIs ....................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-10">10</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-6">6</a>. Rationale ......................................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-12">12</a>
|
|
6.1. Why Create a New URI Scheme for Identifiers from Public
|
|
Namespaces? ...............................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-12">12</a>
|
|
6.2. Why Not Use an Existing URI Scheme for Identifiers
|
|
from Public Namespaces? ...................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-12">12</a>
|
|
6.3. Why Not Create a New URN Namespace ID for
|
|
Identifiers from Public Namespaces? .......................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-12">12</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-7">7</a>. Security Considerations ........................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-13">13</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-8">8</a>. IANA Considerations ............................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-14">14</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-9">9</a>. Acknowledgements ...............................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-14">14</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-10">10</a>. References ....................................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-14">14</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-10.1">10.1</a>. Normative References .....................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-14">14</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-10.2">10.2</a>. Informative References ...................................<a href="https://datatracker.ietf.org/doc/html/rfc4452#page-15">15</a>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 2]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-3"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
<span class="h2"><a class="selflink" id="section-1" href="https://datatracker.ietf.org/doc/html/rfc4452#section-1">1</a>. Introduction</span>
|
|
|
|
This document defines the "info" Uniform Resource Identifier (URI)
|
|
scheme for information assets that have identifiers in public
|
|
namespaces but are not part of the URI allocation. By "information
|
|
asset" this document intends any information construct that has
|
|
identity within a public namespace.
|
|
|
|
<span class="h3"><a class="selflink" id="section-1.1" href="https://datatracker.ietf.org/doc/html/rfc4452#section-1.1">1.1</a>. Terminology</span>
|
|
|
|
In this document, the keywords "MUST", "MUST NOT", "SHALL", "SHALL
|
|
NOT", "SHOULD", "SHOULD NOT", "MAY", "MAY NOT", and "RECOMMENDED" are
|
|
to be interpreted as described in <a href="https://datatracker.ietf.org/doc/html/rfc2119">RFC 2119</a> [<a href="https://datatracker.ietf.org/doc/html/rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] and indicate
|
|
requirement levels for compliant implementations.
|
|
|
|
<span class="h3"><a class="selflink" id="section-1.2" href="https://datatracker.ietf.org/doc/html/rfc4452#section-1.2">1.2</a>. Information Assets</span>
|
|
|
|
There exist many information assets with identifiers in public
|
|
namespaces that are not referenceable by URI schemes. Examples of
|
|
such namespaces include Dewey Decimal Classifications [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-DEWEY" title=""Dewey Decimal Classification"">DEWEY</a>],
|
|
Library of Congress Control Numbers [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-LCCN" title=""Library of Congress Control Number"">LCCN</a>], NISO Serial Item and
|
|
Contribution Identifiers [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-SICI" title=""ANSI/NISO Z39.56-1996 (R2002), "">SICI</a>], NASA Astrophysics Data System
|
|
Bibcodes [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-BIBCODE" title=""NASA Astrophysics Data System Bibliographic Code"">BIBCODE</a>], and National Library of Medicine PubMed
|
|
identifiers [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-PMID" title=""PubMed Overview"">PMID</a>]. Other candidate namespaces include Online
|
|
Computer Library Center OCLC Numbers [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-OCLCNUM" title=""Online Computer Library Center OCLC Control Number"">OCLCNUM</a>] and NISO OpenURL
|
|
Framework identifiers [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-OFI" title=""ANSI/NISO Z39.88-2004, "">OFI</a>].
|
|
|
|
The "info" URI scheme facilitates the referencing of information
|
|
assets that have identifiers in such public namespaces by means of
|
|
URIs. When referencing an information asset by means of its "info"
|
|
URI, the asset SHALL be considered a "resource" as defined in <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc3986">3986</a> [<a href="https://datatracker.ietf.org/doc/html/rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] and SHALL enjoy the same common syntactic, semantic,
|
|
and shared language benefits that the URI presentation confers. As
|
|
such, the "info" URI scheme enables public namespaces that are not
|
|
part of the URI allocation to be represented within the allocation.
|
|
The "info" URI scheme thus provides a bridging mechanism to allow
|
|
public namespaces to become part of the URI allocation.
|
|
|
|
Namespaces declared under the "info" URI scheme are regulated by an
|
|
"info" Registry mechanism. The "info" Registry allows a public
|
|
namespace that is not part of the URI allocation to be declared in a
|
|
registration process by the organization that manages it (the
|
|
Namespace Authority). The "info" Registry supports the declaration
|
|
of public namespaces that are not part of the URI allocation in a
|
|
manner that facilitates the construction of URIs for information
|
|
assets without imposing the burdens of independent URI registration
|
|
and maintenance of resource representations on the Namespace
|
|
Authority. Information assets identified within a registered
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 3]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-4"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
namespace SHALL be added or deleted according to the business
|
|
processes of the Namespace Authority, and yet MAY be referenced
|
|
within network applications via the "info" URI in an open,
|
|
standardized way without additional action on the part of the
|
|
Namespace Authority.
|
|
|
|
The "info" URI scheme exists primarily for identification purposes.
|
|
Implementations MUST NOT assume that an "info" URI can be
|
|
dereferenced to a representation of the resource identified by the
|
|
URI although Namespace Authorities MAY disclose in the registration
|
|
record references to service mechanisms pertaining to identifiers
|
|
from the registered namespace. Applications of the "info" URI scheme
|
|
are restricted to the identification of information assets and the
|
|
declaration of normalization rules for comparing identifiers of such
|
|
information assets regardless of whether any services relating to
|
|
such information assets are accessible via the Internet. References
|
|
to such services MAY be disclosed within an "info" registration
|
|
record, but these services SHALL NOT be regarded as authoritative.
|
|
The "info" URI scheme does not support global resolution methods.
|
|
|
|
<span class="h2"><a class="selflink" id="section-2" href="https://datatracker.ietf.org/doc/html/rfc4452#section-2">2</a>. Application of the "info" URI Scheme</span>
|
|
|
|
Public namespaces that are used for the identification of information
|
|
assets and that are not part of the URI allocation MAY be registered
|
|
as namespaces within the "info" Registry. Namespace Authorities MAY
|
|
register these namespaces in the "info" Registry, thereby making
|
|
these namespaces available to applications that need to reference
|
|
information assets by means of a URI. Registrations of public
|
|
namespaces that are not part of the URI allocation by parties other
|
|
than the Namespace Authority SHALL NOT be permitted, thereby ensuring
|
|
against hostile usurpation or inappropriate usage of registered
|
|
service marks or the public namespaces of others.
|
|
|
|
Registration of a public namespace under the "info" Registry implies
|
|
no particular functionalities of the identifiers from the registered
|
|
namespace other than the identification of information assets. No
|
|
resolution mechanisms can be assumed for the "info" URI scheme,
|
|
though for any particular namespace there MAY exist mechanisms for
|
|
resolving identifiers to network services. The definition of such
|
|
services falls outside the scope of the "info" URI scheme.
|
|
Registration does not define namespace-specific semantics for
|
|
identifiers within a registered namespace, though allowable character
|
|
sets and normalization rules are specified in Sections <a href="https://datatracker.ietf.org/doc/html/rfc4452#section-4">4</a> and <a href="https://datatracker.ietf.org/doc/html/rfc4452#section-5">5</a> so as
|
|
to ensure that the URIs created using such identifiers are compliant
|
|
with applications that use URIs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 4]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-5"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
The registration of a public namespace in the "info" Registry SHALL
|
|
NOT preclude further development of services associated with that
|
|
namespace that MAY qualify the namespace for additional publication
|
|
elsewhere within the URI allocation.
|
|
|
|
<span class="h2"><a class="selflink" id="section-3" href="https://datatracker.ietf.org/doc/html/rfc4452#section-3">3</a>. The "info" Registry</span>
|
|
|
|
The "info" Registry provides a mechanism for the registration of
|
|
public namespaces that are used for the identification of information
|
|
assets and that are not part of the URI allocation.
|
|
|
|
NISO [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-NISO" title=""National Information Standards Organization"">NISO</a>], the National Information Standards Organization, will
|
|
act as the Maintenance Agency for the "info" Registry and will
|
|
delegate the day-to-day operation of the "info" Registry to a
|
|
Registry Operator. As the Maintenance Agency, NISO will ensure that
|
|
the Registry Operator operates the "info" Registry in accordance with
|
|
a publicly articulated policy document established under NISO
|
|
governance and made available on the "info" website,
|
|
<<a href="http://info-uri.info/">http://info-uri.info/</a>>. The "info" Registry policy defines a review
|
|
process for candidate namespaces and provides measures of quality
|
|
control and suitability for entry of namespaces.
|
|
|
|
<span class="h3"><a class="selflink" id="section-3.1" href="https://datatracker.ietf.org/doc/html/rfc4452#section-3.1">3.1</a>. Management Characteristics of the "info" Registry</span>
|
|
|
|
The "info" Registry will be managed according to policies established
|
|
under the auspices of NISO. All such policies, as well as the
|
|
namespace declarations in the "info" Registry, will be public.
|
|
|
|
<span class="h3"><a class="selflink" id="section-3.2" href="https://datatracker.ietf.org/doc/html/rfc4452#section-3.2">3.2</a>. Functional Characteristics of the "info" Registry</span>
|
|
|
|
The "info" Registry will be publicly accessible and will support
|
|
discovery (by both humans and machines) of:
|
|
|
|
o string literals identifying the namespaces for which the Registry
|
|
provides a guarantee of uniqueness and persistence
|
|
o names and contact information of Namespace Authorities
|
|
o syntax requirements for identifiers maintained in such namespaces
|
|
o normalization methodologies for identifiers maintained in such
|
|
namespaces
|
|
o network references to a description of service mechanisms (if any)
|
|
for identifiers maintained in such namespaces
|
|
o ancillary documentation
|
|
|
|
Registry entries refer to the corresponding "namespace" and
|
|
"identifier" components, which are defined in the ABNF given in
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4452#section-4.1">Section 4.1</a> of this document.
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 5]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-6"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
<span class="h3"><a class="selflink" id="section-3.3" href="https://datatracker.ietf.org/doc/html/rfc4452#section-3.3">3.3</a>. Maintenance of the "info" Registry</span>
|
|
|
|
The public namespaces that MAY be registered in the "info" Registry
|
|
will be those of interest to the communities served by NISO, and
|
|
therefore NISO is committed to act as Maintenance Authority for the
|
|
"info" Registry and to assign a Registry Operator to operate it.
|
|
|
|
NISO, a non-profit association accredited by the American National
|
|
Standards Institute (ANSI), identifies, develops, maintains, and
|
|
publishes technical standards to manage information in the digital
|
|
environment. NISO standards apply technologies to the full range of
|
|
information-related needs, including retrieval, re-purposing,
|
|
storage, metadata, and preservation.
|
|
|
|
Founded in 1939, incorporated as a not-for-profit education
|
|
association in 1983, and assuming its current name the following
|
|
year, NISO draws its support from the communities it serves. The
|
|
leaders of over 70 organizations in the fields of publishing,
|
|
libraries, IT, and media serve as its voting members. Hundreds of
|
|
experts and practitioners serve on NISO committees and as officers of
|
|
the association.
|
|
|
|
NISO has been designated by ANSI to represent US interests to the
|
|
International Organization for Standardization's (ISO) Technical
|
|
Committee 46 on Information and Documentation.
|
|
|
|
The NISO headquarters office is located at 4733 Bethesda Ave.,
|
|
Bethesda, MD 20814, USA. (For further information, see the NISO
|
|
website, <<a href="http://www.niso.org/">http://www.niso.org/</a>>.)
|
|
|
|
<span class="h2"><a class="selflink" id="section-4" href="https://datatracker.ietf.org/doc/html/rfc4452#section-4">4</a>. The "info" URI Scheme</span>
|
|
|
|
<span class="h3"><a class="selflink" id="section-4.1" href="https://datatracker.ietf.org/doc/html/rfc4452#section-4.1">4.1</a>. Definition of "info" URI Syntax</span>
|
|
|
|
The "info" URI syntax presented in this document is conformant with
|
|
the generic URI syntax defined in <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a> [<a href="https://datatracker.ietf.org/doc/html/rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]. This
|
|
specification uses the Augmented Backus-Naur Form (ABNF) notation of
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4234">RFC 4234</a> [<a href="https://datatracker.ietf.org/doc/html/rfc4234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC4234</a>] to define the URI. The following core ABNF
|
|
productions are used by this specification as defined by <a href="https://datatracker.ietf.org/doc/html/rfc4234#appendix-B.1">Appendix B.1
|
|
of RFC 4234</a>: ALPHA, DIGIT, HEXDIG.
|
|
|
|
The "info" URI syntax is presented in two parts. Part A contains
|
|
productions specific to the "info" URI scheme, while Part B contains
|
|
generic productions from <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a> [<a href="https://datatracker.ietf.org/doc/html/rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>], which are repeated here
|
|
both for completeness and for reference. The following set of
|
|
productions (Part A) is specific to the "info" URI scheme:
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 6]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-7"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
; Part A:
|
|
; productions specific to the "info" URI scheme
|
|
|
|
info-URI = info-scheme ":" info-identifier [ "#" fragment ]
|
|
|
|
info-scheme = "info"
|
|
|
|
info-identifier = namespace "/" identifier
|
|
|
|
namespace = scheme
|
|
|
|
identifier = *( pchar / "/" )
|
|
|
|
; Note that "info" URIs containing dot-segments (i.e., segments
|
|
; whose full content consists of "." or "..") MAY NOT be suitable
|
|
; for use with applications that perform dot-segment normalization
|
|
|
|
This next set of productions (Part B) are generic productions
|
|
reproduced from <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a> [<a href="https://datatracker.ietf.org/doc/html/rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]:
|
|
|
|
; Part B:
|
|
; generic productions from <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a> [<a href="https://datatracker.ietf.org/doc/html/rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]
|
|
|
|
scheme = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )
|
|
|
|
pchar = unreserved / pct-encoded / sub-delims / ":" / "@"
|
|
|
|
fragment = *( pchar / "/" / "?" )
|
|
|
|
unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"
|
|
|
|
pct-encoded = "%" HEXDIG HEXDIG
|
|
|
|
sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
|
|
/ "*" / "+" / "," / ";" / "="
|
|
An "info" URI has an "info-identifier" as its scheme-specific part
|
|
and MAY take an optional "fragment" component. An "info-identifier"
|
|
is constructed by appending an "identifier" component to a
|
|
"namespace" component separated by a slash "/" character. The "info"
|
|
URI scheme is supportive of hierarchical processing as indicated by
|
|
the presence of the slash "/" character, although the slash "/"
|
|
character SHOULD NOT be interpreted as a strict hierarchy delimiter.
|
|
|
|
Values for the "namespace" component of the "info" URI are name
|
|
tokens composed of URI scheme characters only (cf. the "scheme"
|
|
production). They identify the public namespace in which the
|
|
(unescaped) value for the "identifier" component originates, and are
|
|
registered in the "info" Registry, which guarantees their uniqueness
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 7]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-8"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
and persistence. Although the "namespace" component is
|
|
case-insensitive, the canonical form is lowercase and documents that
|
|
specify values for the "namespace" component SHOULD do so using
|
|
lowercase letters. An implementation SHOULD accept uppercase letters
|
|
as equivalent to lowercase in "namespace" names, for the sake of
|
|
robustness, but SHOULD only generate lowercase "namespace" names, for
|
|
consistency.
|
|
|
|
Values for the "identifier" component of the "info" URI MAY be viewed
|
|
as being hierarchical strings composed of path segments built from
|
|
path segment characters (cf. the "pchar" production), the segments
|
|
being separated by slash "/" characters, although any semantic
|
|
interpretation of the "/" character as a hierarchy delimiter MUST NOT
|
|
be assumed. In their originating public namespace, the (unescaped)
|
|
values for the "identifier" component identify information assets.
|
|
The values for the "identifier" component MUST be %-escaped as
|
|
required by this syntax. The "identifier" component SHOULD be
|
|
treated as case-sensitive, although the "info" Registry MAY record
|
|
the case-sensitivity of identifiers from particular registered public
|
|
namespaces. The "info" Registry MAY also disclose additional
|
|
normalization rules regarding the treatment of punctuation characters
|
|
and the like.
|
|
|
|
Values for the "fragment" component of the "info" URI are strings
|
|
composed of path segment characters (cf. the "pchar" production) plus
|
|
the slash "/" character and the question mark "?" character. No
|
|
semantic role is assigned to the slash "/" character and the question
|
|
mark "?" character within the "fragment" component. The (unescaped)
|
|
values for the "fragment" component identify secondary information
|
|
assets with respect to the primary information asset, which is
|
|
referenced by the "info-identifier". The values for the "fragment"
|
|
component MUST be %-escaped as required by this syntax. The
|
|
"fragment" component MUST be treated as being case-sensitive.
|
|
|
|
<span class="h3"><a class="selflink" id="section-4.2" href="https://datatracker.ietf.org/doc/html/rfc4452#section-4.2">4.2</a>. Allowed Characters Under the "info" URI Scheme</span>
|
|
|
|
The "info" URI syntax uses the same set of allowed US-ASCII
|
|
characters as specified in <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a> [<a href="https://datatracker.ietf.org/doc/html/rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] for a generic URI. An
|
|
"info" URI string SHOULD be represented as a Unicode [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-UNICODE" title=""The Unicode Standard, Version 4.0.0, defined by: The Unicode Standard, Version 4.0"">UNICODE</a>] string
|
|
and be encoded in UTF-8 [<a href="https://datatracker.ietf.org/doc/html/rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>] form. Reserved characters as well
|
|
as excluded US-ASCII characters and non-US-ASCII characters MUST be
|
|
%-escaped before forming the URI. Details of the %-escape encoding
|
|
can be found in <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a> <a href="https://datatracker.ietf.org/doc/html/rfc3986#section-2.4">[RFC3986], Section 2.4</a>.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 8]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-9"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
<span class="h3"><a class="selflink" id="section-4.3" href="https://datatracker.ietf.org/doc/html/rfc4452#section-4.3">4.3</a>. Examples of "info" URIs</span>
|
|
|
|
Some examples of syntactically valid "info" URIs are given below:
|
|
|
|
a) info:ddc/22/eng//004.678
|
|
|
|
where "ddc" is the "namespace" component for a Dewey Decimal
|
|
Classification [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-DEWEY" title=""Dewey Decimal Classification"">DEWEY</a>] namespace and "22/eng//004.678" is the
|
|
"identifier" component for an identifier of an information asset
|
|
within that namespace.
|
|
|
|
The information asset identified by the identifier "22/eng//004.678"
|
|
in the namespace for (22nd Ed.) English-language Dewey Decimal
|
|
Classifications is the classification
|
|
|
|
"Internet"
|
|
|
|
|
|
b) info:lccn/2002022641
|
|
|
|
where "lccn" is the "namespace" component for a Library of Congress
|
|
Control Number [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-LCCN" title=""Library of Congress Control Number"">LCCN</a>] namespace and "2002022641" is the "identifier"
|
|
component for an identifier of an information asset within that
|
|
namespace.
|
|
|
|
The information asset identified by the identifier "2002022641" in
|
|
the namespace for Library of Congress Control Numbers is the metadata
|
|
record
|
|
|
|
"Newcomer, Eric. Understanding Web services: XML, WSDL,
|
|
SOAP, and UDDI. Boston: Addison-Wesley, 2002."
|
|
|
|
|
|
c) info:sici/0363-0277(19950315)120:5%3C%3E1.0.TX;2-V
|
|
|
|
where "sici" is the "namespace" component for a Serial Item and
|
|
Contribution Identifier [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-SICI" title=""ANSI/NISO Z39.56-1996 (R2002), "">SICI</a>] namespace and
|
|
"0363-0277(19950315)120:5%3C%3E1.0.TX;2-V" is the "identifier"
|
|
component for an identifier of an information asset in that namespace
|
|
in %-escaped form, or in unescaped form
|
|
"0363-0277(19950315)120:5<>1.0.TX;2-V".
|
|
|
|
The information asset identified by the identifier
|
|
"0363-0277(19950315)120:5<>1.0.TX;2-V" in the namespace for Serial
|
|
Item and Contribution Identifiers is the journal issue
|
|
|
|
"Library Journal, Vol. 120, no. 5. March 15, 1995."
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 9]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-10"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
d) <rdf:Description about="info:bibcode/2003Icar..163..263Z"/>
|
|
|
|
where "bibcode" is the "namespace" component for a NASA Astrophysics
|
|
Data System (ADS) Bibcode [<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-BIBCODE" title=""NASA Astrophysics Data System Bibliographic Code"">BIBCODE</a>] namespace and
|
|
"2003Icar..163..263Z" is the "identifier" component for an identifier
|
|
of an information asset within that namespace. This example further
|
|
shows an application of an "info" URI as the subject of a Resource
|
|
Description Framework (RDF) statement.
|
|
|
|
The information asset identified by the identifier
|
|
"2003Icar..163..263Z" in the namespace for NASA ADS Bibcodes is the
|
|
metadata record in the ADS system that describes the journal article
|
|
|
|
"K. Zahnle, P. Schenk, H. Levison and L. Dones, Cratering rates
|
|
in the outer Solar System, Icarus, 163 (2003) pp. 263-289."
|
|
|
|
|
|
e) info:pmid/12376099
|
|
|
|
where "pmid" is the "namespace" component for a PubMed Identifier
|
|
[<a href="https://datatracker.ietf.org/doc/html/rfc4452#ref-PMID" title=""PubMed Overview"">PMID</a>] namespace and "12376099" is the "identifier" component for an
|
|
identifier of an information asset in that namespace.
|
|
|
|
The information asset identified by the identifier "12376099" in the
|
|
namespace for PubMed Identifiers is the metadata record in the PubMed
|
|
database that describes the journal article
|
|
|
|
"Wijesuriya SD, Bristow J, Miller WL. Localization and analysis
|
|
of the principal promoter for human tenascin-X. Genomics. 2002
|
|
Oct;80(4):443-52."
|
|
|
|
<span class="h2"><a class="selflink" id="section-5" href="https://datatracker.ietf.org/doc/html/rfc4452#section-5">5</a>. Normalization and Comparison of "info" URIs</span>
|
|
|
|
In order to facilitate comparison of "info" URIs, a sequence of
|
|
normalization steps SHOULD be applied as detailed below. After
|
|
normalizing the URI strings, comparison of two "info" URIs is then
|
|
applied on a character-by-character basis as prescribed by <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.1">[RFC3986], Section 6.2.1</a>.
|
|
|
|
The following generic normalization steps SHOULD anyway be applied by
|
|
applications processing "info" URIs:
|
|
|
|
a) Normalize the case of the "scheme" component to be
|
|
lowercase
|
|
b) Normalize the case of the "namespace" component to be
|
|
lowercase
|
|
c) Unescape all unreserved %-escaped characters in the
|
|
"namespace" and "identifier" components
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 10]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-11"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
d) Normalize the case of any %-escaped characters in the
|
|
"namespace" and "identifier" components to be
|
|
uppercase
|
|
|
|
Further normalization steps MAY be applied by applications to "info"
|
|
URIs based on rules recorded in the "info" Registry for a registered
|
|
public namespace, but such normalization steps remain outside of the
|
|
scope of the "info" URI definition.
|
|
|
|
Since the "info" URI SHOULD be treated as being case-sensitive, a
|
|
canonical form MAY only be arrived at by consulting the "info"
|
|
Registry for possible information on the case-sensitivity for
|
|
identifiers from a registered public namespace, and any case
|
|
normalization step to apply. The "info" Registry MAY also disclose
|
|
additional normalization rules regarding the treatment of punctuation
|
|
characters and the like.
|
|
|
|
In cases, however, where no single canonical form of the "identifier"
|
|
component exists, it is nevertheless RECOMMENDED that a Namespace
|
|
Authority nominate a preferred form, which SHOULD be used wherever
|
|
possible within an "info" URI so that applications MAY have an
|
|
increased chance of successful comparison of two "info" URIs.
|
|
|
|
Note that "info" URIs containing dot-segments (i.e., segments whose
|
|
full content consists of "." or "..") MAY NOT be suitable for use
|
|
with applications that perform dot-segment normalization.
|
|
|
|
The following unnormalized forms of an "info" URI
|
|
|
|
U1. INFO:PII/S0888-7543(02)96852-7
|
|
U2. info:PII/S0888754302968527
|
|
U3. info:pii/S0888%2D7543%2802%2996852%2D7
|
|
U4. info:pii/s0888-7543(02)96852-7
|
|
|
|
are normalized to the following respective forms
|
|
|
|
N1. info:pii/S0888-7543(02)96852-7
|
|
N2. info:pii/S0888754302968527
|
|
N3. info:pii/S0888-7543(02)96852-7
|
|
N4. info:pii/s0888-7543(02)96852-7
|
|
|
|
The "info" URI definition does not prescribe further normalization
|
|
steps, although applications MAY apply additional normalization steps
|
|
according to any rules recorded in the "info" Registry for a
|
|
registered public namespace.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 11]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-12"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
<span class="h2"><a class="selflink" id="section-6" href="https://datatracker.ietf.org/doc/html/rfc4452#section-6">6</a>. Rationale</span>
|
|
|
|
<span class="h3"><a class="selflink" id="section-6.1" href="https://datatracker.ietf.org/doc/html/rfc4452#section-6.1">6.1</a>. Why Create a New URI Scheme for Identifiers from Public</span>
|
|
<span class="h3"> Namespaces?</span>
|
|
|
|
Under <a href="https://datatracker.ietf.org/doc/html/rfc4395">RFC 4395</a>, "Guidelines and Registration Procedures for New URI
|
|
Schemes" [<a href="https://datatracker.ietf.org/doc/html/rfc4395" title=""Guidelines and Registration Procedures for New URI Schemes"">RFC4395</a>], it is stated in <a href="https://datatracker.ietf.org/doc/html/rfc4452#section-2.1">Section 2.1</a> "Demonstrable, New,
|
|
Long-Lived Utility" that "New URI schemes SHOULD have clear utility
|
|
to the broad Internet community, beyond that available with already
|
|
registered URI schemes". The "info" URI scheme allows identifiers
|
|
within public namespaces, used for the identification of information
|
|
assets, to be referred to within the URI allocation. Once a
|
|
namespace is registered in the "info" Registry, the "info" URI scheme
|
|
enables an information asset with an identifier in that namespace to
|
|
be referenced by means of a URI. As a result, the information asset
|
|
SHALL be considered a resource as defined in <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a> [<a href="https://datatracker.ietf.org/doc/html/rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] and
|
|
SHALL enjoy the same common syntactic, semantic, and shared language
|
|
benefits that the URI presentation confers.
|
|
|
|
<span class="h3"><a class="selflink" id="section-6.2" href="https://datatracker.ietf.org/doc/html/rfc4452#section-6.2">6.2</a>. Why Not Use an Existing URI Scheme for Identifiers from Public</span>
|
|
<span class="h3"> Namespaces?</span>
|
|
|
|
Existing URI schemes are not suitable for employment as the "info"
|
|
URI scheme admits of no global dereference mechanism. While examples
|
|
of resource identifiers minted under other URI schemes MAY not always
|
|
be dereferenceable, nevertheless there is always a common expectation
|
|
that such URIs can be dereferenced by various resolution mechanisms,
|
|
whether they be location-dependent or location-independent resource
|
|
identifiers. The "info" URI scheme applies to a class of resource
|
|
identifiers whose Namespace Authorities MAY or MAY NOT choose to
|
|
disclose service mechanisms. Nevertheless, Namespace Authorities are
|
|
encouraged to disclose in the "info" registration record references
|
|
to any such service mechanisms in order to provide a greater utility
|
|
to network applications.
|
|
|
|
<span class="h3"><a class="selflink" id="section-6.3" href="https://datatracker.ietf.org/doc/html/rfc4452#section-6.3">6.3</a>. Why Not Create a New URN Namespace ID for Identifiers from Public</span>
|
|
<span class="h3"> Namespaces?</span>
|
|
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc2141">RFC 2141</a> [<a href="https://datatracker.ietf.org/doc/html/rfc2141" title=""URN Syntax"">RFC2141</a>] states that "Uniform Resource Names (URNs) are
|
|
intended to serve as persistent, location-independent, resource
|
|
identifiers". The "info" URI scheme, on the other hand, does not
|
|
assert the persistence of the identifiers created under this scheme
|
|
but rather of the public namespaces grandfathered under this scheme.
|
|
It exists primarily to disclose the identity of information assets
|
|
and to facilitate a lightweight registration mechanism for public
|
|
namespaces of identifiers managed according to the policies and
|
|
business models of the Namespace Authorities. The "info" URI scheme
|
|
is neutral with respect to identifier persistence. Moreover, for
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 12]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-13"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
"info" to operate as a URN Network Identifier (NID) would require
|
|
that "info" be constituted as a delegated naming authority. It is
|
|
not clear that a URN NID would be an appropriate choice for naming
|
|
authority delegation.
|
|
|
|
Further, the "info" URI scheme is not globally dereferenceable in
|
|
contrast to the specific recommendation given in <a href="https://datatracker.ietf.org/doc/html/rfc1737">RFC 1737</a>,
|
|
"Functional Requirements for Uniform Resource Names" [<a href="https://datatracker.ietf.org/doc/html/rfc1737" title=""Functional Requirements for Uniform Resource Names"">RFC1737</a>] that
|
|
"It is strongly recommended that there be a mapping between the names
|
|
generated by each naming authority and URLs". Individual Namespace
|
|
Authorities registered in the "info" Registry MAY, however, disclose
|
|
references to service mechanisms and are encouraged to do so.
|
|
|
|
An extra consideration is that the "urn" URI syntax explicitly
|
|
excludes generic URI hierarchy by reserving the slash "/" character.
|
|
An "info" URI, on the other hand, admits of hierarchical processing,
|
|
while remaining neutral with respect to supporting actual hierarchy,
|
|
and thus allows the slash "/" character (as well as more liberally
|
|
allowing the ampersand "&" and tilde "~" characters). It therefore
|
|
represents a lower barrier to entry for Namespace Authorities in
|
|
keeping with its intention of acting as a bridging mechanism to allow
|
|
public namespaces to become part of the URI allocation. In sum, an
|
|
"info" URI is more widely supportive of "human transcribability" as
|
|
discussed in <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a> [<a href="https://datatracker.ietf.org/doc/html/rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] than is a "urn" URI.
|
|
|
|
Additionally, the "urn" URI syntax does not support "fragment"
|
|
components as does the "info" URI syntax for indirect identification
|
|
of secondary resources.
|
|
|
|
<span class="h2"><a class="selflink" id="section-7" href="https://datatracker.ietf.org/doc/html/rfc4452#section-7">7</a>. Security Considerations</span>
|
|
|
|
The "info" URI scheme syntax is subject to the same security
|
|
considerations as the generic URI syntax described in <a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a>
|
|
[<a href="https://datatracker.ietf.org/doc/html/rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>].
|
|
|
|
While some "info" Namespace Authorities MAY choose to disclose
|
|
service mechanisms, any security considerations resulting from the
|
|
execution of such services fall outside the scope of this document.
|
|
It is strongly recommended that the registration record of an "info"
|
|
namespace include any such considerations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 13]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-14"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
<span class="h2"><a class="selflink" id="section-8" href="https://datatracker.ietf.org/doc/html/rfc4452#section-8">8</a>. IANA Considerations</span>
|
|
|
|
The IANA registry for URI schemes
|
|
<<a href="http://www.iana.org/assignments/uri-schemes.html">http://www.iana.org/assignments/uri-schemes.html</a>> SHOULD be updated
|
|
to include an entry for the "info" URI scheme when the "info" URI
|
|
scheme is accepted for publication as an RFC. This entry SHOULD
|
|
contain the following values:
|
|
|
|
Scheme Name: info
|
|
|
|
Description: Information Assets with Identifiers in Public
|
|
Namespaces
|
|
|
|
Reference: <a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a>
|
|
|
|
<span class="h2"><a class="selflink" id="section-9" href="https://datatracker.ietf.org/doc/html/rfc4452#section-9">9</a>. Acknowledgements</span>
|
|
|
|
The authors acknowledge the contributions of Michael Mealling,
|
|
Verisign, and Patrick Hochstenbach, Ghent University.
|
|
|
|
<span class="h2"><a class="selflink" id="section-10" href="https://datatracker.ietf.org/doc/html/rfc4452#section-10">10</a>. References</span>
|
|
|
|
<span class="h3"><a class="selflink" id="section-10.1" href="https://datatracker.ietf.org/doc/html/rfc4452#section-10.1">10.1</a>. Normative References</span>
|
|
|
|
[<a id="ref-RFC1737">RFC1737</a>] Sollins, K. and L. Masinter, "Functional Requirements for
|
|
Uniform Resource Names", <a href="https://datatracker.ietf.org/doc/html/rfc1737">RFC 1737</a>, December 1994.
|
|
|
|
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
|
|
Requirement Levels", <a href="https://datatracker.ietf.org/doc/html/bcp14">BCP 14</a>, <a href="https://datatracker.ietf.org/doc/html/rfc2119">RFC 2119</a>, March 1997.
|
|
|
|
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="https://datatracker.ietf.org/doc/html/rfc2141">RFC 2141</a>, May 1997.
|
|
|
|
[<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of ISO
|
|
10646", STD 63, <a href="https://datatracker.ietf.org/doc/html/rfc3629">RFC 3629</a>, November 2003.
|
|
|
|
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
|
|
Resource Identifier (URI): Generic Syntax", STD 66,
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986</a>, January 2005.
|
|
|
|
[<a id="ref-RFC4234">RFC4234</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
|
|
Specifications: ABNF", <a href="https://datatracker.ietf.org/doc/html/rfc4234">RFC 4234</a>, October 2005.
|
|
|
|
[<a id="ref-RFC4395">RFC4395</a>] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
|
|
Registration Procedures for New URI Schemes", <a href="https://datatracker.ietf.org/doc/html/bcp115">BCP 115</a>, <a href="https://datatracker.ietf.org/doc/html/rfc4395">RFC</a>
|
|
<a href="https://datatracker.ietf.org/doc/html/rfc4395">4395</a>, February 2006.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 14]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-15"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
[<a id="ref-UNICODE">UNICODE</a>] The Unicode Consortium, "The Unicode Standard, Version
|
|
4.0.0, defined by: The Unicode Standard, Version 4.0".
|
|
(Reading, MA, Addison-Wesley, 2003). ISBN 0-321-18578-1.
|
|
|
|
<span class="h3"><a class="selflink" id="section-10.2" href="https://datatracker.ietf.org/doc/html/rfc4452#section-10.2">10.2</a>. Informative References</span>
|
|
|
|
[<a id="ref-BIBCODE">BIBCODE</a>] "NASA Astrophysics Data System Bibliographic Code",
|
|
<<a href="http://adsdoc.harvard.edu/abs_doc/help_pages/data.html">http://adsdoc.harvard.edu/abs_doc/help_pages/data.html</a>>.
|
|
|
|
[<a id="ref-DEWEY">DEWEY</a>] "Dewey Decimal Classification",
|
|
<<a href="http://www.oclc.org/dewey/">http://www.oclc.org/dewey/</a>>.
|
|
|
|
[<a id="ref-LCCN">LCCN</a>] "Library of Congress Control Number",
|
|
<<a href="http://lcweb.loc.gov/marc/lccn_structure.html">http://lcweb.loc.gov/marc/lccn_structure.html</a>>.
|
|
|
|
[<a id="ref-NISO">NISO</a>] "National Information Standards Organization",
|
|
<<a href="http://www.niso.org/">http://www.niso.org/</a>>.
|
|
|
|
[<a id="ref-OCLCNUM">OCLCNUM</a>] "Online Computer Library Center OCLC Control Number",
|
|
<<a href="http://www.oclc.org/bibformats/en/fixedfield/oclc.shtm">http://www.oclc.org/bibformats/en/fixedfield/oclc.shtm</a>>.
|
|
|
|
[<a id="ref-OFI">OFI</a>] "ANSI/NISO Z39.88-2004, "The OpenURL Framework for
|
|
Context-Sensitive Services", ISBN 1-880124-61-0",
|
|
<<a href="http://www.niso.org/standards/resources/Z39_88_2004.pdf">http://www.niso.org/standards/resources/Z39_88_2004.pdf</a>>.
|
|
|
|
[<a id="ref-PMID">PMID</a>] "PubMed Overview", <<a href="http://www.ncbi.nlm.nih.gov/entrez/query/static/overview.html">http://www.ncbi.nlm.nih.gov/entrez/</a>
|
|
<a href="http://www.ncbi.nlm.nih.gov/entrez/query/static/overview.html">query/static/overview.html</a>>.
|
|
|
|
[<a id="ref-SICI">SICI</a>] "ANSI/NISO Z39.56-1996 (R2002), "Serial Item and
|
|
Contribution Identifier (SICI)", ISBN 1-880124-28-9",
|
|
<<a href="http://www.niso.org/standards/resources/Z39-56.pdf">http://www.niso.org/standards/resources/Z39-56.pdf</a>>.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 15]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-16"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
Authors' Addresses
|
|
|
|
Herbert Van de Sompel
|
|
Los Alamos National Laboratory
|
|
Research Library, MS-P362
|
|
PO Box 1663
|
|
Los Alamos, NM 87545-1362
|
|
USA
|
|
|
|
EMail: herbertv@lanl.gov
|
|
|
|
|
|
Tony Hammond
|
|
Nature Publishing Group
|
|
Macmillan House
|
|
4 Crinan Street
|
|
London N1 9XW
|
|
UK
|
|
|
|
EMail: t.hammond@nature.com
|
|
|
|
|
|
Eamonn Neylon
|
|
Manifest Solutions
|
|
Bicester, Oxfordshire OX26 2HX
|
|
UK
|
|
|
|
EMail: eneylon@manifestsolutions.com
|
|
|
|
|
|
Stuart L. Weibel
|
|
OCLC Online Computer Library Center, Inc.
|
|
6565 Frantz Road
|
|
Dublin, OH 43017-3395
|
|
USA
|
|
|
|
EMail: weibel@oclc.org
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<span class="grey">Van de Sompel, et al. Informational [Page 16]</span></pre>
|
|
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-17"></span>
|
|
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc4452">RFC 4452</a> The "info" URI Scheme April 2006</span>
|
|
|
|
|
|
Full Copyright Statement
|
|
|
|
Copyright (C) The Internet Society (2006).
|
|
|
|
This document is subject to the rights, licenses and restrictions
|
|
contained in <a href="https://datatracker.ietf.org/doc/html/bcp78">BCP 78</a>, and except as set forth therein, the authors
|
|
retain all their rights.
|
|
|
|
This document and the information contained herein are provided on an
|
|
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
|
|
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
|
|
ENGINEERING TASK FORCE DISCLAIM 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.
|
|
|
|
Intellectual Property
|
|
|
|
The IETF takes no position regarding the validity or scope of any
|
|
Intellectual Property Rights or other rights that might be claimed to
|
|
pertain to the implementation or use of the technology described in
|
|
this document or the extent to which any license under such rights
|
|
might or might not be available; nor does it represent that it has
|
|
made any independent effort to identify any such rights. Information
|
|
on the procedures with respect to rights in RFC documents can be
|
|
found in <a href="https://datatracker.ietf.org/doc/html/bcp78">BCP 78</a> and <a href="https://datatracker.ietf.org/doc/html/bcp79">BCP 79</a>.
|
|
|
|
Copies of IPR disclosures made to the IETF Secretariat and any
|
|
assurances of licenses to be made available, or the result of an
|
|
attempt made to obtain a general license or permission for the use of
|
|
such proprietary rights by implementers or users of this
|
|
specification can be obtained from the IETF on-line IPR repository at
|
|
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
|
|
|
|
The IETF invites any interested party to bring to its attention any
|
|
copyrights, patents or patent applications, or other proprietary
|
|
rights that may cover technology that may be required to implement
|
|
this standard. Please address the information to the IETF at
|
|
ietf-ipr@ietf.org.
|
|
|
|
Acknowledgement
|
|
|
|
Funding for the RFC Editor function is provided by the IETF
|
|
Administrative Support Activity (IASA).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Van de Sompel, et al. Informational [Page 17]
|
|
</pre>
|
|
</div>
|
|
|
|
</div>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<script>$(".visible-nojs").removeClass("visible-nojs");</script>
|
|
<script>$(".hidden-nojs").removeClass("hidden-nojs");</script>
|
|
|
|
<script type="text/javascript"><!--
|
|
var legend_html = "Colour legend:<br /> \
|
|
<table> \
|
|
<tr><td>Unknown:</td> <td><span class='cplate bgwhite'> </span></td></tr> \
|
|
<tr><td>Draft:</td> <td><span class='cplate bgred'> </span></td></tr> \
|
|
<tr><td>Informational:</td> <td><span class='cplate bgorange'> </span></td></tr> \
|
|
<tr><td>Experimental:</td> <td><span class='cplate bgyellow'> </span></td></tr> \
|
|
<tr><td>Best Common Practice:</td> <td><span class='cplate bgmagenta'> </span></td></tr> \
|
|
<tr><td>Proposed Standard:</td> <td><span class='cplate bgblue'> </span></td></tr> \
|
|
<tr><td>Draft Standard (old designation):</td> <td><span class='cplate bgcyan'> </span></td></tr> \
|
|
<tr><td>Internet Standard:</td> <td><span class='cplate bggreen'> </span></td></tr> \
|
|
<tr><td>Historic:</td> <td><span class='cplate bggrey'> </span></td></tr> \
|
|
<tr><td>Obsolete:</td> <td><span class='cplate bgbrown'> </span></td></tr> \
|
|
</table>";
|
|
function showLegend() {
|
|
var elem = document.getElementById('legend');
|
|
elem.innerHTML = legend_html
|
|
elem.style.visibility='visible';
|
|
}
|
|
function hideLegend() {
|
|
var elem = document.getElementById('legend');
|
|
elem.style.visibility='hidden';
|
|
elem.innerHTML = "";
|
|
}
|
|
// -->
|
|
</script>
|
|
|
|
|
|
|
|
|
|
</body></html> |