idnits 2.17.1
draft-mccobb-xplusv-media-type-02.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 3667, Section 5.1 on line 13.
-- Found old boilerplate from RFC 3978, Section 5.5 on line 241.
-- 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.
** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure
Acknowledgement -- however, there's a paragraph with a matching
beginning. Boilerplate error?
** 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.
** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate
instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission
of drafts without verbatim RFC 3978 boilerplate is not accepted.
The following non-3978 patterns matched text found in the document.
That text should be removed or replaced:
By submitting this Internet-Draft, I certify that any applicable patent
or other IPR claims of which I am aware have been disclosed, or
will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
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 :
----------------------------------------------------------------------------
** The document seems to lack an IANA Considerations section. (See Section
2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
when there are no actions for IANA.)
** 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 (April 1, 2005) is 6966 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 181, 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: 10 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: Oct. 1, 2005 April 1, 2005
5 XHTML+Voice - application/xhtml+voice+xml
6 draft-mccobb-xplusv-media-type-02
8 Status of this Memo
10 By submitting this Internet-Draft, I certify that any applicable
11 patent or other IPR claims of which I am aware have been disclosed,
12 and any of which I become aware will be disclosed, in accordance
13 with RFC 3668.
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 (2004). 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 email 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: 7bit. See section 4 of [RFC3236].
96 Security considerations:
98 XHTML+Voice is an extension of XHTML and has the same security issues
99 as XHTML. These include interpreting anchors and forms in XHTML
100 documents, and scripting languages and other dynamic interactive
101 capabilities. See section 7 of [RFC3236].
103 In addition, the scripting language can be accessed by both the XHTML
104 and the VoiceXML 2.0 markup embedded in the XHTML+Voice document.
105 See section 1.3.1.5 of [XPLUSV12].
107 Interoperability considerations :
109 Because XHTML+Voice is built upon W3C standard recommendations, it is
110 designed to be interoperable across a wide range of platforms and
111 client devices. Because the extensions to XHTML are identified by
112 their namespaces, all browsers that have namespace support can run an
113 XHTML+Voice document as an XHTML document without voice interaction.
115 Published specification:
117 The latest published version of XHTML+Voice is [XPLUSV12].
119 Applications which use this media type:
121 XHTML+Voice documents are intended to be deployed on the World
122 Wide Web and rendered by multimodal browsers that support the
123 visual and voice modes of interaction. Because XHTML+Voice is
124 an application of XML, authors can expect XHTML+Voice user
125 agents to be conformant XML 1.0 [XML] processors. See section
126 2 of [RFC3236].
128 Additional information:
130 Magic number(s): There is no single string that is always
131 present.
132 File extension(s): mxml, xhvml, xvml, xvm
133 Macintosh File Type Code(s): TEXT
135 Person & email address to contact for further information:
137 Gerald M. McCobb
138 mccobb@us.ibm.com
140 Intended usage: COMMON
142 Author/Change controller: Gerald McCobb
144 Further information:
146 4. Fragment Identifiers
148 See section 3 of [RFC3236]. Following [RFC3236], fragment
149 identifiers for XHTML+Voice documents designate the element with the
150 corresponding ID attribute value (see [XML] section 3.3.1).
152 While XHTML+Voice adds new ID attributes with fragment identifier
153 namespaces that are not in the same namespace as XHTML, the fragment
154 identifiers are processed in the same namespace as the ID attribute's
155 namespace.
157 5. Recognizing XHTML+Voice files
159 Because XHTML+Voice is XML, an XHTML+Voice document [optionally]
160 starts with an XML declaration which begins with "
167 Because XHTML+Voice is in the XHTML family of languages, the root
168 element of an XHTML+Voice document is 'html' and ' (or ).
195 [XHTMLMOD] "Modularization of XHTML," 10 April, 2001, Murray Altheim,
196 Frank Boumphrey, Sam Dooley, et al, W3C Recommendation,
197 http://www.w3.org/TR/xhtml-modularization/
199 [XHTML11] "XHTML 1.1 - Module-based XHTML," 31 May 2001, Murray
200 Altheim, Shane McCarron, W3C Recommendation,
201 http://www.w3.org/TR/xhtml11/.
203 [DOM2EV] "Document Object Model Level 2 Events Specification,"
204 Tom Pixley, 2000. W3C Recommendation,
205 http://www.w3.org/TR/DOM-Level-2-Events/.
207 [XMLEVNTS] "XML Events - An events syntax for XML", Steven
208 Pemberton, T. V. Raman, and Shane McCarron, 2002. W3C
209 Recommendation, http://www.w3.org/TR/xml-events/.
210 [XPLUSV12] "XHTML+Voice Profile 1.2," 16 March 2004, J. Axelsson,
211 et al, http://www.voicexml.org/specs/multimodal/x+v/12/
213 [VXML20] "Voice Extensible Markup Language (VoiceXML)," 16 March
214 2004, Scott McGlashan et al, W3C Recommendation,
215 http://www.w3.org/TR/voicexml20/.
217 8. Authors' Address
219 Gerald M. McCobb
220 IBM Corporation
221 8051 Congress Avenue, Office 2019
222 Boca Raton, Florida 33487
223 USA
225 Phone: +1-561-862-2109
226 Fax: +1-561-862-3922
227 EMail: mccobb@us.ibm.com
229 9. Full Copyright Statement
231 Copyright (C) The Internet Society (2004). This document is subject
232 to the rights, licenses and restrictions contained in BCP 78, and
233 except as set forth therein, the authors retain all their rights.
235 This document and the information contained herein are provided on
236 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
237 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
238 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
239 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
240 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
241 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
243 Intellectual Property
245 The IETF takes no position regarding the validity or scope of any
246 Intellectual Property Rights or other rights that might be claimed
247 to pertain to the implementation or use of the technology described
248 in this document or the extent to which any license under such
249 rights might or might not be available; nor does it represent that
250 it has made any independent effort to identify any such rights.
251 Information on the procedures with respect to rights in RFC
252 documents can be found in BCP 78 and BCP 79.
254 Copies of IPR disclosures made to the IETF Secretariat and any
255 assurances of licenses to be made available, or the result of an
256 attempt made to obtain a general license or permission for the use
257 of such proprietary rights by implementers or users of this
258 specification can be obtained from the IETF on-line IPR repository
259 at http://www.ietf.org/ipr.
261 The IETF invites any interested party to bring to its attention any
262 copyrights, patents or patent applications, or other proprietary
263 rights that may cover technology that may be required to implement
264 this standard. Please address the information to the IETF at ietf-
265 ipr@ietf.org.
267 Acknowledgement
269 Funding for the RFC Editor function is currently provided by the
270 Internet Society.