[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

XML media types

• From: Jon.Bosak@e... (Jon Bosak)
• To: xml-dev@i..., xml-l@l...
• Date: Fri, 7 Aug 1998 15:58:45 -0700

Following is the body of a message from Jim Whitehead to the W3C XML
SIG.  Please do not reply to this message or attribute its authorship
to me.  -- Jon

========================================================================

 FYI, the IETF has issued the document for XML media types registration as
 Internet Informational Request for Comments 2376, and IANA has added
 text/xml and application/xml to the list of registered media types
 maintained at:

 ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/

 So, text/xml and application/xml are now official Internet media types.

 The RFC itself can be retrieved from:

 ftp://ftp.isi.edu/in-notes/rfc2376.txt

 Since this document has significant discussion on i18n and security issues,
 perhaps a link to it from the W3C's (and other third-party XML resource
 pages) XML pages would be helpful in achieving compliance with this
 document.

 - Jim

 Here is the forwarded IETF announcement message:

 A new Request for Comments is now available in online RFC libraries.


       RFC 2376:

       Title:	    XML Media Types
	 Author(s):  E. Whitehead, M. Murata
	 Status:     Informational
	 Date:       July 1998
       Mailbox:    ejw@i..., murata@f...
	 Pages:      15
       Characters: 32143
       Updates/Obsoletes/See Also: None


       URL:        ftp://ftp.isi.edu/in-notes/rfc2376.txt


 This document proposes two new media subtypes, text/xml and
 application/xml, for use in exchanging network entities which are
 conforming Extensible Markup Language (XML). XML entities are
 currently exchanged via the HyperText Transfer Protocol on the World
 Wide Web, are an integral part of the WebDAV protocol for remote web
 authoring, and are expected to have utility in many domains.

 This memo provides information for the Internet community.  It does
 not specify an Internet standard of any kind.  Distribution of this
 memo is unlimited.

 This announcement is sent to the IETF list and the RFC-DIST list.
 Requests to be added to or deleted from the IETF distribution list
 should be sent to IETF-REQUEST@I....  Requests to be
 added to or deleted from the RFC-DIST distribution list should
 be sent to RFC-DIST-REQUEST@R....

 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
 an EMAIL message to rfc-info@R... with the message body
 help: ways_to_get_rfcs.  For example:

	 To: rfc-info@R...
	 Subject: getting rfcs

	 help: ways_to_get_rfcs

 Requests for special distribution should be addressed to either the
 author of the RFC in question, or to RFC-Manager@R....  Unless
 specifically noted otherwise on the RFC itself, all RFCs are for
 unlimited distribution.echo
 Submissions for Requests for Comments should be sent to
 RFC-EDITOR@R....  Please consult RFC 2223, Instructions to RFC
 Authors, for further information.


 Joyce K. Reynolds and Alegre Ramos
 USC/Information Sciences Institute

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Prev by Date: Paris XML98: Dealing with the Electronic Patient Record variability: Object Oriented XML
• Next by Date: LISTRIVIA (was RE: unsubscribe)
• Previous by thread: Paris XML98: Dealing with the Electronic Patient Record variability: Object Oriented XML
• Next by thread: Offtopic was.Re: Namespaces and XML validation
• Index(es):
  • Date
  • Thread