W3C home > Mailing lists > Public > www-voice@w3.org > July to September 2004

Comments for PR-speech-synthesis-20040715

From: Susan Lesch <lesch@w3.org>
Date: Fri, 27 Aug 2004 16:10:59 -0700
Message-Id: <p06110442bd556df92234@[]>
To: www-voice@w3.org


Your Speech Synthesis Markup Language (SSML) Proposed Recommendation 
[1] looks great and easy to follow. These are only minor editorial 
and markup comments.

s/W3C Specification/W3C specification/
s/XML Parse/XML parse/ (or else capitalize the others in 1.2)
s/there are classes of applications that have knowledge of text 
content to be spoken, and this can be incorporated/there are classes 
of applications that have knowledge of text content to be spoken, and 
that can be incorporated/
s/Future work by W3C will address/Future work by W3C is expected to 
address/ (there is no way to predict or promise)
s/For example, using a US English synthesis processor to process 
British English input./For example, a US English synthesis processor 
could process British English input./ (just an incomplete sentence)
s/text-editor/text editor/
s/Base URI/base URI/
s/specification will address/specification addresses/ (or is expected to)
s/XML Syntax/XML syntax/ (or the title, RDF/XML Syntax Specification)
s/sonicon punctuation/Sonicon punctuation/ (not sure but I think so)

I think but am not sure that you would want to capitalize Documents 
in "Conforming Stand-Alone Speech Synthesis Markup Language 

Also I think we talked about RFC 2119 markup (suggestion at [2]). 
When every occurrence of those keywords is meant in the RFC sense the 
markup is not critical. These may's in 3.1.4 could change to might's 
or else I would do the markup. (I didn't check for other occurrences.)

   "The declared type may not be supported by the processor; this is
    an error. The declared type may be supported but the actual type
    may not match; this is also an error. Finally, no media type may
    be declared; the behavior depends on the specific URI scheme and
    the capabilities of the synthesis processor."

In 3.1.6, in the list of DC elements, s/Copyrights/Rights/

In References:

Not critical but there is an extra space after each title (</cite> ,).

s/<cite>Dublin Core Metadata Initiative.</cite>/Dublin Core Metadata 

s/website/Web site/

In Acknowledgements:


In Appendixes:

s/universal character set/Universal Character Set/ (not critical and 
I'm not sure)

Maybe: s/voice element/<a href="#edef_voice" class="eref">voice</a> element/

The fourth example in Appendix F is a different font size.

In the markup:
Minor tweak in 1.5, "See Appendix C for information on media types 
for SSML." could be part of the first dd (rather than a separate p).

In the embedded CSS for pre.example, font-size: 85%; could be 
font-size: 90%;. 85% is perceptible but requires me to zoom to read 
in my Mozilla, Netscape and Firefox (probably atypical Mac 

[1] http://www.w3.org/TR/2004/PR-speech-synthesis-20040715/
[2] http://www.w3.org/2001/06/manual/#RFC

Best wishes for your project,
Susan Lesch           http://www.w3.org/People/Lesch/
mailto:lesch@w3.org               tel:+1.858.483.4819
World Wide Web Consortium (W3C)    http://www.w3.org/
Received on Friday, 27 August 2004 23:11:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:37 UTC