RFC 4374

The application/xv+xml Media Type

📅 published January 2006, from ietf

RFC 4374: The application/xv+xml Media Type 💖

Okay bestie, this one is giving media type registration 🎀

RFC number: 4374
Title: The application/xv+xml Media Type
Author: Gerald McCobb, IBM Corporation
Category: Informational
Date: January 2006
Obsoletes/Updates: the title block lists nothing here, so this doc doesn't obsolete or update any other RFC 💅

Status of This Memo ✨

Okay so this memo is just giving info to the Internet community 🫶 It is not an Internet standard of any kind, and it can be shared with anyone (distribution is unlimited).

Copyright Notice 🌸

Abstract 🦋

This doc is all about registering the MIME sub-type application/xv+xml. The vibe is that it's the media descriptor for XHTML+Voice multimodal language documents 🎙️✨

1. Introduction 💜

So XHTML+Voice is part of the XHTML family of document types, which is defined by XHTML Modularization [4]. It extends XHTML 1.1 [5] with a modularized subset of VoiceXML 2.0 [9], XML Events [7], and a few extensions to both XHTML and VoiceXML 2.0. XHTML 1.1, VoiceXML 2.0, and XML Events are all W3C Recommendations, so they're officially legit 👑

The language integration in XHTML+Voice supports every module defined by XHTML Modularization and adds voice interaction to XHTML elements, which is how you get multimodal apps 🔥 The document type for XHTML+Voice is an XHTML Host language document type that conforms to the spec.

XHTML+Voice 1.2 [8] is maintained by the VoiceXML Forum, and you can find it at <http://www.voicexml.org/specs/multimodal/x+v/12/> 🌈

1.1. application/xv+xml Usage 🧚

The application/xv+xml media type is basically the media descriptor for XHTML+Voice multimodal documents. It tells applications that extra markup can be processed. That markup runs a voice browser component and activates handlers for DOM Level 2 events [6] through XML Events [7] ✨

Also, this media type registration is not intended for e-mail usage. Tea 🍵 Not e-mail 🙅‍♀️

2. IANA Registration 🎀

Here's the registration template, copied word for word so it's accurate 💅

   To: ietf-types@iana.org
   Subject: Registration of MIME media type
            application/xv+xml

   MIME media type name: application

   MIME subtype name: xv+xml

   Required parameters: none

   Optional parameters:

   charset: has the same semantics as the charset parameter of the
   "application/xml" media type specified in [1].

Encoding considerations:
   XHTML+Voice has the same media type encoding considerations
   specified in Section 3.2 of [1].

Security considerations:
   XHTML+Voice is an extension of XHTML and has the same security
   issues as XHTML.  These include interpreting anchors and forms in
   XHTML documents, and scripting languages and other dynamic
   interactive capabilities.  See Section 7 of [2].
   In addition, the scripting language can be accessed by both the
   XHTML and the VoiceXML 2.0 markup embedded in the XHTML+Voice
   document.  See Section 1.3.1.5 of [8].
   XML-Events [7] allows an author to attach a handler to any node in
   the document.  The handler that is activated in response to a
   specified event may be either a voice dialog or a script that can
   be in either the same or an external document.

Interoperability considerations:
   Because XHTML+Voice is built upon W3C standard recommendations, it
   is designed to be interoperable across a wide range of platforms
   and client devices.  Because the extensions to XHTML are
   identified by their namespaces, all browsers that have namespace
   support can run an XHTML+Voice document as an XHTML document
   without voice interaction.

Published specification:
   The latest published version of XHTML+Voice is [8].

Applications which use this media type:
   XHTML+Voice documents are intended to be deployed on the World
   Wide Web and rendered by multimodal browsers that support the
   visual and voice modes of interaction.  Because XHTML+Voice is an
   application of XML, authors can expect XHTML+Voice user agents to
   be conformant XML 1.0 [3] processors.  See section 2 of [2].

Additional information:
   Magic number(s): There is no single string that is always present.
   File extension(s): mxml, xhvml, xvml, xvm
   Macintosh File Type Code(s): TEXT

Person & e-mail address to contact for further information:

   Gerald McCobb
   mccobb@us.ibm.com

Intended usage: LIMITED USE

Author/Change controller: Gerald McCobb

Further information:

3. Fragment Identifiers 🦋

