W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > March 2002

Last Call: draft-w3c-rdfcore-rdfxml-mediatype-00 ready to submit?

From: Aaron Swartz <me@aaronsw.com>
Date: Tue, 26 Mar 2002 11:31:59 -0600
To: Brian McBride <bwm@hplb.hpl.hp.com>
CC: RDF Core <w3c-rdfcore-wg@w3.org>
Message-ID: <B8C60CAF.2CB1C%me@aaronsw.com>
Hi all,

Since I haven't gotten any comments the past few days, I was wondering if it
was alright to submit my most recent draft-draft of the media type
registration. It'll be published as an IETF Internet-Draft, essentailly an
IETF work-in-progress working draft.

Brian, since I'd like to label it as coming from the WG, what process should
I go thru. Do we have to sign off on it at a telecon or can I just send it

The text copy of the draft is below. The latest copy is always available at:

 - Aaron

Network Working Group                                          A. Swartz
Internet-Draft                                               AaronSw.com
Expires: September 24, 2002                               March 26, 2002

              application/rdf+xml Media Type Registration

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-

   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://

   The list of Internet-Draft Shadow Directories can be accessed at

   This Internet-Draft will expire on September 24, 2002.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.


   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 W3C design principles of interoperability,
   evolution, and decentralization.

Swartz                 Expires September 24, 2002               [Page 1]

Internet-Draft             application/rdf+xml                March 2002

Table of Contents

   1. Discussion of this Document  . . . . . . . . . . . . . . . . . . 3
   2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3. application/rdf+xml Registration . . . . . . . . . . . . . . . . 3
   4. Fragment Identifiers . . . . . . . . . . . . . . . . . . . . . . 5
   5. Historical Considerations  . . . . . . . . . . . . . . . . . . . 5
   6. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . . 5
   7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5
      References . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
      Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
      Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 7

Swartz                 Expires September 24, 2002               [Page 2]

Internet-Draft             application/rdf+xml                March 2002

1. 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-
   rdf-comments-request@w3.org>.  The mailing list is publically
   archived at <http://lists.w3.org/Archives/Public/www-rdf-comments/>.

2. 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

3. application/rdf+xml Registration

   This is a media type registration as defined in Multipurpose Internet
   Mail Extensions (MIME) Part Four: Registration Procedures [6]

      MIME media type name: application

      MIME subtype name: rdf+xml

      Required parameters: none

      Optional parameters: charset

         Same as charset parameter of application/xml as specified in
         RFC 3023 [4].

      Encoding considerations:

         Same as charset parameter of application/xml as specified in
         RFC 3023 [4].

      Security considerations:

         Security considerations include many of those described in
         section 10 of RFC 3023 [4] 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

Swartz                 Expires September 24, 2002               [Page 3]

Internet-Draft             application/rdf+xml                March 2002

         of Trust" will make it more clear how to build secure RDF

      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 [3].

      Published specification: see RDF/XML Syntax Grammar [1] and RDF
      Model Theory [2] (working drafts as of 2002-03) and the older RDF
      Model and Syntax [3]

      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

         File extension(s): .rdf

         Macintosh File Type Code(s): "TEXT"

      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://

      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 24, 2002               [Page 4]

Internet-Draft             application/rdf+xml                March 2002

4. Fragment Identifiers

   Section 4.1 of the URI specification [5] 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.

   However, in RDF, the thing identified by a URI with fragment
   identifier does not bear any particular relationship to the thing
   identified by the URI alone.  This differs from some readings of the
   URI specification [5], so attention is recommended when creating new
   RDF terms which use fragment identifiers.

   The rdf:ID and rdf:about attributes can be used to define fragments
   in an RDF document.

5. Historical Considerations

   This media type was reserved in RFC 3023 [4], 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

6. IANA Considerations

   This document calls for registration of a new MIME content-type,
   according to the registration template in section 2.

7. Acknowledgements

   Thanks to Dan Connolly for writing the first version of this draft
   [8], to Andy Powell for reminding us we needed one, to Marshall Rose
   for his xml2rfc [9] converter, and to Graham Klyne, Jan Grant and xxx
   for their helpful comments on early versions of this document.


   [1]  Beckett, D., "RDF/XML Syntax Specification (Revised)", W3C rdf-
        syntax-grammar, March 2002, <http://www.w3.org/TR/rdf-syntax-

Swartz                 Expires September 24, 2002               [Page 5]

Internet-Draft             application/rdf+xml                March 2002

   [2]  Hayes, P., "RDF Model Theory", W3C rdf-mt, February 2002,

   [3]  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>.

   [4]  Murata, M., St.Laurent, S. and D. Kohn, "XML Media Types", RFC
        3023, January 2001.

   [5]  Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
        Identifiers (URI): Generic Syntax", RFC 2396, August 1998.

   [6]  Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet
        Mail Extensions (MIME) Part Four: Registration Procedures", BCP
        13, RFC 2048, November 1996.

   [7]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [8]  Connolly, D., "A media type for Resource Description Framework
        (RDF)", March 2001, <http://www.w3.org/2001/03mr/rdf_mt>.

   [9]  <http://xml.resource.org/>

Author's Address

   Aaron Swartz
   349 Marshman
   Highland Park, IL  60035

   Phone: +1 847 432 8857
   EMail: me@aaronsw.com
   URI:   http://www.aaronsw.com/

Swartz                 Expires September 24, 2002               [Page 6]

Internet-Draft             application/rdf+xml                March 2002

Full Copyright Statement

   Copyright (C) The Internet Society (2002).  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

   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


   Funding for the RFC Editor function is currently provided by the
   Internet Society.

Swartz                 Expires September 24, 2002               [Page 7]
Received on Tuesday, 26 March 2002 12:32:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:24:11 UTC