added list of issues at top of document

Author: danielweck

css3-speech/Overview.html

@@ -159,12 +159,17 @@ <h2 class="no-num no-toc" id=status>Status of this document</h2>
   <p>This document has been developed in cooperation with the <a
    href="/Voice/Group/">Voice Browser working group</a> (<a
    href="http://cgi.w3.org/MemberAccess/AccessRequest">W3C Members only</a>).
-   
 
   <p>The following features are at-risk and may be dropped at the end of the
    CR period if there has not been enough interest from implementers:
-   &lsquo;<a href="#phonemes"><code class=property>phonemes</code></a>&rsquo;
-   
+
+  <ul>
+   <li><a href="#issue-phonemes">phonemes</a>
+
+   <li><a href="#issue-mark">mark</a>
+
+   <li><a href="#issue-speak_none">speak:none</a>
+  </ul>
 
   <p>The CSS WG maintains an <a
    href="http://www.w3.org/Style/CSS/Tracker/products/29">issues list</a> for
@@ -645,23 +650,26 @@ <h2 id=speaking-props><span class=secno>5. </span>Speaking properties:
     descendants, use the &lsquo;<a href="#display-def"><code
     class=property>display</code></a>&rsquo; property <a href="#CSS3BOX"
     rel=biblioentry>[CSS3BOX]<!--{{CSS3BOX}}--></a>).
-    <p class=issue>ISSUE: &lsquo;<code class=css>speak:none</code>&rsquo; is
-     arguably unnecessary, as it can be fully realized using &lsquo;<code
-     class=css>display:none</code>&rsquo; and because the function of
-     &lsquo;<a href="#speak"><code class=property>speak</code></a>&rsquo; is
-     primarily to specify *how* to speak text content, not to control *if* it
-     should be spoken. There is also a concern about accessibility good
-     practices, in particular with regards to whether this specification
-     should allow authors to "hide" text in the aural dimension, when it is
-     visible on the visual canvas. Note that "display:none" is different than
-     "visibility:hidden". The former effectively &lsquo;<code
+    <p class=issue id="issue-speak_none">ISSUE: &lsquo;<code
+     class=css>speak:none</code>&rsquo; is arguably unnecessary, as it can be
+     fully realized using &lsquo;<code class=css>display:none</code>&rsquo;.
+     The function of &lsquo;<a href="#speak"><code
+     class=property>speak</code></a>&rsquo; should primarily be to specify
+     *how* to speak text content, not to control *if* it should be spoken.
+     There is also a concern about accessibility good practices, in
+     particular with regards to whether this specification should allow
+     authors to "hide" text in the aural dimension, when it is actually
+     visible on the graphical canvas. Note that "display:none" is different
+     than "visibility:hidden". The former effectively &lsquo;<code
      class=property>deactivates</code>&rsquo; an element (so to speak)
      whereas the latter is more similar to "voice-volume:0%". In other words,
      "visibility:hidden" preserves the visual space that the element would
      normally occupy if it was visible (resulting in an empty or transparent
      area that still takes part in the page layout), and conversely
      "voice-volume:0%" results in an audio silence lasting as long as the
-     duration of non-silent TTS playback.</p>
+     duration of non-silent TTS playback. There is a <a
+     href="http://lists.w3.org/Archives/Public/www-style/2011Jan/0355.html">related
+     discussion</a> on the public mailing-list.</p>
 
    <dt><strong>normal</strong>
 
@@ -1550,12 +1558,12 @@ <h2 id=mark-props><span class=secno>9. </span>Mark properties: &lsquo;<a
 </pre>
   </div>
 
-  <p class=issue>ISSUE: in SSML, the &lsquo;<a href="#mark"><code
-   class=property>mark</code></a>&rsquo; element acts as a destination anchor
-   and as a mean to raise an event when the point is reached within the
-   speech stream. This functionality arguably isn't purely of stylistic
-   nature, but this may be required but for the sake of covering SSML's
-   feature-set. There is a <a
+  <p class=issue id=issue-mark>ISSUE: in SSML, the &lsquo;<a
+   href="#mark"><code class=property>mark</code></a>&rsquo; element acts as a
+   destination anchor and as a mean to raise an event when the point is
+   reached within the speech stream. This functionality arguably isn't purely
+   of stylistic nature (if at all), so it is judged "at risk" of being
+   removed from this specification draft. There is a <a
    href="http://lists.w3.org/Archives/Public/www-style/2010Dec/0239.html">related
    discussion</a> on the public mailing-list.
 
@@ -2074,6 +2082,13 @@ <h2 id=phonetic-props><span class=secno>12. </span>Phonetics: &lsquo;<a
     class=css>@phonetic-alphabet</code>&rsquo;</a>.
   </dl>
 
+  <p class=issue id=issue-phonemes>ISSUE: the &lsquo;<a
+   href="#phonemes"><code class=property>phonemes</code></a>&rsquo; property
+   covers functionality that is arguably not strictly related to styling (it
+   relates to the broader aspect of pronunciation lexicons). There is a <a
+   href="http://lists.w3.org/Archives/Public/www-style/2011Jan/0248.html">related
+   discussion</a> on the public mailing-list.
+
   <h3 id=phonetic-alphabet><span class=secno>12.1. </span>@phonetic-alphabet</h3>
 
   <p> A phonetic alphabet is a collection of symbols that represent the

