Internet DRAFT - draft-brown-paradisec-namespace
draft-brown-paradisec-namespace
Internet-Draft L. Brown
Australian National University.
The Paradisec URN Namespace
Document: draft-brown-paradisec-namespace-00.txt 20th May 2005
Expires: November 2005
Comments
Comments are solicited and should be sent to lpb900@anusf.anu.edu.au
Status of this Memo
By submitting this Internet-Draft, each author represents
that any applicable patent or other IPR claims of which he
or she is aware have been or will be disclosed, and any of
which he or she becomes aware will be disclosed, in
accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note
that other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at
any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document describes a Uniform Resource Name (URN) namespace for the
identification of resources in the Pacific And Regional Archive for
Digital Sources in Endangered Cultures (PARADISEC) archive. This
namespace will provide persistent means of accessing the archives
contents allowing for reliable citation.
1. Introduction and Community Considerations
PARADISEC is a partnership between four major Australian universities
which exists to ensure the long term survival of languages and
cultures that may have otherwise been forgotten by history. With an
increasingly large amount of research papers being produced citing
information within the PARADISEC archive it is important that they
have an identifier scheme which encourages the persistence of these
citations and therefore the communities ongoing ability to access them.
The PARADISEC URN namespace is intended as a means of providing online
resource access to linguists, students and other interested individuals
in a persistent manner.
2. Specification Template
Namespace ID:
"paradisec" requested.
Registration Information:
registration version: 1
registration date: 2005-05-01
Declared registrant of the namespace:
Luke Brown
ANU Supercomputing Facility
Building 56, Australian National University
ACTON, ACT, Australia, 0200
Email: lpb900@anusf.anu.edu.au
Declaration of syntactic structure:
The Pacific And Regional Archive for Digital Sources in Endangered
Cultures (PARADISEC) Namespace Specific String (NSS) conforms to the
URN Syntax specification [1] and takes the form:
URN:PARADISEC:<Collection>:<Item>:<File>
The PARADISEC NSS adheres to the following ABNF [3] definition:
NSS = Collection / Item / File
Collection = DIGIT / ALPHA / reserved
Item = DIGIT / ALPHA / reserved
File = DIGIT / ALPHA / reserved
reserved = "/" / "." / "-" / ":"
Relevant ancillary documentation:
Further information on the PARADISEC project can be located at
http://www.paradisec.org.au/
Identifier uniqueness considerations:
The PARADISEC curators assign unique identifiers to all resources
which are added to the archive.
Identifier persistence considerations:
PARADISEC identifiers are never reassigned and location independent
to facilitate persistence.
Process of identifier assignment:
Identifiers are assigned by PARADISEC curators upon submission of
materials into the PARADISEC archive by linguists.
Process for identifier resolution:
Resolution of PARADISEC URNs will be achieved through an extension
of the DDDS [2] approach. This extension allows for per-resource
resolution of URNs using the DNS.
Rules for Lexical Equivalence:
PARADISEC URNs are not case sensitive.
Conformance with URN Syntax:
The PARADISEC syntax extends the invalid character set in [1]
further prohibiting use of the following: "!", "@", "#", "$",
"%", "^", "&", "*", "(", ")", "+", "=", "[", "]", "{", "}",
"|", "\", ";", "'", """, "<", ">", "_" and "?"
Validation mechanism:
None specified outside of the data ingestion procedure.
Scope:
Global.
3. Security Considerations
No new security considerations are presented.
4. IANA Considerations
This document includes a URN Namespace registration request
to be entered into the IANA registry for URN NIDs.
5. References:
5.1 Normative References
[1] Moats, R., "URN Syntax", RFC 2141, May 1997.
[2] Mealling, M, "Dynamic Delegation Discovery System
(DDDS)", RFC 3401, October 2002
5.2 Informative References
[3] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
6. Author's Address
Luke Brown
ANU Supercomputing Facility
Building 56, Australian National University
ACTON, ACT, Australia, 0200
Email: lpb900@anusf.anu.edu.au
7. Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, 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.
Disclaimer of validity:
"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 BCP 78 and BCP 79.
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 http://www.ietf.org/ipr.
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.
Internet-Drafts Boilerplate
"Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Expires: November 2005.
