Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3LCXYaC022549; Thu, 21 Apr 2005 05:33:34 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j3LCXY7W022548; Thu, 21 Apr 2005 05:33:34 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.133]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3LCXXVP022455 for ; Thu, 21 Apr 2005 05:33:33 -0700 (PDT) (envelope-from mccobb@us.ibm.com) Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e35.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j3LCXRLg361694 for ; Thu, 21 Apr 2005 08:33:27 -0400 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j3LCXR7j368648 for ; Thu, 21 Apr 2005 06:33:27 -0600 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j3LCXQXB009926 for ; Thu, 21 Apr 2005 06:33:26 -0600 Received: from d03nm118.boulder.ibm.com (d03nm118.boulder.ibm.com [9.17.195.144]) by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j3LCXQgh009923; Thu, 21 Apr 2005 06:33:26 -0600 In-Reply-To: <424ce891.128044187@smtp.bjoern.hoehrmann.de> To: Bjoern Hoehrmann Cc: ietf-types@iana.org, ietf-xml-mime@imc.org MIME-Version: 1.0 Subject: Re: Request for comments regarding draft-mccobb-xplusv-media-type-01 X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 Message-ID: From: Gerald McCobb Date: Thu, 21 Apr 2005 08:33:25 -0400 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Build V70_M4_01112005 Beta 3|January 11, 2005) at 04/21/2005 06:33:26, Serialize complete at 04/21/2005 06:33:26 Content-Type: multipart/alternative; boundary="=_alternative 0044F6D285256FEA_=" Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0044F6D285256FEA_= Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable In response to your previous comments (thanks) I submitted=20 draft-mccobb-xplusv-media-type-02.txt to internet-drafts@ietf.org. Please = review and thanks in advance: Network Working Group G. McCobb Internet-Draft IBM Corporation Expires: Oct. 1, 2005 April 1, 2005 XHTML+Voice - application/xhtml+voice+xml draft-mccobb-xplusv-media-type-02 Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance=20 with RFC 3668. 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=20 months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as=20 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. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved Abstract This document describes the registration of the MIME sub-type application/xhtml+voice+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 . 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 [RFC2119]. McCobb Expires Oct. 1, 2005 [Page 1] =0C Internet-Draft XHTML+Voice - application/xhtml+voice+xml April 1, 2005 2. Introduction XHTML+Voice is a member of the XHTML family of document types, as specified by XHTML Modularization [XHTMLMOD]. XHTML+Voice extends XHTML 1.1 [XHTML11] with a modularized subset of VoiceXML 2.0 [VXML20], XML Events [XMLEVNTS], 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 [XPLUSV12] is maintained by the VoiceXML Forum, at URI location . 2.1 application/xhtml+voice+xml Usage The application/xhtml+voice+xml media type is intended to be a media descriptor for XHTML+Voice multimodal documents. Multimodal browsers have special processing requirements for XHTML+Voice documents, such as running a voice browser component, and support for the DOM Level 2 Event Model [DOM2EV] and XML Events [XMLEVNTS]. This media type registration is not intended for email usage. 3. IANA Registration To: ietf-types@iana.org Subject: Registration of Standard MIME media type=20 application/xhtml+voice+xml MIME media type name: application MIME subtype name: xhtml+voice+xml Required parameters: none Optional parameters: charset: has the same semantics as the charset parameter of the "application/xml" media type specified in [RFC3023]. Encoding considerations: 7bit. See section 4 of [RFC3236]. Security considerations: =20 XHTML+Voice is an extension of XHTML and has the same security issues McCobb Expires Oct. 1, 2005 [Page 2] =0C Internet-Draft XHTML+Voice - application/xhtml+voice+xml April 1, 2005 as XHTML. These include interpreting anchors and forms in XHTML documents, and scripting languages and other dynamic interactive capabilities. See section 7 of [RFC3236]. 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 [XPLUSV12]. 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. =20 Published specification: The latest published version of XHTML+Voice is [XPLUSV12]. 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 [XML] processors. See section 2 of [RFC3236]. 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 & email address to contact for further information: Gerald M. McCobb mccobb@us.ibm.com Intended usage: COMMON Author/Change controller: Gerald McCobb Further information: 4. Fragment Identifiers See section 3 of [RFC3236]. Following [RFC3236], fragment McCobb Expires Oct. 1, 2005 [Page 3] =0C Internet-Draft XHTML+Voice - application/xhtml+voice+xml April 1, 2005 identifiers for XHTML+Voice documents designate the element with the corresponding ID attribute value (see [XML] section 3.3.1). While XHTML+Voice adds new ID attributes with fragment identifier namespaces that are not in the same namespace as XHTML, the fragment identifiers are processed in the same namespace as the ID attribute's namespace. 5. Recognizing XHTML+Voice files Because XHTML+Voice is XML, an XHTML+Voice document [optionally] starts with an XML declaration which begins with " =20 Because XHTML+Voice is in the XHTML family of languages, the root element of an XHTML+Voice document is 'html' and ' (or ). [XHTMLMOD] "Modularization of XHTML," 10 April, 2001, Murray Altheim, Frank Boumphrey, Sam Dooley, et al, W3C Recommendation,=20 http://www.w3.org/TR/xhtml-modularization/ McCobb Expires Oct. 1, 2005 [Page 4] =0C Internet-Draft XHTML+Voice - application/xhtml+voice+xml April 1, 2005 [XHTML11] "XHTML 1.1 - Module-based XHTML," 31 May 2001, Murray=20 Altheim, Shane McCarron, W3C Recommendation, http://www.w3.org/TR/xhtml11/. [DOM2EV] "Document Object Model Level 2 Events Specification,"=20 Tom Pixley, 2000. W3C Recommendation, http://www.w3.org/TR/DOM-Level-2-Events/. [XMLEVNTS] "XML Events - An events syntax for XML", Steven Pemberton, T. V. Raman, and Shane McCarron, 2002. W3C Recommendation, http://www.w3.org/TR/xml-events/. [XPLUSV12] "XHTML+Voice Profile 1.2," 16 March 2004, J. Axelsson, et al, http://www.voicexml.org/specs/multimodal/x+v/12/ [VXML20] "Voice Extensible Markup Language (VoiceXML)," 16 March 2004, Scott McGlashan et al, W3C Recommendation, http://www.w3.org/TR/voicexml20/. 8. Authors' Address Gerald M. McCobb IBM Corporation 8051 Congress Avenue, Office 2019 Boca Raton, Florida 33487 USA Phone: +1-561-862-2109 Fax: +1-561-862-3922 EMail: mccobb@us.ibm.com 9. Full Copyright Statement Copyright (C) The Internet Society (2004). 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. This document and the information contained herein are provided on=20 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE=20 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR=20 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF=20 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED=20 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any McCobb Expires Oct. 1, 2005 [Page 5] =0C Internet-Draft XHTML+Voice - application/xhtml+voice+xml April 1, 2005 Intellectual Property Rights or other rights that might be claimed=20 to pertain to the implementation or use of the technology described=20 in this document or the extent to which any license under such=20 rights might or might not be available; nor does it represent that=20 it has made any independent effort to identify any such rights.=20 Information on the procedures with respect to rights in RFC=20 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=20 specification can be obtained from the IETF on-line IPR repository=20 at http://www.ietf.org/ipr.=20 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 ietf- ipr@ietf.org. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Mccobb Expires May 15, 2005 [Page 6] Regards, Gerald McCobb IBM 8051 Congress Avenue Boca Raton, FL 33487 Tel. # 561-862-2109 T/L 975-2109 Bjoern Hoehrmann 03/26/2005 06:06 PM =20 To: Gerald McCobb/Boca Raton/IBM@IBMUS cc: ietf-types@iana.org, ietf-xml-mime@imc.org Subject: Re: Request for comments regarding=20 draft-mccobb-xplusv-media-type-01 * Gerald McCobb wrote: >2.1 application/xhtml+voice+xml Usage > > The application/xhtml+voice+xml media type is intended to be a media > descriptor for XHTML+Voice documents. > > This media type registration is not intended for email usage. The draft does not really explain why there is a need for such a type in the first place; why don't you use application/xhtml+xml? > Optional parameters: > version: refers to the XHTML+Voice language version in the document. > Acceptable values are 1.0, 1.1, and 1.2 (default). What are the processing requirements for this parameter? > charset: has the same meaning as the text/html media type. See > section 2 of [RFC 2854]. A word seems to be missing here. It is not really clear why the draft refers to RFC 2854 rather than RFC 3023 or RFC 3236.=20 > Security considerations: >=20 > XHTML+Voice is an extension of XHTML and has the same security issues > as XHTML. These include interpreting anchors and forms in HTML > documents, and scripting languages and other dynamic interactive > capabilities. See section 7 of [RFC 2854]. So the extensions to XHTML have no security considerations? > File extension(s): html, htm, mxml, xvml I don't think .html and .htm should be listed here, they are already in common use for application/xhtml+xml and text/html. >4. Fragment Identifiers > > See section 3 of [RFC 2854]. It is unclear what this means, RFC 2854 and RFC 3236 have inconsistent rules for fragment identifiers and XHTML+Voice adds new ID attributes so that the fragment identifier namespaces are different. >6. Security Considerations > > Security considerations for this media type are discussed in the MIME > type registration that appears in section 4. Section 4 has no security considerations... >7. References The draft should be clear about which of these references are informative and which normative. --=20 Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehrma= nn.de Weinh. Str. 22 =B7 Telefon: +49(0)621/4309674 =B7 http://www.bjoernsworld.de 68309 Mannheim =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.de/= =20 --=_alternative 0044F6D285256FEA_= Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
In response to your previous commen= ts (thanks) I submitted draft-mccobb-xplusv-media-type-02.txt to internet-draf= ts@ietf.org.  Please review and thanks in advance:


