Internet DRAFT - draft-porter-srgsxml-media-reg
draft-porter-srgsxml-media-reg
Brad Porter
Steph Tryphonas
Tellme Networks Inc.
March 11, 2002
The 'application/srgs+xml' Media Type
draft-tryphonas-srgsxml-media-reg-00.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 September 11, 2002.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract
This document defines the 'application/srgs+xml' media type
for the XML version of the Speech Recognition Grammar
Specification.
1. Introduction
The Speech Recognition Grammar Specification defines XML and ABNF
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.
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+xml
MIME media type name: application
MIME subtype name: srgs+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 [XMLMIME].
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 SRGS.
Additional information:
Magic number:
There is no single initial byte sequence that is always present
for XML version of Speech Recognition Grammar Specification files.
See RFC 3023 [XMLMIME] for information pertaining to
the identification of XML media types.
File extension: .grxml
Macintosh File Type code: TEXT
Person & email address to contact for further information:
Steph Tryphonas <s-tryphonas@tellme.com>
Brad Porter <b-porter@tellme.com>
Intended usage: COMMON
Author/Change controller:
The Speech Grammar Recognition 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+xml', the fragment
identifier notation is exactly that for application/xml, as
specified in RFC 3023 [XMLMIME].
4. Encoding considerations
The considerations as specified in RFC 3023 [XMLMIME] also
hold for 'application/srgs+xml'.
5. Recognizing XML version of SRGS
All XML versions of SRGS files will have the string "<grammar" near the beginning
of the file. Some will also begin with an XML declaration
which begins with "<?xml", though that alone does not indicate
an SRGS document.
All XML versions of SRGS files may also include a declaration of the SRGS
namespace. This should appear shortly after the string
"<grammar", and should read 'xmlns="http://www.w3.org/2001/06/grammar"'.
6. Charset default rules
The considerations as specified in RFC 3023 [XMLMIME] also
hold for 'application/srgs+xml'.
7. Security considerations
The considerations as specified in RFC 3023 [XMLMIME] also
hold for 'application/srgs+xml'.
8. Author's Address
Brad Porter
Tellme Networks Inc.
Mountain View, California 94041
phone:+1-650-930-9000
mailto:b-porter@tellme.com
Steph Tryphonas
Tellme Networks Inc.
Mountain View, California 94041
phone:+1-650-930-9000
mailto:s-tryphonas@tellme.com
9. References
[SRGS1] "Speech Recognition Grammar Specification
for the W3C Speech Interface Framework" (work in progress), August 2001,
<http://www.w3.org/TR/2001/WD-speech-grammar-20010820 >
[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 <http://www.w3.org/TR/REC-xml>
(or <http://www.w3.org/TR/2000/REC-xml-20001006>).
[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, <http://www.w3.org/TR/REC-xml-names>.
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.
