W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2001

SSML, further comments

From: <DPawson@rnib.org.uk>
Date: Mon, 22 Jan 2001 13:06:11 -0000
Message-ID: <9B66BBD37D5DD411B8CE00508B69700F4F0051@pborolocal.rnib.org.uk>
To: www-voice@w3.org
After another read of the spec. Some more comments.

 1.2, list item 4, para 3.
"TTS systems are expert at performing text-topohoneme conversions
so most words of most documents can be handled automatically".
 Rather too sweeping for my liking. Certainly not the case for
the systems I've seen :-)



2.4 Sub attribute.

A nice feature for a user would be to permit these to be collated
externally, and passed in as a sort of configuration file.

It would save typing for regularly repeated  occurrences.
<sub>
<el>W3C</el>
<use>World Wide Web Consortium</use>
</sub>

or something similar? 

2.8 break element.
  A refinement on this would be the ability to explicitly state
the required duration for various punctuation elements and other
break types (paragraph, sentance).

Again suggest this be externally configurable, for re-use optimisation.

2.10 Usage note 1. Could be confusion between this and 3.2.
If the default is to pause conversion till the audio is complete,
then it should be explicitly stated here. I support that requirement btw.


2.12 usage note. Why hasn't a namespace been explicitly called up?
  This would then nullify the requirement stated in 5.1 (I can't see
any need for that requirement. Is it justifiable?)

3.6 Value.

I suspect that the overall impact of this may be achieved by a simple
XSLT transform anyway, which may make this redundant?

My only final comment is where can I find an implementation :-)
Good spec.

Regards DaveP
(AC, RNIB)
Received on Monday, 22 January 2001 08:06:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 October 2006 12:48:53 GMT