Network Working Group                                          G. McCobb
Internet-Draft                                           IBM Corporation
Expires: Oct. 1, 2005                                      April 1, 2005


                XHTML+Voice - application/xhtml+voice+xml
                    draft-mccobb-xplusv-media-type-02


Status of this Memo

   By submitting this Int= ernet-Draft, I certify that any applicable
   patent or other IPR cl= aims of which I am aware have been disclosed,
   and any of which I bec= ome aware will be disclosed, in accordance
   with RFC 3668.

   Internet-Drafts are wo= rking 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 dr= aft documents valid for a maximum of six
   months and may be upda= ted, 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 In= ternet-Drafts can be accessed at
   http://www.ietf.org/ie= tf/1id-abstracts.txt.

   The list of Internet-D= raft Shadow Directories can be accessed at
   http://www.ietf.org/sh= adow.html.

Copyright Notice

   Copyright (C) The Inte= rnet Society (2004).  All Rights Reserved

Abstract

   This document describes the registration of the MIME sub-type
   application/xhtml+voic= e+xml.  This sub-type is intended for use as a
   media descriptor for X= HTML+Voice multimodal language documents.  The
   XHTML+Voice 1.2 langua= ge specification is maintained by the VoiceXML
   Forum at <http://ww= w.voicexml.org/specs/multimodal/x+v/12/>.

1.  Conventions used in this d= ocument

   The key words "MU= ST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", &q= uot;SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL&quo= t; in this
   document are to be int= erpreted as described in BCP 14, RFC 2119
   [RFC2119].



McCobb                   Expires Oct. 1, 2005                   [Page 1]
=0C
Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005


2. Introduction

   XHTML+Voice is a member of the XHTML family of document types, as
   specified by XHTML Mod= ularization [XHTMLMOD].  XHTML+Voice extends
   XHTML 1.1 [XHTML11] wi= th a modularized subset of VoiceXML 2.0
   [VXML20], XML Events [= XMLEVNTS], and a few extensions to both XHTML
   and VoiceXML 2.0. &nbs= p;XHTML 1.1, VoiceXML 2.0 and XML Events are W3C
   Recommendations.

   The language integrati= on defined by XHTML+Voice supports all modules
   defined by XHTML Modul= arization, and adds voice interaction to XHTML
   elements to enable mul= timodal applications.  The defined document
   type for XHTML+Voice is XHTML Host language document type conformant.

   XHTML+Voice 1.2 [XPLUS= V12] is maintained by the VoiceXML Forum, at
   URI location <http:= //www.voicexml.org/specs/multimodal/x+v/12/>.

2.1 application/xhtml+voice+xml Usa= ge

   The application/xhtml+= voice+xml media type is intended to be a media
   descriptor for XHTML+V= oice multimodal documents. Multimodal browsers
   have special processing requirements for XHTML+Voice documents, such
   as running a voice bro= wser component, and support for the DOM Level
   2 Event Model [DOM2EV] and XML Events [XMLEVNTS].

   This media type regist= ration is not intended for email usage.

3. IANA Registration

      To: ietf-types= @iana.org
      Subject: Regis= tration of Standard MIME media type
               application/xhtml+voice+xml

      MIME media type name: application

      MIME subtype n= ame: xhtml+voice+xml

      Required param= eters: none

      Optional param= eters:

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

      Encoding consi= derations: 7bit.  See section 4 of [RFC3236].

      Security consi= derations:
 
   XHTML+Voice is an exte= nsion of XHTML and has the same security issues


McCobb                   Expires Oct. 1, 2005                   [Page 2]
=0C
Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005

   as XHTML.  These include interpreting anchors and forms in XHTML
   documents, and scripti= ng languages and other dynamic interactive
   capabilities.  See section 7 of [RFC3236].

   In addition, the scrip= ting language can be accessed by both the XHTML
   and the VoiceXML 2.0 m= arkup embedded in the XHTML+Voice document.
   See section 1.3.1.5 of [XPLUSV12].

      Interoperabili= ty considerations :

   Because XHTML+Voice is built upon W3C standard recommendations, it is
   designed to be interop= erable 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 speci= fication:

         T= he latest published version of XHTML+Voice is [XPLUSV12].

      Applications w= hich use this media type:

         X= HTML+Voice documents are intended to be deployed on the World
         W= ide Web and rendered by multimodal browsers that support the
         v= isual and voice modes of interaction.  Because XHTML+Voice is
         an application of XML, authors can expect XHTML+Voice user
         a= gents to be conformant XML 1.0 [XML] processors.  See section
         2 of [RFC3236].

      Additional inf= ormation:

         M= agic number(s):  There is no single string that is always
             present.
         F= ile extension(s): mxml, xhvml, xvml, xvm
         M= acintosh File Type Code(s): TEXT

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

         G= erald M. McCobb
         m= ccobb@us.ibm.com

      Intended usage: COMMON

      Author/Change controller: Gerald McCobb

      Further inform= ation:

4. Fragment Identifiers

   See section 3 of [RFC3= 236].  Following [RFC3236], fragment


McCobb                   Expires Oct. 1, 2005                   [Page 3]
=0C
Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005

   identifiers for XHTML+= Voice documents designate the element with the
   corresponding ID attri= bute value (see [XML] section 3.3.1).

   While XHTML+Voice adds new ID attributes with fragment identifier
   namespaces that are not in the same namespace as XHTML, the fragment
   identifiers are proces= sed in the same namespace as the ID attribute's
   namespace.

5. Recognizing XHTML+Voice files

   Because XHTML+Voice is XML, an XHTML+Voice document [optionally]
   starts with an XML dec= laration which begins with "<?xml" and has a
   DOCTYPE declaration &q= uot;<!DOCTYPE html".  XHTML+Voice 1.2 has the
   following DOCTYPE decl= aration:
 
   <!DOCTYPE html PUBL= IC "-//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+Vo= ice document is 'html' and '<html' can be found
   near the top of the do= cument.  

6. Security Considerations

   Security considerations for this media type are discussed in the MIME
   type registration that appears in section 3.

