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

Re: [speech] PLS Pronunciation Lexicons, link/rel support in HTML5

From: Peter Sorotokin <psorotok@adobe.com>
Date: Sun, 6 Feb 2011 20:42:15 -0800
To: Daniel Weck <daniel.weck@gmail.com>, Dan Burnett <dburnett@voxeo.com>, EPUB WG <epub@openebook.org>, "www-voice@w3.org" <www-voice@w3.org>, fantasai <fantasai@inkedblade.net>
Message-ID: <C974B827.F081%psorotok@adobe.com>

I think that EPUB3 should define the value for rel attribute
("pronunciation") itself and require documents that require pronunciation
data to reference one explicitly.

Also limiting EPUB document to only one PLS is not consistent with other
resources. It makes it harder, for instance to merge two documents together
and I do not see any particular wins on implementation side. It is also not
future-proof (e.g. we may add an ability to add multiple pronunciation
files, e.g. For American and British pronunciations - or who knows what

I think we should treat PLS documents exactly like we do CSS: include as
many as you want and reference what you need explicitly.


On 2/5/11 3:59 AM, "Daniel Weck" <daniel.weck@gmail.com> wrote:

> Just a quick heads-up about this issue, which has now been filed by
> the Accessibility Task Force:
> http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#
> HTML5_Spec_Bugs_Awaiting_Decision
> Regards, Daniel
> On 2 Feb 2011, at 20:25, Daniel Weck wrote:
>> Hi Daniel (CC to the EPUB and Voice-Browser working groups),
>> I have reactivated this HTML5 issue [1] which proposes the adoption
>> of a "pronunciation" link/rel extension [2], in order to provide
>> first-class support for PLS pronunciation lexicons within HTML pages.
>> In the upcoming v3.0 of EPUB [3], PLS files can be included at the
>> publication level (i.e. not on a per-HTML file basis), so EPUB
>> doesn't actually depend on this particular link/rel extension (it
>> relies only on the "application/pls+xml" MIME type).
>> Based on Ian Hickson's comments in the W3C bug tracker, it seems
>> that a proposed "rel" extension gets accepted once the submitter can
>> prove that it is adopted:
>> "You'll need to write a spec first, and demonstrate that people are
>> using the keyword. ... Please let us know once this keyword is
>> deployed, for reconsideration."
>> Consequently, I am tempted to propose a small addition to the EPUB3
>> specification, so that XHTML5 documents in a publication can
>> reference PLS files, just like CSS files (providing they are
>> declared in the EPUB manifest, of course). EPUB would therefore
>> showcase a concrete adoption of the link/rel "pronunciation"
>> extension, which would help moving its status from "proposal" to
>> "accepted" in the HTML5 working group. I don't believe this is a
>> requirement for "rel" extensions to actually work, but it would be
>> nice to get official endorsement, especially given that this is
>> pretty much a critical issue with regards to content accessibility.
>> Comments welcome.
>> Regards, Daniel
>> [1]
>> http://www.w3.org/Bugs/Public/show_bug.cgi?id=7601#c6
>> [2]
>> http://wiki.whatwg.org/wiki/RelExtensions
>> [3]
>> http://epub-revision.googlecode.com/svn/trunk/build/spec/epub30-overview.html
>> #sec-tts
> Daniel Weck
> daniel.weck@gmail.com
Received on Monday, 7 February 2011 04:43:14 UTC

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