As I've been going through the effort of defining a number of Atom
extensions, I've consistently come back to the thought that it
would be interesting to explore the creation of a "Common
Extensions Namespace" under which multiple standardized extensions
can be grouped. I've written an initial draft of the concept but
before I submit it as an Internet Draft, I'd like to get some
feedback from the group. Please review the attached and let me
know what you think.
- James
Network Working Group J.
Snell
Internet-Draft September
2005
Expires: March 5, 2006
Atom Common Extensions Namespace
draft-snell-atompub-ace-00.txt
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.
This Internet-Draft will expire on March 5, 2006.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document introduces a common namespace for standardized
extensions to the Atom 1.0 Syndication Format.
Snell Expires March 5, 2006
[Page 1]
Internet-Draft A.C.E. September
2005
Table of Contents
1.
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Notational
Conventions . . . . . . . . . . . . . . . . . . . . 3
3. The Atom Common Extensions
Namespace . . . . . . . . . . . . . 3
4. Registry of Atom Common
Extensions . . . . . . . . . . . . . . 3
5. Security
Considerations . . . . . . . . . . . . . . . . . . . 4
6. IANA
Considerations . . . . . . . . . . . . . . . . . . . . . 4
7.
References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Author's
Address . . . . . . . . . . . . . . . . . . . . . . . 4
A.
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
Intellectual Property and Copyright
Statements . . . . . . . . 5
Snell Expires March 5, 2006
[Page 2]
Internet-Draft A.C.E. September
2005
1. Introduction
The Atom Common Extensions Namespace is a single XML Namespace with
which standardized Atom 1.0 extensions MAY be associated. This
document defines the common namespace and creates an IANA
Registry of
Atom Common Extensions.
2. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this
document are to be interpreted as described in BCP 14,
[RFC2119], as
scoped to those conformance targets.
3. The Atom Common Extensions Namespace
The Atom Common Extensions Namespace is an expansion of the Atom
1.0
Syndication Format XML Namespace. XML elements and attributes
defined as Atom 1.0 Extensions that are standardized in
accordance to
the process specified in "Section 4: Registry of Atom Common
Extensions" MAY use the Atom Common Extensions Namespace as an
alternative to defining their own extension specific XML
namespaces.
The Atom Common Extensions Namespace
"http://www.w3.org/2005/Atom/ace";
4. Registry of Atom Common Extensions
This specification defines a Registry of Atom Common Extensions
maintained by IANA. The members of the Registry consist of Atom
1.0
Extensions that define XML elements and attributes falling under
the
the Atom Common Extensions Namespace. New assignments are
subject to
IESG approval as outlined in [RFC2334]. Requests should be made by
email to IANA, which will then forward the request to the IESG
requesting approval. The request should use the following
template:
o Name: (A unique informal name by which the extension can be
referred.)
o Description:
o Elements and Attributes: (definitions for each of the XML
elements
and attributes to be associated with the Atom Common Extensions
Namespace)
o Security Considerations:
Extension elements and attributes introduced by new assignments to
the registry MUST be uniquely named within the Atom Common
Extensions
Namespace and MUST NOT duplicate the function and purpose of other
elements and attributes specified by other extensions in the
Snell Expires March 5, 2006
[Page 3]
Internet-Draft A.C.E. September
2005
registry.
5. Security Considerations
There are no security considerations introduced by this
specification.
6. IANA Considerations
This specification creates a Registry of Atom Common Extensions as
described in section 4.
7. References
[I-D.ietf-atompub-format]
Sayre, R. and M. Nottingham, "The Atom Syndication
Format", draft-ietf-atompub-format-11 (work in
progress),
August 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2334] Luciani, J., Armitage, G., Halpern, J., and N.
Doraswamy,
"Server Cache Synchronization Protocol (SCSP)", RFC
2334,
April 1998.
[W3C.REC-xml-infoset-20040204]
Tobin, R. and J. Cowan, "XML Information Set (Second
Edition)", W3C REC REC-xml-infoset-20040204,
February 2004.
[W3C.REC-xml-names-19990114]
Hollander, D., Bray, T., and A. Layman, "Namespaces in
XML", W3C REC REC-xml-names-19990114, January 1999.
Author's Address
James M Snell
Phone:
Email: [EMAIL PROTECTED]
URI: http://snellspace.com
Appendix A. Acknowledgements
TBD
Snell Expires March 5, 2006
[Page 4]
Internet-Draft A.C.E. September
2005
Intellectual Property Statement
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
[EMAIL PROTECTED]
Disclaimer of Validity
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.
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.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Snell Expires March 5, 2006
[Page 5]
