Brad Porter Steph Tryphonas Tellme Networks Inc. June 26, 2002 The 'application/srgs' Media Type draft-porter-srgs-media-reg-01.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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 December 26, 2002. Copyright Notice Copyright (C) The Internet Society (2002). All Rights Reserved. Abstract This document defines the 'application/srgs' media type for the augmented BNF version of the Speech Recognition Grammar Specification. 1. Introduction Speech Recognition Grammar Specification is an augmented BNF based language which defines syntax for representating 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 is presented in two forms, an augmented BNF syntax and an XML syntax. Only the ABNF syntax is discussed here. While not an XML syntax itself, the ABNF syntax of the Speech Recognition Grammar Specification uses the same character set, encoding, and security considerations already established for XML. Feedback or discussion about this draft should be directed to the Voice Browser Working Group public mailing list, www-voice@w3.org with archives at http://lists.w3.org/Archives/Public/www-voice/. 2. Registration of MIME media type application/srgs MIME media type name: application MIME subtype name: srgs Required parameters: none Optional parameters: charset Except for the different syntactic representation, the ABNF grammar format follows the character encoding behavior in XML which is is specified in RFC 3023 [XMLMIME]. ABNF grammar processor must accept both the UTF-8 and UTF-16 encodings of ISO/IEC 10646. 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 character encoding is part of the self-identifying grammar header. The following is an example of an ABNF self-identifying grammar header for SRGS with the an optional character encoding. #ABNF 1.0 ISO-8859-1; Encoding considerations: See Section 4 of this document. Security considerations: See Section 7 of this document. Interoperability considerations: SRGS v1.0 [SRGS1] specifies user agent conformance rules that dictate behaviour that must be followed when dealing with, among other things, unrecognized elements. Published specification: See [SRGS1]. Applications which use this media type: Content authors and developers have already begun hand and tool authoring on the Web with the ABNF form of the Speech Recognition Grammar Specification v1.0. Additional information: Magic number: The first character of an ABNF document version of SRGS following must be the "#" symbol. It must be followed immediately by the exact string "ABNF". Next follows a single space character. These characters must be encoded using the appropriate document encoding as specified by the XML byte-order mark. File extension: .gram Macintosh File Type code: TEXT Person & email address to contact for further information: Steph Tryphonas Brad Porter Intended usage: COMMON Author/Change controller: The SRGS v1.0 specification is a work product of the World Wide Web Consortium's Voice Browser Working Group. The W3C has change control over this specification. 3. Fragment identifiers For documents labeled as 'application/srgs', the fragment identifier notation is exactly that for application/xml, as specified in RFC 3023 [XMLMIME] with the exception that an ABNF rulename acts as an XML ID. 4. Encoding considerations The considerations as specified in RFC 3023 [XMLMIME] also hold for 'application/srgs'. 5. Recognizing ABNF Speech Recognition Grammar Specification All ABNF SRGS files must begin with the characters "#ABNF " encoded in the appropriate document encoding as specified by the preceding optional XML byte-order mark. 6. Charset default rules The considerations as specified in RFC 3023 [XMLMIME] also hold for 'application/srgs'. 7. Security considerations The considerations as specified in RFC 3023 [XMLMIME] also hold for 'application/srgs'. 8. Author's Address Steph Tryphonas Tellme Networks Inc. Mountain View, California 94041 phone:+1-650-930-9000 mailto:s-tryphonas@tellme.com Brad Porter Tellme Networks Inc. Mountain View, California 94041 phone:+1-650-930-9000 mailto:b-porter@tellme.com 9. References [SRGS1] "Speech Recognition Grammar Specification for the W3C Speech Interface Framework", Working Draft 20 August 2001, (or ) [MIME] Freed, N., and Borenstein, N., "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996. [XML] "Extensible Markup Language (XML) 1.0", W3C Recommendation, February 1998. Available at (or ). [XMLMIME] Murata, M., St.Laurent, S., Kohn, D., "XML Media Types", RFC 3023, January 2001. [XMLNAME] Bray, T., Hollander, D. and A. Layman, "Namespaces in XML", January 1999, . A. Full Copyright Statement Copyright (C) The Internet Society (2002). All Rights Reserved This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.