idnits 2.17.1
draft-mccobb-xv-media-type-00.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** It looks like you're using RFC 3978 boilerplate. You should update this
to the boilerplate described in the IETF Trust License Policy document
(see https://trustee.ietf.org/license-info), which is required now.
-- Found old boilerplate from RFC 3978, Section 5.1 on line 14.
-- Found old boilerplate from RFC 3978, Section 5.5 on line 275.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 252.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 259.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 265.
** This document has an original RFC 3978 Section 5.4 Copyright Line,
instead of the newer IETF Trust Copyright according to RFC 4748.
** This document has an original RFC 3978 Section 5.5 Disclaimer, instead
of the newer disclaimer which includes the IETF Trust according to RFC
4748.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
== No 'Intended status' indicated for this document; assuming Proposed
Standard
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
** There is 1 instance of too long lines in the document, the longest one
being 3 characters in excess of 72.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the RFC 3978 Section 5.4 Copyright Line does not
match the current year
== The document doesn't use any RFC 2119 keywords, yet seems to have RFC
2119 boilerplate text.
-- The document seems to lack a disclaimer for pre-RFC5378 work, but may
have content which was first submitted before 10 November 2008. If you
have contacted all the original authors and they are all willing to grant
the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
this comment. If not, you may need to add the pre-RFC5378 disclaimer.
(See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- The document date (July 26, 2005) is 6842 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
== Unused Reference: '2' is defined on line 197, but no explicit reference
was found in the text
== Unused Reference: '8' is defined on line 217, but no explicit reference
was found in the text
** Obsolete normative reference: RFC 2396 (ref. '2') (Obsoleted by RFC 3986)
** Obsolete normative reference: RFC 3023 (ref. '3') (Obsoleted by RFC 7303)
** Downref: Normative reference to an Informational RFC: RFC 3236 (ref. '4')
-- Possible downref: Non-RFC (?) normative reference: ref. '5'
-- Possible downref: Non-RFC (?) normative reference: ref. '6'
-- Possible downref: Non-RFC (?) normative reference: ref. '7'
-- Possible downref: Non-RFC (?) normative reference: ref. '8'
-- Possible downref: Non-RFC (?) normative reference: ref. '9'
-- Possible downref: Non-RFC (?) normative reference: ref. '10'
-- Possible downref: Non-RFC (?) normative reference: ref. '11'
Summary: 7 errors (**), 0 flaws (~~), 5 warnings (==), 14 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 Network Working Group G. McCobb
3 Internet-Draft IBM Corporation
4 Expires: January 27, 2006 July 26, 2005
6 XHTML+Voice - application/xv+xml
7 draft-mccobb-xv-media-type-00
9 Status of this Memo
11 By submitting this Internet-Draft, each author represents that any
12 applicable patent or other IPR claims of which he or she is aware
13 have been or will be disclosed, and any of which he or she becomes
14 aware will be disclosed, in accordance with Section 6 of BCP 79.
16 Internet-Drafts are working documents of the Internet Engineering
17 Task Force (IETF), its areas, and its working groups. Note that
18 other groups may also distribute working documents as Internet-
19 Drafts.
21 Internet-Drafts are draft documents valid for a maximum of six months
22 and may be updated, replaced, or obsoleted by other documents at any
23 time. It is inappropriate to use Internet-Drafts as reference
24 material or to cite them other than as "work in progress."
26 The list of current Internet-Drafts can be accessed at
27 http://www.ietf.org/ietf/1id-abstracts.txt.
29 The list of Internet-Draft Shadow Directories can be accessed at
30 http://www.ietf.org/shadow.html.
32 This Internet-Draft will expire on January 27, 2006.
34 Copyright Notice
36 Copyright (C) The Internet Society (2005).
38 Abstract
40 This document describes the registration of the MIME sub-type
41 application/xv+xml. This sub-type is intended for use as a media
42 descriptor for XHTML+Voice multimodal language documents. The XHTML+
43 Voice 1.2 language specification is maintained by the VoiceXML Forum
44 at .
46 1. Conventions used in this document
48 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
49 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
50 document are to be interpreted as described in BCP 14, RFC 2119 [1].
52 2. Introduction
54 XHTML+Voice is a member of the XHTML family of document types, as
55 specified by XHTML Modularization [6]. XHTML+Voice extends XHTML 1.1
56 [7] with a modularized subset of VoiceXML 2.0 [11], XML Events [9],
57 and a few extensions to both XHTML and VoiceXML 2.0. XHTML 1.1,
58 VoiceXML 2.0 and XML Events are W3C Recommendations.
60 The language integration defined by XHTML+Voice supports all modules
61 defined by XHTML Modularization, and adds voice interaction to XHTML
62 elements to enable multimodal applications. The defined document
63 type for XHTML+Voice is XHTML Host language document type conformant.
65 XHTML+Voice 1.2 [10] is maintained by the VoiceXML Forum, at URI
66 location .
68 2.1 application/xv+xml Usage
70 The application/xv+xml media type is intended to be a media
71 descriptor for XHTML+Voice multimodal documents. It is used to
72 inform applications that additional markup for running a voice
73 browser component and activating handlers for DOM Level 2 events via
74 XML Events [9] can be processed.
76 This media type registration is not intended for e-mail usage.
78 3. IANA Registration
80 To: ietf-types@iana.org
81 Subject: Registration of MIME media type
82 application/xv+xml
84 MIME media type name: application
86 MIME subtype name: xv+xml
88 Required parameters: none
90 Optional parameters:
92 charset: has the same semantics as the charset parameter of the
93 "application/xml" media type specified in [3].
95 Encoding considerations:
97 XHTML+Voice has the same media type encoding considerations
98 specified in section 3.2 of [3].
100 Security considerations:
102 XHTML+Voice is an extension of XHTML and has the same security
103 issues as XHTML. These include interpreting anchors and forms in
104 XHTML documents, and scripting languages and other dynamic
105 interactive capabilities. See section 7 of [4].
107 In addition, the scripting language can be accessed by both the
108 XHTML and the VoiceXML 2.0 markup embedded in the XHTML+Voice
109 document. See section 1.3.1.5 of [10].
111 XML-Events [9] allows an author to attach a handler to any node in
112 the document. The handler that is activated in response to a
113 specified event may be either a voice dialog or a script that can
114 be either in the same or an external document.
116 Interoperability considerations:
118 Because XHTML+Voice is built upon W3C standard recommendations, it
119 is designed to be interoperable across a wide range of platforms
120 and client devices. Because the extensions to XHTML are
121 identified by their namespaces, all browsers that have namespace
122 support can run an XHTML+Voice document as an XHTML document
123 without voice interaction.
125 Published specification:
127 The latest published version of XHTML+Voice is [10].
129 Applications which use this media type:
131 XHTML+Voice documents are intended to be deployed on the World
132 Wide Web and rendered by multimodal browsers that support the
133 visual and voice modes of interaction. Because XHTML+Voice is an
134 application of XML, authors can expect XHTML+Voice user agents to
135 be conformant XML 1.0 [5] processors. See section 2 of [4].
137 Additional information:
139 Magic number(s): There is no single string that is always
140 present.
142 File extension(s): mxml, xhvml, xvml, xvm
144 Macintosh File Type Code(s): TEXT
146 Person & e-mail address to contact for further information:
148 Gerald McCobb
149 mccobb@us.ibm.com
151 Intended usage: LIMITED USE
153 Author/Change controller: Gerald McCobb
155 Further information:
157 4. Fragment Identifiers
159 See section 3 of [4]. Following [4], fragment identifiers for XHTML+
160 Voice documents designate the element with the corresponding ID
161 attribute value (see [5] section 3.3.1).
163 While XHTML+Voice adds new ID attributes with fragment identifier
164 namespaces that are not in the same namespace as XHTML, uniqueness of
165 the ID attribute values is preserved within the document. See
166 sections 1.3.1 and 5.3 of [10].
168 5. Recognizing XHTML+Voice files
170 Because XHTML+Voice is XML, an XHTML+Voice document [optionally]
171 starts with an XML declaration which begins with "
178 Because XHTML+Voice is in the XHTML family of languages, the root
179 element of an XHTML+Voice document is 'html' and '