Check Section 3 of [2] for the full scoop. Following [2], fragment identifiers for XHTML+Voice documents point to the element with the matching ID attribute value (see [3], Section 3.3.1) 🎯

XHTML+Voice adds new ID attributes with fragment identifier namespaces that aren't in the same namespace as XHTML, but uniqueness of the ID attribute values is still preserved within the document. See sections 1.3.1 and 5.3 of [8] 🧠

4. Recognizing XHTML+Voice files 🔍

Since XHTML+Voice is XML, an XHTML+Voice document can optionally start with an XML declaration that begins with <?xml, and it can have a DOCTYPE declaration starting with <!DOCTYPE html. XHTML+Voice 1.2 uses this DOCTYPE declaration:

<!DOCTYPE html PUBLIC "-//VoiceXML Forum//DTD XHTML+Voice 1.2//EN"
"http://www.voicexml.org/specs/multimodal/x+v/12/dtd/xhtml+voice12.dtd">

And because XHTML+Voice belongs to the XHTML family, the root element is html, and <html can be found near the top of the document 🌟

5. Security Considerations 🚨

Security considerations for this media type are discussed in the MIME type registration that appears in Section 2. Read that section closely, because it covers scripting, anchors, forms, and handlers that can run voice dialogs or scripts. This is serious business, bestie 😭

6. IANA Considerations 📜

As described in Section 2, this document specifies the registration of a MIME type for XHTML+Voice documents according to [1] 💅

7. Normative References 📚

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

[2]  Baker, M. and P. Stark, "The 'application/xhtml+xml' Media
     Type", RFC 3236, January 2002.

[3]  Bray, T. and others, "Extensible Markup Language (XML) 1.0", W3C
     Recommendation, http://www.w3.org/TR/REC-xml", February 2004.

[4]  Dooley, S. and others, "Modularization of XHTML", W3C
     Recommendation, http://www.w3.org/TR/xhtml-modularization",
     April 2001.

[5]  Altheim, M. and S. McCarron, "XHTML 1.1 - Module-based XHTML",
     W3C Recommendation, http://www.w3.org/TR/xhtml11/, May 2001.

[6]  Pixley, T., "Document Object Model Level 2 Events
     Specification", W3C Recommendation,
     http://www.w3.org/TR/DOM-Level-2-Events/, November 2000.

[7]  Pemberton, S., Raman, T., and S. McCarron, "XML Events - An
     events syntax for XML", W3C Recommendation,
     http://www.w3.org/TR/xml-events/, January 2002.

[8]  Axelsson, J. and others, "XHTML+Voice Profile 1.2",
     http://www.voicexml.org/specs/multimodal/x+v/12/, March 2004.

[9]  McGlashan, S. and others, "Voice Extensible Markup Language
     (VoiceXML)", W3C Recommendation,
     http://www.w3.org/TR/voicexml20/, March 2004.

Author's Address 🏡

Gerald McCobb
International Business Machines Corporation
8051 Congress Ave.
Boca Raton, FL  33487
USA

Phone: +1 561 862 2109
EMail: mccobb@us.ibm.com

Full Copyright Statement ⭐

This document is subject to the rights, licenses and restrictions in BCP 78. Except as set forth there, the authors keep 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.

Intellectual Property 🧾

The IETF doesn't take a position on whether any Intellectual Property Rights or other rights that might be claimed for the technology in this document are valid or in scope. It also doesn't say whether licenses for those rights are available, or whether it has tried to find any of those rights. For the procedures on rights in RFC documents, check BCP 78 and BCP 79 📖

Copies of IPR disclosures sent to the IETF Secretariat, along with any assurances of licenses that will be made available, or the results of attempts to get a general license or permission for implementers or users, can be found in the IETF's online IPR repository at http://www.ietf.org/ipr 🔍

The IETF invites anyone to tell it about any copyrights, patents, patent applications, or other proprietary rights that might cover technology needed to implement this standard. Send that info to the IETF at ietf-ipr@ietf.org 💌

Acknowledgement 🌷

Funding for the RFC Editor function comes from the IETF Administrative Support Activity (IASA) 💖

That's the whole RFC, bestie! 🌈✨

📦 where this page comes from

ietf: rfc4374 2006-01
💖 girlified by claude-haiku-5-5 on 2026-10-16: a language model's rewrite of the original, under its terms