RE: Please review requirements carefully

I think that sentence should probably be added to FPR21 through FPR24, FPR 35, FPR 39, FPR 40, FPR 51-53.  As they all require timeliness of notifications.  Arguably FPR 26 covers some of this, but I don't think it would hurt to have Milan's sentences added.

From: Young, Milan [mailto:Milan.Young@nuance.com]
Sent: Monday, January 03, 2011 4:23 PM
To: Dan Burnett; Michael Bodell
Cc: public-xg-htmlspeech@w3.org
Subject: RE: Please review requirements carefully

FPR22. The web app should be notified that speech is considered to have started for the purposes of recognition.

Any objections to adding the following sentence to the description?  "Notification should be delivered in a timely manner after detection occurs."


________________________________
From: public-xg-htmlspeech-request@w3.org [mailto:public-xg-htmlspeech-request@w3.org] On Behalf Of Dan Burnett
Sent: Monday, January 03, 2011 2:21 AM
To: Michael Bodell
Cc: public-xg-htmlspeech@w3.org
Subject: Please review requirements carefully

Welcome back and Happy New Year!

We will very shortly be prioritizing our First Pass requirements.  If any requirement is not currently clear enough to prioritize, send clarification text or supplemental text to the list IMMEDIATELY.
This means that if your personal understanding of the requirement as listed is not clear enough that you could assign an importance to it for yourself/your organization, then you need to speak up.

-- dan

On Dec 22, 2010, at 6:49 PM, Michael Bodell wrote:

I've updated the latest requirements draft (http://www.w3.org/2005/Incubator/htmlspeech/live/draft-20101223-requirements.html) which includes the 7 new requirements from the last teleconference (http://www.w3.org/2010/12/16-htmlspeech-minutes.html), moves the old section 3 into an Appendix (and removes the strikeout), and tries to start the organization of the first pass requirements.  I've provided a two level organization structure that makes sense to me in the table of contents (First: Is it a feature requirement? An ease of authoring requirement? Or a security/privacy requirement?; Second: Does it apply to speech services [both reco and synth]? Does it apply to just reco? Does it apply to just synth?) that helps to provide some structure to the document.  I haven't reordered requirements inside of these levels (I.e., putting ones that are similar near each other beyond original order) and I haven't renamed/renumbered the requirements yet nor reordered the content.  I'm holding off on renaming as it makes it harder to track changes and also renaming and reordering the content takes a decent chunk of time and I want to make sure we like this ordering before committing to that.  Probably a good topic for our first January call.

Reminder that if any requirement is not currently clear enough to prioritize to send clarification text or supplemental text to the list.

Hope everyone has a Merry Christmas and a Happy New Year!