Re: Wording changes to add clarity

I've updated the spec with these changes:
https://dvcs.w3.org/hg/speech-api/rev/a561a5ec2d65

As always, the current draft spec is at:
http://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html

/Glen Shires

On Thu, Oct 11, 2012 at 10:09 AM, Glen Shires <gshires@google.com> wrote:

> One more I propose to change:
>
> Rename addFromUri method to addFromURI  (we capitalize URI everywhere else
> in the spec)
>
> /Glen Shires
>
> On Thu, Oct 11, 2012 at 3:43 AM, Hans Wennborg <hwennborg@google.com>wrote:
>
>> On Thu, Oct 11, 2012 at 1:55 AM, Glen Shires <gshires@google.com> wrote:
>> > I propose the following changes in wording, which I believe do not
>> change
>> > the intent or normative meaning, but add clarification.  If there's no
>> > disagreement, I will add these to the spec on Friday.
>> >
>> > result event
>> >   Substitute "See here[link to SpeechRecognitionEvent] for more
>> > information." with "The event MUST use the SpeechRecognitionEvent
>> > interface."
>> >
>> > nomatch event
>> >   Add "The event MUST use the SpeechRecognitionEvent interface."
>> >   Substitute "The result field..." with "The results field..."
>> >
>> > The stop method
>> >   Substitute "just the audio that it has received to date" with "just
>> the
>> > audio that it has already received for this recognition."
>> >   Substitute "based on the audio that it has collected to date" with
>> "based
>> > on the audio that it has already collected for this recognition."
>> >
>> > Also to be consistent in the headings of the definitions:
>> >   Substitute "The stop method" with "stop method" and elsewhere in
>> headings
>> > where "The" is superfluous.
>> >   Add the word "attribute" to the headings that omit it, including
>> sections
>> > 5.1.6, 5.1.7 and 5.1.8.
>>
>> These all sound good to me. Thanks!
>>
>
>