Network Working Group A. Swartz
Internet-Draft AaronSw.com
Expires: September 2, 2004 March 4, 2004
application/rdf+xml Media Type Registration
draft-swartz-rdfcore-rdfxml-mediatype-04
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
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 September 2, 2004.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
This document describes a media type (application/rdf+xml) for use
with the XML serialization of the Resource Description Framework
(RDF). RDF is a language designed to support the Semantic Web, by
facilitating resource description and data exchange on the Web. RDF
provides common structures that can be used for interoperable data
exchange and follows the World Wide Web Consortium (W3C) design
principles of interoperability, evolution, and decentralization.
Discussion of this Document
Please send comments to <mailto:www-rdf-comments@w3.org>. To
subscribe, send a message with the body 'subscribe' to <mailto:www-
Swartz Expires September 2, 2004 [Page 1]
Internet-Draft application/rdf+xml March 2004
rdf-comments-request@w3.org>. The mailing list is publically
archived at <http://lists.w3.org/Archives/Public/www-rdf-comments/>.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. application/rdf+xml Registration . . . . . . . . . . . . . . . . 3
3. Fragment Identifiers . . . . . . . . . . . . . . . . . . . . . . 5
4. Historical Considerations . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5
References . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 7
Swartz Expires September 2, 2004 [Page 2]
Internet-Draft application/rdf+xml March 2004
1. Introduction
RDF is a language designed to support the Semantic Web, by
facilitating resource description and data exchange on the Web. RDF
provides common structures that can be used for interoperable data
exchange and follows the W3C design principles of interoperability,
evolution, and decentralization.
While the RDF data model [2] can be serialized in many ways, the W3C
has defined the RDF/XML syntax [1] to allow RDF to be serialized in
an XML format. The application/rdf+xml media type allows RDF
consumers to identify RDF/XML documents so that they can be processed
properly.
2. application/rdf+xml Registration
This is a media type registration as defined in Multipurpose Internet
Mail Extensions (MIME) Part Four: Registration Procedures [7]
MIME media type name: application
MIME subtype name: rdf+xml
Required parameters: none
Optional parameters: charset
Same as charset parameter of application/xml.
Encoding considerations:
Same as charset parameter of application/xml.
Security considerations:
Security considerations include many of those described in
section 10 of RFC 3023 [5] and more, due to the semantic nature
of RDF. RDF documents may make assertions about anything and
it is expected that future work with Digital Signature and "Web
of Trust" will make it more clear how to build secure RDF
systems.
Interoperability considerations:
It is recommended that RDF documents follow the newer RDF/XML
Syntax Grammar [1] as opposed to the older RDF Model and Syntax
specification [4].
Swartz Expires September 2, 2004 [Page 3]
Internet-Draft application/rdf+xml March 2004
RDF is intended to allow common information to be exchanged
between disparate applications. A basis for building common
understanding is provided by a formal semantics [3], and
applications that use RDF should do so in ways that are
consistent with this.
Published specification: see RDF/XML Syntax Grammar [1] and RDF:
Concepts and Abstract Syntax [2] and the older RDF Model and
Syntax [4]
Applications which use this media type:
RDF is device-, platform-, and vendor-neutral and is supported
by a range of Web user agents and authoring tools.
Additional information:
Magic number(s): none
Although no byte sequences can be counted on to consistently
identify RDF, RDF documents will have the sequence "http://
www.w3.org/1999/02/22-rdf-syntax-ns#" to identify the RDF
namespace. This will usually be towards the top of the
document.
File extension(s): .rdf
Macintosh File Type Code(s): "rdf "
For further information:
Dan Brickley <danbri@w3.org>
RDF Interest Group <www-rdf-interest@w3.org>
More information may be found on the RDF website: <http://
www.w3.org/RDF/>
Intended usage: COMMON
Author/Change controller:
The RDF specification is a work product of the World Wide Web
Consortium. The W3C and the W3C RDF Core Working Group have
change control over the specification.
Swartz Expires September 2, 2004 [Page 4]
Internet-Draft application/rdf+xml March 2004
3. Fragment Identifiers
The rdf:ID and rdf:about attributes can be used to define fragments
in an RDF document.
Section 4.1 of the URI specification [6] notes that the semantics of
a fragment identifier (part of a URI after a "#") is a property of
the data resulting from a retrieval action, and that the format and
interpretation of fragment identifiers is dependent on the media type
of the retrieval result.
In RDF, the thing identified by a URI with fragment identifier does
not necessarily bear any particular relationship to the thing
identified by the URI alone. This differs from some readings of the
URI specification [6], so attention is recommended when creating new
RDF terms which use fragment identifiers.
More details on RDF's treatment of fragment identifiers can be found
in the section "Fragment Identifiers" of the RDF Concepts document
[2].
4. Historical Considerations
This media type was reserved in RFC 3023 [5], saying:
RDF documents identified using this MIME type are XML documents
whose content describes metadata, as defined by [RDF]. As a
format based on XML, RDF documents SHOULD use the '+xml' suffix
convention in their MIME content-type identifier. However, no
content type has yet been registered for RDF and so this media
type should not be used until such registration has been
completed.
5. IANA Considerations
This document calls for registration of a new MIME content-type,
according to the registration template in section 2.
6. Acknowledgements
Thanks to Dan Connolly for writing the first version of this draft
[9], to Andy Powell for reminding us we needed one, to Marshall Rose
for his xml2rfc [10] converter, and to Graham Klyne, Jan Grant, and
Dave Beckett for their helpful comments on early versions of this
document.
References
Swartz Expires September 2, 2004 [Page 5]
Internet-Draft application/rdf+xml March 2004
[1] Beckett, D., "RDF/XML Syntax Specification (Revised)", W3C rdf-
syntax-grammar, February 2004, <http://www.w3.org/TR/2004/REC-
rdf-syntax-grammar-20040210/>.
[2] Klyne, G. and J. Carroll, "Resource Description Framework (RDF):
Concepts and Abstract Syntax", W3C rdf-concepts, February 2004,
<http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/>.
[3] Hayes, P., "RDF Model Theory", W3C rdf-mt, February 2004,
<http://www.w3.org/TR/2004/REC-rdf-mt-20040210/>.
[4] Lassila, O. and R. Swick, "Resource Description Framework (RDF)
Model and Syntax Specification", W3C REC-rdf-syntax, February
1999, <http://www.w3.org/TR/REC-rdf-syntax>.
[5] Murata, M., St.Laurent, S. and D. Kohn, "XML Media Types", RFC
3023, January 2001.
[6] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[7] Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet
Mail Extensions (MIME) Part Four: Registration Procedures", BCP
13, RFC 2048, November 1996.
[8] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[9] Connolly, D., "A media type for Resource Description Framework
(RDF)", March 2001, <http://www.w3.org/2001/03mr/rdf_mt>.
[10] <http://xml.resource.org/>
Author's Address
Aaron Swartz
AaronSw.com
349 Marshman
Highland Park, IL 60035
USA
Phone: +1 847 432 8857
EMail: me@aaronsw.com
URI: http://www.aaronsw.com/
Swartz Expires September 2, 2004 [Page 6]
Internet-Draft application/rdf+xml March 2004
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Swartz Expires September 2, 2004 [Page 7]
