Copyright ©2007 W3C® (MIT , ERCIM , Keio), All Rights Reserved. W3C liability, trademark, document use, and software licensing rules apply.
This document details the responses made by the Voice Browser Working Group to issues raised during the Call for Implementations (beginning 11 January 2006 and ending 20 February 2006) and subsequently including the second Last Call (beginning 4 November 2006 and ending 24 November 2006) review of Semantic Interpretation for Speech Recognition (SISR) Version 1.0. Comments were provided by Voice Browser Working Group members, other W3C Working Groups, and the public via the www-voice-request@w3.org (archive) mailing list.
This document of the W3C's Voice Browser Working Group describes the disposition of comments as of 22nd January 2007 on both the Candidate Recommendation and Last Call Working Draft of Semantic Interpretation for Speech Recognition (SISR) Version 1.0. It may be updated, replaced or rendered obsolete by other W3C documents at any time.
For background on this work, please see the Voice Browser Activity Statement.
This document describes the disposition of comments in relation to the Candidate Recommendation and Last Call Working Draft versions of Semantic Interpretation for Speech Recognition (SISR) Version 1.0 (http://www.w3.org/TR/2006/CR-semantic-interpretation-20060111/ and http://www.w3.org/TR/2006/WD-semantic-interpretation-20061103 respectively). Each issue is described by the name of the commentator, a description of the issue, and either the resolution or the reason that the issue was not resolved.
The full set of issues raised for the Semantic Interpretation for Speech Recognition (SISR) Version 1.0 since November 2004, their resolution and in most cases the reasoning behind the resolution are available from sisr10-cr.html [W3C Members Only]. This document provides the analysis of the issues that were submitted and resolved as part of the Call for Implementations. It includes issues that were submitted outside the official review period, up to 22nd January 2007.
Notation: Each original comment is tracked by a change request designator, SISR-DOC. Each point within that original comment is identified by a point number. For example, SISR-DOC1.2 is the second point in the first change request for the specification.
| Item | Commentator | Nature | Disposition |
|---|---|---|---|
| SISR-DOC15.1 | Jerry Carter (VBWG Group) | Clarifications, Typographical, and Other Editorial | Accepted |
| SISR-DOC15.2 | Jerry Carter (VBWG Group) | Clarifications, Typographical, and Other Editorial | Accepted |
| SISR-DOC15.3 | Jerry Carter (VBWG Group) | Clarifications, Typographical, and Other Editorial | Accepted |
| SISR-DOC16.1 | Jean-Francois Peyroux (Microsoft) | Clarifications, Typographical, and Other Editorial | Accepted |
| SISR-DOC14.1 | Jerry Carter (VBWG Group) | Request to Change Existing Features | Accepted |
| SISR-DOC17.1 | Paolo Baggia (VBWG Group) | Feature Requests | Rejected |
From Jerry Carter:
Short statement or example showing that external references are treated the same as local ones.
Resolution: Accepted
The informative note in section 3.3.2.1 was improved. In
addition, a bug in the same note was rectified. Previously, the
language implied that implicit rule references could only be
referenced by the rules.latest() notation, which was
neither the intent nor the case in all three of the implementations
reported (the latter was confirmed by personal communications with
Nuance, Loquendo, and Voxpilot).
Email Trail:
From Jerry Carter:
In section 6.3.2, add: The variable meta is initialized to a new object as constructed by the expression new Object().
Resolution: Accepted
Suggestion applied (its omission was an editorial bug).
Email Trail:
From Jerry Carter:
Possibly add an explicit note that "A grammar using semantics/1.0-literals can return non-string values from remote <ruleref> elements which use semantics/1.0."
Resolution: Accepted
Sentence added to the "Authoring Notes" in section 3.2.4.
Email Trail:
From Jean-Francois Peyroux:
It looks like this spec has a typo in it. In section 5, in the 3rd example, the <ruleref uri="#USAirport" /> should probably be enclosed in an <item> element since it is part of a <one-of>.
Resolution: Accepted
Typo addressed as suggested.
Email Trail:
None.
From Jerry Carter (summarized):
Timing information is important [in rich multimodal applications] and often necessary for this integration. Therefore, the EMMA result from the speech system and the EMMA result from the touch screen SHOULD/MUST contain timing information. Satisfying this requirement, however, does not justify exposing timing information to SISR programs. A processor may (and I believe SHOULD) attach this to the EMMA result outside of SISR processing -- as is done with emma:confidence, emma:model-ref, emma:grammar-ref, etc. There are two [ed: now three] implementations of SISR and neither implements timing metadata.
Resolution: Accepted
The group's resolution was to:
starttime and endtime variables).Email Trail:
From Paolo Baggia:
Feedback from Loquendo customers: Making global variables non read-only is useful for application developers.
Resolution: Rejected
The group discussed this change and decided the necessary changes were too substantive at this stage of the process to warrant the change..
Email Trail: