Re: [css3-speech] LC comment: use of generic SPAN element in voice-stress example and client-side use question

Hello Greg,
just a heads-up to let you know that the CSS Working Group has reviewed this issue, and the consensus is to accept changing the markup from 'span' to 'em', as it makes more sense in the context of this particular example. However, the HTML default user-agent stylesheet remains out-of-scope (we will start a separate cross-group discussion for this).

As per the W3C process, you may choose to accept this resolution, or you may decide to raise an objection. Please let us know.

Kind regards, Dan

On 12 Oct 2011, at 15:20, Daniel Weck wrote:

> Hi Greg,
> CSS2 provides [1] a sample user-agent default stylesheet for HTML4, which obviously is informative (as you rightly pointed-out, CSS is markup-agnostic).
> 
> I considered adding a similar appendix for CSS3-Speech, but I should think that modern HTML5 would be a better candidate, which unfortunately means working with a moving target at this point in time. I also believe that this should be a concerted effort, which wouldn't really fit in the release timeframe for Level 3 of the CSS Speech Module.
> 
> This is something we should aim for during the next revision of the specification, which would allow time for the community at large to reach a consensus on recommended default speech values for HTML5 markup. In other words, I suggest to defer your proposal to include a " default user-agent stylesheet" informative appendix, and I would encourage a parallel activity to take place (e.g. within the realm of a W3C Community Group?).
> 
> Please let me know if this addresses your concerns for this round of editing.
> 
> Regarding your question #2, I suggest you take a look at the "cascade" definition [2], which unambiguously defines the resolution process of user-defined versus author-defined styles.
> 
> Regards, Daniel
> 
> [1]
> http://www.w3.org/TR/CSS2/sample.html
> 
> [2]
> http://www.w3.org/TR/CSS2/cascade.html#cascade
> 
> On 1 Oct 2011, at 04:15, Gregory Rosmaita wrote:
> 
>> aloha!
>> 
>> currently, the example contained in 10.5. "The 'voice-stress' property"
>> contains speech values applied via use of the generic SPAN element --
>> while there is nothing inherently wrong with this approach as it is
>> markup-language agnostic, and hence may be intentional...  i wonder,
>> however, if a "learning opportunity" may be lost by not providing an
>> example that includes the sort of real-life bindings for which css3 may
>> be most extensively used:
>> 
>> for example, a VERY simple client-side css3-speech stylesheet might
>> contain:
>> 
>> body { voice-stress: normal; }
>> i { voice-stress: moderate; }
>> em { voice-stress: moderate; }
>> b { voice-stress: strong; }
>> strong { voice-stress: strong; }
>> 
>> as a means of ensuring that an end user can set equivalent values for
>> synonymical bits of markup -- in the age of script-driven sites and
>> aggregated content, it is not unusual for a single "document instance"
>> to contain content that uses both the EM/STRONG and B/STRONG tandem
>> 
>> OPTIONS:
>> 
>> 1. is this something that could/should be addressed/included as an
>> informative appendix?  a sample client-side css3-speech stylesheet for
>> "generic" HTML-based browsing?  if so, i could assist in the composition
>> of such an appendix/example...
>> 
>> 2. do client-side css3-speech settings over-ride or compliment author-
>> defined speech styling?  using the simple client side stylesheet
>> thumbnailed above, would the voice-stress settings set by the user
>> trump those provided by an author, or -- if the author provides different
>> css3-speech properties than those provided by the user (for example, a
>> change in voice-stress or voice-volume) -- could/would the client AND
>> author provided properties be applied to the marked text?
>> 
>> for example, barring the presence of a !important on the client-side
>> css3-speech stylesheet, could a speech output user set the currently
>> active speech engine to apply both the user-defined AND the author
>> defined properties, should the end user so desire?
>> 
>> <!-- client-side stylesheet -->
>> body { voice-stress: normal; }
>> i { voice-stress: moderate; }
>> b { voice-stress: strong; voice-volume: loud; }
>> 
>> <!-- author-defined stylesheet -->
>> i { voice-range: high; }
>> b { voice-range: x-high; }
>> 
>> ------------------------------------------------------
>> It is better to ask some of the questions than to know
>> all the answers.                      -- James Thurber
>> ------------------------------------------------------
>>   Gregory J. Rosmaita: gregory.rosmaita@gmail.com
>>        Camera Obscura: http://www.hicom.net/~oedipus
>> Oedipus' Online Complex: http://my.opera.com/oedipus
>> ------------------------------------------------------
>> 
>

Received on Wednesday, 19 October 2011 23:46:51 UTC