Request for comments regarding draft-mccobb-xv-media-type-00
Gerald McCobb <[email protected]> Fri, 12 Aug 2005 18:33:32 -0400
| Newsgroups | gmane.ietf.types,gmane.ietf.xml-mime |
|---|---|
| Message-ID | <OFD22126B4.25173883-ON85256FCF.005885B7-8525705B.007BE382@us.ibm.com> |
This is a multipart message in MIME format.
--=_alternative 007BE3818525705B_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
This is a request for comments regarding the internet draft=20
draft-mccobb-xv-media-type-00 for media type "application/xv+xml".
This media type is for XHTML+Voice documents. The XHTML+Voice=20
specification
is located at http://www.voicexml.org/specs/multimodal/x+v/12/ .
Network Working Group G. McCobb
Internet-Draft IBM Corporation
Expires: January 27, 2006 July 26, 2005
XHTML+Voice - application/xv+xml
draft-mccobb-xv-media-type-00
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 27, 2006.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document describes the registration of the MIME sub-type
application/xv+xml. This sub-type is intended for use as a media
descriptor for XHTML+Voice multimodal language documents. The XHTML+
Voice 1.2 language specification is maintained by the VoiceXML Forum
at <http://www.voicexml.org/specs/multimodal/x+v/12/>.
McCobb Expires January 27, 2006 [Page 1]
=0C
Internet-Draft XHTML+Voice - application/xv+xml July 2005
1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 [1].
2. Introduction
XHTML+Voice is a member of the XHTML family of document types, as
specified by XHTML Modularization [6]. XHTML+Voice extends XHTML 1.1
[7] with a modularized subset of VoiceXML 2.0 [11], XML Events [9],
and a few extensions to both XHTML and VoiceXML 2.0. XHTML 1.1,
VoiceXML 2.0 and XML Events are W3C Recommendations.
The language integration defined by XHTML+Voice supports all modules
defined by XHTML Modularization, and adds voice interaction to XHTML
elements to enable multimodal applications. The defined document
type for XHTML+Voice is XHTML Host language document type conformant.
XHTML+Voice 1.2 [10] is maintained by the VoiceXML Forum, at URI
location <http://www.voicexml.org/specs/multimodal/x+v/12/>.
2.1 application/xv+xml Usage
The application/xv+xml media type is intended to be a media
descriptor for XHTML+Voice multimodal documents. It is used to
inform applications that additional markup for running a voice
browser component and activating handlers for DOM Level 2 events via
XML Events [9] can be processed.
This media type registration is not intended for e-mail usage.
3. IANA Registration
To: [email protected]
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 [3].
McCobb Expires January 27, 2006 [Page 2]
=0C
Internet-Draft XHTML+Voice - application/xv+xml July 2005
Encoding considerations:
XHTML+Voice has the same media type encoding considerations
specified in section 3.2 of [3].
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 [4].
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 [10].
XML-Events [9] 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 either in 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 [10].
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 [5] processors. See section 2 of [4].
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
McCobb Expires January 27, 2006 [Page 3]
=0C
Internet-Draft XHTML+Voice - application/xv+xml July 2005
Person & e-mail address to contact for further information:
Gerald McCobb
[email protected]
Intended usage: LIMITED USE
Author/Change controller: Gerald McCobb
Further information:
4. Fragment Identifiers
See section 3 of [4]. Following [4], fragment identifiers for XHTML+
Voice documents designate the element with the corresponding ID
attribute value (see [5] section 3.3.1).
While XHTML+Voice adds new ID attributes with fragment identifier
namespaces that are not in the same namespace as XHTML, uniqueness of
the ID attribute values is preserved within the document. See
sections 1.3.1 and 5.3 of [10].
5. Recognizing XHTML+Voice files
Because XHTML+Voice is XML, an XHTML+Voice document [optionally]
starts with an XML declaration which begins with "<?xml" and has a
DOCTYPE declaration "<!DOCTYPE html". XHTML+Voice 1.2 has the
following 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">
Because XHTML+Voice is in the XHTML family of languages, the root
element of an XHTML+Voice document is 'html' and '<html' can be found
near the top of the document.
6. Security Considerations
Security considerations for this media type are discussed in the MIME
type registration that appears in section 3.
McCobb Expires January 27, 2006 [Page 4]
=0C
Internet-Draft XHTML+Voice - application/xv+xml July 2005
7. IANA Considerations
As described in Section 3, this document specifies the registration
of a MIME type for XHTML+Voice documents according to [3].
8. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels, BCP 14", RFC 2119, March 1997.
[2] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396,
August 1998.
[3] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types",
RFC 3023, January 2001.
[4] Baker, M. and P. Stark, "The 'application/xhtml+xml' Media
Type", RFC 3236, January 2002.
[5] Bray, T. and others, "Extensible Markup Language (XML) 1.0, W3C
Recommendation, http://www.w3.org/TR/REC-xml", February 2004.
[6] Dooley, S. and others, "Modularization of XHTML, W3C
Recommendation, http://www.w3.org/TR/xhtml-modularization",
April 2001.
[7] Altheim, M. and S. McCarron, "XHTML 1.1 - Module-based XHTML,
W3C Recommendation, http://www.w3.org/TR/xhtml11/", May 2001.
[8] Pixley, T., "Document Object Model Level 2 Events
Specification, W3C Recommendation,
http://www.w3.org/TR/DOM-Level-2-Events/", November 2000.
[9] 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.
[10] Axelsson, J. and others, "XHTML+Voice Profile 1.2,
http://www.voicexml.org/specs/multimodal/x+v/12/", March 2004.
[11] McGlashan, S. and others, "Voice Extensible Markup Language
(VoiceXML), W3C Recommendation,
http://www.w3.org/TR/voicexml20/", March 2004.
McCobb Expires January 27, 2006 [Page 5]
=0C
Internet-Draft XHTML+Voice - application/xv+xml July 2005
Author's Address
Gerald McCobb
International Business Machines Corporation
8051 Congress Ave.
Boca Raton, FL 33487
USA
Phone: +1 561 862 2109
Email: [email protected]
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
[email protected].
Disclaimer of Validity
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.
McCobb Expires January 27, 2006 [Page 6]
=0C
Internet-Draft XHTML+Voice - application/xv+xml July 2005
Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
McCobb Expires January 27, 2006 [Page 7]
Regards,
Gerald McCobb
IBM
8051 Congress Avenue
Boca Raton, FL 33487
Tel. # 561-862-2109 T/L 975-2109
--=_alternative 007BE3818525705B_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
<br><font size=3D2 face=3D"Courier New">This is a request for comments rega=
rding
the internet draft </font>
<br><font size=3D2 face=3D"Courier New">draft-mccobb-xv-media-type-00 for m=
edia
type "application/xv+xml".</font>
<br><font size=3D2 face=3D"Courier New">This media type is for XHTML+Voice
documents. The XHTML+Voice specification</font>
<br><font size=3D2 face=3D"Courier New">is located at http://www.voicexml.o=
rg/specs/multimodal/x+v/12/
.</font>
<br>
<br>
<br>
<br>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">Network Working Group
G. McCobb</font>
<br><font size=3D2 face=3D"Courier New">Internet-Draft
IBM Corporation</font>
<br><font size=3D2 face=3D"Courier New">Expires: January 27, 2006 &n=
bsp;
July 26, 2005</font>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">
XHTML+Voice - application/xv+xml</font>
<br><font size=3D2 face=3D"Courier New">
draft-mccobb-xv-media-type-00</fon=
t>
<br>
<br><font size=3D2 face=3D"Courier New">Status of this Memo</font>
<br>
<br><font size=3D2 face=3D"Courier New"> By submitting this Int=
ernet-Draft,
each author represents that any</font>
<br><font size=3D2 face=3D"Courier New"> applicable patent or o=
ther
IPR claims of which he or she is aware</font>
<br><font size=3D2 face=3D"Courier New"> have been or will be d=
isclosed,
and any of which he or she becomes</font>
<br><font size=3D2 face=3D"Courier New"> aware will be disclose=
d,
in accordance with Section 6 of BCP 79.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Internet-Drafts are wo=
rking
documents of the Internet Engineering</font>
<br><font size=3D2 face=3D"Courier New"> Task Force (IETF), its
areas, and its working groups. Note that</font>
<br><font size=3D2 face=3D"Courier New"> other groups may also
distribute working documents as Internet-</font>
<br><font size=3D2 face=3D"Courier New"> Drafts.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Internet-Drafts are dr=
aft
documents valid for a maximum of six months</font>
<br><font size=3D2 face=3D"Courier New"> and may be updated, re=
placed,
or obsoleted by other documents at any</font>
<br><font size=3D2 face=3D"Courier New"> time. It is inap=
propriate
to use Internet-Drafts as reference</font>
<br><font size=3D2 face=3D"Courier New"> material or to cite th=
em
other than as "work in progress."</font>
<br>
<br><font size=3D2 face=3D"Courier New"> The list of current In=
ternet-Drafts
can be accessed at</font>
<br><font size=3D2 face=3D"Courier New"> http://www.ietf.org/ie=
tf/1id-abstracts.txt.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> The list of Internet-D=
raft
Shadow Directories can be accessed at</font>
<br><font size=3D2 face=3D"Courier New"> http://www.ietf.org/sh=
adow.html.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> This Internet-Draft wi=
ll
expire on January 27, 2006.</font>
<br>
<br><font size=3D2 face=3D"Courier New">Copyright Notice</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Copyright (C) The Inte=
rnet
Society (2005).</font>
<br>
<br><font size=3D2 face=3D"Courier New">Abstract</font>
<br>
<br><font size=3D2 face=3D"Courier New"> This document describes
the registration of the MIME sub-type</font>
<br><font size=3D2 face=3D"Courier New"> application/xv+xml. &n=
bsp;This
sub-type is intended for use as a media</font>
<br><font size=3D2 face=3D"Courier New"> descriptor for XHTML+V=
oice
multimodal language documents. The XHTML+</font>
<br><font size=3D2 face=3D"Courier New"> Voice 1.2 language spe=
cification
is maintained by the VoiceXML Forum</font>
<br><font size=3D2 face=3D"Courier New"> at <http://www.voic=
exml.org/specs/multimodal/x+v/12/>.</font>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">McCobb
Expires January 27, 2006
[Page 1]</font>
<br><font size=3D2 face=3D"Courier New">=0C</font>
<br><font size=3D2 face=3D"Courier New">Internet-Draft =
XHTML+Voice
- application/xv+xml July 2005</font>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">1. Conventions used in this d=
ocument</font>
<br>
<br><font size=3D2 face=3D"Courier New"> The key words "MU=
ST",
"MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT",</font>
<br><font size=3D2 face=3D"Courier New"> "SHOULD", &q=
uot;SHOULD
NOT", "RECOMMENDED", "MAY", and "OPTIONAL&quo=
t;
in this</font>
<br><font size=3D2 face=3D"Courier New"> document are to be int=
erpreted
as described in BCP 14, RFC 2119 [1].</font>
<br>
<br><font size=3D2 face=3D"Courier New">2. Introduction</font>
<br>
<br><font size=3D2 face=3D"Courier New"> XHTML+Voice is a member
of the XHTML family of document types, as</font>
<br><font size=3D2 face=3D"Courier New"> specified by XHTML Mod=
ularization
[6]. XHTML+Voice extends XHTML 1.1</font>
<br><font size=3D2 face=3D"Courier New"> [7] with a modularized
subset of VoiceXML 2.0 [11], XML Events [9],</font>
<br><font size=3D2 face=3D"Courier New"> and a few extensions to
both XHTML and VoiceXML 2.0. XHTML 1.1,</font>
<br><font size=3D2 face=3D"Courier New"> VoiceXML 2.0 and XML E=
vents
are W3C Recommendations.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> The language integrati=
on
defined by XHTML+Voice supports all modules</font>
<br><font size=3D2 face=3D"Courier New"> defined by XHTML Modul=
arization,
and adds voice interaction to XHTML</font>
<br><font size=3D2 face=3D"Courier New"> elements to enable mul=
timodal
applications. The defined document</font>
<br><font size=3D2 face=3D"Courier New"> type for XHTML+Voice is
XHTML Host language document type conformant.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> XHTML+Voice 1.2 [10] is
maintained by the VoiceXML Forum, at URI</font>
<br><font size=3D2 face=3D"Courier New"> location <http://ww=
w.voicexml.org/specs/multimodal/x+v/12/>.</font>
<br>
<br><font size=3D2 face=3D"Courier New">2.1 application/xv+xml Usage<=
/font>
<br>
<br><font size=3D2 face=3D"Courier New"> The application/xv+xml
media type is intended to be a media</font>
<br><font size=3D2 face=3D"Courier New"> descriptor for XHTML+V=
oice
multimodal documents. It is used to</font>
<br><font size=3D2 face=3D"Courier New"> inform applications th=
at
additional markup for running a voice</font>
<br><font size=3D2 face=3D"Courier New"> browser component and
activating handlers for DOM Level 2 events via</font>
<br><font size=3D2 face=3D"Courier New"> XML Events [9] can be
processed.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> This media type regist=
ration
is not intended for e-mail usage.</font>
<br>
<br><font size=3D2 face=3D"Courier New">3. IANA Registration</font>
<br>
<br><font size=3D2 face=3D"Courier New"> To: ietf-types=
@iana.org</font>
<br><font size=3D2 face=3D"Courier New"> Subject: Regis=
tration
of MIME media type</font>
<br><font size=3D2 face=3D"Courier New">
application/xv+xml</font>
<br>
<br><font size=3D2 face=3D"Courier New"> MIME media type
name: application</font>
<br>
<br><font size=3D2 face=3D"Courier New"> MIME subtype n=
ame:
xv+xml</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Required param=
eters:
none</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Optional param=
eters:</font>
<br>
<br><font size=3D2 face=3D"Courier New"> charset: has t=
he
same semantics as the charset parameter of the</font>
<br><font size=3D2 face=3D"Courier New"> "applicat=
ion/xml"
media type specified in [3].</font>
<br>
<br>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">McCobb
Expires January 27, 2006
[Page 2]</font>
<br><font size=3D2 face=3D"Courier New">=0C</font>
<br><font size=3D2 face=3D"Courier New">Internet-Draft =
XHTML+Voice
- application/xv+xml July 2005</font>
<br>
<br>
<br><font size=3D2 face=3D"Courier New"> Encoding consideration=
s:</font>
<br>
<br><font size=3D2 face=3D"Courier New"> XHTML+Voice has
the same media type encoding considerations</font>
<br><font size=3D2 face=3D"Courier New"> specified in s=
ection
3.2 of [3].</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Security consideration=
s:</font>
<br>
<br><font size=3D2 face=3D"Courier New"> XHTML+Voice is
an extension of XHTML and has the same security</font>
<br><font size=3D2 face=3D"Courier New"> issues as XHTM=
L.
These include interpreting anchors and forms in</font>
<br><font size=3D2 face=3D"Courier New"> XHTML document=
s,
and scripting languages and other dynamic</font>
<br><font size=3D2 face=3D"Courier New"> interactive ca=
pabilities.
See section 7 of [4].</font>
<br>
<br><font size=3D2 face=3D"Courier New"> In addition, t=
he
scripting language can be accessed by both the</font>
<br><font size=3D2 face=3D"Courier New"> XHTML and the
VoiceXML 2.0 markup embedded in the XHTML+Voice</font>
<br><font size=3D2 face=3D"Courier New"> document. &nbs=
p;See
section 1.3.1.5 of [10].</font>
<br>
<br><font size=3D2 face=3D"Courier New"> XML-Events [9]
allows an author to attach a handler to any node in</font>
<br><font size=3D2 face=3D"Courier New"> the document.
The handler that is activated in response to a</font>
<br><font size=3D2 face=3D"Courier New"> specified event
may be either a voice dialog or a script that can</font>
<br><font size=3D2 face=3D"Courier New"> be either in t=
he
same or an external document.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Interoperability consi=
derations:</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Because XHTML+=
Voice
is built upon W3C standard recommendations, it</font>
<br><font size=3D2 face=3D"Courier New"> is designed to
be interoperable across a wide range of platforms</font>
<br><font size=3D2 face=3D"Courier New"> and client dev=
ices.
Because the extensions to XHTML are</font>
<br><font size=3D2 face=3D"Courier New"> identified by
their namespaces, all browsers that have namespace</font>
<br><font size=3D2 face=3D"Courier New"> support can run
an XHTML+Voice document as an XHTML document</font>
<br><font size=3D2 face=3D"Courier New"> without voice
interaction.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Published specificatio=
n:</font>
<br>
<br><font size=3D2 face=3D"Courier New"> The latest pub=
lished
version of XHTML+Voice is [10].</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Applications which use
this media type:</font>
<br>
<br><font size=3D2 face=3D"Courier New"> XHTML+Voice do=
cuments
are intended to be deployed on the World</font>
<br><font size=3D2 face=3D"Courier New"> Wide Web and r=
endered
by multimodal browsers that support the</font>
<br><font size=3D2 face=3D"Courier New"> visual and voi=
ce
modes of interaction. Because XHTML+Voice is an</font>
<br><font size=3D2 face=3D"Courier New"> application of
XML, authors can expect XHTML+Voice user agents to</font>
<br><font size=3D2 face=3D"Courier New"> be conformant
XML 1.0 [5] processors. See section 2 of [4].</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Additional information=
:</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Magic number(s=
):
There is no single string that is always</font>
<br><font size=3D2 face=3D"Courier New"> present.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> File extension=
(s):
mxml, xhvml, xvml, xvm</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Macintosh File
Type Code(s): TEXT</font>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">McCobb
Expires January 27, 2006
[Page 3]</font>
<br><font size=3D2 face=3D"Courier New">=0C</font>
<br><font size=3D2 face=3D"Courier New">Internet-Draft =
XHTML+Voice
- application/xv+xml July 2005</font>
<br>
<br>
<br><font size=3D2 face=3D"Courier New"> Person & e-mail ad=
dress
to contact for further information:</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Gerald McCobb<=
/font>
<br><font size=3D2 face=3D"Courier New"> [email protected].=
com</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Intended usage: =
LIMITED
USE</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Author/Change controll=
er:
Gerald McCobb</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Further information:</=
font>
<br>
<br>
<br>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">4. Fragment Identifiers</font>
<br>
<br><font size=3D2 face=3D"Courier New"> See section 3 of [4].
Following [4], fragment identifiers for XHTML+</font>
<br><font size=3D2 face=3D"Courier New"> Voice documents design=
ate
the element with the corresponding ID</font>
<br><font size=3D2 face=3D"Courier New"> attribute value (see [=
5]
section 3.3.1).</font>
<br>
<br><font size=3D2 face=3D"Courier New"> While XHTML+Voice adds
new ID attributes with fragment identifier</font>
<br><font size=3D2 face=3D"Courier New"> namespaces that are not
in the same namespace as XHTML, uniqueness of</font>
<br><font size=3D2 face=3D"Courier New"> the ID attribute values
is preserved within the document. See</font>
<br><font size=3D2 face=3D"Courier New"> sections 1.3.1 and 5.3
of [10].</font>
<br>
<br><font size=3D2 face=3D"Courier New">5. Recognizing XHTML+Voice fi=
les</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Because XHTML+Voice is
XML, an XHTML+Voice document [optionally]</font>
<br><font size=3D2 face=3D"Courier New"> starts with an XML dec=
laration
which begins with "<?xml" and has a</font>
<br><font size=3D2 face=3D"Courier New"> DOCTYPE declaration &q=
uot;<!DOCTYPE
html". XHTML+Voice 1.2 has the</font>
<br><font size=3D2 face=3D"Courier New"> following DOCTYPE decl=
aration:</font>
<br>
<br><font size=3D2 face=3D"Courier New"> <!DOCTYPE html PUBL=
IC
"-//VoiceXML Forum//DTD XHTML+Voice 1.2//EN"</font>
<br><font size=3D2 face=3D"Courier New"> "http://www.voice=
xml.org/specs/multimodal/x+v/12/dtd/xhtml+voice12.dtd"></font>
<br>
<br><font size=3D2 face=3D"Courier New"> Because XHTML+Voice is
in the XHTML family of languages, the root</font>
<br><font size=3D2 face=3D"Courier New"> element of an XHTML+Vo=
ice
document is 'html' and '<html' can be found</font>
<br><font size=3D2 face=3D"Courier New"> near the top of the do=
cument.</font>
<br>
<br><font size=3D2 face=3D"Courier New">6. Security Considerations</f=
ont>
<br>
<br><font size=3D2 face=3D"Courier New"> Security considerations
for this media type are discussed in the MIME</font>
<br><font size=3D2 face=3D"Courier New"> type registration that
appears in section 3.</font>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">McCobb
Expires January 27, 2006
[Page 4]</font>
<br><font size=3D2 face=3D"Courier New">=0C</font>
<br><font size=3D2 face=3D"Courier New">Internet-Draft =
XHTML+Voice
- application/xv+xml July 2005</font>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">7. IANA Considerations</font>
<br>
<br><font size=3D2 face=3D"Courier New"> As described in Section
3, this document specifies the registration</font>
<br><font size=3D2 face=3D"Courier New"> of a MIME type for XHT=
ML+Voice
documents according to [3].</font>
<br>
<br><font size=3D2 face=3D"Courier New">8. Normative References</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [1] Bradner, S.,
"Key words for use in RFCs to Indicate Requirement</font>
<br><font size=3D2 face=3D"Courier New"> L=
evels,
BCP 14", RFC 2119, March 1997.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [2] Berners-Lee,
T., Fielding, R., and L. Masinter, "Uniform</font>
<br><font size=3D2 face=3D"Courier New"> R=
esource
Identifiers (URI): Generic Syntax", RFC 2396,</font>
<br><font size=3D2 face=3D"Courier New"> A=
ugust
1998.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [3] Murata, M.,
St. Laurent, S., and D. Kohn, "XML Media Types",</font>
<br><font size=3D2 face=3D"Courier New"> R=
FC
3023, January 2001.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [4] Baker, M. a=
nd
P. Stark, "The 'application/xhtml+xml' Media</font>
<br><font size=3D2 face=3D"Courier New"> T=
ype",
RFC 3236, January 2002.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [5] Bray, T. and
others, "Extensible Markup Language (XML) 1.0, W3C</font>
<br><font size=3D2 face=3D"Courier New"> R=
ecommendation,
http://www.w3.org/TR/REC-xml", February 2004.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [6] Dooley, S.
and others, "Modularization of XHTML, W3C</font>
<br><font size=3D2 face=3D"Courier New"> R=
ecommendation,
http://www.w3.org/TR/xhtml-modularization",</font>
<br><font size=3D2 face=3D"Courier New"> A=
pril
2001.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [7] Altheim, M.
and S. McCarron, "XHTML 1.1 - Module-based XHTML,</font>
<br><font size=3D2 face=3D"Courier New"> W=
3C
Recommendation, http://www.w3.org/TR/xhtml11/", May 2001.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [8] Pixley, T.,
"Document Object Model Level 2 Events</font>
<br><font size=3D2 face=3D"Courier New"> S=
pecification,
W3C Recommendation,</font>
<br><font size=3D2 face=3D"Courier New"> h=
ttp://www.w3.org/TR/DOM-Level-2-Events/",
November 2000.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [9] Pemberton,
S., Raman, T., and S. McCarron, "XML Events - An</font>
<br><font size=3D2 face=3D"Courier New"> e=
vents
syntax for XML, W3C Recommendation,</font>
<br><font size=3D2 face=3D"Courier New"> h=
ttp://www.w3.org/TR/xml-events/",
January 2002.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [10] Axelsson, J.
and others, "XHTML+Voice Profile 1.2,</font>
<br><font size=3D2 face=3D"Courier New"> h=
ttp://www.voicexml.org/specs/multimodal/x+v/12/",
March 2004.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> [11] McGlashan,
S. and others, "Voice Extensible Markup Language</font>
<br><font size=3D2 face=3D"Courier New"> (=
VoiceXML),
W3C Recommendation,</font>
<br><font size=3D2 face=3D"Courier New"> h=
ttp://www.w3.org/TR/voicexml20/",
March 2004.</font>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">McCobb
Expires January 27, 2006
[Page 5]</font>
<br><font size=3D2 face=3D"Courier New">=0C</font>
<br><font size=3D2 face=3D"Courier New">Internet-Draft =
XHTML+Voice
- application/xv+xml July 2005</font>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">Author's Address</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Gerald McCobb</font>
<br><font size=3D2 face=3D"Courier New"> International Business
Machines Corporation</font>
<br><font size=3D2 face=3D"Courier New"> 8051 Congress Ave.</fo=
nt>
<br><font size=3D2 face=3D"Courier New"> Boca Raton, FL 3=
3487</font>
<br><font size=3D2 face=3D"Courier New"> USA</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Phone: +1 561 862 2109=
</font>
<br><font size=3D2 face=3D"Courier New"> Email: [email protected]=
om</font>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">Intellectual Property Statement</fo=
nt>
<br>
<br><font size=3D2 face=3D"Courier New"> The IETF takes no posi=
tion
regarding the validity or scope of any</font>
<br><font size=3D2 face=3D"Courier New"> Intellectual Property
Rights or other rights that might be claimed to</font>
<br><font size=3D2 face=3D"Courier New"> pertain to the impleme=
ntation
or use of the technology described in</font>
<br><font size=3D2 face=3D"Courier New"> this document or the e=
xtent
to which any license under such rights</font>
<br><font size=3D2 face=3D"Courier New"> might or might not be
available; nor does it represent that it has</font>
<br><font size=3D2 face=3D"Courier New"> made any independent e=
ffort
to identify any such rights. Information</font>
<br><font size=3D2 face=3D"Courier New"> on the procedures with
respect to rights in RFC documents can be</font>
<br><font size=3D2 face=3D"Courier New"> found in BCP 78 and BCP
79.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Copies of IPR disclosu=
res
made to the IETF Secretariat and any</font>
<br><font size=3D2 face=3D"Courier New"> assurances of licenses
to be made available, or the result of an</font>
<br><font size=3D2 face=3D"Courier New"> attempt made to obtain
a general license or permission for the use of</font>
<br><font size=3D2 face=3D"Courier New"> such proprietary rights
by implementers or users of this</font>
<br><font size=3D2 face=3D"Courier New"> specification can be o=
btained
from the IETF on-line IPR repository at</font>
<br><font size=3D2 face=3D"Courier New"> http://www.ietf.org/ip=
r.</font>
<br>
<br><font size=3D2 face=3D"Courier New"> The IETF invites any i=
nterested
party to bring to its attention any</font>
<br><font size=3D2 face=3D"Courier New"> copyrights, patents or
patent applications, or other proprietary</font>
<br><font size=3D2 face=3D"Courier New"> rights that may cover
technology that may be required to implement</font>
<br><font size=3D2 face=3D"Courier New"> this standard. P=
lease
address the information to the IETF at</font>
<br><font size=3D2 face=3D"Courier New"> [email protected].</fo=
nt>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">Disclaimer of Validity</font>
<br>
<br><font size=3D2 face=3D"Courier New"> This document and the
information contained herein are provided on an</font>
<br><font size=3D2 face=3D"Courier New"> "AS IS" basis
and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS</font>
<br><font size=3D2 face=3D"Courier New"> OR IS SPONSORED BY (IF
ANY), THE INTERNET SOCIETY AND THE INTERNET</font>
<br><font size=3D2 face=3D"Courier New"> ENGINEERING TASK FORCE
DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,</font>
<br><font size=3D2 face=3D"Courier New"> INCLUDING BUT NOT LIMI=
TED
TO ANY WARRANTY THAT THE USE OF THE</font>
<br><font size=3D2 face=3D"Courier New"> INFORMATION HEREIN WILL
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED</font>
<br><font size=3D2 face=3D"Courier New"> WARRANTIES OF MERCHANT=
ABILITY
OR FITNESS FOR A PARTICULAR PURPOSE.</font>
<br>
<br>
<br>
<br>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">McCobb
Expires January 27, 2006
[Page 6]</font>
<br><font size=3D2 face=3D"Courier New">=0C</font>
<br><font size=3D2 face=3D"Courier New">Internet-Draft =
XHTML+Voice
- application/xv+xml July 2005</font>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">Copyright Statement</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Copyright (C) The Inte=
rnet
Society (2005). This document is subject</font>
<br><font size=3D2 face=3D"Courier New"> to the rights, licenses
and restrictions contained in BCP 78, and</font>
<br><font size=3D2 face=3D"Courier New"> except as set forth th=
erein,
the authors retain all their rights.</font>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">Acknowledgment</font>
<br>
<br><font size=3D2 face=3D"Courier New"> Funding for the RFC Ed=
itor
function is currently provided by the</font>
<br><font size=3D2 face=3D"Courier New"> Internet Society.</fon=
t>
<br>
<br>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">McCobb
Expires January 27, 2006
[Page 7]</font>
<br><font size=3D2 face=3D"sans-serif"><br>
Regards,<br>
Gerald McCobb<br>
IBM<br>
8051 Congress Avenue<br>
Boca Raton, FL 33487<br>
Tel. # 561-862-2109 T/L 975-2109<br>
</font>
--=_alternative 007BE3818525705B_=--