Re: Outline of Final Report

Ah, good point.  I meant only to indicate that these were three  
different pieces of work that needed to be addressed.  Would it be  
better if I called them "aspects" rather than components?  That is  
closer what I intended.  They are all must-address aspects of a  
solution.  We may later make a design decision to call some of them  
components, but we don't have agreement on that yet.

-- dan

On Apr 13, 2011, at 1:26 PM, Young, Milan wrote:

> Hello Dan,
>
> I'd like to clarify that I don't believe that the three components  
> that
> you listed below need to be distinct (ie "different").
>
> I could imagine, for example, a solution based on the web layer
> effectively communicating directly with the speech service.  Such an
> implementation would blur the line between the script API and speech
> service API.
>
>
>
> -----Original Message-----
> From: public-xg-htmlspeech-request@w3.org
> [mailto:public-xg-htmlspeech-request@w3.org] On Behalf Of Dan Burnett
> Sent: Wednesday, April 13, 2011 10:10 AM
> To: public-xg-htmlspeech@w3.org
> Subject: Outline of Final Report
>
> Group,
>
> I have put together an outline document for our Final Report, with
> placeholders for the sections I expect we will need.  This is only a
> first draft, and we can discuss it during tomorrow's teleconference.
>
> Note that I have already listed the one design decision we agree upon
> -- that a script API, a markup API, and a speech service API are  
> different components that must be addressed in some way.
>
> I am hopeful that we can begin to develop and record other design
> agreements.
>
> -- dan
>

Received on Wednesday, 13 April 2011 20:32:54 UTC