Using Serial Item and Contribution Identifiers as Unifirm Resource Names
draft-hakala-sici-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Juna Hakala | ||
| Last updated | 2002-08-07 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document discusses how Serial Item and Contribution Identifiers (SICIs; persistent and unique identifiers for serial issues and contributions such as articles) can be supported within the URN framework and the syntax for URNs defined in RFC 2141 [Moats]. Much of the discussion below is based on the ideas expressed in RFC 2288 [Lynch]. Chapter 5 contains a URN namespace registration request modelled according to the template in RFC 2611 [Daigle et al.].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)