idnits 2.17.1
draft-mccobb-xplusv-media-type-04.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 13.
-- Found old boilerplate from RFC 3978, Section 5.5 on line 253.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 264.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 271.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 277.
** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line
245), which is fine, but *also* found old RFC 2026, Section 10.4C,
paragraph 1 text on line 33.
** 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 lines with control characters in the document.
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 (June 10, 2005) is 6893 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: 'RFC2396' is defined on line 192, but no explicit
reference was found in the text
** Obsolete normative reference: RFC 2396 (Obsoleted by RFC 3986)
** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303)
** Downref: Normative reference to an Informational RFC: RFC 3236
-- Possible downref: Non-RFC (?) normative reference: ref. 'XML'
-- Possible downref: Non-RFC (?) normative reference: ref. 'XHTMLMOD'
-- Possible downref: Non-RFC (?) normative reference: ref. 'XHTML11'
-- Possible downref: Non-RFC (?) normative reference: ref. 'DOM2EV'
-- Possible downref: Non-RFC (?) normative reference: ref. 'XMLEVNTS'
-- Possible downref: Non-RFC (?) normative reference: ref. 'XPLUSV12'
-- Possible downref: Non-RFC (?) normative reference: ref. 'VXML20'
Summary: 8 errors (**), 0 flaws (~~), 4 warnings (==), 14 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
1 Network Working Group G. McCobb
2 Internet-Draft IBM Corporation
3 Expires: Dec. 10, 2005 June 10, 2005
5 XHTML+Voice - application/xhtml-voice+xml
6 draft-mccobb-xplusv-media-type-04
8 Status of this Memo
10 By submitting this Internet-Draft, each author represents that any
11 applicable patent or other IPR claims of which he or she is aware
12 have been or will be disclosed, and any of which he or she becomes
13 aware will be disclosed, in accordance with Section 6 of BCP 79.
15 Internet-Drafts are working documents of the Internet Engineering
16 Task Force (IETF), its areas, and its working groups. Note that
17 other groups may also distribute working documents as
18 Internet-Drafts.
20 Internet-Drafts are draft documents valid for a maximum of six
21 months and may be updated, replaced, or obsoleted by other documents
22 at any time. It is inappropriate to use Internet-Drafts as
23 reference material or to cite them other than as "work in progress."
25 The list of current Internet-Drafts can be accessed at
26 http://www.ietf.org/ietf/1id-abstracts.txt.
28 The list of Internet-Draft Shadow Directories can be accessed at
29 http://www.ietf.org/shadow.html.
31 Copyright Notice
33 Copyright (C) The Internet Society (2005). All Rights Reserved.
35 Abstract
37 This document describes the registration of the MIME sub-type
38 application/xhtml-voice+xml. This sub-type is intended for use as a
39 media descriptor for XHTML+Voice multimodal language documents. The
40 XHTML+Voice 1.2 language specification is maintained by the VoiceXML
41 Forum at .
43 1. Conventions used in this document
45 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
46 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
47 document are to be interpreted as described in BCP 14, RFC 2119
48 [RFC2119].
50 2. Introduction
52 XHTML+Voice is a member of the XHTML family of document types, as
53 specified by XHTML Modularization [XHTMLMOD]. XHTML+Voice extends
54 XHTML 1.1 [XHTML11] with a modularized subset of VoiceXML 2.0
55 [VXML20], XML Events [XMLEVNTS], and a few extensions to both XHTML
56 and VoiceXML 2.0. XHTML 1.1, VoiceXML 2.0 and XML Events are W3C
57 Recommendations.
59 The language integration defined by XHTML+Voice supports all modules
60 defined by XHTML Modularization, and adds voice interaction to XHTML
61 elements to enable multimodal applications. The defined document
62 type for XHTML+Voice is XHTML Host language document type conformant.
64 XHTML+Voice 1.2 [XPLUSV12] is maintained by the VoiceXML Forum, at
65 URI location .
67 2.1 application/xhtml-voice+xml Usage
69 The application/xhtml-voice+xml media type is intended to be a media
70 descriptor for XHTML+Voice multimodal documents. Multimodal browsers
71 have special processing requirements for XHTML+Voice documents, such
72 as running a voice browser component, and support for the DOM Level
73 2 Event Model [DOM2EV] and XML Events [XMLEVNTS].
75 This media type registration is not intended for e-mail usage.
77 3. IANA Registration
79 To: ietf-types@iana.org
80 Subject: Registration of Standard MIME media type
81 application/xhtml-voice+xml
83 MIME media type name: application
85 MIME subtype name: xhtml-voice+xml
87 Required parameters: none
89 Optional parameters:
91 charset: has the same semantics as the charset parameter of the
92 "application/xml" media type specified in [RFC3023].
94 Encoding considerations:
95 XHTML+Voice has the same media type encoding
96 considerations specified in section 3.2 of [RFC3023].
98 Security considerations:
100 XHTML+Voice is an extension of XHTML and has the same security issues
101 as XHTML. These include interpreting anchors and forms in XHTML
102 documents, and scripting languages and other dynamic interactive
103 capabilities. See section 7 of [RFC3236].
105 In addition, the scripting language can be accessed by both the XHTML
106 and the VoiceXML 2.0 markup embedded in the XHTML+Voice document.
107 See section 1.3.1.5 of [XPLUSV12].
109 XML-Events [XMLEVNTS] allows an author to attach a handler to any
110 node in the document. The handler that is activated in response to a
111 specified event may be either a voice dialog or a script that can be
112 either in the same or an external document.
114 Interoperability considerations :
116 Because XHTML+Voice is built upon W3C standard recommendations, it is
117 designed to be interoperable across a wide range of platforms and
118 client devices. Because the extensions to XHTML are identified by
119 their namespaces, all browsers that have namespace support can run an
120 XHTML+Voice document as an XHTML document without voice interaction.
122 Published specification:
124 The latest published version of XHTML+Voice is [XPLUSV12].
126 Applications which use this media type:
128 XHTML+Voice documents are intended to be deployed on the World
129 Wide Web and rendered by multimodal browsers that support the
130 visual and voice modes of interaction. Because XHTML+Voice is
131 an application of XML, authors can expect XHTML+Voice user
132 agents to be conformant XML 1.0 [XML] processors. See section
133 2 of [RFC3236].
135 Additional information:
137 Magic number(s): There is no single string that is always
138 present.
139 File extension(s): mxml, xhvml, xvml, xvm
140 Macintosh File Type Code(s): TEXT
142 Person & e-mail address to contact for further information:
144 Gerald M. McCobb
145 mccobb@us.ibm.com
147 Intended usage: LIMITED USE
149 Author/Change controller: Gerald McCobb
150 Further information:
152 4. Fragment Identifiers
154 See section 3 of [RFC3236]. Following [RFC3236], fragment
155 identifiers for XHTML+Voice documents designate the element with the
156 corresponding ID attribute value (see [XML] section 3.3.1).
158 While XHTML+Voice adds new ID attributes with fragment identifier
159 namespaces that are not in the same namespace as XHTML, uniqueness
160 of the ID attribute values is preserved within the document. See
161 sections 1.3.1 and 5.3 of [XPLUSV12].
163 5. Recognizing XHTML+Voice files
165 Because XHTML+Voice is XML, an XHTML+Voice document [optionally]
166 starts with an XML declaration which begins with "
173 Because XHTML+Voice is in the XHTML family of languages, the root
174 element of an XHTML+Voice document is 'html' and ' (or ).
206 [XHTMLMOD] "Modularization of XHTML," 10 April, 2001, Murray Altheim,
207 Frank Boumphrey, Sam Dooley, et al, W3C Recommendation,
208 http://www.w3.org/TR/xhtml-modularization/
210 [XHTML11] "XHTML 1.1 - Module-based XHTML," 31 May 2001, Murray
211 Altheim, Shane McCarron, W3C Recommendation,
212 http://www.w3.org/TR/xhtml11/.
214 [DOM2EV] "Document Object Model Level 2 Events Specification,"
215 Tom Pixley, 2000. W3C Recommendation,
216 http://www.w3.org/TR/DOM-Level-2-Events/.
218 [XMLEVNTS] "XML Events - An events syntax for XML", Steven
219 Pemberton, T. V. Raman, and Shane McCarron, 2002. W3C
220 Recommendation, http://www.w3.org/TR/xml-events/.
222 [XPLUSV12] "XHTML+Voice Profile 1.2," 16 March 2004, J. Axelsson,
223 et al, http://www.voicexml.org/specs/multimodal/x+v/12/
225 [VXML20] "Voice Extensible Markup Language (VoiceXML)," 16 March
226 2004, Scott McGlashan et al, W3C Recommendation,
227 http://www.w3.org/TR/voicexml20/.
229 9. Authors' Address
231 Gerald M. McCobb
232 IBM Corporation
233 8051 Congress Avenue, Office 2019
234 Boca Raton, Florida 33487
235 USA
237 Phone: +1-561-862-2109
238 Fax: +1-561-862-3922
239 E-mail: mccobb@us.ibm.com
241 10. Full Copyright Statement
243 Copyright (C) The Internet Society (2005). This document is subject
244 to the rights, licenses and restrictions contained in BCP 78, and
245 except as set forth therein, the authors retain all their rights.
247 This document and the information contained herein are provided on
248 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
249 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
250 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
251 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
252 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
253 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
255 Intellectual Property
257 The IETF takes no position regarding the validity or scope of any
258 Intellectual Property Rights or other rights that might be claimed
259 to pertain to the implementation or use of the technology described
260 in this document or the extent to which any license under such
261 rights might or might not be available; nor does it represent that
262 it has made any independent effort to identify any such rights.
263 Information on the procedures with respect to rights in RFC
264 documents can be found in BCP 78 and BCP 79.
266 Copies of IPR disclosures made to the IETF Secretariat and any
267 assurances of licenses to be made available, or the result of an
268 attempt made to obtain a general license or permission for the use
269 of such proprietary rights by implementers or users of this
270 specification can be obtained from the IETF on-line IPR repository
271 at http://www.ietf.org/ipr.
273 The IETF invites any interested party to bring to its attention any
274 copyrights, patents or patent applications, or other proprietary
275 rights that may cover technology that may be required to implement
276 this standard. Please address the information to the IETF at ietf-
277 ipr@ietf.org.
279 Acknowledgement
281 Funding for the RFC Editor function is currently provided by the
282 Internet Society.