css3-speech/Overview.src.html

@@ -89,19 +89,25 @@ <h2 id="status" class="no-num no-toc">Status of this document</h2>
 <hr>
 
 <p>This document is a draft of one of the "modules" for the
-upcoming CSS3 specification.
+upcoming CSS3 specification.</p>
 
 <p>This document has been developed in
 cooperation with the <a href="/Voice/Group/">Voice Browser working
 group</a> (<a href="http://cgi.w3.org/MemberAccess/AccessRequest">W3C
-Members only</a>).
+Members only</a>).</p>
 
 <p>The following features are at-risk and may be dropped at the
 end of the CR period if there has not been enough interest from
-implementers: 'phonemes'
+implementers:
+<ul>
+<li><a href="#issue-phonemes">phonemes</a></li>
+<li><a href="#issue-mark">mark</a></li>
+<li><a href="#issue-speak_none">speak:none</a></li>
+</ul>
+</p>
 
 <p>The CSS WG maintains an <a href="http://www.w3.org/Style/CSS/Tracker/products/29">issues
-list</a> for this module.
+list</a> for this module.</p>
 
 <h2 id="contents" class="no-num no-toc">Table of contents</h2>
 <!--toc-->
@@ -410,7 +416,8 @@ <h2 id="speaking-props"><span class="secno">5. </span>Speaking properties:
 and will be spoken. (To be sure to suppress rendering of an element
 and its descendants, use the 'display' property [[CSS3BOX]]).
 
-<p class="issue">ISSUE: 'speak:none' is arguably unnecessary, as it can be fully realized using 'display:none' and because the function of 'speak' is primarily to specify *how* to speak text content, not to control *if* it should be spoken. There is also a concern about accessibility good practices, in particular with regards to whether this specification should allow authors to "hide" text in the aural dimension, when it is visible on the visual canvas. Note that "display:none" is different than "visibility:hidden". The former effectively 'deactivates' an element (so to speak) whereas the latter is more similar to "voice-volume:0%". In other words, "visibility:hidden" preserves the visual space that the element would normally occupy if it was visible (resulting in an empty or transparent area that still takes part in the page layout), and conversely "voice-volume:0%" results in an audio silence lasting as long as the duration of non-silent TTS playback.
+<p class="issue" id="issue-speak_none">ISSUE: 'speak:none' is arguably unnecessary, as it can be fully realized using 'display:none'. The function of 'speak' should primarily be to specify *how* to speak text content, not to control *if* it should be spoken. There is also a concern about accessibility good practices, in particular with regards to whether this specification should allow authors to "hide" text in the aural dimension, when it is actually visible on the graphical canvas. Note that "display:none" is different than "visibility:hidden". The former effectively 'deactivates' an element (so to speak) whereas the latter is more similar to "voice-volume:0%". In other words, "visibility:hidden" preserves the visual space that the element would normally occupy if it was visible (resulting in an empty or transparent area that still takes part in the page layout), and conversely "voice-volume:0%" results in an audio silence lasting as long as the duration of non-silent TTS playback.
+There is a <a href="http://lists.w3.org/Archives/Public/www-style/2011Jan/0355.html">related discussion</a> on the public mailing-list.
 </p>
 
 </dd>
@@ -1158,9 +1165,10 @@ <h2 id="mark-props"><span class="secno">9. </span>Mark properties:
 div {mark: "start" "end" }
 </pre></div>
 
-<p class="issue">ISSUE: in SSML, the 'mark' element acts as a destination anchor
+<p class="issue" id="issue-mark">ISSUE: in SSML, the 'mark' element acts as a destination anchor
 and as a mean to raise an event when the point is reached within the speech stream.
-This functionality arguably isn't purely of stylistic nature, but this may be required but for the sake of covering SSML's feature-set. There is a <a href="http://lists.w3.org/Archives/Public/www-style/2010Dec/0239.html">related discussion</a> on the public mailing-list.
+This functionality arguably isn't purely of stylistic nature (if at all), so it is judged "at risk" of being removed from this specification draft.
+There is a <a href="http://lists.w3.org/Archives/Public/www-style/2010Dec/0239.html">related discussion</a> on the public mailing-list.
 </p>
 
 <h2 id="voice-char-props"><span class="secno">10. </span>Voice
@@ -1645,6 +1653,10 @@ <h2 id="phonetic-props"><span class="secno">12. </span>Phonetics:
 
 </dl>
 
+<p class="issue" id="issue-phonemes">ISSUE: the 'phonemes' property covers functionality that is arguably not strictly related to styling (it relates to the broader aspect of pronunciation lexicons).
+There is a <a href="http://lists.w3.org/Archives/Public/www-style/2011Jan/0248.html">related discussion</a> on the public mailing-list.
+</p>
+
 
 <h3 id="phonetic-alphabet">@phonetic-alphabet</h3>