idnits 2.17.1 draft-froumentin-voice-mediatypes-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 18. -- Found old boilerplate from RFC 3978, Section 5.1 on line 340. -- Found old boilerplate from RFC 3978, Section 5.5 on line 419. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 396. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 403. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 409. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** An RFC 3978, Section 5.1 paragraph was found, but not on the first page, as required. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 2005) is 6922 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'XML' is mentioned on line 205, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'CCXML' -- Possible downref: Non-RFC (?) normative reference: ref. 'PLS' ** Obsolete normative reference: RFC 2396 (Obsoleted by RFC 3986) ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) -- Possible downref: Non-RFC (?) normative reference: ref. 'SRGS' -- Possible downref: Non-RFC (?) normative reference: ref. 'SSML' Summary: 7 errors (**), 0 flaws (~~), 3 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Froumentin 3 Internet-Draft W3C 4 Expires: November 2, 2005 May 2005 6 The W3C Speech Interface Framework Media Types: application/ 7 voicexml+xml, application/ssml+xml, application/srgs, application/ 8 srgs+xml, application/ccxml+xml and application/pls+xml 9 draft-froumentin-voice-mediatypes-02 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of Section 3 of RFC 3667. By submitting this Internet-Draft, each 15 author represents that any applicable patent or other IPR claims of 16 which he or she is aware have been or will be disclosed, and any of 17 which he or she become aware will be disclosed, in accordance with 18 RFC 3668. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on November 2, 2005. 38 By submitting this Internet-Draft, each author represents that any 39 applicable patent or other IPR claims of which he or she is aware 40 have been or will be disclosed, and any of which he or she becomes 41 aware will be disclosed, in accordance with Section 6 of BCP 79. 43 Copyright Notice 45 Copyright (C) The Internet Society (2005). 47 Abstract 49 This document defines the media types for the languages of the W3C 50 Speech Interface Framework, as designed by the Voice Browser 51 Working Group in the following specifications: the Voice Extensible 52 Markup Language XML, the Speech Synthesis Markup Language (SSML), 53 The Speech Recognition Grammar Specification (SRGS), Call Control 54 XML (CCXML) and the Pronunciation Lexicon Specification (PLS). 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Registration of application/voicexml+xml, 60 application/ssml+xml, application/srgs+xml, 61 application/ccxml+xml and application/pls+xml . . . . . . . . 4 62 2.1 Encoding considerations . . . . . . . . . . . . . . . . . 4 63 2.2 Interoperability considerations . . . . . . . . . . . . . 4 64 2.3 Published specifications . . . . . . . . . . . . . . . . . 4 65 2.4 Applications which use these media types . . . . . . . . . 4 66 2.5 Security Considerations . . . . . . . . . . . . . . . . . 5 67 2.6 Additional Information . . . . . . . . . . . . . . . . . . 5 68 2.6.1 Magic numbers . . . . . . . . . . . . . . . . . . . . 5 69 2.6.2 File extensions . . . . . . . . . . . . . . . . . . . 5 70 2.6.3 Fragment identifiers . . . . . . . . . . . . . . . . . 5 71 2.6.4 Macintosh File Type Code . . . . . . . . . . . . . . . 5 72 2.6.5 Person & email address to contact for further 73 information . . . . . . . . . . . . . . . . . . . . . 6 74 2.6.6 Intended usage . . . . . . . . . . . . . . . . . . . . 6 75 2.6.7 Change Controller . . . . . . . . . . . . . . . . . . 6 76 3. Registration of application/srgs . . . . . . . . . . . . . . . 7 77 3.1 Encoding considerations . . . . . . . . . . . . . . . . . 7 78 3.2 Interoperability considerations . . . . . . . . . . . . . 7 79 3.3 Published specifications . . . . . . . . . . . . . . . . . 7 80 3.4 Applications which use this media types . . . . . . . . . 7 81 3.5 Security Considerations . . . . . . . . . . . . . . . . . 7 82 3.6 Additional Information . . . . . . . . . . . . . . . . . . 8 83 3.6.1 Magic numbers . . . . . . . . . . . . . . . . . . . . 8 84 3.6.2 File extensions . . . . . . . . . . . . . . . . . . . 8 85 3.6.3 Macintosh File Type Code . . . . . . . . . . . . . . . 8 86 3.6.4 Person & email address to contact for further 87 information . . . . . . . . . . . . . . . . . . . . . 8 88 3.6.5 Intended usage . . . . . . . . . . . . . . . . . . . . 8 89 3.6.6 Change Controller . . . . . . . . . . . . . . . . . . 8 90 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 91 5. IPR Disclosure Acknowledgement . . . . . . . . . . . . . . . . 10 92 6. Normative References . . . . . . . . . . . . . . . . . . . . . 10 93 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 11 94 Intellectual Property and Copyright Statements . . . . . . . . 12 96 1. Introduction 98 This specification defines the media types of the VoiceXML, SSML, 99 SRGS, CCXML and PLS, the specifications of the W3C Speech Interface 100 Platform. 102 VoiceXML is an XML language designed for creating audio dialogs that 103 feature synthesized speech, digitized audio, recognition of spoken 104 and DTMF key input, recording of spoken input, telephony, and mixed 105 initiative conversations. The associated media type defined in this 106 document is "application/voicexml+xml". 108 The Speech Synthesis Markup Language Specification (SSML) defines an 109 XML-based markup language for assisting the generation of synthetic 110 speech in Web and other applications. The essential role of SSML is 111 to provide authors of synthesizable content a standard way to control 112 aspects of speech such as pronunciation, volume, pitch, rate, etc. 113 across different synthesis-capable platforms. The asociated media 114 type defined in this document is "application/ssml+xml". 116 The Speech Recognition Grammar Specification (SRGS) defines syntax 117 for representing grammars for use in speech recognition so that 118 developers can specify the words and patterns of words to be listened 119 for by a speech recognizer. The syntax of the grammar format exists 120 in two forms, an Augmented BNF Form and an XML Form. The respective 121 media types defined in this document are "application/srgs" and 122 "application/srgs+xml". 124 The Call Control eXtensible Markup Language (CCXML) is an XML 125 language designed to provide telephony call control support for 126 dialog systems, such as VoiceXML. The associated media type defined 127 in this document is "application/ccxml+xml". 129 The Pronunciation Lexicon Specification (PLS) defines an XML syntax 130 for specifying pronunciation lexicons to be used by speech 131 recognition and speech synthesis engines in voice browser 132 applications. The associated media type defined in this document is 133 "application/pls+xml". 135 2. Registration of application/voicexml+xml, application/ssml+xml, 136 application/srgs+xml, application/ccxml+xml and application/pls+xml 138 MIME media type name: application 140 MIME subtype names: voicexml+xml, ssml+xml, srgs+xml, ccxml+xml, 141 pls+xml 143 Required parameters: none 145 Optional parameters: 147 "charset": This parameter has identical semantics to the 148 charset parameter of the "application/xml" media type as 149 specified in RFC 3023 [RFC3023]. 151 2.1 Encoding considerations 153 Identical to those of "application/xml" as described in RFC 3023 154 [RFC3023], section 3.2. 156 2.2 Interoperability considerations 158 There are no known interoperability issues. 160 2.3 Published specifications 162 Voice Extensible Markup Language 2.0 [VoiceXML2.0] 164 Voice Extensible Markup Language 2.1 [VoiceXML2.1] 166 Speech Synthesis Markup Language (SSML) Version 1.0 [SSML] 168 Speech Recognition Grammar Specification Version 1.0 [SRGS] 170 Voice Browser Call Control: CCXML Version 1.0 [CCXML] 172 Pronunciation Lexicon Specification (PLS) Version 1.0 [PLS] 174 2.4 Applications which use these media types 176 Various W3C Speech Interface Platform implementations use these media 177 types. 179 2.5 Security Considerations 181 Several instructions in the cited specifications may cause arbitrary 182 URIs to be dereferenced. In this case, the security issues of 183 [RFC2396], section 7, should be considered. 185 In addition, because of the extensibility features of those 186 specifications, it is possible that the registered media types may 187 describe content that has security implications beyond those 188 described here. However, if the processor follows only the normative 189 semantics of the specifications, this content will be ignored. Only 190 in the case where the processor recognizes and processes the 191 additional content, or where further processing of that content is 192 dispatched to other processors, would security issues potentially 193 arise. And in that case, they would fall outside the domain of this 194 registration document. 196 2.6 Additional Information 198 2.6.1 Magic numbers 200 Although no byte sequences can be counted on to always be present, 201 XML MIME entities in ASCII-compatible charsets (including UTF-8) 202 often begin with hexadecimal 3C 3F 78 6D 6C (" 232 2.6.6 Intended usage 234 COMMON 236 2.6.7 Change Controller 238 The Speech Interface Framework specifications set is a work product 239 of the World Wide Web Consortium's Voice Browser Working Group. The 240 W3C has change control over these specifications. 242 3. Registration of application/srgs 244 MIME media type name: application 246 MIME subtype names: srgs 248 Required parameters: none 250 Optional parameters: none 252 3.1 Encoding considerations 254 The ABNF Form of SRGS follows the character encoding handling defined 255 for XML: an ABNF grammar processor must accept both the UTF-8 and 256 UTF-16 encodings of ISO/IEC 10646 and may support other character 257 encodings. 259 3.2 Interoperability considerations 261 There are no known interoperability issues. 263 3.3 Published specifications 265 Speech Recognition Grammar Specification Version 1.0 [SRGS] 267 3.4 Applications which use this media types 269 Various SRGS implementations use this media type. 271 3.5 Security Considerations 273 Several instructions in SRGS may cause arbitrary URIs to be 274 dereferenced. In this case, the security issues of [RFC2396], 275 section 7, should be considered. 277 In addition, because of the extensibility features of SRGS, it is 278 possible that the registered media types may describe content that 279 has security implications beyond those described here. However, if 280 the processor follows only the normative semantics of the 281 specifications, this content will be ignored. Only in the case where 282 the processor recognizes and processes the additional content, or 283 where further processing of that content is dispatched to other 284 processors, would security issues potentially arise. And in that 285 case, they would fall outside the domain of this registration 286 document. 288 3.6 Additional Information 290 3.6.1 Magic numbers 292 The ABNF self-identifying header must be present in any legal stand- 293 alone ABNF Form grammar document. The first character of an ABNF 294 document must be the "#" symbol (x23) unless preceded by an optional 295 XML 1.0 byte order mark. The ABNF byte order mark follows the XML 296 definition and requirements. For example, documents encoded in 297 UTF-16 must begin with the byte order mark. The optional byte order 298 mark and required "#" symbol must be followed immediately by the 299 exact string "ABNF" (x41 x42 x4d x46) or the appropriate equivalent 300 for the document's encoding (e.g. for UTF-16 little-endian: x23 x00 301 x41 x00 x42 x00 x4d x00 x46 x00). If the byte order mark is absent 302 on a grammar encoded in UTF-16 then the grammar processor should 303 perform auto-detection of character encoding in a manner analogous to 304 auto-detection of character encoding in XML. Next follows a single 305 space character (x20) and the required version number which is "1.0" 306 for this specification (x31 x2e x30). 308 3.6.2 File extensions 310 .gram 312 3.6.3 Macintosh File Type Code 314 "TEXT" 316 3.6.4 Person & email address to contact for further information 318 World Wide Web Consortium 320 3.6.5 Intended usage 322 COMMON 324 3.6.6 Change Controller 326 The SRGS specification is a work product of the World Wide Web 327 Consortium's Voice Browser Working Group. The W3C has change control 328 over the SRGS specification. 330 4. IANA Considerations 332 This document calls for registration of six new MIME media types, 333 according to the registrations in Section 2 and Section 3. 335 5. IPR Disclosure Acknowledgement 337 By submitting this Internet-Draft, each author represents that any 338 applicable patent or other IPR claims of which he or she is aware 339 have been or will be disclosed, and any of which he or she becomes 340 aware will be disclosed, in accordance with Section 6 of BCP 79. 342 6. Normative References 344 [CCXML] Auburn, RJ., Ed., "Voice Browser Call Control: CCXML 345 Version 1.0, W3C Working Draft", January 2005, 346 . 348 [PLS] Baggia, P., Ed., "Pronunciation Lexicon Specification 349 (PLS) Version 1.0, W3C Working Draft", February 2005, 350 . 353 [RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 354 Resource Identifiers (URI): Generic Syntax. IETF RFC 355 2396", August 1998, . 357 [RFC3023] Murate, M., St.Laurent, S., and D. Kohn, "XML Media 358 Types", January 2001, 359 . 361 [SRGS] Hunt, A., Ed. and S. McGlashan, Ed., "Speech Recognition 362 Grammar Specification Version 1.0, W3C Recommendation", 363 March 2004, 364 . 366 [SSML] Burnett, D., Ed., Walker, M., Ed., and A. Hunt, Ed., 367 "Speech Synthesis Markup Language (SSML) Version 1.0, W3C 368 Recomendation", September 2004, 369 . 372 [VoiceXML2.0] 373 McGlashan, S., Ed., "Voice Extensible Markup Language 374 (VoiceXML) Version 2.0, W3C Recommendation", March 2004, 375 . 377 [VoiceXML2.1] 378 Oshry, M., Ed., "Voice Extensible Markup Language 379 (VoiceXML) Version 2.1, W3C Working Draft", July 2004, 380 . 382 Author's Address 384 Max Froumentin 385 World Wide Web Consortium 387 Intellectual Property Statement 389 The IETF takes no position regarding the validity or scope of any 390 Intellectual Property Rights or other rights that might be claimed to 391 pertain to the implementation or use of the technology described in 392 this document or the extent to which any license under such rights 393 might or might not be available; nor does it represent that it has 394 made any independent effort to identify any such rights. Information 395 on the procedures with respect to rights in RFC documents can be 396 found in BCP 78 and BCP 79. 398 Copies of IPR disclosures made to the IETF Secretariat and any 399 assurances of licenses to be made available, or the result of an 400 attempt made to obtain a general license or permission for the use of 401 such proprietary rights by implementers or users of this 402 specification can be obtained from the IETF on-line IPR repository at 403 http://www.ietf.org/ipr. 405 The IETF invites any interested party to bring to its attention any 406 copyrights, patents or patent applications, or other proprietary 407 rights that may cover technology that may be required to implement 408 this standard. Please address the information to the IETF at 409 ietf-ipr@ietf.org. 411 Disclaimer of Validity 413 This document and the information contained herein are provided on an 414 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 415 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 416 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 417 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 418 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 419 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 421 Copyright Statement 423 Copyright (C) The Internet Society (2005). This document is subject 424 to the rights, licenses and restrictions contained in BCP 78, and 425 except as set forth therein, the authors retain all their rights. 427 Acknowledgment 429 Funding for the RFC Editor function is currently provided by the 430 Internet Society.