7. Normative References

   [RFC2119]  Bradne= r, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2396]  Berner= s-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifiers (URI): Generic Syntax", RFC 2396,
              August 1998.

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

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

   [XML]     &n= bsp;"Extensible Markup Language (XML) 1.0", W3C
              Recommendation.  Available at <http://www.w3.org/TR/R= EC-
              xml> (or <http://www.w3.org/TR/2000/REC-xml-20001006>= ;).

   [XHTMLMOD] "Modul= arization of XHTML," 10 April, 2001, Murray Altheim,
              Frank Boumphrey, Sam Dooley, et al, W3C Recommendation,
              http://www.w3.org/TR/xhtml-modularization/



McCobb                   Expires Oct. 1, 2005                   [Page 4]
=0C
Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005


   [XHTML11]  "= XHTML 1.1 - Module-based XHTML," 31 May 2001, Murray
              Altheim, Shane McCarron, W3C Recommendation,
              http://www.w3.org/TR/xhtml11/.

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

   [XMLEVNTS] "XML E= vents - An events syntax for XML", Steven
              Pemberton, T. V. Raman, and Shane McCarron, 2002.  W3C
              Recommendation, http://www.w3.org/TR/xml-events/.
   [XPLUSV12] "XHTML= +Voice Profile 1.2," 16 March 2004, J. Axelsson,
              et al, http://www.voicexml.org/specs/multimodal/x+v/12/

   [VXML20]   "= Voice Extensible Markup Language (VoiceXML)," 16 March
              2004, Scott McGlashan et al, W3C Recommendation,
              http://www.w3.org/TR/voicexml20/.

8. Authors' Address

   Gerald M. McCobb
   IBM Corporation
   8051 Congress Avenue, Office 2019
   Boca Raton, Florida 33= 487
   USA

   Phone: +1-561-862-2109=
   Fax:   +1-561-862= -3922
   EMail: mccobb@us.ibm.c= om


9. Full Copyright Statement

   Copyright (C) The Inte= rnet Society (2004).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth th= erein, the authors retain all their rights.

   This document and the information contained herein are provided on
   an "AS IS" b= asis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
   REPRESENTS OR IS SPONS= ORED BY (IF ANY), THE INTERNET SOCIETY AND THE
   INTERNET ENGINEERING T= ASK 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 MERCHANT= ABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

   Intellectual Property<= /font>

   The IETF takes no posi= tion regarding the validity or scope of any



McCobb                   Expires Oct. 1, 2005                   [Page 5]
=0C
Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005



   Intellectual Property Rights or other rights that might be claimed
   to pertain to the impl= ementation 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 indepe= ndent effort to identify any such rights.  
   Information on the pro= cedures with respect to rights in RFC
   documents can be found in BCP 78 and BCP 79.

   Copies of IPR disclosu= res 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 ri= ghts by implementers or users of this
   specification can be o= btained from the IETF on-line IPR repository
   at http://www.ietf.org= /ipr.  

   The IETF invites any i= nterested 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.  P= lease address the information to the IETF at ietf-
   ipr@ietf.org.

Acknowledgement

   Funding for the RFC Ed= itor function is currently provided by the
   Internet Society.

























Mccobb                   Expires May 15, 2005                   [Page 6]


Regards,
Gerald McCobb
IBM
8051 Congress Avenue
Boca Raton, FL 33487
Tel. # 561-862-2109 T/L 975-2109


Bjoern Hoehrmann <derhoermi@gm= x.net>

03/26/2005 06:06 PM

       
        To:        Gerald McCobb/Boca Raton/IBM@IBMUS
        cc:        ietf-types@iana.org, ietf-xml-mime@imc.org
        Subject:        Re: Request for comments regarding draft-mccobb-= xplusv-media-type-01



* Gerald McCobb wrote:
>2.1 application/xhtml+voice+xml Usage
>
>   The application/xhtml+voice+xml media type is intended to be a media
>   descriptor for XHTML+Voice documents.
>
>   This media type registration is not intended for email usage.
The draft does not really explain why there is a need for such a
type in the first place; why don't you use application/xhtml+xml?

>      Optional parameters:
>   version:  refers to the XHTML+Voice language version in the document.
>             Acceptable values are 1.0, 1.1, and 1.2 (default).

What are the processing requirements for this parameter?

>   charset:  has the same meaning as the text/html media type.  See
>   section 2 of [RFC 2854].

A word seems to be missing here. It is not really clear why the draft
refers to RFC 2854 rather than RFC 3023 or RFC 3236.

>      Security considerations:
>
>   XHTML+Voice is an extension of XHTML and has the same security issues
>   as XHTML.  These include interpreting anchors and forms in HTML
>   documents, and scripting languages and other dynamic interactiv= e
>   capabilities.  See section 7 of [RFC 2854].

So the extensions to XHTML have no security considerations?

>         File extension(s): html, htm, mxml, xvml
I don't think .html and .htm should be listed here, they are already in
common use for application/xhtml+xml and text/html.

>4. Fragment Identifiers
>
>   See section 3 of [RFC 2854].

It is unclear what this means, RFC 2854 and RFC 3236 have inconsistent
rules for fragment identifiers and XHTML+Voice adds new ID attributes
so that the fragment identifier namespaces are different.

>6. Security Considerations
>
>   Security considerations for this media type are discussed in the MIME
>   type registration that appears in section 4.

Section 4 has no security considerations...

>7. References

The draft should be clear about which of these references are
informative and which normative.
--
Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehrma= nn.de
Weinh. Str. 22 =B7 Telefon: +49(0)621/4309674 =B7 http://www.bjoernsworld.d= e
68309 Mannheim =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.de/

--=_alternative 0044F6D285256FEA_=-- Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37LE0IT017376; Thu, 7 Apr 2005 14:14:00 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j37LE0bV017375; Thu, 7 Apr 2005 14:14:00 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from homer.w3.org (homer.w3.org [128.30.52.30]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37LDxlf017368 for ; Thu, 7 Apr 2005 14:13:59 -0700 (PDT) (envelope-from liam@w3.org) Received: by homer.w3.org (Postfix, from userid 16040) id 640E14F363; Thu, 7 Apr 2005 17:13:58 -0400 (EDT) Date: Thu, 7 Apr 2005 17:13:58 -0400 From: Liam Quin To: Bjoern Hoehrmann Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: Re: W3C Last Call and Media Type request for comments: XQuery and XQueryX Message-ID: <20050407211358.GA1005@w3.org> References: <20050407200151.GN1785@w3.org> <425b93d4.13001640@smtp.bjoern.hoehrmann.de> <20050407204611.GS1785@w3.org> <425e9d44.15417140@smtp.bjoern.hoehrmann.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <425e9d44.15417140@smtp.bjoern.hoehrmann.de> X-Feet: bare, comfortable. happy and free! User-Agent: Mutt/1.5.6+20040907i Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Thu, Apr 07, 2005 at 11:06:49PM +0200, Bjoern Hoehrmann wrote: > * Liam Quin wrote: > >It lets people put XQuery documents on public Web servers that may > >not be configured correctly. But it's not clear that this is the > >right approach. > > What kind of misconfiguration did you have in mind here? Configured to > use an incorrect charset parameter? That's then easily addressed by not > having a charset parameter. That might in fact be the best approach for us. I'll take it up internally, thanks! > >We expect to add to it later. Right now the specifications are new > >enough (in terms of Process) that security implications have not > >all been explored. I'd welcome help in this area. What sort of > >additional text did you expect in this section? > > http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-03.txt > section 6 covers this Note that date on that document is April 1st -- we'll be able to take it into account for the next publication, which I hope will be for Candidate Recommendation. On whether it should be normative within XQuery, I'll take it up internally. > it seems inconsistent with other W3C Technical Reports. This process of registering MIME types is new, so we're treading new ground here. Thanks again for your help. Liam -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/ Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37L6WoJ016565; Thu, 7 Apr 2005 14:06:32 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j37L6WPj016564; Thu, 7 Apr 2005 14:06:32 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by above.proper.com (8.12.11/8.12.9) with SMTP id j37L6UZZ016548 for ; Thu, 7 Apr 2005 14:06:31 -0700 (PDT) (envelope-from derhoermi@gmx.net) Received: (qmail invoked by alias); 07 Apr 2005 21:06:24 -0000 Received: from dsl-084-056-238-149.arcor-ip.net (EHLO localhost) [84.56.238.149] by mail.gmx.net (mp021) with SMTP; 07 Apr 2005 23:06:24 +0200 X-Authenticated: #723575 From: Bjoern Hoehrmann To: Liam Quin Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: Re: W3C Last Call and Media Type request for comments: XQuery and XQueryX Date: Thu, 07 Apr 2005 23:06:49 +0200 Message-ID: <425e9d44.15417140@smtp.bjoern.hoehrmann.de> References: <20050407200151.GN1785@w3.org> <425b93d4.13001640@smtp.bjoern.hoehrmann.de> <20050407204611.GS1785@w3.org> In-Reply-To: <20050407204611.GS1785@w3.org> X-Mailer: Forte Agent 1.92/32.572 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: * Liam Quin wrote: >It lets people put XQuery documents on public Web servers that may >not be configured correctly. But it's not clear that this is the >right approach. What kind of misconfiguration did you have in mind here? Configured to use an incorrect charset parameter? That's then easily addressed by not having a charset parameter. >We expect to add to it later. Right now the specifications are new >enough (in terms of Process) that security implications have not >all been explored. I'd welcome help in this area. What sort of >additional text did you expect in this section? http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-03.txt section 6 covers this. For example, it seems possible to construct a query such that it loops indefinitely through infinite recursion, that's probably something implementations should protect against. >It's non-normative within the context of the XQueryX specification: >an implementation does not need to support anything here in order >to claim conformance. If you do support application/xquery+xml though, >this is how you must do it. http://www.w3.org/TR/2005/WD-xquery-20050404/#id-conform-optional-features is not marked non-normative, even though none of the features in that section are required in order to claim conformance, so this principle does not seem to be applied consistently; and it seems inconsistent with other W3C Technical Reports. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37KkONY014503; Thu, 7 Apr 2005 13:46:24 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j37KkODu014502; Thu, 7 Apr 2005 13:46:24 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from homer.w3.org (homer.w3.org [128.30.52.30]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37KkOMD014495 for ; Thu, 7 Apr 2005 13:46:24 -0700 (PDT) (envelope-from liam@w3.org) Received: by homer.w3.org (Postfix, from userid 16040) id C147A4F477; Thu, 7 Apr 2005 16:46:23 -0400 (EDT) Date: Thu, 7 Apr 2005 16:46:23 -0400 From: Liam Quin To: Bjoern Hoehrmann Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: Re: W3C Last Call and Media Type request for comments: XQuery and XQueryX Message-ID: <20050407204611.GS1785@w3.org> References: <20050407200151.GN1785@w3.org> <425b93d4.13001640@smtp.bjoern.hoehrmann.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <425b93d4.13001640@smtp.bjoern.hoehrmann.de> X-Feet: bare, comfortable. happy and free! User-Agent: Mutt/1.5.6+20040907i Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Thu, Apr 07, 2005 at 10:28:58PM +0200, Bjoern Hoehrmann wrote: [...] >> If an XQuery document contains an encoding declaration, it overrides the >> default encoding specified by the MIME charset parameter. > > That's inconsistent with pretty much all other media types that allow a > charset parameter. What's the point of having a charset parameter here? It lets people put XQuery documents on public Web servers that may not be configured correctly. But it's not clear that this is the right approach. Thank you for the comment. >> I.5 Charset Default Rules >> >> XQuery documents use the Unicode character set and, by default, the >> UTF-8 encoding. > > That's incorrect then, it defaults to the character encoding specified > in the charset parameter (which then defaults to UTF-8). In the MIME context that's true -- so far XQueryX has mostly (entirely?) been used offline, where there's no charset parameter. Thanks for spotting this. > >I.6 Security Considerations [...] > Compared to http://www.ietf.org/rfc/rfc2046.txt section 4.5.2 this seems > very incomplete... We expect to add to it later. Right now the specifications are new enough (in terms of Process) that security implications have not all been explored. I'd welcome help in this area. What sort of additional text did you expect in this section? > >**** Registration for application/xquery+xml also at [4] > > > >C The application/xquery+xml Media Type (Non-Normative) > > Non-Normative? Is there a normative version of this text? It's non-normative within the context of the XQueryX specification: an implementation does not need to support anything here in order to claim conformance. If you do support application/xquery+xml though, this is how you must do it. I hope that's clearer. It's been difficult to see the balance between making th documents stand alone and making them also work as part of a larger specification. Liam -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/ Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37KdIXI013985; Thu, 7 Apr 2005 13:39:18 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j37KdIHb013984; Thu, 7 Apr 2005 13:39:18 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from homer.w3.org (homer.w3.org [128.30.52.30]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37KdIt8013977 for ; Thu, 7 Apr 2005 13:39:18 -0700 (PDT) (envelope-from liam@w3.org) Received: by homer.w3.org (Postfix, from userid 16040) id B7CD44F060; Thu, 7 Apr 2005 16:39:17 -0400 (EDT) Date: Thu, 7 Apr 2005 16:39:17 -0400 From: "'Liam Quin'" To: Larry Masinter Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: Re: W3C Last Call and Media Type request for comments: XQuery andXQueryX Message-ID: <20050407203917.GR1785@w3.org> References: <20050407200151.GN1785@w3.org> <0IEL00HBUFTEYQ@mailsj-v1.corp.adobe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <0IEL00HBUFTEYQ@mailsj-v1.corp.adobe.com> X-Feet: bare, comfortable. happy and free! User-Agent: Mutt/1.5.6+20040907i Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Thu, Apr 07, 2005 at 01:34:26PM -0700, Larry Masinter wrote: > > > I.4 Recognizing XQuery Files > > > > An XQuery file may have the string xquery version "V.V" near the > > beginning of the document, where "V.V" is a version number. Currently > > the version number, if present, must be "1.0". > > I can't figure this out. Is the string "xquery" appear, > "xquery version 1.0", or something else? I think the quotes > are misplaced. The xquery version information looks like: xquery version "1.0"; or, for example, xquery version "1.0" encoding "utf-8"; It's clearer in the formatted version -- mea culpa, I should have reformatted it I think. Liam -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/ Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37KYpXF013704; Thu, 7 Apr 2005 13:34:51 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j37KYpSV013703; Thu, 7 Apr 2005 13:34:51 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from psmtp.com (exprod6og4.obsmtp.com [64.18.1.124]) by above.proper.com (8.12.11/8.12.9) with SMTP id j37KYmV5013692 for ; Thu, 7 Apr 2005 13:34:50 -0700 (PDT) (envelope-from LMM@acm.org) Received: from source ([192.150.20.142]) by exprod6ob4.obsmtp.com ([64.18.5.12]) with SMTP; Thu, 07 Apr 2005 13:34:41 PDT Received: from inner-relay-3.corp.adobe.com ([153.32.251.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id j37KegTK022151 for ; Thu, 7 Apr 2005 13:40:43 -0700 (PDT) Received: from calsj-dev (calsj-dev.corp.adobe.com [153.32.1.193]) by inner-relay-3.corp.adobe.com (8.12.9/8.12.9) with ESMTP id j37KYR0v013104 for ; Thu, 7 Apr 2005 13:34:37 -0700 (PDT) Received: from calsj-dev (localhost [127.0.0.1]) by mailsj-v1.corp.adobe.com (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTP id <0IEL00F3YFTFQE@mailsj-v1.corp.adobe.com> for ietf-xml-mime@imc.org; Thu, 07 Apr 2005 13:34:27 -0700 (PDT) Received: from MasinterT40 (c-131-136.corp.adobe.com [153.32.131.136]) by mailsj-v1.corp.adobe.com (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTP id <0IEL00HBTFTEYQ@mailsj-v1.corp.adobe.com> for ietf-xml-mime@imc.org; Thu, 07 Apr 2005 13:34:27 -0700 (PDT) Date: Thu, 07 Apr 2005 13:34:26 -0700 From: Larry Masinter Subject: RE: W3C Last Call and Media Type request for comments: XQuery andXQueryX In-reply-to: <20050407200151.GN1785@w3.org> To: "'Liam Quin'" , ietf-types@iana.org Cc: ietf-xml-mime@imc.org, public-qt-comments@w3.org Message-id: <0IEL00HBUFTEYQ@mailsj-v1.corp.adobe.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcU7rKw8knTi2WGYSE+qgK21eFyEJwABF32A Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > I.4 Recognizing XQuery Files > > An XQuery file may have the string xquery version "V.V" near the > beginning of the document, where "V.V" is a version number. Currently > the version number, if present, must be "1.0". I can't figure this out. Is the string "xquery" appear, "xquery version 1.0", or something else? I think the quotes are misplaced. Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37KSfkh013254; Thu, 7 Apr 2005 13:28:41 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j37KSfd3013253; Thu, 7 Apr 2005 13:28:41 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by above.proper.com (8.12.11/8.12.9) with SMTP id j37KSeGc013242 for ; Thu, 7 Apr 2005 13:28:41 -0700 (PDT) (envelope-from derhoermi@gmx.net) Received: (qmail invoked by alias); 07 Apr 2005 20:28:34 -0000 Received: from dsl-084-056-238-149.arcor-ip.net (EHLO localhost) [84.56.238.149] by mail.gmx.net (mp030) with SMTP; 07 Apr 2005 22:28:34 +0200 X-Authenticated: #723575 From: Bjoern Hoehrmann To: Liam Quin Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: Re: W3C Last Call and Media Type request for comments: XQuery and XQueryX Date: Thu, 07 Apr 2005 22:28:58 +0200 Message-ID: <425b93d4.13001640@smtp.bjoern.hoehrmann.de> References: <20050407200151.GN1785@w3.org> In-Reply-To: <20050407200151.GN1785@w3.org> X-Mailer: Forte Agent 1.92/32.572 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: * Liam Quin wrote: >I.2 Registration of MIME Media Type application/xquery >Optional parameters: charset > >The syntax of XQuery is expressed in Unicode but may be written with any >Unicode-compatible character encoding, including UTF-8 or UTF-16, or >transported as US-ASCII or Latin-1 with Unicode characters outside the >range of the given encoding represented using an XML-style ෝ >syntax. >If an XQuery document contains an encoding declaration, it overrides the >default encoding specified by the MIME charset parameter. That's inconsistent with pretty much all other media types that allow a charset parameter. What's the point of having a charset parameter here? >I.5 Charset Default Rules > >XQuery documents use the Unicode character set and, by default, the >UTF-8 encoding. That's incorrect then, it defaults to the character encoding specified in the charset parameter (which then defaults to UTF-8). >I.6 Security Considerations > >Queries written in XQuery may cause arbitrary URIs to be dereferenced. >Therefore, the security issues of [Uniform Resource Locators (URL)] >Section 6 should be considered. In addition, the contents of file: URIs >can in some cases be accessed, processed and returned as results. > >Furthermore, because the XQuery language permits extensions, it is >possible that application/xquery may describe content that has security >implications beyond those described here. > >The XML Query Working group is working on a facility to allow XQuery >expressions to be used to create and update persistent data. Untrusted >queries should not be given write access to data. Compared to http://www.ietf.org/rfc/rfc2046.txt section 4.5.2 this seems very incomplete... >**** Registration for application/xquery+xml also at [4] > >C The application/xquery+xml Media Type (Non-Normative) Non-Normative? Is there a normative version of this text? -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37K1rND009911; Thu, 7 Apr 2005 13:01:53 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j37K1r9o009910; Thu, 7 Apr 2005 13:01:53 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from homer.w3.org (homer.w3.org [128.30.52.30]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j37K1qHg009902 for ; Thu, 7 Apr 2005 13:01:52 -0700 (PDT) (envelope-from liam@w3.org) Received: by homer.w3.org (Postfix, from userid 16040) id 441BB4EFC7; Thu, 7 Apr 2005 16:01:51 -0400 (EDT) Date: Thu, 7 Apr 2005 16:01:51 -0400 From: Liam Quin To: ietf-types@iana.org Cc: ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: W3C Last Call and Media Type request for comments: XQuery and XQueryX Message-ID: <20050407200151.GN1785@w3.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Feet: bare, comfortable. happy and free! User-Agent: Mutt/1.5.6+20040907i Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: [ Notes: (1) - I'm trying to follow a new procedure here. Becasue not everything is in place, the documents I refer to probably don't have perfect wording. The documentation on the process was released after the documents were frozen for Last Call, but we can make any needed changes for the next round of publication. I see that we failed to define the correct syntax for parameters, and would welcome comments on any other areas wheer we need to improve. (2) The following text will be inserted in the next published versions of the documents: This registration is for community review and will be (or has been) submitted to the IESG for review, approval, and registration with IANA. (3) We are using Bugzilla to track comments on these documents; comments on these MIME-related pats of the documents may be made on the ietf-types mailing list or in Bugzilla. See the individual documents and their respective "Status of this Document" sections for further information. - Liam ] In accordance with the draft Media Type Specifications and Registration Procedures [1], and on behalf of the W3C XML Query Working Group [2], I hereby give notice that W3C has published two specifications at the stage "Last Call Working Draft" which each incorporate definitions of a standards-tree MIME media type, as allowed for in section 3.1 of [1], and request comments on these definitions. The types and subtypes are application/xquery defined in "XQuery 1.0: An XML Query Language" [3] optional parameter: charset application/xquery+xml defined in "XML Syntax for XQuery 1.0 (XQueryX)" [4] optional parameter: charset **** Registration for application/xquery also at [3] I The application/xquery Media Type (Non-Normative) --------------------------------------------------- This Appendix specifies the media type for XQuery Version 1.0. XQuery is a language for querying over collections of data from XML data sources, as specified in the main body of this document. I.1 Introduction ---------------- This document, together with its normative references, defines the language XQuery Version 1.0. This Appendix provides information about the application/xquery media type, which is intended to be used for transmitting queries written in the XQuery language. This document was prepared by members of the W3C XML Query Working Group. Please send comments to public-qt-comments [at] w3.org, a public mailing list with archives at http://lists.w3.org/Archives/Public/public-qt-comments. I.2 Registration of MIME Media Type application/xquery ------------------------------------------------------ MIME media type name: application MIME subtype name: xquery Required parameters: none Optional parameters: charset The syntax of XQuery is expressed in Unicode but may be written with any Unicode-compatible character encoding, including UTF-8 or UTF-16, or transported as US-ASCII or Latin-1 with Unicode characters outside the range of the given encoding represented using an XML-style ෝ syntax. I.2.1 Interoperability Considerations None known. I.2.2 Applications Using this Media Type The public XQuery Web page lists more than two dozen implementations of the XQuery language, both proprietary and open source. This new media type is being registered to allow for deployment of XQuery on the World Wide Web. I.2.3 File Extensions The most common file extensions in use for XQuery are .xq and .xquery. The appropriate Macintosh file type code is TEXT. I.2.4 Intended Usage The intended usage of this media type is for interchange of XQuery expressions. I.2.5 Author/Change Controller XQuery was produced by, and is maintained by, the World Wide Web Consortium's XML Query Working Group. The W3C has change control over this specification. I.3 Encoding Considerations For use with transports that are not 8-bit clean, quoted-printable encoding is recommended since the XQuery syntax itself uses the US-ASCII-compatible subset of Unicode. An XQuery document may contain an encoding declaration as part of its version declaration: xquery version "1.0" encoding "utf-8"; If an XQuery document contains an encoding declaration, it overrides the default encoding specified by the MIME charset parameter. I.4 Recognizing XQuery Files An XQuery file may have the string xquery version "V.V" near the beginning of the document, where "V.V" is a version number. Currently the version number, if present, must be "1.0". I.5 Charset Default Rules XQuery documents use the Unicode character set and, by default, the UTF-8 encoding. I.6 Security Considerations Queries written in XQuery may cause arbitrary URIs to be dereferenced. Therefore, the security issues of [Uniform Resource Locators (URL)] Section 6 should be considered. In addition, the contents of file: URIs can in some cases be accessed, processed and returned as results. Furthermore, because the XQuery language permits extensions, it is possible that application/xquery may describe content that has security implications beyond those described here. The XML Query Working group is working on a facility to allow XQuery expressions to be used to create and update persistent data. Untrusted queries should not be given write access to data. **** Registration for application/xquery+xml also at [4] C The application/xquery+xml Media Type (Non-Normative) ------------------------------------------------------- This Appendix specifies the media type for XQueryX Version 1.0. XQueryX is the XML syntax of a language, XQuery, for querying over data from XML data sources, as specified in [XQuery 1.0: An XML Query Language]. C.1 Introduction ---------------- This document, together with its normative references, defines the XML syntax for the XML Query language XQuery Version 1.0. This Appendix specifies the application/xquery+xml media type, which is intended to be used for transmitting queries expressed in the XQueryX syntax. This document was prepared by members of the W3C XML Query Working Group. Please send comments to public-qt-comments [at] w3.org, a public mailing list with archives at http://lists.w3.org/Archives/Public/public-qt-comments. C.2 Registration of MIME Media Type application/xquery+xml MIME media type name: application MIME subtype name: xquery+xml Required parameters: none Optional parameters: charset This parameter has identical semantics to the charset parameter of the application/xml media type as specified in [RFC3023]. C.2.1 Encoding Considerations The considerations as specified in RFC 3023 [XMLMIME] also hold for 'application/xquery+xml'. C.2.2 Fragment Identifiers For documents labeled as 'application/xquery+xml', fragment identifiers are handled as specified in RFC 3023 [XMLMIME]. C.2.3 Restrictions on usage The intended usage of this media type is for interchange of XQueryX expressions. C.2.4 Security Considerations Queries written in XQueryX may cause arbitrary URIs to be dereferenced. Therefore, the security issues of [Uniform Resource Locators (URL)] Section 6 should be considered. In addition, the contents of file: URIs can in some cases be accessed, processed and returned as results. Furthermore, because the XQuery language (and thus the XQueryX language) permits extensions, it is possible that application/xquery+xml may describe content that has security implications beyond those described here. However, if the processor follows only the normative semantics of this specification, this content will be ignored. Only in the case where the processor recognizes and processes the additional content, or where further processing of that content is dispatched to other processors, would security issues arise. The XML Query Working group is working on a facility to allow XQuery (and thus XQueryX) expressions to be used to create and update persistent data. Untrusted queries should not be given write access to data. C.2.5 Interoperability Considerations See Section 5 ConformanceXQ. C.2.6 Applications That Use This Media Type The public XQuery Web page lists more than two dozen implementations of the XQuery language, both proprietary and open source. Some of these are known to support XQueryX. This new media type is being registered to allow for deployment of XQueryX on the World Wide Web. There is no experimental, vendor specific, or personal tree predecessor to "application/xquery+xml", reflecting the fact that no applications currently recognize it. This new type is being registered in order to allow for the expected deployment of XQueryX 1.0 on the World Wide Web, as a first class XML application. C.2.7 Additional Information C.2.7.1 Recognizing XQuery Files ("Magic Numbers") Although no byte sequences can be counted on to consistently identify XQueryX, XQueryX documents will have the sequence "http://www.w3.org/yyyy/mm/XQueryX" to identify the XQueryX namespace (where "yyyy" is exactly four decimal digits and "mm" is exactly two decimal digits). This sequence will normally be found in a namespace attribute of the first element in the document. C.2.7.2 File Extensions The most common file extension in use for XQueryX is .xqx. C.2.7.3 Macintosh File Type Code(s) The appropriate Macintosh file type code is TEXT. C.2.8 Person and Email Address to Contact For Further Information Jim Melton, Oracle Corp., jim.melton [at] oracle.com C.2.9 Intended Usage COMMON C.2.10 Author/Change Controller XQuery was produced by, and is maintained by, the World Wide Web Consortium's XML Query Working Group. The W3C has change control over this specification. [1] http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-02.txt [2] http://www.w3.org/XML/Query [3] http://www.w3.org/TR/2005/WD-xquery-20050404/#id-mime-type [4] http://www.w3.org/TR/2005/WD-xqueryx-20050404/#xqueryx-id-mime-type -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/ Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j35D45N5072603; Tue, 5 Apr 2005 06:04:05 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j35D45O3072602; Tue, 5 Apr 2005 06:04:05 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.132]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j35D43ed072592 for ; Tue, 5 Apr 2005 06:04:03 -0700 (PDT) (envelope-from mccobb@us.ibm.com) Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.195.12]) by e34.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j35D3v5b463260 for ; Tue, 5 Apr 2005 09:03:57 -0400 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by westrelay03.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j35D3vCK180612 for ; Tue, 5 Apr 2005 07:03:57 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j35D3uj2029281 for ; Tue, 5 Apr 2005 07:03:56 -0600 Received: from d03nm120.boulder.ibm.com (d03nm120.boulder.ibm.com [9.17.195.146]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j35D3uoC029278; Tue, 5 Apr 2005 07:03:56 -0600 In-Reply-To: <424ce891.128044187@smtp.bjoern.hoehrmann.de> To: ietf-types@iana.org Cc: ietf-xml-mime@imc.org MIME-Version: 1.0 Subject: Re: Request for comments regarding draft-mccobb-xplusv-media-type-01 X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 Message-ID: From: Gerald McCobb Date: Tue, 5 Apr 2005 09:03:55 -0400 X-MIMETrack: Serialize by Router on D03NM120/03/M/IBM(Release 6.53HF294 | January 28, 2005) at 04/05/2005 07:03:55, Serialize complete at 04/05/2005 07:03:56, Serialize by Router on D03NM120/03/M/IBM(Release 6.53HF294 | January 28, 2005) at 04/05/2005 07:03:56 Content-Type: multipart/alternative; boundary="=_alternative 0047BF0485256FDA_=" Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multipart message in MIME format. --=_alternative 0047BF0485256FDA_= Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable In response to your previous comments (thanks) I submitted=20 draft-mccobb-xplusv-media-type-02.txt to internet-drafts@ietf.org. Please = review and thanks in advance: Network Working Group G. McCobb Internet-Draft IBM Corporation Expires: Oct. 1, 2005 April 1, 2005 XHTML+Voice - application/xhtml+voice+xml draft-mccobb-xplusv-media-type-02 Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance=20 with RFC 3668. 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=20 months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as=20 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. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved Abstract This document describes the registration of the MIME sub-type application/xhtml+voice+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 . 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 [RFC2119]. McCobb Expires Oct. 1, 2005 [Page 1] =0C Internet-Draft XHTML+Voice - application/xhtml+voice+xml April 1, 2005 2. Introduction XHTML+Voice is a member of the XHTML family of document types, as specified by XHTML Modularization [XHTMLMOD]. XHTML+Voice extends XHTML 1.1 [XHTML11] with a modularized subset of VoiceXML 2.0 [VXML20], XML Events [XMLEVNTS], 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 [XPLUSV12] is maintained by the VoiceXML Forum, at URI location . 2.1 application/xhtml+voice+xml Usage The application/xhtml+voice+xml media type is intended to be a media descriptor for XHTML+Voice multimodal documents. Multimodal browsers have special processing requirements for XHTML+Voice documents, such as running a voice browser component, and support for the DOM Level 2 Event Model [DOM2EV] and XML Events [XMLEVNTS]. This media type registration is not intended for email usage. 3. IANA Registration To: ietf-types@iana.org Subject: Registration of Standard MIME media type=20 application/xhtml+voice+xml MIME media type name: application MIME subtype name: xhtml+voice+xml Required parameters: none Optional parameters: charset: has the same semantics as the charset parameter of the "application/xml" media type specified in [RFC3023]. Encoding considerations: 7bit. See section 4 of [RFC3236]. Security considerations: =20 XHTML+Voice is an extension of XHTML and has the same security issues McCobb Expires Oct. 1, 2005 [Page 2] =0C Internet-Draft XHTML+Voice - application/xhtml+voice+xml April 1, 2005 as XHTML. These include interpreting anchors and forms in XHTML documents, and scripting languages and other dynamic interactive capabilities. See section 7 of [RFC3236]. 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 [XPLUSV12]. 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. =20 Published specification: The latest published version of XHTML+Voice is [XPLUSV12]. 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 [XML] processors. See section 2 of [RFC3236]. 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 & email address to contact for further information: Gerald M. McCobb mccobb@us.ibm.com Intended usage: COMMON Author/Change controller: Gerald McCobb Further information: 4. Fragment Identifiers See section 3 of [RFC3236]. Following [RFC3236], fragment McCobb Expires Oct. 1, 2005 [Page 3] =0C Internet-Draft XHTML+Voice - application/xhtml+voice+xml April 1, 2005 identifiers for XHTML+Voice documents designate the element with the corresponding ID attribute value (see [XML] section 3.3.1). While XHTML+Voice adds new ID attributes with fragment identifier namespaces that are not in the same namespace as XHTML, the fragment identifiers are processed in the same namespace as the ID attribute's namespace. 5. Recognizing XHTML+Voice files Because XHTML+Voice is XML, an XHTML+Voice document [optionally] starts with an XML declaration which begins with " =20 Because XHTML+Voice is in the XHTML family of languages, the root element of an XHTML+Voice document is 'html' and ' (or ). [XHTMLMOD] "Modularization of XHTML," 10 April, 2001, Murray Altheim, Frank Boumphrey, Sam Dooley, et al, W3C Recommendation,=20 http://www.w3.org/TR/xhtml-modularization/ McCobb Expires Oct. 1, 2005 [Page 4] =0C Internet-Draft XHTML+Voice - application/xhtml+voice+xml April 1, 2005 [XHTML11] "XHTML 1.1 - Module-based XHTML," 31 May 2001, Murray=20 Altheim, Shane McCarron, W3C Recommendation, http://www.w3.org/TR/xhtml11/. [DOM2EV] "Document Object Model Level 2 Events Specification,"=20 Tom Pixley, 2000. W3C Recommendation, http://www.w3.org/TR/DOM-Level-2-Events/. [XMLEVNTS] "XML Events - An events syntax for XML", Steven Pemberton, T. V. Raman, and Shane McCarron, 2002. W3C Recommendation, http://www.w3.org/TR/xml-events/. [XPLUSV12] "XHTML+Voice Profile 1.2," 16 March 2004, J. Axelsson, et al, http://www.voicexml.org/specs/multimodal/x+v/12/ [VXML20] "Voice Extensible Markup Language (VoiceXML)," 16 March 2004, Scott McGlashan et al, W3C Recommendation, http://www.w3.org/TR/voicexml20/. 8. Authors' Address Gerald M. McCobb IBM Corporation 8051 Congress Avenue, Office 2019 Boca Raton, Florida 33487 USA Phone: +1-561-862-2109 Fax: +1-561-862-3922 EMail: mccobb@us.ibm.com 9. Full Copyright Statement Copyright (C) The Internet Society (2004). 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. This document and the information contained herein are provided on=20 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE=20 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR=20 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF=20 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED=20 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any McCobb Expires Oct. 1, 2005 [Page 5] =0C Internet-Draft XHTML+Voice - application/xhtml+voice+xml April 1, 2005 Intellectual Property Rights or other rights that might be claimed=20 to pertain to the implementation or use of the technology described=20 in this document or the extent to which any license under such=20 rights might or might not be available; nor does it represent that=20 it has made any independent effort to identify any such rights.=20 Information on the procedures with respect to rights in RFC=20 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=20 specification can be obtained from the IETF on-line IPR repository=20 at http://www.ietf.org/ipr.=20 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 ietf- ipr@ietf.org. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Mccobb Expires May 15, 2005 [Page 6] Regards, Gerald McCobb IBM 8051 Congress Avenue Boca Raton, FL 33487 Tel. # 561-862-2109 T/L 975-2109 Bjoern Hoehrmann 03/26/2005 06:06 PM =20 To: Gerald McCobb/Boca Raton/IBM@IBMUS cc: ietf-types@iana.org, ietf-xml-mime@imc.org Subject: Re: Request for comments regarding=20 draft-mccobb-xplusv-media-type-01 * Gerald McCobb wrote: >2.1 application/xhtml+voice+xml Usage > > The application/xhtml+voice+xml media type is intended to be a media > descriptor for XHTML+Voice documents. > > This media type registration is not intended for email usage. The draft does not really explain why there is a need for such a type in the first place; why don't you use application/xhtml+xml? > Optional parameters: > version: refers to the XHTML+Voice language version in the document. > Acceptable values are 1.0, 1.1, and 1.2 (default). What are the processing requirements for this parameter? > charset: has the same meaning as the text/html media type. See > section 2 of [RFC 2854]. A word seems to be missing here. It is not really clear why the draft refers to RFC 2854 rather than RFC 3023 or RFC 3236.=20 > Security considerations: >=20 > XHTML+Voice is an extension of XHTML and has the same security issues > as XHTML. These include interpreting anchors and forms in HTML > documents, and scripting languages and other dynamic interactive > capabilities. See section 7 of [RFC 2854]. So the extensions to XHTML have no security considerations? > File extension(s): html, htm, mxml, xvml I don't think .html and .htm should be listed here, they are already in common use for application/xhtml+xml and text/html. >4. Fragment Identifiers > > See section 3 of [RFC 2854]. It is unclear what this means, RFC 2854 and RFC 3236 have inconsistent rules for fragment identifiers and XHTML+Voice adds new ID attributes so that the fragment identifier namespaces are different. >6. Security Considerations > > Security considerations for this media type are discussed in the MIME > type registration that appears in section 4. Section 4 has no security considerations... >7. References The draft should be clear about which of these references are informative and which normative. --=20 Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehrma= nn.de Weinh. Str. 22 =B7 Telefon: +49(0)621/4309674 =B7 http://www.bjoernsworld.de 68309 Mannheim =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.de/= =20 --=_alternative 0047BF0485256FDA_= Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
In response to your previous commen= ts (thanks) I submitted draft-mccobb-xplusv-media-type-02.txt to internet-draf= ts@ietf.org.  Please review and thanks in advance:


Network Working Group                                          G. McCobb
Internet-Draft                                           IBM Corporation
Expires: Oct. 1, 2005                                      April 1, 2005


                XHTML+Voice - application/xhtml+voice+xml
                    draft-mccobb-xplusv-media-type-02


Status of this Memo

   By submitting this Int= ernet-Draft, I certify that any applicable
   patent or other IPR cl= aims of which I am aware have been disclosed,
   and any of which I bec= ome aware will be disclosed, in accordance
   with RFC 3668.

   Internet-Drafts are wo= rking 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 dr= aft documents valid for a maximum of six
   months and may be upda= ted, 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 In= ternet-Drafts can be accessed at
   http://www.ietf.org/ie= tf/1id-abstracts.txt.

   The list of Internet-D= raft Shadow Directories can be accessed at
   http://www.ietf.org/sh= adow.html.

Copyright Notice

   Copyright (C) The Inte= rnet Society (2004).  All Rights Reserved

Abstract

   This document describes the registration of the MIME sub-type
   application/xhtml+voic= e+xml.  This sub-type is intended for use as a
   media descriptor for X= HTML+Voice multimodal language documents.  The
   XHTML+Voice 1.2 langua= ge specification is maintained by the VoiceXML
   Forum at <http://ww= w.voicexml.org/specs/multimodal/x+v/12/>.

1.  Conventions used in this d= ocument

   The key words "MU= ST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", &q= uot;SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL&quo= t; in this
   document are to be int= erpreted as described in BCP 14, RFC 2119
   [RFC2119].



McCobb                   Expires Oct. 1, 2005                   [Page 1]
=0C
Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005


2. Introduction

   XHTML+Voice is a member of the XHTML family of document types, as
   specified by XHTML Mod= ularization [XHTMLMOD].  XHTML+Voice extends
   XHTML 1.1 [XHTML11] wi= th a modularized subset of VoiceXML 2.0
   [VXML20], XML Events [= XMLEVNTS], and a few extensions to both XHTML
   and VoiceXML 2.0. &nbs= p;XHTML 1.1, VoiceXML 2.0 and XML Events are W3C
   Recommendations.

   The language integrati= on defined by XHTML+Voice supports all modules
   defined by XHTML Modul= arization, and adds voice interaction to XHTML
   elements to enable mul= timodal applications.  The defined document
   type for XHTML+Voice is XHTML Host language document type conformant.

   XHTML+Voice 1.2 [XPLUS= V12] is maintained by the VoiceXML Forum, at
   URI location <http:= //www.voicexml.org/specs/multimodal/x+v/12/>.

2.1 application/xhtml+voice+xml Usa= ge

   The application/xhtml+= voice+xml media type is intended to be a media
   descriptor for XHTML+V= oice multimodal documents. Multimodal browsers
   have special processing requirements for XHTML+Voice documents, such
   as running a voice bro= wser component, and support for the DOM Level
   2 Event Model [DOM2EV] and XML Events [XMLEVNTS].

   This media type regist= ration is not intended for email usage.

3. IANA Registration

      To: ietf-types= @iana.org
      Subject: Regis= tration of Standard MIME media type
               application/xhtml+voice+xml

      MIME media type name: application

      MIME subtype n= ame: xhtml+voice+xml

      Required param= eters: none

      Optional param= eters:

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

      Encoding consi= derations: 7bit.  See section 4 of [RFC3236].

      Security consi= derations:
 
   XHTML+Voice is an exte= nsion of XHTML and has the same security issues


McCobb                   Expires Oct. 1, 2005                   [Page 2]
=0C
Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005

   as XHTML.  These include interpreting anchors and forms in XHTML
   documents, and scripti= ng languages and other dynamic interactive
   capabilities.  See section 7 of [RFC3236].

   In addition, the scrip= ting language can be accessed by both the XHTML
   and the VoiceXML 2.0 m= arkup embedded in the XHTML+Voice document.
   See section 1.3.1.5 of [XPLUSV12].

      Interoperabili= ty considerations :

   Because XHTML+Voice is built upon W3C standard recommendations, it is
   designed to be interop= erable 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 speci= fication:

         T= he latest published version of XHTML+Voice is [XPLUSV12].

      Applications w= hich use this media type:

         X= HTML+Voice documents are intended to be deployed on the World
         W= ide Web and rendered by multimodal browsers that support the
         v= isual and voice modes of interaction.  Because XHTML+Voice is
         an application of XML, authors can expect XHTML+Voice user
         a= gents to be conformant XML 1.0 [XML] processors.  See section
         2 of [RFC3236].

      Additional inf= ormation:

         M= agic number(s):  There is no single string that is always
             present.
         F= ile extension(s): mxml, xhvml, xvml, xvm
         M= acintosh File Type Code(s): TEXT

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

         G= erald M. McCobb
         m= ccobb@us.ibm.com

      Intended usage: COMMON

      Author/Change controller: Gerald McCobb

      Further inform= ation:

4. Fragment Identifiers

   See section 3 of [RFC3= 236].  Following [RFC3236], fragment


McCobb                   Expires Oct. 1, 2005                   [Page 3]
=0C
Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005

   identifiers for XHTML+= Voice documents designate the element with the
   corresponding ID attri= bute value (see [XML] section 3.3.1).

   While XHTML+Voice adds new ID attributes with fragment identifier
   namespaces that are not in the same namespace as XHTML, the fragment
   identifiers are proces= sed in the same namespace as the ID attribute's
   namespace.

5. Recognizing XHTML+Voice files

   Because XHTML+Voice is XML, an XHTML+Voice document [optionally]
   starts with an XML dec= laration which begins with "<?xml" and has a
   DOCTYPE declaration &q= uot;<!DOCTYPE html".  XHTML+Voice 1.2 has the
   following DOCTYPE decl= aration:
 
   <!DOCTYPE html PUBL= IC "-//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+Vo= ice document is 'html' and '<html' can be found
   near the top of the do= cument.  

6. Security Considerations

   Security considerations for this media type are discussed in the MIME
   type registration that appears in section 3.

7. Normative References

   [RFC2119]  Bradne= r, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2396]  Berner= s-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifiers (URI): Generic Syntax", RFC 2396,
              August 1998.

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

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

   [XML]     &n= bsp;"Extensible Markup Language (XML) 1.0", W3C
              Recommendation.  Available at <http://www.w3.org/TR/R= EC-
              xml> (or <http://www.w3.org/TR/2000/REC-xml-20001006>= ;).

   [XHTMLMOD] "Modul= arization of XHTML," 10 April, 2001, Murray Altheim,
              Frank Boumphrey, Sam Dooley, et al, W3C Recommendation,
              http://www.w3.org/TR/xhtml-modularization/



McCobb                   Expires Oct. 1, 2005                   [Page 4]
=0C
Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005


   [XHTML11]  "= XHTML 1.1 - Module-based XHTML," 31 May 2001, Murray
              Altheim, Shane McCarron, W3C Recommendation,
              http://www.w3.org/TR/xhtml11/.

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

   [XMLEVNTS] "XML E= vents - An events syntax for XML", Steven
              Pemberton, T. V. Raman, and Shane McCarron, 2002.  W3C
              Recommendation, http://www.w3.org/TR/xml-events/.
   [XPLUSV12] "XHTML= +Voice Profile 1.2," 16 March 2004, J. Axelsson,
              et al, http://www.voicexml.org/specs/multimodal/x+v/12/

   [VXML20]   "= Voice Extensible Markup Language (VoiceXML)," 16 March
              2004, Scott McGlashan et al, W3C Recommendation,
              http://www.w3.org/TR/voicexml20/.

8. Authors' Address

   Gerald M. McCobb
   IBM Corporation
   8051 Congress Avenue, Office 2019
   Boca Raton, Florida 33= 487
   USA

   Phone: +1-561-862-2109=
   Fax:   +1-561-862= -3922
   EMail: mccobb@us.ibm.c= om


9. Full Copyright Statement

   Copyright (C) The Inte= rnet Society (2004).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth th= erein, the authors retain all their rights.

   This document and the information contained herein are provided on
   an "AS IS" b= asis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
   REPRESENTS OR IS SPONS= ORED BY (IF ANY), THE INTERNET SOCIETY AND THE
   INTERNET ENGINEERING T= ASK 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 MERCHANT= ABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

   Intellectual Property<= /font>

   The IETF takes no posi= tion regarding the validity or scope of any



McCobb                   Expires Oct. 1, 2005                   [Page 5]
=0C
Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005



   Intellectual Property Rights or other rights that might be claimed
   to pertain to the impl= ementation 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 indepe= ndent effort to identify any such rights.  
   Information on the pro= cedures with respect to rights in RFC
   documents can be found in BCP 78 and BCP 79.

   Copies of IPR disclosu= res 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 ri= ghts by implementers or users of this
   specification can be o= btained from the IETF on-line IPR repository
   at http://www.ietf.org= /ipr.  

   The IETF invites any i= nterested 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.  P= lease address the information to the IETF at ietf-
   ipr@ietf.org.

Acknowledgement

   Funding for the RFC Ed= itor function is currently provided by the
   Internet Society.

























Mccobb                   Expires May 15, 2005                   [Page 6]

Regards,
Gerald McCobb
IBM
8051 Congress Avenue
Boca Raton, FL 33487
Tel. # 561-862-2109 T/L 975-2109


Bjoern Hoehrmann <derhoermi@gm= x.net>

03/26/2005 06:06 PM

       
        To:        Gerald McCobb/Boca Raton/IBM@IBMUS
        cc:        ietf-types@iana.org, ietf-xml-mime@imc.org
        Subject:        Re: Request for comments regarding draft-mccobb-= xplusv-media-type-01



* Gerald McCobb wrote:
>2.1 application/xhtml+voice+xml Usage
>
>   The application/xhtml+voice+xml media type is intended to be a media
>   descriptor for XHTML+Voice documents.
>
>   This media type registration is not intended for email usage.
The draft does not really explain why there is a need for such a
type in the first place; why don't you use application/xhtml+xml?

>      Optional parameters:
>   version:  refers to the XHTML+Voice language version in the document.
>             Acceptable values are 1.0, 1.1, and 1.2 (default).

What are the processing requirements for this parameter?

>   charset:  has the same meaning as the text/html media type.  See
>   section 2 of [RFC 2854].

A word seems to be missing here. It is not really clear why the draft
refers to RFC 2854 rather than RFC 3023 or RFC 3236.

>      Security considerations:
>
>   XHTML+Voice is an extension of XHTML and has the same security issues
>   as XHTML.  These include interpreting anchors and forms in HTML
>   documents, and scripting languages and other dynamic interactiv= e
>   capabilities.  See section 7 of [RFC 2854].

So the extensions to XHTML have no security considerations?

>         File extension(s): html, htm, mxml, xvml
I don't think .html and .htm should be listed here, they are already in
common use for application/xhtml+xml and text/html.

>4. Fragment Identifiers
>
>   See section 3 of [RFC 2854].

It is unclear what this means, RFC 2854 and RFC 3236 have inconsistent
rules for fragment identifiers and XHTML+Voice adds new ID attributes
so that the fragment identifier namespaces are different.

>6. Security Considerations
>
>   Security considerations for this media type are discussed in the MIME
>   type registration that appears in section 4.

Section 4 has no security considerations...

>7. References

The draft should be clear about which of these references are
informative and which normative.
--
Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehrma= nn.de
Weinh. Str. 22 =B7 Telefon: +49(0)621/4309674 =B7 http://www.bjoernsworld.d= e
68309 Mannheim =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.de/

--=_alternative 0047BF0485256FDA_=-- Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j34C3C8w004576; Mon, 4 Apr 2005 05:03:12 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j34C3CBv004575; Mon, 4 Apr 2005 05:03:12 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from homer.w3.org (homer.w3.org [128.30.52.30]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j34C3A7r004559 for ; Mon, 4 Apr 2005 05:03:11 -0700 (PDT) (envelope-from mf@w3.org) Received: from localhost.localdomain (homer.w3.org [128.30.52.30]) by homer.w3.org (Postfix) with ESMTP id 8E0BB4F208; Mon, 4 Apr 2005 08:03:07 -0400 (EDT) From: Max Froumentin To: ietf-types@iana.org Subject: please review draft-froumentin-voice-mediatypes-00 Organization: World Wide Web Consortium - http://www.w3.org Cc: ietf-xml-mime@imc.org, w3t-archive@w3.org Date: Mon, 04 Apr 2005 13:02:36 +0100 Message-ID: <87acoe3g2r.fsf@w3.org> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id j34C3B7r004567 Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: draft-froumentin-voice-mediatypes-00 contains the registration of the 6 media types of the W3C Speech Interface Framework (including the following specifications: SSML, SRGS, CCXML, PLS and VoiceXML) Draft available at http://www.ietf.org/internet-drafts/draft-froumentin-voice-mediatypes-00.txt and copied below. Max Froumentin, W3C Network Working Group M. Froumentin Internet-Draft W3C Expires: September 2, 2005 March 2005 The W3C Speech Interface Framework Media Types: application/voicexml+xml, application/ssml+xml, application/srgs, application/srgs+xml, application/ccxml+xml and application/pls+xml draft-froumentin-voice-mediatypes-00 Status of this Memo This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. 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 become aware will be disclosed, in accordance with RFC 3668. 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 September 2, 2005. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This document defines the media type for the languages of the W3C Speech Interface Framework: VoiceXML, SSML, SRGS, CCXML and PLS. Froumentin Expires September 2, 2005 [Page 1] Internet-Draft W3C Speech Interface Framework Media Types March 2005 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Registration of application/voicexml+xml, application/ssml+xml, application/srgs+xml, application/ccxml+xml and application/pls+xml . . . . . . . . 4 2.1 Encoding considerations . . . . . . . . . . . . . . . . . 4 2.2 Interoperability considerations . . . . . . . . . . . . . 4 2.3 Published specifications . . . . . . . . . . . . . . . . . 4 2.4 Applications which use these media types . . . . . . . . . 4 2.5 Security Considerations . . . . . . . . . . . . . . . . . 4 2.6 Additional Information . . . . . . . . . . . . . . . . . . 5 2.6.1 Magic numbers . . . . . . . . . . . . . . . . . . . . 5 2.6.2 File extensions . . . . . . . . . . . . . . . . . . . 5 2.6.3 Fragment identifiers . . . . . . . . . . . . . . . . . 5 2.6.4 Macintosh File Type Code . . . . . . . . . . . . . . . 5 2.6.5 Person & email address to contact for further information . . . . . . . . . . . . . . . . . . . . . 5 2.6.6 Intended usage . . . . . . . . . . . . . . . . . . . . 5 2.6.7 Change Controller . . . . . . . . . . . . . . . . . . 5 3. Registration of application/srgs . . . . . . . . . . . . . . . 7 3.1 Encoding considerations . . . . . . . . . . . . . . . . . 7 3.2 Interoperability considerations . . . . . . . . . . . . . 7 3.3 Published specifications . . . . . . . . . . . . . . . . . 7 3.4 Applications which use this media types . . . . . . . . . 7 3.5 Security Considerations . . . . . . . . . . . . . . . . . 7 3.6 Additional Information . . . . . . . . . . . . . . . . . . 7 3.6.1 Magic numbers . . . . . . . . . . . . . . . . . . . . 7 3.6.2 File extensions . . . . . . . . . . . . . . . . . . . 8 3.6.3 Macintosh File Type Code . . . . . . . . . . . . . . . 8 3.6.4 Person & email address to contact for further information . . . . . . . . . . . . . . . . . . . . . 8 3.6.5 Intended usage . . . . . . . . . . . . . . . . . . . . 8 3.6.6 Change Controller . . . . . . . . . . . . . . . . . . 8 4. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 9 Intellectual Property and Copyright Statements . . . . . . . . 10 Froumentin Expires September 2, 2005 [Page 2] Internet-Draft W3C Speech Interface Framework Media Types March 2005 1. Introduction This specification defines the media types of the VoiceXML, SSML, SRGS, CCXML and PLS, the specifications of the W3C Speech Interface Platform VoiceXML is an XML language designed for creating audio dialogs that feature synthesized speech, digitized audio, recognition of spoken and DTMF key input, recording of spoken input, telephony, and mixed initiative conversations. The associated media type defined in this document is "application/voicexml+xml". The Speech Synthesis Markup Language Specification (SSML) defines an XML-based markup language for assisting the generation of synthetic speech in Web and other applications. The essential role of SSML is to provide authors of synthesizable content a standard way to control aspects of speech such as pronunciation, volume, pitch, rate, etc. across different synthesis-capable platforms. The asociated media type defined in this document is "application/ssml+xml". The Speech Recognition Grammar Specification (SRGS) defines syntax for representing grammars for use in speech recognition so that developers can specify the words and patterns of words to be listened for by a speech recognizer. The syntax of the grammar format exists in two forms, an Augmented BNF Form and an XML Form. The respective media types defined in this document are "application/srgs" and "application/srgs+xml". The Call Control eXtensible Markup Language (CCXML) is an XML language designed to provide telephony call control support for dialog systems, such as VoiceXML. The associated media type defined in this document is "application/ccxml+xml". The Pronunciation Lexicon Specification (PLS) defines an XML syntax for specifying pronunciation lexicons to be used by speech recognition and speech synthesis engines in voice browser applications. The associated media type defined in this document is "application/pls+xml". Froumentin Expires September 2, 2005 [Page 3] Internet-Draft W3C Speech Interface Framework Media Types March 2005 2. Registration of application/voicexml+xml, application/ssml+xml, application/srgs+xml, application/ccxml+xml and application/pls+xml MIME media type name: application MIME subtype names: voicexml+xml, ssml+xml, srgs+xml, ccxml+xml, pls+xml Required parameters: none Optional parameters: "charset": This parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in RFC 3023 [RFC3023]. 2.1 Encoding considerations Identical to those of "application/xml" as described in RFC 3023 [RFC3023], section 3.2 2.2 Interoperability considerations There are no known interoperability issues. 2.3 Published specifications Voice Extensible Markup Language 2.0 [VoiceXML2.0] Voice Extensible Markup Language 2.1 [VoiceXML2.1] Speech Synthesis Markup Language (SSML) Version 1.0 [SSML] Speech Recognition Grammar Specification Version 1.0 [SRGS] Voice Browser Call Control: CCXML Version 1.0 [CCXML] Pronunciation Lexicon Specification (PLS) Version 1.0 [PLS] 2.4 Applications which use these media types Various W3C Speech Interface Platform implementations use these media types 2.5 Security Considerations Several instructions in the cited specifications may cause arbitrary URIs to be dereferenced. In this case, the security issues of [RFC2396], section 7, should be considered. In addition, because of the extensibility features of those specifications, it is possible that the registered media types may describe content that has security implications beyond those described here. However, if the processor follows only the normative semantics of the specifications, this content will be ignored. Only in the case where the processor recognizes and processes the additional content, or where further processing of that content is Froumentin Expires September 2, 2005 [Page 4] Internet-Draft W3C Speech Interface Framework Media Types March 2005 dispatched to other processors, would security issues potentially arise. And in that case, they would fall outside the domain of this registration document. 2.6 Additional Information 2.6.1 Magic numbers Although no byte sequences can be counted on to always be present, XML MIME entities in ASCII-compatible charsets (including UTF-8) often begin with hexadecimal 3C 3F 78 6D 6C (" 2.6.6 Intended usage COMMON 2.6.7 Change Controller The Speech Interface Framework specifications set is a work product of the World Wide Web Consortium's Voice Browser Working Group. The Froumentin Expires September 2, 2005 [Page 5] Internet-Draft W3C Speech Interface Framework Media Types March 2005 W3C has change control over these specifications. Froumentin Expires September 2, 2005 [Page 6] Internet-Draft W3C Speech Interface Framework Media Types March 2005 3. Registration of application/srgs MIME media type name: application MIME subtype names: srgs Required parameters: none Optional parameters: none 3.1 Encoding considerations The ABNF Form of SRGS follows the character encoding handling defined for XML: an ABNF grammar processor must accept both the UTF-8 and UTF-16 encodings of ISO/IEC 10646 and may support other character encodings. 3.2 Interoperability considerations There are no known interoperability issues. 3.3 Published specifications Speech Recognition Grammar Specification Version 1.0 [SRGS] 3.4 Applications which use this media types Various SRGS implementations use this media type. 3.5 Security Considerations Several instructions in SRGS may cause arbitrary URIs to be dereferenced. In this case, the security issues of [RFC2396], section 7, should be considered. In addition, because of the extensibility features of SRGS, it is possible that the registered media types may describe content that has security implications beyond those described here. However, if the processor follows only the normative semantics of the specifications, this content will be ignored. Only in the case where the processor recognizes and processes the additional content, or where further processing of that content is dispatched to other processors, would security issues potentially arise. And in that case, they would fall outside the domain of this registration document. 3.6 Additional Information 3.6.1 Magic numbers The ABNF self-identifying header must be present in any legal Froumentin Expires September 2, 2005 [Page 7] Internet-Draft W3C Speech Interface Framework Media Types March 2005 stand-alone ABNF Form grammar document. The first character of an ABNF document must be the "#" symbol (x23) unless preceded by an optional XML 1.0 byte order mark [XML ú4.3.3]. The ABNF byte order mark follows the XML definition and requirements. For example, documents encoded in UTF-16 must begin with the byte order mark. The optional byte order mark and required "#" symbol must be followed immediately by the exact string "ABNF" (x41 x42 x4d x46) or the appropriate equivalent for the document's encoding (e.g. for UTF-16 little-endian: x23 x00 x41 x00 x42 x00 x4d x00 x46 x00). If the byte order mark is absent on a grammar encoded in UTF-16 then the grammar processor should perform auto-detection of character encoding in a manner analogous to auto-detection of character encoding in XML [XML úF]. Next follows a single space character (x20) and the required version number which is "1.0" for this specification (x31 x2e x30). 3.6.2 File extensions .gram 3.6.3 Macintosh File Type Code "TEXT" 3.6.4 Person & email address to contact for further information World Wide Web Consortium 3.6.5 Intended usage COMMON 3.6.6 Change Controller The SRGS specification is a work product of the World Wide Web Consortium's Voice Browser Working Group. The W3C has change control over the SRGS specification. 4. References [CCXML] Auburn, RJ., Ed., "Voice Browser Call Control: CCXML Version 1.0, W3C Working Draft", January 2005, . [PLS] Baggia, P., Ed., "Pronunciation Lexicon Specification (PLS) Version 1.0, W3C Working Draft", February 2005, . Froumentin Expires September 2, 2005 [Page 8] Internet-Draft W3C Speech Interface Framework Media Types March 2005 [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax. IETF RFC 2396", August 1998, . [RFC3023] Murata, M., St.Laurent, S. and D. Kohn, "XML Media Types", January 2001, . [SRGS] Hunt, A., Ed. and S. McGlashan, Ed., "Speech Recognition Grammar Specification Version 1.0, W3C Recommendation", March 2004, . [SSML] Burnett, D., Ed., Walker, M., Ed. and A. Hunt, Ed., "Speech Synthesis Markup Language (SSML) Version 1.0, W3C Recomendation", September 2004, . [VoiceXML2.0] McGlashan, S., Ed., "Voice Extensible Markup Language (VoiceXML) Version 2.0, W3C Recommendation", March 2004, . [VoiceXML2.1] Oshry, M., Ed., "Voice Extensible Markup Language (VoiceXML) Version 2.1, W3C Working Draft", July 2004, . Author's Address Max Froumentin World Wide Web Consortium Froumentin Expires September 2, 2005 [Page 9] Internet-Draft W3C Speech Interface Framework Media Types March 2005 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 ietf-ipr@ietf.org. 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. 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. Froumentin Expires September 2, 2005 [Page 10]