Mercurial > hg > ttml / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset
SDP-US - Editorial (*) - General cleanup, add issues, colorize example, etc.
authorGlenn Adams <glenn@skynav.com>
Thu, 06 Dec 2012 01:41:57 -0700
changeset 325 680c5fb178d4
parent 324 40a560b280a1
child 326 0cde9fd09d37
SDP-US - Editorial (*) - General cleanup, add issues, colorize example, etc.
ttml10-sdp-us/Overview.html
ttml10-sdp-us/Overview.src.html 
--- a/ttml10-sdp-us/Overview.html	Wed Dec 05 20:12:26 2012 -0700
+++ b/ttml10-sdp-us/Overview.html	Thu Dec 06 01:41:57 2012 -0700
@@ -390,7 +390,7 @@
   
     <h2 id="subtitle">A profile of TTML for internet delivery of Captions originated in the United States</h2>
   
-  <h2 id="w3c-editor-s-draft-29-november-2012"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft 29 November 2012</h2>
+  <h2 id="w3c-editor-s-draft-06-december-2012"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft 06 December 2012</h2>
   <dl>
     
       <dt>This version:</dt>
@@ -503,7 +503,7 @@
       
     
   
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2. </span>Conformance</a></li><li class="tocline"><a href="#terms" class="tocxref"><span class="secno">3. </span>Terms, Definitions, and Conventions</a></li><li class="tocline"><a href="#SimpleProfile" class="tocxref"><span class="secno">4. </span>Simple Delivery Profile for Closed Captions</a><ul class="toc"><li class="tocline"><a href="#Use_of_TTML_Constrained_Feature_Template" class="tocxref"><span class="secno">4.1 </span>Use of TTML Constrained Feature Template</a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="#structural-constraints" class="tocxref"><span class="secno">5. </span>Structural Constraints</a></li><li class="tocline"><a href="#Constrained_Features" class="tocxref"><span class="secno">6. </span>Constrained Features</a><ul class="toc"><li class="tocline"><a href="#Constrained_TTML_Feature_core" class="tocxref"><span class="secno">6.1 </span>Use of Constrained TTML Feature <span>core</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario" class="tocxref"><span class="secno">6.1.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints" class="tocxref"><span class="secno">6.1.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Use_of_Constrained_TTML_Feature_content" class="tocxref"><span class="secno">6.2 </span>Use of Constrained TTML Feature <span>content</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-1" class="tocxref"><span class="secno">6.2.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-1" class="tocxref"><span class="secno">6.2.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Use_of_Constrained_TTML_Feature_content_presentation" class="tocxref"><span class="secno">6.3 </span>Use of Constrained TTML Feature <span>presentation</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-2" class="tocxref"><span class="secno">6.3.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-2" class="tocxref"><span class="secno">6.3.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Use_of_Constrained_TTML_Feature_content_profile" class="tocxref"><span class="secno">6.4 </span>Use of Constrained TTML Feature <span>profile</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-3" class="tocxref"><span class="secno">6.4.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-3" class="tocxref"><span class="secno">6.4.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Use_of_Constrained_TTML_Feature_content_structure" class="tocxref"><span class="secno">6.5 </span>Use of Constrained TTML Feature <span>structure</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-4" class="tocxref"><span class="secno">6.5.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-4" class="tocxref"><span class="secno">6.5.2 </span>Constraints</a></li></ul></li></ul></li><li class="tocline"><a href="#Style_Constraints" class="tocxref"><span class="secno">7. </span>Style Constraints</a><ul class="toc"><li class="tocline"><a href="#Constrained_TTML_Feature_backgroundColor" class="tocxref"><span class="secno">7.1 </span>Use of Constrained TTML Feature <span>backgroundColor-*</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-5" class="tocxref"><span class="secno">7.1.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-5" class="tocxref"><span class="secno">7.1.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_color" class="tocxref"><span class="secno">7.2 </span>Use of Constrained TTML Feature <span>color</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-6" class="tocxref"><span class="secno">7.2.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-6" class="tocxref"><span class="secno">7.2.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_display_region" class="tocxref"><span class="secno">7.3 </span>Use of Constrained TTML Feature <span>display-region</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-7" class="tocxref"><span class="secno">7.3.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-7" class="tocxref"><span class="secno">7.3.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_extent_region" class="tocxref"><span class="secno">7.4 </span>Use of Constrained TTML Feature <span>extent-region</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-8" class="tocxref"><span class="secno">7.4.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-8" class="tocxref"><span class="secno">7.4.2 </span>Constraints</a></li><li class="tocline"><a href="#examples" class="tocxref"><span class="secno">7.4.3 </span>Examples</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_display_display_fontFamily_generic" class="tocxref"><span class="secno">7.5 </span>Use of Constrained TTML Feature <span>fontFamily-generic</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-9" class="tocxref"><span class="secno">7.5.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-9" class="tocxref"><span class="secno">7.5.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_display_display_fontSize" class="tocxref"><span class="secno">7.6 </span>Use of Constrained TTML Feature <span>fontSize</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-10" class="tocxref"><span class="secno">7.6.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-10" class="tocxref"><span class="secno">7.6.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_display_display_fontStyle_italic" class="tocxref"><span class="secno">7.7 </span>Use of Constrained TTML Feature <span>fontStyle-italic</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-11" class="tocxref"><span class="secno">7.7.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-11" class="tocxref"><span class="secno">7.7.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_length_percentage" class="tocxref"><span class="secno">7.8 </span>Use of Constrained TTML Feature <span>length-percentage</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-12" class="tocxref"><span class="secno">7.8.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-12" class="tocxref"><span class="secno">7.8.2 </span>Constraints</a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_length_positive" class="tocxref"><span class="secno">7.9 </span>Use of Constrained TTML Feature <span>length-positive</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-13" class="tocxref"><span class="secno">7.9.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-13" class="tocxref"><span class="secno">7.9.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_styling" class="tocxref"><span class="secno">7.10 </span>Use of Constrained TTML Feature <span>styling-*</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-14" class="tocxref"><span class="secno">7.10.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-14" class="tocxref"><span class="secno">7.10.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_styling_inheritance_content" class="tocxref"><span class="secno">7.11 </span>Use of Constrained TTML Feature <span>styling-inheritance-content</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-15" class="tocxref"><span class="secno">7.11.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-15" class="tocxref"><span class="secno">7.11.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_styling_inheritance_region" class="tocxref"><span class="secno">7.12 </span>Use of Constrained TTML Feature <span>styling-inheritance-region</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-16" class="tocxref"><span class="secno">7.12.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-16" class="tocxref"><span class="secno">7.12.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_textAlign_absolute" class="tocxref"><span class="secno">7.13 </span>Use of Constrained TTML Feature <span>textAlign-absolute</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-17" class="tocxref"><span class="secno">7.13.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-17" class="tocxref"><span class="secno">7.13.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_textDecoration_under" class="tocxref"><span class="secno">7.14 </span>Use of Constrained TTML Feature <span>textDecoration-under</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-18" class="tocxref"><span class="secno">7.14.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-18" class="tocxref"><span class="secno">7.14.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_textOutline_unblurred" class="tocxref"><span class="secno">7.15 </span>Use of Constrained TTML Feature <span>textOutline-unblurred</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-19" class="tocxref"><span class="secno">7.15.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-19" class="tocxref"><span class="secno">7.15.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_writingMode_horizontal_lr" class="tocxref"><span class="secno">7.16 </span>Use of Constrained TTML Feature <span>writingMode-horizontal-lr</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-20" class="tocxref"><span class="secno">7.16.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-20" class="tocxref"><span class="secno">7.16.2 </span>Constraints</a></li></ul></li></ul></li><li class="tocline"><a href="#layout_constraints" class="tocxref"><span class="secno">8. </span>Layout Constraints</a><ul class="toc"><li class="tocline"><a href="#Constrained_TTML_Feature_layout" class="tocxref"><span class="secno">8.1 </span>Use of Constrained TTML Feature <span>layout</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-21" class="tocxref"><span class="secno">8.1.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-21" class="tocxref"><span class="secno">8.1.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_lineBreak-uax14" class="tocxref"><span class="secno">8.2 </span>Use of Constrained TTML Feature <span>lineBreak-uax14</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-22" class="tocxref"><span class="secno">8.2.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-22" class="tocxref"><span class="secno">8.2.2 </span>Constraints</a></li></ul></li></ul></li><li class="tocline"><a href="#timing_constraints" class="tocxref"><span class="secno">9. </span>Timing Constraints</a><ul class="toc"><li class="tocline"><a href="#Constrained_TTML_Feature_timing" class="tocxref"><span class="secno">9.1 </span>Use of Constrained TTML Feature <span>timing</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-23" class="tocxref"><span class="secno">9.1.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-23" class="tocxref"><span class="secno">9.1.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_time_offset" class="tocxref"><span class="secno">9.2 </span>Use of Constrained TTML Feature <span>time-offset</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-24" class="tocxref"><span class="secno">9.2.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-24" class="tocxref"><span class="secno">9.2.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#frameRate" class="tocxref"><span class="secno">9.3 </span>Use of Constrained TTML Feature <span>frameRate and frameRateMultiplier</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-25" class="tocxref"><span class="secno">9.3.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-25" class="tocxref"><span class="secno">9.3.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#animation" class="tocxref"><span class="secno">9.4 </span>Use of Constrained TTML Feature <span>animation</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-26" class="tocxref"><span class="secno">9.4.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-26" class="tocxref"><span class="secno">9.4.2 </span>Constraints</a></li></ul></li></ul></li><li class="tocline"><a href="#other_constraints" class="tocxref"><span class="secno">10. </span>Other Constraints</a><ul class="toc"><li class="tocline"><a href="#Encoding_Constraints" class="tocxref"><span class="secno">10.1 </span>Encoding Constraints</a><ul class="toc"><li class="tocline"><a href="#usage-scenario-27" class="tocxref"><span class="secno">10.1.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-27" class="tocxref"><span class="secno">10.1.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#User_Ease_of_Use_Constraints" class="tocxref"><span class="secno">10.2 </span>User Ease of Use Constraints</a></li></ul></li><li class="tocline"><a href="#Features_in_TTML_1.0_Used" class="tocxref"><span class="secno">11. </span>Features in TTML 1.0 Used in This Profile</a></li><li class="tocline"><a href="#error_handling" class="tocxref"><span class="secno">12. </span>Error handling</a></li><li class="tocline"><a href="#future_needs" class="tocxref"><span class="secno">A. </span>Future Needs for TTML next for Simple Delivery</a><ul class="toc"><li class="tocline"><a href="#Section2" class="tocxref"><span class="secno">A.1 </span>Values for fontFamily support</a></li><li class="tocline"><a href="#Section3" class="tocxref"><span class="secno">A.2 </span>Support for character edge features</a></li><li class="tocline"><a href="#Section4" class="tocxref"><span class="secno">A.3 </span>Specify rendering model that accounts for drawing performance</a></li></ul></li><li class="tocline"><a href="#mapping-of-us-government-requirements-to-constrained-profile-features" class="tocxref"><span class="secno">B. </span>Mapping of US Government Requirements to Constrained Profile Features</a></li><li class="tocline"><a href="#code-points" class="tocxref"><span class="secno">C. </span>Code points</a><ul class="toc"><li class="tocline"><a href="#color-values" class="tocxref"><span class="secno">C.1 </span>Color values</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C.2 </span>Acknowledgements</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2. </span>Conformance</a></li><li class="tocline"><a href="#terms" class="tocxref"><span class="secno">3. </span>Terms, Definitions, and Conventions</a></li><li class="tocline"><a href="#SimpleProfile" class="tocxref"><span class="secno">4. </span>Simple Delivery Profile for Closed Captions</a><ul class="toc"><li class="tocline"><a href="#Use_of_TTML_Constrained_Feature_Template" class="tocxref"><span class="secno">4.1 </span>Use of TTML Constrained Feature Template</a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="#structural-constraints" class="tocxref"><span class="secno">5. </span>Structural Constraints</a></li><li class="tocline"><a href="#Constrained_Features" class="tocxref"><span class="secno">6. </span>Constrained Features</a><ul class="toc"><li class="tocline"><a href="#Constrained_TTML_Feature_core" class="tocxref"><span class="secno">6.1 </span>Use of Constrained TTML Feature <span>core</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario" class="tocxref"><span class="secno">6.1.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints" class="tocxref"><span class="secno">6.1.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Use_of_Constrained_TTML_Feature_content" class="tocxref"><span class="secno">6.2 </span>Use of Constrained TTML Feature <span>content</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-1" class="tocxref"><span class="secno">6.2.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-1" class="tocxref"><span class="secno">6.2.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Use_of_Constrained_TTML_Feature_content_presentation" class="tocxref"><span class="secno">6.3 </span>Use of Constrained TTML Feature <span>presentation</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-2" class="tocxref"><span class="secno">6.3.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-2" class="tocxref"><span class="secno">6.3.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Use_of_Constrained_TTML_Feature_content_profile" class="tocxref"><span class="secno">6.4 </span>Use of Constrained TTML Feature <span>profile</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-3" class="tocxref"><span class="secno">6.4.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-3" class="tocxref"><span class="secno">6.4.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Use_of_Constrained_TTML_Feature_content_structure" class="tocxref"><span class="secno">6.5 </span>Use of Constrained TTML Feature <span>structure</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-4" class="tocxref"><span class="secno">6.5.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-4" class="tocxref"><span class="secno">6.5.2 </span>Constraints</a></li></ul></li></ul></li><li class="tocline"><a href="#Style_Constraints" class="tocxref"><span class="secno">7. </span>Style Constraints</a><ul class="toc"><li class="tocline"><a href="#Constrained_TTML_Feature_backgroundColor" class="tocxref"><span class="secno">7.1 </span>Use of Constrained TTML Feature <span>backgroundColor-*</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-5" class="tocxref"><span class="secno">7.1.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-5" class="tocxref"><span class="secno">7.1.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_color" class="tocxref"><span class="secno">7.2 </span>Use of Constrained TTML Feature <span>color</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-6" class="tocxref"><span class="secno">7.2.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-6" class="tocxref"><span class="secno">7.2.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_display_region" class="tocxref"><span class="secno">7.3 </span>Use of Constrained TTML Feature <span>display-region</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-7" class="tocxref"><span class="secno">7.3.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-7" class="tocxref"><span class="secno">7.3.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_extent_region" class="tocxref"><span class="secno">7.4 </span>Use of Constrained TTML Feature <span>extent-region</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-8" class="tocxref"><span class="secno">7.4.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-8" class="tocxref"><span class="secno">7.4.2 </span>Constraints</a></li><li class="tocline"><a href="#examples" class="tocxref"><span class="secno">7.4.3 </span>Examples</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_display_display_fontFamily_generic" class="tocxref"><span class="secno">7.5 </span>Use of Constrained TTML Feature <span>fontFamily-generic</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-9" class="tocxref"><span class="secno">7.5.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-9" class="tocxref"><span class="secno">7.5.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_display_display_fontSize" class="tocxref"><span class="secno">7.6 </span>Use of Constrained TTML Feature <span>fontSize</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-10" class="tocxref"><span class="secno">7.6.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-10" class="tocxref"><span class="secno">7.6.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_display_display_fontStyle_italic" class="tocxref"><span class="secno">7.7 </span>Use of Constrained TTML Feature <span>fontStyle-italic</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-11" class="tocxref"><span class="secno">7.7.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-11" class="tocxref"><span class="secno">7.7.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_length_percentage" class="tocxref"><span class="secno">7.8 </span>Use of Constrained TTML Feature <span>length-percentage</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-12" class="tocxref"><span class="secno">7.8.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-12" class="tocxref"><span class="secno">7.8.2 </span>Constraints</a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_length_positive" class="tocxref"><span class="secno">7.9 </span>Use of Constrained TTML Feature <span>length-positive</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-13" class="tocxref"><span class="secno">7.9.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-13" class="tocxref"><span class="secno">7.9.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_styling" class="tocxref"><span class="secno">7.10 </span>Use of Constrained TTML Feature <span>styling-*</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-14" class="tocxref"><span class="secno">7.10.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-14" class="tocxref"><span class="secno">7.10.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_styling_inheritance_content" class="tocxref"><span class="secno">7.11 </span>Use of Constrained TTML Feature <span>styling-inheritance-content</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-15" class="tocxref"><span class="secno">7.11.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-15" class="tocxref"><span class="secno">7.11.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_styling_inheritance_region" class="tocxref"><span class="secno">7.12 </span>Use of Constrained TTML Feature <span>styling-inheritance-region</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-16" class="tocxref"><span class="secno">7.12.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-16" class="tocxref"><span class="secno">7.12.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_textAlign_absolute" class="tocxref"><span class="secno">7.13 </span>Use of Constrained TTML Feature <span>textAlign-absolute</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-17" class="tocxref"><span class="secno">7.13.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-17" class="tocxref"><span class="secno">7.13.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_textDecoration_under" class="tocxref"><span class="secno">7.14 </span>Use of Constrained TTML Feature <span>textDecoration-under</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-18" class="tocxref"><span class="secno">7.14.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-18" class="tocxref"><span class="secno">7.14.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_textOutline_unblurred" class="tocxref"><span class="secno">7.15 </span>Use of Constrained TTML Feature <span>textOutline-unblurred</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-19" class="tocxref"><span class="secno">7.15.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-19" class="tocxref"><span class="secno">7.15.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_writingMode_horizontal_lr" class="tocxref"><span class="secno">7.16 </span>Use of Constrained TTML Feature <span>writingMode-horizontal-lr</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-20" class="tocxref"><span class="secno">7.16.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-20" class="tocxref"><span class="secno">7.16.2 </span>Constraints</a></li></ul></li></ul></li><li class="tocline"><a href="#layout_constraints" class="tocxref"><span class="secno">8. </span>Layout Constraints</a><ul class="toc"><li class="tocline"><a href="#Constrained_TTML_Feature_layout" class="tocxref"><span class="secno">8.1 </span>Use of Constrained TTML Feature <span>layout</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-21" class="tocxref"><span class="secno">8.1.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-21" class="tocxref"><span class="secno">8.1.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_lineBreak-uax14" class="tocxref"><span class="secno">8.2 </span>Use of Constrained TTML Feature <span>lineBreak-uax14</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-22" class="tocxref"><span class="secno">8.2.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-22" class="tocxref"><span class="secno">8.2.2 </span>Constraints</a></li></ul></li></ul></li><li class="tocline"><a href="#timing_constraints" class="tocxref"><span class="secno">9. </span>Timing Constraints</a><ul class="toc"><li class="tocline"><a href="#Constrained_TTML_Feature_timing" class="tocxref"><span class="secno">9.1 </span>Use of Constrained TTML Feature <span>timing</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-23" class="tocxref"><span class="secno">9.1.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-23" class="tocxref"><span class="secno">9.1.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#Constrained_TTML_Feature_time_offset" class="tocxref"><span class="secno">9.2 </span>Use of Constrained TTML Feature <span>time-offset</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-24" class="tocxref"><span class="secno">9.2.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-24" class="tocxref"><span class="secno">9.2.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#frameRate" class="tocxref"><span class="secno">9.3 </span>Use of Constrained TTML Feature <span>ttp:frameRate and ttp:frameRateMultiplier</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-25" class="tocxref"><span class="secno">9.3.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-25" class="tocxref"><span class="secno">9.3.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#animation" class="tocxref"><span class="secno">9.4 </span>Use of Constrained TTML Feature <span>animation</span></a><ul class="toc"><li class="tocline"><a href="#usage-scenario-26" class="tocxref"><span class="secno">9.4.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-26" class="tocxref"><span class="secno">9.4.2 </span>Constraints</a></li></ul></li></ul></li><li class="tocline"><a href="#other_constraints" class="tocxref"><span class="secno">10. </span>Other Constraints</a><ul class="toc"><li class="tocline"><a href="#Encoding_Constraints" class="tocxref"><span class="secno">10.1 </span>Encoding Constraints</a><ul class="toc"><li class="tocline"><a href="#usage-scenario-27" class="tocxref"><span class="secno">10.1.1 </span>Usage Scenario</a></li><li class="tocline"><a href="#constraints-27" class="tocxref"><span class="secno">10.1.2 </span>Constraints</a></li></ul></li><li class="tocline"><a href="#User_Ease_of_Use_Constraints" class="tocxref"><span class="secno">10.2 </span>User Ease of Use Constraints</a></li></ul></li><li class="tocline"><a href="#Features_in_TTML_1.0_Used" class="tocxref"><span class="secno">11. </span>Features in TTML 1.0 Used in This Profile</a></li><li class="tocline"><a href="#error_handling" class="tocxref"><span class="secno">12. </span>Error handling</a></li><li class="tocline"><a href="#future_needs" class="tocxref"><span class="secno">A. </span>Future Needs for TTML next for Simple Delivery</a><ul class="toc"><li class="tocline"><a href="#Section2" class="tocxref"><span class="secno">A.1 </span>Values for font family support</a></li><li class="tocline"><a href="#Section3" class="tocxref"><span class="secno">A.2 </span>Support for character edge features</a></li><li class="tocline"><a href="#Section4" class="tocxref"><span class="secno">A.3 </span>Specify rendering model that accounts for drawing performance</a></li></ul></li><li class="tocline"><a href="#mapping-of-us-government-requirements-to-constrained-profile-features" class="tocxref"><span class="secno">B. </span>Mapping of US Government Requirements to Constrained Profile Features</a></li><li class="tocline"><a href="#code-points" class="tocxref"><span class="secno">C. </span>Code points</a><ul class="toc"><li class="tocline"><a href="#color-values" class="tocxref"><span class="secno">C.1 </span>Color values</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C.2 </span>Acknowledgements</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></section>
 
 <section id="introduction">
 <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
@@ -624,16 +624,17 @@
 <section class="Structural_Constraints" id="structural-constraints">
 <!--OddPage--><h2><span class="secno">5. </span>Structural Constraints</h2>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
-<div><div class="numbered constraint" title="R0001">A document <em class="rfc2119" title="must">must</em> contain both a head and body element.</div></div>
-<div><div class="numbered constraint" title="R0002">A document <em class="rfc2119" title="must">must</em> contain both a styling and a layout element.</div></div>
-<div><div class="numbered constraint" title="R0003">A document <em class="rfc2119" title="must not">must not</em> use a div element inside a div element.</div></div>
-<div><div class="numbered constraint" title="R0004">A document <em class="rfc2119" title="must">must</em> contain only a single level of span element within a p element.</div></div>
+<div><div class="numbered constraint" title="R0001">A document <em class="rfc2119" title="must">must</em> contain both a <code>head</code> and <code>body</code> element.</div></div>
+<div><div class="numbered constraint" title="R0002">A document <em class="rfc2119" title="must">must</em> contain both a <code>styling</code> and a <code>layout</code> element.</div></div>
+<div><div class="numbered constraint" title="R0003">A document <em class="rfc2119" title="must not">must not</em> use a <code>div</code> element inside a <code>div</code> element.</div></div>
+<div><div class="numbered constraint" title="R0004">A document <em class="rfc2119" title="must not">must not</em> use more than one level of <code>span</code> element within a <code>p</code> element.</div></div>
 <div><div class="numbered" title="E0001">Single level of spans.</div></div>
-<div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;"><span style="color: blue;">&lt;</span><span style="color: #a31515;">span</span><span style="color: blue;"> </span><span style="color: red;">style</span><span style="color: blue;">=</span>"<span style="color: blue;">s1</span>"<span style="color: blue;">&gt;</span>A<span style="color: blue;">&lt;/</span><span style="color: #a31515;">span</span><span style="color: blue;">&gt;</span>
+<div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;"><span style="color: blue;">&lt;</span><span style="color: #a31515;">span</span><span style="color: blue;"> </span><span style="color: red;">style</span><span style="color: blue;">=</span>"<span style="color: blue;">s1</span>"<span style="color: blue;">&gt;</span>A<span style="color: blue;">&lt;/</span><span style="color: #a31515;">span</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">&lt;</span><span style="color: #a31515;">span</span><span style="color: blue;"> </span><span style="color: red;">style</span><span style="color: blue;">=</span>"<span style="color: blue;">s3</span>"<span style="color: blue;">&gt;</span>B<span style="color: blue;">&lt;/</span><span style="color: #a31515;">span</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">&lt;</span><span style="color: #a31515;">span</span><span style="color: blue;"> </span><span style="color: red;">style</span><span style="color: blue;">=</span>"<span style="color: blue;">s1</span>"<span style="color: blue;">&gt;</span>C<span style="color: blue;">&lt;/</span><span style="color: #a31515;">span</span><span style="color: blue;">&gt;</span></pre></div>
-<div><div class="numbered constraint" title="R0005">A document <em class="rfc2119" title="must">must</em> reference all styles using a style attribute to a style element.</div></div>
-<div><div class="numbered constraint" title="R0006">A document <em class="rfc2119" title="must">must</em> have all elements are in order of time. That is, in a par context, a timed element <em class="rfc2119" title="must not">must not</em> lexically precede another timed element with an earlier start time.</div></div>
+<div><div class="numbered constraint" title="R0005">A document <em class="rfc2119" title="must">must</em> reference all styles using a <code>style</code> attribute making reference to a <code>style</code> element.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 2</span></div><p class="">The above requirement needs to be rewritten for clarity, changing the sense to be a proscription.</p></div>
+<div><div class="numbered constraint" title="R0006">A document <em class="rfc2119" title="must">must</em> have all elements are in order of time. That is, in a parallel timing context, a timed element <em class="rfc2119" title="must not">must not</em> lexically precede another timed element with an earlier start time.</div></div>
 </section>
 <section id="Constrained_Features">
 <!--OddPage--><h2><span class="secno">6. </span>Constrained Features</h2>
@@ -764,8 +765,9 @@
 <section class="Core_Constraints" id="constraints-3">
 <h4><span class="secno">6.4.2 </span>Constraints</h4>
 <div><div class="numbered constraint" title="R0008">Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents referencing this profile using the following URI: <dfn id="dfn-http-www.w3.org-tr-profile-simple-delivery">http://www.w3.org/TR/profile/simple-delivery</dfn>.</div></div>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>See also <a href="#conformance">Conformance</a>. [<cite><a class="bibref" href="#bib-TTML10">TTML10</a></cite>] allows zero or more profiles (ttp:profile in the head element) to be specified and used simultaneously. A presentation processor may reject documents it does not understand.</p></div></div>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>When the <code>use</code> attribute is used on the <code>ttp:profile</code> element could indicate the geographical region for which the profile is used. For example, specific styling capabilities could be used in a particular geographical region. See also <a href="#other_constraints">Other Constraints</a>.</p></div></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>See also <a href="#conformance">Conformance</a>. [<cite><a class="bibref" href="#bib-TTML10">TTML10</a></cite>] allows zero or more profiles (<code>ttp:profile</code> in the <code>head</code> element) to be specified and used simultaneously. A presentation processor may reject documents it does not understand.</p></div></div>
+<div class="issue"><div class="issue-title"><span>Issue 3</span></div><p class="">The phrase <em>does not understand</em> above is not well defined.</p></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>When the <code>use</code> attribute is used on the <code>ttp:profile</code> element, it may indicate the geographical region for which the profile is used. For example, specific styling capabilities could be used in a particular geographical region. See also <a href="#other_constraints">Other Constraints</a>.</p></div></div>
 </section>
 </section>
 <section id="Use_of_Constrained_TTML_Feature_content_structure">
@@ -826,21 +828,27 @@
 <section class="Core_Constraints" id="constraints-5">
 <h4><span class="secno">7.1.2 </span>Constraints</h4>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
-<div><div class="numbered constraint" title="R0009">The backgroundColor <em class="rfc2119" title="must">must</em> be expressed in #rrggbbaa format exclusively using the <dfn id="dfn-hexdigit">&lt;hexdigit&gt;</dfn> style value expression.</div></div>
-<div><div class="numbered constraint" title="R0010">The backgroundColor <em class="rfc2119" title="must">must</em> support the colors outlined in <a href="#color-values">Color Values</a>.</div></div>
+<div><div class="numbered constraint" title="R0009">The <code>tts:backgroundColor</code> attribute <em class="rfc2119" title="must">must</em> be expressed in <code>#rrggbbaa</code> format exclusively using the <dfn id="dfn-hexdigit">&lt;hexdigit&gt;</dfn> style value expression.</div></div>
+<div><div class="numbered constraint" title="R0010">The <code>tts:backgroundColor</code> attribute <em class="rfc2119" title="must">must</em> support the colors outlined in <a href="#color-values">Color Values</a>.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 4</span></div><p class="">The phrase <em>attribute <em class="rfc2119" title="must">must</em> support</em> above is probably incorrect.</p></div>
 <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>These colors are identical to those identified in the CEA708-D, Section 8.8 [RBG resolution of 4 bits for each primary (03)].</p></div></div>
-<div><div class="numbered constraint" title="R0011">The alpha component of backgroundColor <em class="rfc2119" title="must">must</em> support the opacity values outlined in <a href="#color-values">Color Values</a>.</div></div>
-<div><div class="numbered constraint" title="R0012">The alpha component of backgroundColor for a region <em class="rfc2119" title="must">must</em> be zero (0).</div></div>
-<div><div class="numbered constraint" title="R0013">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify a backgroundColor for p and span elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</div></div>
-<div><div class="numbered constraint" title="R0014">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify a backgroundColor for p and span elements to allow for semi-transparent and transparent opacities.</div></div>
+<div><div class="numbered constraint" title="R0011">The alpha component of a <code>tts:backgroundColor</code> attribute <em class="rfc2119" title="must">must</em> support the opacity values outlined in <a href="#color-values">Color Values</a>.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 5</span></div><p class="">The phrase <em>attribute <em class="rfc2119" title="must">must</em> support</em> above is probably incorrect.</p></div>
+<div><div class="numbered constraint" title="R0012">The alpha component of a <code>tts:backgroundColor</code> attribute for a <code>region</code> <em class="rfc2119" title="must">must</em> be zero (0).</div></div>
+<div><div class="numbered constraint" title="R0013">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify a <code>tts:backgroundColor</code> for <code>p</code> and <code>span</code> elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 6</span></div><p class="">The phrase <em>the user</em> above is probably incorrect.</p></div>
+<div><div class="numbered constraint" title="R0014">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify a <code>tts:backgroundColor</code> for <code>p</code> and <code>span</code> elements to allow for semi-transparent and transparent opacities.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 7</span></div><p class="">The phrase <em>the user</em> above is probably incorrect.</p></div>
 <div><div class="numbered" title="E0002">Multiple Background Styles. The <code>tts:backgroundColor</code> is specified distinctly for a region, a paragraph selected into
 that region, and a span of text in that paragraph.</div></div>
-<div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">&lt;region id="r1" tts:backgroundColor="#00000000"/&gt;
+
+<div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example" style="font-family: monospace; font-size: 13; color: black; background: white;"><span style="color:blue;">&lt;</span><span style="color:maroon;">region</span>&nbsp;<span style="color:red;">id</span><span style="color:blue;">="r1"</span>&nbsp;<span style="color:red;">tts</span><span style="color:blue;">:</span><span style="color:red;">backgroundColor</span><span style="color:blue;">="#00000000"/&gt;</span>
 ...
-&lt;p region="r1" tts:backgroundColor="#1049edff"&gt;
-  Twinkle, twinkle, little bat!&lt;br&gt;
-  How &lt;span tts:backgroundColor="#ed1078ff"&gt;I wonder&lt;/span&gt; where you're at!
-&lt;/p&gt;</pre></div>
+<span style="color:blue;">&lt;</span><span style="color:maroon;">p</span>&nbsp;<span style="color:red;">region</span><span style="color:blue;">="r1"</span>&nbsp;<span style="color:red;">tts</span><span style="color:blue;">:</span><span style="color:red;">backgroundColor</span><span style="color:blue;">="#1049edff"&gt;</span>
+&nbsp;&nbsp;Twinkle,&nbsp;twinkle,&nbsp;little&nbsp;bat!<span style="color:blue;">&lt;</span><span style="color:maroon;">br</span><span style="color:blue;">&gt;</span>
+&nbsp;&nbsp;How&nbsp;<span style="color:blue;">&lt;</span><span style="color:maroon;">span</span>&nbsp;<span style="color:red;">tts</span><span style="color:blue;">:</span><span style="color:red;">backgroundColor</span><span style="color:blue;">="#ed1078ff"&gt;</span>I&nbsp;wonder<span style="color:blue;">&lt;/</span><span style="color:maroon;">span</span><span style="color:blue;">&gt;</span>&nbsp;where&nbsp;you're&nbsp;at!
+<span style="color:blue;">&lt;/</span><span style="color:maroon;">p</span><span style="color:blue;">&gt;</span></pre></div>
+
 </section>
 </section>
 <section id="Constrained_TTML_Feature_color">
@@ -868,12 +876,16 @@
 <section class="Core_Constraints" id="constraints-6">
 <h4><span class="secno">7.2.2 </span>Constraints</h4>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
-<div><div class="numbered constraint" title="R0015">The color <em class="rfc2119" title="must">must</em> be expressed in #rrggbbaa format exclusively using the <dfn id="dfn-hexdigit-1">&lt;hexdigit&gt;</dfn> style value expression.</div></div>
-<div><div class="numbered constraint" title="R0016">The color <em class="rfc2119" title="must">must</em> support the colors outlined in <a href="#color-values">Color Values</a>.</div></div>
+<div><div class="numbered constraint" title="R0015">The <code>tts:color</code> attribute <em class="rfc2119" title="must">must</em> be expressed in <code>#rrggbbaa</code> format exclusively using the <dfn id="dfn-hexdigit-1">&lt;hexdigit&gt;</dfn> style value expression.</div></div>
+<div><div class="numbered constraint" title="R0016">The <code>tts:color</code> attribute <em class="rfc2119" title="must">must</em> support the colors outlined in <a href="#color-values">Color Values</a>.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 8</span></div><p class="">The phrase <em>attribute <em class="rfc2119" title="must">must</em> support</em> above is probably incorrect.</p></div>
 <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>These colors are identical to those identified in the CEA708-D, Section 8.8 [RBG resolution of 4 bits for each primary (03)].</p></div></div>
-<div><div class="numbered constraint" title="R0017">The alpha component of color <em class="rfc2119" title="must">must</em> support the opacity values outlined in <a href="#color-values">Color Values</a>.</div></div>
-<div><div class="numbered constraint" title="R0018">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify a color for p and span elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</div></div>
-<div><div class="numbered constraint" title="R0019">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify a color for p and span elements to allow for semi-transparent and transparent opacities.</div></div>
+<div><div class="numbered constraint" title="R0017">The alpha component of a <code>tts:color</code> attribute <em class="rfc2119" title="must">must</em> support the opacity values outlined in <a href="#color-values">Color Values</a>.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 9</span></div><p class="">The phrase <em>attribute <em class="rfc2119" title="must">must</em> support</em> above is probably incorrect.</p></div>
+<div><div class="numbered constraint" title="R0018">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify a <code>tts:color</code> attribute for <code>p</code> and <code>span</code> elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 10</span></div><p class="">The phrase <em>the user</em> above is probably incorrect.</p></div>
+<div><div class="numbered constraint" title="R0019">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify a <code>tts:color</code> attribute for <code>p</code> and <code>span</code> elements to allow for semi-transparent and transparent opacities.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 11</span></div><p class="">The phrase <em>the user</em> above is probably incorrect.</p></div>
 </section>
 </section>
 <section id="Constrained_TTML_Feature_display_region">
@@ -920,7 +932,7 @@
 <td>#extent-region</td>
 <td>Required with constraints</td>
 <td>region<br>
-root</td>
+tt</td>
 <td>&nbsp;</td>
 <td>&nbsp;</td>
 </tr>
@@ -928,7 +940,7 @@
 </section>
 <section class="Core_Constraints" id="constraints-8">
 <h4><span class="secno">7.4.2 </span>Constraints</h4>
-<div><div class="numbered constraint" title="R0020">The origin and extent of a region <em class="rfc2119" title="must not">must not</em> be specified such that the region extends outside of the root container.</div></div>
+<div><div class="numbered constraint" title="R0020">The <code>tts:origin</code> and <code>tts:extent</code> attributes of a <code>region</code> element <em class="rfc2119" title="must not">must not</em> be specified such that the region extends outside of the root container.</div></div>
 <div><div class="numbered constraint" title="R0021">A presentation processor <em class="rfc2119" title="must">must</em> fix the root container origin so that it corresponds with the top, left corner of the related
 media object [<cite><a class="bibref" href="#bib-TTML10SE">TTML10SE</a></cite>], Section 2.2.</div></div>
 <div><div class="numbered constraint" title="R0022">A presentation processor <em class="rfc2119" title="must">must</em> fix the root container extent so that it corresponds with the extent of the related
@@ -950,14 +962,15 @@
 <p>A Paint-on caption typically appears on the screen one character at a time and is displayed like a Pop-up caption.</p>
 <p>These caption styles are further elucidated by examples below.</p>
 <div><div class="numbered" title="E0003">Pop-up style</div></div>
-<div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;"><span style="color: blue;">&lt;</span><span style="color: #a31515;">tt</span><span style="color: blue;"> </span><span style="color: red;">xml:lang</span><span style="color: blue;">=</span>"<span style="color: blue;">en-us</span>"<span style="color: blue;"> </span><span style="color: red;">xmlns</span><span style="color: blue;">=</span>"<span style="color: blue;">http://www.w3.org/ns/ttml</span>"<span style="color: blue;"> </span>
+<div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;"><span style="color: blue;">&lt;</span><span style="color: #a31515;">tt</span><span style="color: blue;"> </span><span style="color: red;">xml:lang</span><span style="color: blue;">=</span>"<span style="color: blue;">en-us</span>"<span style="color: blue;"> </span><span style="color: red;">xmlns</span><span style="color: blue;">=</span>"<span style="color: blue;">http://www.w3.org/ns/ttml</span>"<span style="color: blue;"> </span>
 <span style="color: blue;">    </span><span style="color: red;">xmlns:s</span><span style="color: blue;">=</span>'<span style="color: blue;">http://www.w3.org/ns/ttml#styling</span>'<span style="color: blue;"> </span>
 <span style="color: blue;">    </span><span style="color: red;">xmlns:p</span><span style="color: blue;">=</span>'<span style="color: blue;">http://www.w3.org/ns/ttml#parameter</span>'<span style="color: blue;"> &gt;</span>
 <span style="color: blue;">  &lt;</span><span style="color: #a31515;">head</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">    &lt;</span><span style="color: #a31515;">p:profile</span><span style="color: blue;"> </span><span style="color: red;">use</span><span style="color: blue;">=</span>"<span style="color: blue;">http://www.w3.org/ns/ttml/profile/online-delivery</span>"<span style="color: blue;">/&gt;</span>
 <span style="color: blue;">    &lt;</span><span style="color: #a31515;">styling</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">      &lt;!--</span><span style="color: green;"> A typical transparent region with centered text that has an outline </span><span style="color: blue;">--&gt;</span>
-<span style="color: blue;">      &lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">bottomMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">#000000ff 5%</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">#00000000</span>"<span style="color: blue;"> </span><span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style="color: blue;">=</span>'<span style="color: blue;">20% 58%</span>'<span style="color: blue;"> </span><span style="color: red;">s:extent</span><span style="color: blue;">=</span>'<span style="color: blue;">60% 18%</span>'<span style="color: blue;">/&gt;</span>
+<span style="color: blue;">      &lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">bottomMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">#000000ff 5%</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">#00000000</span>"<span style="color: blue;"> </span>
+             <span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style="color: blue;">=</span>'<span style="color: blue;">20% 58%</span>'<span style="color: blue;"> </span><span style="color: red;">s:extent</span><span style="color: blue;">=</span>'<span style="color: blue;">60% 18%</span>'<span style="color: blue;">/&gt;</span>
 <span style="color: blue;">    &lt;/</span><span style="color: #a31515;">styling</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">    &lt;</span><span style="color: #a31515;">layout</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">      &lt;!--</span><span style="color: green;"> typical 'Pop-up' type region </span><span style="color: blue;">--&gt;</span>
@@ -974,12 +987,14 @@
 <section>
 <div><div class="numbered" title="E0004">Positioned style. An off-screen narrator is present and no graphics are used. Content placed in a single region in the bottom one-third of that region.</div></div>
 <!-- div data-include=example2.xml'></div -->
-<div class="example"><div class="example-title"><span>Example 4</span></div><pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;"><span style="color: blue;">&lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">bottomMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">black 1px</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">transparent</span>"<span style="color: blue;"> </span><span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style="color: blue;">=</span>'<span style="color: blue;">20% 58%</span>'<span style="color: blue;"> </span><span style="color: red;">s:extent</span><span style="color: blue;">=</span>'<span style="color: blue;">60% 18%</span>'<span style="color: blue;">/&gt;</span>
-<span style="color: blue;">&lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">topMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">black 1px</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">transparent</span>"<span style="color: blue;"> </span><span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style="color: blue;">=</span>'<span style="color: blue;">20% 10%</span>'<span style="color: blue;"> </span><span style="color: red;">s:extent</span><span style="color: blue;">=</span>'<span style="color: blue;">60% 18%</span>'<span style="color: blue;">/&gt;</span></pre></div></section>
+<div class="example"><div class="example-title"><span>Example 4</span></div><pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;"><span style="color: blue;">&lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">bottomMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">black 1px</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">transparent</span>"<span style="color: blue;"> </span>
+       <span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style="color: blue;">=</span>'<span style="color: blue;">20% 58%</span>'<span style="color: blue;"> </span><span style="color: red;">s:extent</span><span style="color: blue;">=</span>'<span style="color: blue;">60% 18%</span>'<span style="color: blue;">/&gt;</span>
+<span style="color: blue;">&lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">topMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">black 1px</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">transparent</span>"<span style="color: blue;"> </span>
+       <span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style="color: blue;">=</span>'<span style="color: blue;">20% 10%</span>'<span style="color: blue;"> </span><span style="color: red;">s:extent</span><span style="color: blue;">=</span>'<span style="color: blue;">60% 18%</span>'<span style="color: blue;">/&gt;</span></pre></div></section>
 <section>
 <div><div class="numbered" title="E0005">Moving regions. Content is positioned based on location of speaker, visible in the bottom two lines individually positioned in region(s) so as to avoid background content..</div></div>
 <!-- div data-include=example3.xml'></div -->
-<div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;"><span style="color: blue;">&lt;?</span><span style="color: #a31515;">xml</span><span style="color: blue;"> </span><span style="color: red;">version</span><span style="color: blue;">=</span>"<span style="color: blue;">1.0</span>"<span style="color: blue;"> </span><span style="color: red;">encoding</span><span style="color: blue;">=</span>"<span style="color: blue;">utf-8</span>"<span style="color: blue;">?&gt;</span>
+<div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;"><span style="color: blue;">&lt;?</span><span style="color: #a31515;">xml</span><span style="color: blue;"> </span><span style="color: red;">version</span><span style="color: blue;">=</span>"<span style="color: blue;">1.0</span>"<span style="color: blue;"> </span><span style="color: red;">encoding</span><span style="color: blue;">=</span>"<span style="color: blue;">utf-8</span>"<span style="color: blue;">?&gt;</span>
 <span style="color: blue;">&lt;</span><span style="color: #a31515;">tt</span><span style="color: blue;"> </span><span style="color: red;">xml:lang</span><span style="color: blue;">=</span>"<span style="color: blue;">en-us</span>"<span style="color: blue;"> </span><span style="color: red;">xmlns</span><span style="color: blue;">=</span>"<span style="color: blue;">http://www.w3.org/ns/ttml</span>"<span style="color: blue;"> </span><span style="color: red;">xmlns:s</span><span style="color: blue;">=</span>'<span style="color: blue;">http://www.w3.org/ns/ttml#styling</span>'<span style="color: blue;">&gt;</span>
 <span style="color: blue;">  &lt;</span><span style="color: #a31515;">head</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">    &lt;</span><span style="color: #a31515;">styling</span><span style="color: blue;">&gt;</span>
@@ -1052,18 +1067,18 @@
 <section class="Core_Constraints" id="constraints-9">
 <h4><span class="secno">7.5.2 </span>Constraints</h4>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
-<div><div class="numbered constraint" title="R0023">The document <em class="rfc2119" title="must">must</em> use the tts:fontFamily attribute using only the following values:</div></div>
+<div><div class="numbered constraint" title="R0023">A document <em class="rfc2119" title="must not">must not</em> specify a <code>tts:fontFamily</code> attribute whose value is not one of the following:</div></div>
 <ul>
-<li>default</li>
-<li>monospaceSerif</li>
-<li>proportionalSerif</li>
-<li>monospaceSansSerif</li>
-<li>proportionalSansSerif</li>
-<li>casual</li>
-<li>cursive</li>
-<li>smallCaps</li>
+<li><code>default</code></li>
+<li><code>monospaceSerif</code></li>
+<li><code>proportionalSerif</code></li>
+<li><code>monospaceSansSerif</code></li>
+<li><code>proportionalSansSerif</code></li>
+<li><code>casual</code></li>
+<li><code>cursive</code></li>
+<li><code>smallCaps</code></li>
 </ul>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Values of tts:fontFamily that do not not correspond to generic font family names in [<cite><a class="bibref" href="#bib-TTML10">TTML10</a></cite>], such as <code>casual</code>, <code>cursive</code> and <code>smallCaps</code>, may be used. These are to be interpreted as local font names, which, if not available, the <code>default</code> font family is to be used.</p></div></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Values of <code>tts:fontFamily</code> that do not not correspond to generic font family names in [<cite><a class="bibref" href="#bib-TTML10">TTML10</a></cite>], such as <code>casual</code>, <code>cursive</code> and <code>smallCaps</code>, may be used. These are to be interpreted as local font names, which, if not available, the <code>default</code> font family is to be used.</p></div></div>
 <div><div class="numbered constraint" title="R0024">A presentation processor <em class="rfc2119" title="must">must</em> map the generic font names to fonts as follows:</div></div>
 <table>
 <tbody><tr>
@@ -1112,8 +1127,14 @@
 <td>Similar to Engravers Gothic</td>
 </tr>
 </tbody></table>
-<div><div class="numbered constraint" title="R0025">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify a generic fontFamily for the document using the values shown in the preceding table.</div></div>
-<div><div class="numbered constraint" title="R0026">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify character edge attributes and types for the generic fontFamily names for the values shown in the preceding table.</div></div>
+<p></p>
+<div><div class="numbered constraint" title="R0025">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify a generic font family for the document using the values shown in the preceding table.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 12</span></div><p class="">The phrase <em>the user</em> above is probably incorrect.</p></div>
+<div class="issue"><div class="issue-title"><span>Issue 13</span></div><p class="">The phrase <em>for the document</em> above is probably incorrect.</p></div>
+<div class="issue"><div class="issue-title"><span>Issue 14</span></div><p class="">The above requirement appears to be redundant with R0023 and its preceding prologue.</p></div>
+<div><div class="numbered constraint" title="R0026">The presentation processor <em class="rfc2119" title="must">must</em> allow the user to specify character edge attributes and types for the generic font family names for the values shown in the preceding table.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 15</span></div><p class="">The phrase <em>the user</em> above is probably incorrect.</p></div>
+<div class="issue"><div class="issue-title"><span>Issue 16</span></div><p class="">The phrase <em>character edge attributes</em> above needs to point at a definition since this is not a TTML concept.</p></div>
 <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Presentation processor and Unicode code point support is defined in <a href="#code-points">Code Point support</a></p></div></div>
 <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Text outline can be specified using a style property to apply to characters selected for specific areas for content flowed into a region. Text outline applies a specific character edge to content. For example, when the textOutline style property is used, a type of shadow or thickness can be applied to content.</p></div></div>
 </section>
@@ -1140,14 +1161,15 @@
 <td>&nbsp;</td>
 </tr>
 </tbody></table>
+<div class="issue"><div class="issue-title"><span>Issue 17</span></div><p class="">What does <em>(root)</em> mean in the Scope column of the above table?</p></div>
 </section>
 <section class="Core_Constraints" id="constraints-10">
 <h4><span class="secno">7.6.2 </span>Constraints</h4>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
-<div><div class="numbered constraint" title="R0027">A document <em class="rfc2119" title="must not">must not</em> specify <code>tts:fontSize</code> using a value that is not one of 50%, 75%, 100%, 150% or 200%.</div></div>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Use of a fontSize of less than 75% (i.e. 50%) may result in unreadable content for a user.</p></div></div>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Specifying a fontSize is used for a document could allow the user to select a preferred fontSize.</p></div></div>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>If a specific fontSize is not supported, then, follow the semantics for a presentation processor defined in [<cite><a class="bibref" href="#bib-TTML10">TTML10</a></cite>], Section 8.2.9.</p></div></div>
+<div><div class="numbered constraint" title="R0027">A document <em class="rfc2119" title="must not">must not</em> specify a <code>tts:fontSize</code> attribute using a value that is not one of 50%, 75%, 100%, 150% or 200%.</div></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Use of a font size of less than 75% (i.e. 50%) may result in unreadable content for a user.</p></div></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Specifying a font size is used for a document could allow the user to select a preferred font size.</p></div></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>If a specific font size is not supported, then, follow the semantics for a presentation processor defined in [<cite><a class="bibref" href="#bib-TTML10">TTML10</a></cite>], Section 8.2.9.</p></div></div>
 <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Constraining the root container extent to the active video area means that the default
 font size of 1c and the default cell grid of 32 x 15 (as specified in TTML 1.0) implies an initial font height of 6.67% of the video height.</p></div></div>
 </section>
@@ -1178,6 +1200,7 @@
 <h4><span class="secno">7.7.2 </span>Constraints</h4>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
 <div><div class="numbered constraint" title="R0028">The capability <em class="rfc2119" title="must">must</em> exist for the user to specify the italic style for the font families identified in this profile.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 18</span></div><p class="">The phrase <em>the user</em> above is probably incorrect.</p></div>
 </section>
 </section>
 <section id="Constrained_TTML_Feature_length_percentage">
@@ -1206,8 +1229,8 @@
 <h4><span class="secno">7.8.2 </span>Constraints</h4>
 <p>None</p>
 <section>
-<div><div class="numbered" title="E0006">Using 10% for the tts:extent of the root container region (for example, of an 720x640 region), the equivalence to pixel units (px) could be obtained. For example, using this snippet:</div></div>
-<div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;"><span style="color:blue;">&lt;</span><span style="color:#a31515;">style</span><span style="color:blue;"> </span><span style="color:red;">xml:id</span><span style="color:blue;">=</span>"<span style="color:blue;">topLeftStyle</span>"<span style="color:blue;"> </span><span style="color:red;">s:fontSize</span><span style="color:blue;">=</span>"<span style="color:blue;">150%</span>"<span style="color:blue;"> </span><span style="color:red;">s:textAlign</span><span style="color:blue;">=</span>"<span style="color:blue;">left</span>"<span style="color:blue;"> </span><span style="color:red;">s:backgroundColor</span><span style="color:blue;">=</span>"<span style="color:blue;">#ffffffff</span>"<span style="color:blue;"> </span><span style="color:red;">s:color</span><span style="color:blue;">=</span>"<span style="color:blue;">#ff0000ff</span>"<span style="color:blue;"> </span><span style="color:red;">s:origin</span><span style="color:blue;">=</span>'<span style="color:blue;">10% 10%</span>'<span style="color:blue;"> </span><span style="color:red;">s:extent</span><span style="color:blue;">=</span>'<span style="color:blue;">40% 18%</span>'<span style="color:blue;">/&gt;</span></pre></div>
+<div><div class="numbered" title="E0006">Using 10% for the <code>tts:extent</code> of the root container region (for example, of an 720x640 region), the equivalence to pixel units (px) could be obtained. For example, using this snippet:</div></div>
+<div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;"><span style="color:blue;">&lt;</span><span style="color:#a31515;">style</span><span style="color:blue;"> </span><span style="color:red;">xml:id</span><span style="color:blue;">=</span>"<span style="color:blue;">topLeftStyle</span>"<span style="color:blue;"> </span><span style="color:red;">s:fontSize</span><span style="color:blue;">=</span>"<span style="color:blue;">150%</span>"<span style="color:blue;"> </span><span style="color:red;">s:textAlign</span><span style="color:blue;">=</span>"<span style="color:blue;">left</span>"<span style="color:blue;"> </span><span style="color:red;">s:backgroundColor</span><span style="color:blue;">=</span>"<span style="color:blue;">#ffffffff</span>"<span style="color:blue;"> </span><span style="color:red;">s:color</span><span style="color:blue;">=</span>"<span style="color:blue;">#ff0000ff</span>"<span style="color:blue;"> </span><span style="color:red;">s:origin</span><span style="color:blue;">=</span>'<span style="color:blue;">10% 10%</span>'<span style="color:blue;"> </span><span style="color:red;">s:extent</span><span style="color:blue;">=</span>'<span style="color:blue;">40% 18%</span>'<span style="color:blue;">/&gt;</span></pre></div>
 <!-- div data-include=fontsize-example.xml'></div >
                         <style xml:id="topLeftStyle" s:fontSize="150%" s:textAlign="left" s:backgroundColor="#ffffffff" s:color="#ff0000ff" 
                          s:origin='10% 10%' s:extent='40% 18%'/> -->
@@ -1270,9 +1293,14 @@
 <h4><span class="secno">7.10.2 </span>Constraints</h4>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
 <div><div class="numbered constraint" title="R0029">Styles <em class="rfc2119" title="must">must</em> be applied either by reference or through use of inline styling.</div></div>
-<div><div class="numbered constraint" title="R0030">Styles <em class="rfc2119" title="must">must</em> be applied with a single style element using the style attribute.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 19</span></div><p class="">The phrase <em><em class="rfc2119" title="must">must</em> be applied</em> above is not well defined.</p></div>
+<div class="issue"><div class="issue-title"><span>Issue 20</span></div><p class="">The above requirement appears to be redundant with R0005.</p></div>
+<div><div class="numbered constraint" title="R0030">Styles <em class="rfc2119" title="must">must</em> be applied with a single <code>style</code> element using the <code>style</code> attribute.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 21</span></div><p class="">The phrase <em><em class="rfc2119" title="must">must</em> be applied</em> above is not well defined.</p></div>
+<div class="issue"><div class="issue-title"><span>Issue 22</span></div><p class="">The above requirement needs to be elaborated in terms of markup usage.</p></div>
 <div><div class="numbered constraint" title="R0031">Style elements <em class="rfc2119" title="must not">must not</em> reference other styles.</div></div>
-<div><div class="numbered constraint" title="R0032">Style elements <em class="rfc2119" title="must not">must not</em> be child elements of region elements.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 23</span></div><p class="">The phrase <em>reference other styles</em> above is not well defined.</p></div>
+<div><div class="numbered constraint" title="R0032">A <code>region</code> element <em class="rfc2119" title="must not">must not</em> contain a child <code>style</code> element.</div></div>
 <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>The constraints in this section result in a document that contains style blocks that are complete and self-contained.</p></div></div>
 </section>
 </section>
@@ -1382,8 +1410,11 @@
 <section class="Core_Constraints" id="constraints-18">
 <h4><span class="secno">7.14.2 </span>Constraints</h4>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
-<div><div class="numbered constraint" title="R0033">The tts:textDecoration-under attribute <em class="rfc2119" title="must">must</em> support the constraints identified in this profile.</div></div>
+<div><div class="numbered constraint" title="R0033">The <code>tts:textDecoration-under</code> attribute <em class="rfc2119" title="must">must</em> support the constraints identified in this profile.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 24</span></div><p class="">The phrase <em>attribute <em class="rfc2119" title="must">must</em> support</em> above is probably incorrect.</p></div>
+<div class="issue"><div class="issue-title"><span>Issue 25</span></div><p class="">There is no such thing as a tts:textDecoration-under attribute. In any case, this requirement should actually specify a requirement.</p></div>
 <div><div class="numbered constraint" title="R0034">The capability <em class="rfc2119" title="must">must</em> exist for the user to specify the underline decoration for the font families identified in this profile.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 26</span></div><p class="">The phrase <em>the user</em> above is probably incorrect.</p></div>
 </section>
 </section>
 <section id="Constrained_TTML_Feature_textOutline_unblurred">
@@ -1412,9 +1443,16 @@
 <h4><span class="secno">7.15.2 </span>Constraints</h4>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
 <div><div class="numbered constraint" title="R0035">Character edge attributes <em class="rfc2119" title="must">must</em> be expressed using textOutline-unblurred based on the settings identified in CEA-708-D, Section 8.5.8.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 27</span></div><p class="">Not well defined.</p></div>
+<div class="issue"><div class="issue-title"><span>Issue 28</span></div><p class="">The phrase <em>character edge attributes</em> above needs to point at a definition since this is not a TTML concept.</p></div>
 <div><div class="numbered constraint" title="R0036">A text outline <em class="rfc2119" title="must">must</em> be expressed using textOutline-unblurred of up to 10% thickness.</div></div>
-<div><div class="numbered constraint" title="R0037">The user <em class="rfc2119" title="must">must</em> be able to specify character edge and type attributes using tts:textOutline attribute.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 29</span></div><p class="">Not well defined.</p></div>
+<div><div class="numbered constraint" title="R0037">The user <em class="rfc2119" title="must">must</em> be able to specify character edge and type attributes using <code>tts:textOutline</code> attribute.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 30</span></div><p class="">The phrase <em>the user</em> above is probably incorrect.</p></div>
+<div class="issue"><div class="issue-title"><span>Issue 31</span></div><p class="">The phrase <em>character edge attributes</em> above needs to point at a definition since this is not a TTML concept.</p></div>
 <div><div class="numbered constraint" title="R0038">The user <em class="rfc2119" title="should">should</em> be able to specify the rendering of character edge types of: none, raised, depressed, uniform or drop shadowed edges.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 32</span></div><p class="">The phrase <em>the user</em> above is probably incorrect.</p></div>
+<div class="issue"><div class="issue-title"><span>Issue 33</span></div><p class="">The phrase <em>character edge attributes</em> above needs to point at a definition since this is not a TTML concept.</p></div>
 <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>This requirement targets the capabilities of a presentation processor.</p></div></div>
 </section>
 </section>
@@ -1509,11 +1547,11 @@
 <div><div class="numbered constraint" title="R0043">If the aspect ratio of the root container is 4:3 (16:9), then, respectively, more than 152 (168) characters <em class="rfc2119" title="must not">must not</em> be
 present in all displayed text lines.</div></div>
 <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>These requirements accommodate content originated in Europe but displayed in the US, as well as content displayed using 16:9 format.</p></div></div>
-<div><div class="numbered constraint" title="R0044">At most one p element <em class="rfc2119" title="must">must</em> be selected into a region at a time.</div></div>
+<div><div class="numbered constraint" title="R0044">More than one <code>p</code> element <em class="rfc2119" title="must not">must not</em> be selected into a region in any synchronic intermediate document.</div></div>
 <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>The style properites of region and the content selected for the region impact how selected text flows into a region (i.e. selected text may flow outside of the region such as on a mobile device).</p></div></div>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Constraining one p element to a region logically places content from two different speakers to different region(s).</p></div></div>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>When a document author wants to construct a single phrase from a speaker with more than one line in a region, the br within a p element can be used. This construction adheres to the constraints in this section. For example for one speaker with more than one line:</p></div></div>
-<div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;"><span style="color:blue;">&lt;</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span> I always get the fuzzy end<span style="color:blue;">&lt;</span><span style="color:#a31515;">br</span><span style="color:blue;">/&gt;</span>of the lollipop<span style="color:blue;">&lt;/</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span></pre></div></section>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Constraining one <code>p</code> element to a region logically places content from two different speakers to different region(s).</p></div></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>When a document author wants to construct a single phrase from a speaker with more than one line in a region, the <code>br</code> element within a <code>p</code> element can be used. This construction adheres to the constraints in this section. For example for one speaker with more than one line:</p></div></div>
+<div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;"><span style="color:blue;">&lt;</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span> I always get the fuzzy end<span style="color:blue;">&lt;</span><span style="color:#a31515;">br</span><span style="color:blue;">/&gt;</span>of the lollipop<span style="color:blue;">&lt;/</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span></pre></div></section>
 </section>
 </section>
 <section id="timing_constraints">
@@ -1544,24 +1582,28 @@
 <section class="Core_Constraints" id="constraints-23">
 <h4><span class="secno">9.1.2 </span>Constraints</h4>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
-<div><div class="numbered constraint" title="R0045">Timing <em class="rfc2119" title="must">must</em> be expressed in the hh:mm:ss.ms or hh:mm:ss:ff format used in the timeExpression.</div></div>
+<div><div class="numbered constraint" title="R0045">Timing <em class="rfc2119" title="must">must</em> be expressed in either the <code>hh:mm:ss.ms</code> or the <code>hh:mm:ss:ff</code> format used in a time expression.</div></div>
 <div><div class="numbered constraint" title="R0046">Timing <em class="rfc2119" title="must">must</em> be expressed in the same format throughout the document.</div></div>
-<div><div class="numbered constraint" title="R0047">Presentation processors <em class="rfc2119" title="must">must</em> support durations (dur) on the p and span elements, and <em class="rfc2119" title="may">may</em> (but need not) support on other element types;
-as such, a document <em class="rfc2119" title="should not">should not</em> use a duration on an element type other than p or span.</div></div>
-<div><div class="numbered constraint" title="R0048">For timing in hh:mm:ss.ms, the following format <em class="rfc2119" title="must">must</em> be used:</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 34</span></div><p class="">The phrase <em>in the same format</em> above needs elaboration.</p></div>
+<div><div class="numbered constraint" title="R0047">Presentation processors <em class="rfc2119" title="must">must</em> support durations (<code>dur</code>) on the <code>p</code> and <code>span</code> elements, and <em class="rfc2119" title="may">may</em> (but need not) support on other element types;
+as such, a document <em class="rfc2119" title="should not">should not</em> use a duration on an element type other than <code>p</code> or <code>span</code>.</div></div>
+<div><div class="numbered constraint" title="R0048">For time expressions that use the <code>hh:mm:ss.ms</code> format, the following constraints apply:</div></div>
 <ul>
 <li>Exactly 2 digits <em class="rfc2119" title="must">must</em> be used in each of the hours, minutes, and second components (include leading zeros).</li>
 <li>Exactly 3 decimal places <em class="rfc2119" title="must">must</em> be used for the milliseconds component (include zeros).</li>
 </ul>
-<div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;"><span style="color:blue;">&lt;</span><span style="color:#a31515;">p</span><span style="color:blue;"> </span><span style="color:red;">begin</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:01.000</span>'<span style="color:blue;"> </span><span style="color:red;">end</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:11.123</span>'<span style="color:blue;"> </span><span style="color:red;">region</span><span style="color:blue;">=</span>"<span style="color:blue;">r1</span>"<span style="color:blue;"> &gt;</span>Test<span style="color:blue;">&lt;/</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span></pre></div>
-<div><div class="numbered constraint" title="R0049">For timing in hh:mm:ss.ms, the following format <em class="rfc2119" title="must">must</em> be used:</div></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>The phrase <em>milliseconds component</em> above refers to a particular use of the <code>fraction</code> of a <code>clock-time</code> time expression as defined by [<cite><a class="bibref" href="#bib-TTML10">TTML10</a></cite>] Section 10.3.1.</p></div></div>
+<div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;"><span style="color:blue;">&lt;</span><span style="color:#a31515;">p</span><span style="color:blue;"> </span><span style="color:red;">begin</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:01.000</span>'<span style="color:blue;"> </span><span style="color:red;">end</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:11.123</span>'<span style="color:blue;"> </span><span style="color:red;">region</span><span style="color:blue;">=</span>"<span style="color:blue;">r1</span>"<span style="color:blue;"> &gt;</span>Test<span style="color:blue;">&lt;/</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span></pre></div>
+<div><div class="numbered constraint" title="R0049">For time expressions that use the <code>hh:mm:ss:ff</code> format, the following constraints apply:</div></div>
 <ul>
 <li>Exactly 2 digits <em class="rfc2119" title="must">must</em> be used in each of the hours, minutes, second, and frame components (include leading zeros).</li>
-<li>A ttp:frameRate attribute <em class="rfc2119" title="must">must</em> be present on the root element.</li>
-<li>A ttp:frameRateMultiplier attribute <em class="rfc2119" title="may">may</em> be present on the root element.</li>
+<li>A <code>ttp:frameRate</code> attribute <em class="rfc2119" title="must">must</em> be present on the <code>tt</code> element.</li>
+<li>A <code>ttp:frameRateMultiplier</code> attribute <em class="rfc2119" title="may">may</em> be present on the <code>tt</code> element.</li>
 </ul>
 <p></p>
-<div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;"><span style="color:blue;">&lt;</span><span style="color:#a31515;">p</span><span style="color:blue;"> </span><span style="color:red;">begin</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:01:00</span>'<span style="color:blue;"> </span><span style="color:red;">end</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:11:22</span>'<span style="color:blue;"> </span><span style="color:red;">region</span><span style="color:blue;">=</span>"<span style="color:blue;">r1</span>"<span style="color:blue;"> &gt;</span>Test<span style="color:blue;">&lt;/</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span></pre></div></section>
+<div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;"><span style="color:blue;">&lt;</span><span style="color:#a31515;">p</span><span style="color:blue;"> </span><span style="color:red;">begin</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:01:00</span>'<span style="color:blue;"> </span><span style="color:red;">end</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:11:22</span>'<span style="color:blue;"> </span><span style="color:red;">region</span><span style="color:blue;">=</span>"<span style="color:blue;">r1</span>"<span style="color:blue;"> &gt;</span>Test<span style="color:blue;">&lt;/</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span></pre></div>
+<div class="issue"><div class="issue-title"><span>Issue 35</span></div><p class="">The above example should also show a <code>tt</code> element with a <code>ttp:frameRate</code> attribute.</p></div>
+</section>
 </section>
 <section id="Constrained_TTML_Feature_time_offset">
 <h3><span class="secno">9.2 </span>Use of Constrained TTML Feature <span>time-offset</span></h3>
@@ -1588,11 +1630,11 @@
 <section class="Core_Constraints" id="constraints-24">
 <h4><span class="secno">9.2.2 </span>Constraints</h4>
 <p>None</p>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Since the ttp:timebase attribute is outside of this profile, the implicit timebase used here is media as specified in [<cite><a class="bibref" href="#bib-TTML10">TTML10</a></cite>].</p></div></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Since the <code>ttp:timeBase</code> attribute is not supported by this profile, the implicit timebase is <code>media</code> as specified in [<cite><a class="bibref" href="#bib-TTML10">TTML10</a></cite>].</p></div></div>
 </section>
 </section>
 <section id="frameRate">
-<h3><span class="secno">9.3 </span>Use of Constrained TTML Feature <span>frameRate and frameRateMultiplier</span></h3>
+<h3><span class="secno">9.3 </span>Use of Constrained TTML Feature <span>ttp:frameRate and ttp:frameRateMultiplier</span></h3>
 <p></p>
 <section class="Usage_Scenario" id="usage-scenario-25">
 <h4><span class="secno">9.3.1 </span>Usage Scenario</h4>
@@ -1613,7 +1655,7 @@
 <td>&nbsp;</td>
 </tr>
 </tbody></table>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Use of the #frameRateMultiplier feature is optional in a document (see <a href="#Features_in_TTML_1.0_Used">Features in TTML1.0 Used in This Profile</a>).</p></div></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Use of the <code>#frameRateMultiplier</code> feature is optional in a document (see <a href="#Features_in_TTML_1.0_Used">Features in TTML1.0 Used in This Profile</a>).</p></div></div>
 </section>
 <section class="Core_Constraints" id="constraints-25">
 <h4><span class="secno">9.3.2 </span>Constraints</h4>
@@ -1645,11 +1687,13 @@
 <section class="Core_Constraints" id="constraints-26">
 <h4><span class="secno">9.4.2 </span>Constraints</h4>
 <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
-<div><div class="numbered constraint" title="R0050">The set element <em class="rfc2119" title="must">must</em> only animate the region or span element.</div></div>
-<div><div class="numbered constraint" title="R0051">The use of set elements applied to a region element <em class="rfc2119" title="must">must</em> only animate the tts:display, tts:origin or tts:extent attribute.</div></div>
-<div><div class="numbered constraint" title="R0052">The use of set elements applied to a span element <em class="rfc2119" title="must">must</em> only animate the tts:color attribute.</div></div>
-<div><div class="numbered constraint" title="R0053">No more than 6 set elements <em class="rfc2119" title="must">must</em> be used within a given element.</div></div>
-<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Animation is constrained to the scenarios where the region needs to be moved – i.e. when the “snap” display effect is required.</p></div></div>
+<div><div class="numbered constraint" title="R0050">The <code>set</code> element <em class="rfc2119" title="must">must</em> only animate the <code>region</code> or <code>span</code> element.</div></div>
+<div class="issue"><div class="issue-title"><span>Issue 36</span></div><p class="">Does the above requirement mean that <code>set</code> must not appear as a child of any element other than region or span elements?</p></div>
+<div><div class="numbered constraint" title="R0051">The use of <code>set</code> elements applied to a <code>region</code> element <em class="rfc2119" title="must">must</em> only animate the <code>tts:display</code>, <code>tts:origin</code> or <code>tts:extent</code> attribute.</div></div>
+<div><div class="numbered constraint" title="R0052">The use of <code>set</code> elements applied to a <code>span</code> element <em class="rfc2119" title="must">must</em> only animate the <code>tts:color</code> attribute.</div></div>
+<div><div class="numbered constraint" title="R0053">More than six (6) <code>set</code> child elements <em class="rfc2119" title="must not">must not</em> be specified within a given element.</div></div>
+<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Animation is constrained to the scenarios where the region needs to be moved, e.g., when a <em>snap</em> display effect is desired.</p></div></div>
+<div class="issue"><div class="issue-title"><span>Issue 37</span></div><p class="">The phrase <em>snap display effect</em> is not defined.</p></div>
 <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Animation is constrained to the scenarios to change the foreground color of content when flashing text is required.</p></div></div>
 </section>
 </section>
@@ -1670,7 +1714,7 @@
 <th>Constraint</th>
 </tr>
 <tr>
-<td>document representation</td>
+<td>document encoding</td>
 <td>Required with constraints</td>
 <td>&nbsp;</td>
 <td>&nbsp;</td>
@@ -1698,7 +1742,7 @@
 </section>
 <section id="Features_in_TTML_1.0_Used">
 <!--OddPage--><h2><span class="secno">11. </span>Features in TTML 1.0 Used in This Profile</h2>
-<pre style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;"><span style="color: blue;">&lt;?</span><span style="color: #a31515;">xml</span><span style="color: blue;"> </span><span style="color: red;">version</span><span style="color: blue;">=</span>"<span style="color: blue;">1.0</span>"<span style="color: blue;"> </span><span style="color: red;">encoding</span><span style="color: blue;">=</span>"<span style="color: blue;">utf-8</span>"<span style="color: blue;">?&gt;</span>
+<pre style="font-family: monospace; font-size: 10pt; color: black; background: white;"><span style="color: blue;">&lt;?</span><span style="color: #a31515;">xml</span><span style="color: blue;"> </span><span style="color: red;">version</span><span style="color: blue;">=</span>"<span style="color: blue;">1.0</span>"<span style="color: blue;"> </span><span style="color: red;">encoding</span><span style="color: blue;">=</span>"<span style="color: blue;">utf-8</span>"<span style="color: blue;">?&gt;</span>
 <span style="color: blue;">&lt;?</span><span style="color: #a31515;">xml</span><span style="color: blue;"> </span><span style="color: red;">version</span><span style="color: blue;">=</span>"<span style="color: blue;">1.0</span>"<span style="color: blue;"> </span><span style="color: red;">encoding</span><span style="color: blue;">=</span>"<span style="color: blue;">utf-8</span>"<span style="color: blue;">?&gt;</span>
 <span style="color: blue;">&lt;</span><span style="color: #a31515;">profile</span><span style="color: blue;"> </span><span style="color: red;">xmlns</span><span style="color: blue;">=</span>"<span style="color: blue;">http://www.w3.org/ns/ttml#parameter</span>"<span style="color: blue;">&gt;</span>
 <span style="color: blue;">  &lt;</span><span style="color: #a31515;">features</span><span style="color: blue;"> </span><span style="color: red;">xml:base</span><span style="color: blue;">=</span>"<span style="color: blue;">http://www.w3.org/ns/ttml/feature/</span>"<span style="color: blue;">&gt;</span>
@@ -1740,7 +1784,7 @@
 </pre></section>
 <section id="error_handling">
 <!--OddPage--><h2><span class="secno">12. </span>Error handling</h2>
-<div class="issue"><div class="issue-title"><span>Issue 2</span></div><p class="">This section needs to be rewritten to be better organized, more specific (define what is meant by 'understood', 'known', 'unknown'), grammatical, and use correct terminology (e.g., well-formed vs valid).</p></div>
+<div class="issue"><div class="issue-title"><span>Issue 38</span></div><p class="">This section needs to be rewritten to be better organized, more specific (define what is meant by 'understood', 'known', 'unknown'), grammatical, and use correct terminology (e.g., well-formed vs valid).</p></div>
 <p>A presentation processor may be presented with documents that contain features that are not understood. The table that follows outlines the behavior expected under specific conditions. The pre-requisite if the caption file is syntactically valid XML.</p>
 <table style="width: 100%;">
 <tbody><tr>
@@ -1764,7 +1808,7 @@
 <section class="appendix" id="future_needs">
 <!--OddPage--><h2><span class="secno">A. </span>Future Needs for TTML next for Simple Delivery</h2>
 <section class="appendix" id="Section2">
-<h3><span class="secno">A.1 </span>Values for fontFamily support</h3>
+<h3><span class="secno">A.1 </span>Values for font family support</h3>
 <p>The casual, cursive and smallCaps generic font families are expected to be considered for inclusion in a future version of TTML.</p>
 </section>
 <section class="appendix" id="Section3">
@@ -1839,20 +1883,20 @@
 </tbody></table>
 <p>TTML Mandatory Features</p>
 <ul>
-<li>core</li>
-<li>content</li>
-<li>presentation</li>
-<li>structure</li>
-<li>time-offset</li>
-<li>timing</li>
+<li><code>#core</code></li>
+<li><code>#content</code></li>
+<li><code>#presentation</code></li>
+<li><code>#structure</code></li>
+<li><code>#time-offset</code></li>
+<li><code>#timing</code></li>
 </ul>
 <p>TTML Features Required That Support Other Requirements</p>
 <ul>
-<li>styling</li>
-<li>styling-referential</li>
-<li>styling-inline</li>
-<li>styling-inheritance-content</li>
-<li>styling-inheritance-region</li>
+<li><code>#styling</code></li>
+<li><code>#styling-referential</code></li>
+<li><code>#styling-inline</code></li>
+<li><code>#styling-inheritance-content</code></li>
+<li><code>#styling-inheritance-region</code></li>
 </ul>
 <p></p>
 </section>
@@ -2877,7 +2921,7 @@
 Presentation processors may also provide Glyph coverage for additional Unicode code points
 <section class="color_values" id="color-values">
 <h3><span class="secno">C.1 </span>Color values</h3>
-<p>For color values of the form #rrggbbaa, presentation processors <em class="rfc2119" title="must">must</em> support combinations where the rr, gg, bb components may be either 00 or ff; and the aa component may be 00, 54, A8 or FF. e.g: #00ffff54. Additionally presentation processors <em class="rfc2119" title="should">should</em> support values for rr, gg, and bb of 54 or A8, and <em class="rfc2119" title="may">may</em> support all possible values between 00 to ff.</p>
+<p>For color values of the form <code>#rrggbbaa</code>, presentation processors <em class="rfc2119" title="must">must</em> support combinations where the red, green, and blue components may be either <code>00</code> or <code>FF</code>; and the alpha component may be <code>00</code>, <code>54</code>, <code>A8</code> or <code>FF</code>, e.g, #00FFFF54. Additionally presentation processors <em class="rfc2119" title="should">should</em> support values for red, green, and blue of <code>54</code> or <code>A8</code>, and <em class="rfc2119" title="may">may</em> support all possible values between <code>00</code> and <code>FF</code>.</p>
 <table>
 <tbody><tr>
 <th>Color</th>
@@ -2926,10 +2970,10 @@
 
 
 <section id="references" class="appendix"><!--OddPage--><h2><span class="secno">D. </span>References</h2><section id="normative-references"><h3><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 
-</dd><dt id="bib-TTML10">[TTML10]</dt><dd>G. Adams. <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/"><cite>Timed Text Markup Language (TTML) 1.0</cite></a> W3C Recommendation. URL: <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
+</dd><dt id="bib-TTML10">[TTML10]</dt><dd>G. Adams. <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/"><cite>Timed Text Markup Language (TTML) 1.0</cite></a>, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
 </dd><dt id="bib-UNICODE">[UNICODE]</dt><dd>The Unicode Consortium. <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><cite>The Unicode Standard.</cite></a> 2003. Defined by: The Unicode Standard, Version 4.0 (Boston, MA, Addison-Wesley, ISBN 0-321-18578-1), as updated from time to time by the publication of new versions URL: <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</a> 
 </dd><dt id="bib-XML10">[XML10]</dt><dd>C. M. Sperberg-McQueen; et al. <a href="http://www.w3.org/TR/2008/REC-xml-20081126/"><cite>Extensible Markup Language (XML) 1.0 (Fifth Edition).</cite></a> 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</a> 
 </dd></dl></section><section id="informative-references"><h3><span class="secno">D.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-CEA608">[CEA608]</dt><dd>CEA-608, <a href="http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/Line-21-Data-Service.aspx"><cite>Line-21 Data Services</cite></a>, ANSI/CEA Standard. URL: <a href="http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/Line-21-Data-Service.aspx">http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/Line-21-Data-Service.aspx</a>
 </dd><dt id="bib-CEA708">[CEA708]</dt><dd>CEA-708, <a href="http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/CEA-708-D.aspx"><cite>Digital Television (DTV) Closed Captioning</cite></a>, ANSI/CEA Standard. URL: <a href="http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/CEA-708-D.aspx">http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/CEA-708-D.aspx</a>
-</dd><dt id="bib-TTML10SE">[TTML10SE]</dt><dd>G. Adams. <a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html"><cite>Timed Text Markup Language (TTML) 1.0 (Second Edition)</cite></a> W3C Editor's Draft. URL: <a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html</a>
+</dd><dt id="bib-TTML10SE">[TTML10SE]</dt><dd>G. Adams. <a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html"><cite>Timed Text Markup Language (TTML) 1.0 (Second Edition)</cite></a>, W3C Editor's Draft. URL: <a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html</a>
 </dd></dl></section></section></body></html>
--- a/ttml10-sdp-us/Overview.src.html	Wed Dec 05 20:12:26 2012 -0700
+++ b/ttml10-sdp-us/Overview.src.html	Thu Dec 06 01:41:57 2012 -0700
@@ -78,8 +78,8 @@
     localBiblio: {
         "CEA608" : "CEA-608, <a href=\"http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/Line-21-Data-Service.aspx\"><cite>Line-21 Data Services</cite></a>, ANSI/CEA Standard. URL: <a href=\"http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/Line-21-Data-Service.aspx\">http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/Line-21-Data-Service.aspx</a>",
         "CEA708" : "CEA-708, <a href=\"http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/CEA-708-D.aspx\"><cite>Digital Television (DTV) Closed Captioning</cite></a>, ANSI/CEA Standard. URL: <a href=\"http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/CEA-708-D.aspx\">http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/CEA-708-D.aspx</a>",
-        "TTML10" :  "G. Adams. <a href=\"http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/\"><cite>Timed Text Markup Language (TTML) 1.0</cite></a> W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/\">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>",
-        "TTML10SE" :  "G. Adams. <a href=\"http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html\"><cite>Timed Text Markup Language (TTML) 1.0 (Second Edition)</cite></a> W3C Editor's Draft. URL: <a href=\"http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html\">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html</a>"
+        "TTML10" :  "G. Adams. <a href=\"http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/\"><cite>Timed Text Markup Language (TTML) 1.0</cite></a>, W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/\">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>",
+        "TTML10SE" :  "G. Adams. <a href=\"http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html\"><cite>Timed Text Markup Language (TTML) 1.0 (Second Edition)</cite></a>, W3C Editor's Draft. URL: <a href=\"http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html\">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html</a>"
     }
 };
 function term(doc, content) {
@@ -423,18 +423,19 @@
 <section class='Structural_Constraints'>
 <h3>Structural Constraints</h3>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
-<div data-transform='constraint'>A document MUST contain both a head and body element.</div>
-<div data-transform='constraint'>A document MUST contain both a styling and a layout element.</div>
-<div data-transform='constraint'>A document MUST NOT use a div element inside a div element.</div>
-<div data-transform='constraint'>A document MUST contain only a single level of span element within a p element.</div>
+<div data-transform='constraint'>A document MUST contain both a <code>head</code> and <code>body</code> element.</div>
+<div data-transform='constraint'>A document MUST contain both a <code>styling</code> and a <code>layout</code> element.</div>
+<div data-transform='constraint'>A document MUST NOT use a <code>div</code> element inside a <code>div</code> element.</div>
+<div data-transform='constraint'>A document MUST NOT use more than one level of <code>span</code> element within a <code>p</code> element.</div>
 <div data-transform='example'>Single level of spans.</div>
-<pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">
+<pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;">
 <span style="color: blue;">&lt;</span><span style="color: #a31515;">span</span><span style="color: blue;"> </span><span style="color: red;">style</span><span style="color: blue;">=</span>"<span style="color: blue;">s1</span>"<span style="color: blue;">&gt;</span>A<span style="color: blue;">&lt;/</span><span style="color: #a31515;">span</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">&lt;</span><span style="color: #a31515;">span</span><span style="color: blue;"> </span><span style="color: red;">style</span><span style="color: blue;">=</span>"<span style="color: blue;">s3</span>"<span style="color: blue;">&gt;</span>B<span style="color: blue;">&lt;/</span><span style="color: #a31515;">span</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">&lt;</span><span style="color: #a31515;">span</span><span style="color: blue;"> </span><span style="color: red;">style</span><span style="color: blue;">=</span>"<span style="color: blue;">s1</span>"<span style="color: blue;">&gt;</span>C<span style="color: blue;">&lt;/</span><span style="color: #a31515;">span</span><span style="color: blue;">&gt;</span>
 </pre>
-<div data-transform='constraint'>A document MUST reference all styles using a style attribute to a style element.</div>
-<div data-transform='constraint'>A document MUST have all elements are in order of time. That is, in a par context, a timed element MUST NOT lexically precede another timed element with an earlier start time.</div>
+<div data-transform='constraint'>A document MUST reference all styles using a <code>style</code> attribute making reference to a <code>style</code> element.</div>
+<p class=issue>The above requirement needs to be rewritten for clarity, changing the sense to be a proscription.</p>
+<div data-transform='constraint'>A document MUST have all elements are in order of time. That is, in a parallel timing context, a timed element MUST NOT lexically precede another timed element with an earlier start time.</div>
 </section>
 <section id='Constrained_Features'>
 <h2>Constrained Features</h2>
@@ -565,8 +566,9 @@
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <div data-transform='constraint'>Presentation processors MUST support the capability to present documents referencing this profile using the following URI: <dfn>http://www.w3.org/TR/profile/simple-delivery</dfn>.</div>
-<div class='note'><p>See also <a href="#conformance">Conformance</a>. [[!TTML10]] allows zero or more profiles (ttp:profile in the head element) to be specified and used simultaneously. A presentation processor may reject documents it does not understand.</p></div>
-<div class='note'><p>When the <code>use</code> attribute is used on the <code>ttp:profile</code> element could indicate the geographical region for which the profile is used. For example, specific styling capabilities could be used in a particular geographical region. See also <a href="#other_constraints">Other Constraints</a>.</p></div>
+<div class='note'><p>See also <a href="#conformance">Conformance</a>. [[!TTML10]] allows zero or more profiles (<code>ttp:profile</code> in the <code>head</code> element) to be specified and used simultaneously. A presentation processor may reject documents it does not understand.</p></div>
+<p class=issue>The phrase <em>does not understand</em> above is not well defined.</p>
+<div class='note'><p>When the <code>use</code> attribute is used on the <code>ttp:profile</code> element, it may indicate the geographical region for which the profile is used. For example, specific styling capabilities could be used in a particular geographical region. See also <a href="#other_constraints">Other Constraints</a>.</p></div>
 </section>
 </section>
 <section id='Use_of_Constrained_TTML_Feature_content_structure'>
@@ -627,23 +629,40 @@
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
-<div data-transform='constraint'>The backgroundColor MUST be expressed in #rrggbbaa format exclusively using the <dfn>&lt;hexdigit&gt;</dfn> style value expression.</div>
-<div data-transform='constraint'>The backgroundColor MUST support the colors outlined in <a href="#color-values">Color Values</a>.</div>
+<div data-transform='constraint'>The <code>tts:backgroundColor</code> attribute MUST be expressed in <code>#rrggbbaa</code> format exclusively using the <dfn>&lt;hexdigit&gt;</dfn> style value expression.</div>
+<div data-transform='constraint'>The <code>tts:backgroundColor</code> attribute MUST support the colors outlined in <a href="#color-values">Color Values</a>.</div>
+<p class=issue>The phrase <em>attribute MUST support</em> above is probably incorrect.</p>
 <div class='note'><p>These colors are identical to those identified in the CEA708-D, Section 8.8 [RBG resolution of 4 bits for each primary (03)].</p></div>
-<div data-transform='constraint'>The alpha component of backgroundColor MUST support the opacity values outlined in <a href="#color-values">Color Values</a>.</div>
-<div data-transform='constraint'>The alpha component of backgroundColor for a region MUST be zero (0).</div>
-<div data-transform='constraint'>The presentation processor MUST allow the user to specify a backgroundColor for p and span elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</div>
-<div data-transform='constraint'>The presentation processor MUST allow the user to specify a backgroundColor for p and span elements to allow for semi-transparent and transparent opacities.</div>
+<div data-transform='constraint'>The alpha component of a <code>tts:backgroundColor</code> attribute MUST support the opacity values outlined in <a href="#color-values">Color Values</a>.</div>
+<p class=issue>The phrase <em>attribute MUST support</em> above is probably incorrect.</p>
+<div data-transform='constraint'>The alpha component of a <code>tts:backgroundColor</code> attribute for a <code>region</code> MUST be zero (0).</div>
+<div data-transform='constraint'>The presentation processor MUST allow the user to specify a <code>tts:backgroundColor</code> for <code>p</code> and <code>span</code> elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</div>
+<p class=issue>The phrase <em>the user</em> above is probably incorrect.</p>
+<div data-transform='constraint'>The presentation processor MUST allow the user to specify a <code>tts:backgroundColor</code> for <code>p</code> and <code>span</code> elements to allow for semi-transparent and transparent opacities.</div>
+<p class=issue>The phrase <em>the user</em> above is probably incorrect.</p>
 <div data-transform='example'>Multiple Background Styles. The <code>tts:backgroundColor</code> is specified distinctly for a region, a paragraph selected into
 that region, and a span of text in that paragraph.</div>
-<pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">
-&lt;region id="r1" tts:backgroundColor="#00000000"/&gt;
+
+<pre class="example" style="font-family: monospace; font-size: 13; color: black; background: white;"><span 
+        style="color:blue;">&lt;</span><span style="color:maroon;">region</span>&nbsp;<span 
+        style="color:red;">id</span><span style="color:blue;">=&quot;r1&quot;</span>&nbsp;<span 
+        style="color:red;">tts</span><span style="color:blue;">:</span><span 
+        style="color:red;">backgroundColor</span><span style="color:blue;">=&quot;#00000000&quot;/&gt;</span>
 ...
-&lt;p region="r1" tts:backgroundColor="#1049edff"&gt;
-  Twinkle, twinkle, little bat!&lt;br&gt;
-  How &lt;span tts:backgroundColor="#ed1078ff"&gt;I wonder&lt;/span&gt; where you're at!
-&lt;/p&gt;
-</pre>
+<span style="color:blue;">&lt;</span><span style="color:maroon;">p</span>&nbsp;<span 
+        style="color:red;">region</span><span style="color:blue;">=&quot;r1&quot;</span>&nbsp;<span 
+        style="color:red;">tts</span><span style="color:blue;">:</span><span 
+        style="color:red;">backgroundColor</span><span style="color:blue;">=&quot;#1049edff&quot;&gt;</span>
+&nbsp;&nbsp;Twinkle,&nbsp;twinkle,&nbsp;little&nbsp;bat!<span style="color:blue;">&lt;</span><span 
+        style="color:maroon;">br</span><span style="color:blue;">&gt;</span>
+&nbsp;&nbsp;How&nbsp;<span style="color:blue;">&lt;</span><span style="color:maroon;">span</span>&nbsp;<span 
+        style="color:red;">tts</span><span style="color:blue;">:</span><span 
+        style="color:red;">backgroundColor</span><span style="color:blue;">=&quot;#ed1078ff&quot;&gt;</span>I&nbsp;wonder<span 
+        style="color:blue;">&lt;/</span><span style="color:maroon;">span</span><span 
+        style="color:blue;">&gt;</span>&nbsp;where&nbsp;you&#39;re&nbsp;at!
+<span style="color:blue;">&lt;/</span><span style="color:maroon;">p</span><span 
+        style="color:blue;">&gt;</span></pre>
+
 </section>
 </section>
 <section id='Constrained_TTML_Feature_color'>
@@ -671,12 +690,16 @@
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
-<div data-transform='constraint'>The color MUST be expressed in #rrggbbaa format exclusively using the <dfn>&lt;hexdigit&gt;</dfn> style value expression.</div>
-<div data-transform='constraint'>The color MUST support the colors outlined in <a href="#color-values">Color Values</a>.</div>
+<div data-transform='constraint'>The <code>tts:color</code> attribute MUST be expressed in <code>#rrggbbaa</code> format exclusively using the <dfn>&lt;hexdigit&gt;</dfn> style value expression.</div>
+<div data-transform='constraint'>The <code>tts:color</code> attribute MUST support the colors outlined in <a href="#color-values">Color Values</a>.</div>
+<p class=issue>The phrase <em>attribute MUST support</em> above is probably incorrect.</p>
 <div class='note'><p>These colors are identical to those identified in the CEA708-D, Section 8.8 [RBG resolution of 4 bits for each primary (03)].</p></div>
-<div data-transform='constraint'>The alpha component of color MUST support the opacity values outlined in <a href="#color-values">Color Values</a>.</div>
-<div data-transform='constraint'>The presentation processor MUST allow the user to specify a color for p and span elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</div>
-<div data-transform='constraint'>The presentation processor MUST allow the user to specify a color for p and span elements to allow for semi-transparent and transparent opacities.</div>
+<div data-transform='constraint'>The alpha component of a <code>tts:color</code> attribute MUST support the opacity values outlined in <a href="#color-values">Color Values</a>.</div>
+<p class=issue>The phrase <em>attribute MUST support</em> above is probably incorrect.</p>
+<div data-transform='constraint'>The presentation processor MUST allow the user to specify a <code>tts:color</code> attribute for <code>p</code> and <code>span</code> elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</div>
+<p class=issue>The phrase <em>the user</em> above is probably incorrect.</p>
+<div data-transform='constraint'>The presentation processor MUST allow the user to specify a <code>tts:color</code> attribute for <code>p</code> and <code>span</code> elements to allow for semi-transparent and transparent opacities.</div>
+<p class=issue>The phrase <em>the user</em> above is probably incorrect.</p>
 </section>
 </section>
 <section id='Constrained_TTML_Feature_display_region'>
@@ -723,7 +746,7 @@
 <td>#extent-region</td>
 <td>Required with constraints</td>
 <td>region<br />
-root</td>
+tt</td>
 <td>&#160;</td>
 <td>&#160;</td>
 </tr>
@@ -731,7 +754,7 @@
 </section>
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
-<div data-transform='constraint'>The origin and extent of a region MUST NOT be specified such that the region extends outside of the root container.</div>
+<div data-transform='constraint'>The <code>tts:origin</code> and <code>tts:extent</code> attributes of a <code>region</code> element MUST NOT be specified such that the region extends outside of the root container.</div>
 <div data-transform='constraint'>A presentation processor MUST fix the root container origin so that it corresponds with the top, left corner of the related
 media object [[TTML10SE]], Section 2.2.</div>
 <div data-transform='constraint'>A presentation processor MUST fix the root container extent so that it corresponds with the extent of the related
@@ -753,7 +776,7 @@
 <p>A Paint-on caption typically appears on the screen one character at a time and is displayed like a Pop-up caption.</p>
 <p>These caption styles are further elucidated by examples below.</p>
 <div data-transform='example'>Pop-up style</div>
-<pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">
+<pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;">
  
     <span style="color: blue;">&lt;</span><span style="color: #a31515;">tt</span><span style="color: blue;"> </span><span style="color: red;">xml:lang</span><span style="color: blue;">=</span>"<span style="color: blue;">en-us</span>"<span style="color: blue;"> </span><span style="color: red;">xmlns</span><span style="color: blue;">=</span>"<span style="color: blue;">http://www.w3.org/ns/ttml</span>"<span style="color: blue;"> </span>
 <span style="color: blue;">    </span><span style="color: red;">xmlns:s</span><span style="color: blue;">=</span>'<span style="color: blue;">http://www.w3.org/ns/ttml#styling</span>'<span style="color: blue;"> </span>
@@ -762,7 +785,8 @@
 <span style="color: blue;">    &lt;</span><span style="color: #a31515;">p:profile</span><span style="color: blue;"> </span><span style="color: red;">use</span><span style="color: blue;">=</span>"<span style="color: blue;">http://www.w3.org/ns/ttml/profile/online-delivery</span>"<span style="color: blue;">/&gt;</span>
 <span style="color: blue;">    &lt;</span><span style="color: #a31515;">styling</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">      &lt;!--</span><span style="color: green;"> A typical transparent region with centered text that has an outline </span><span style="color: blue;">--&gt;</span>
-<span style="color: blue;">      &lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">bottomMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">#000000ff 5%</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">#00000000</span>"<span style="color: blue;"> </span><span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style=
+<span style="color: blue;">      &lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">bottomMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">#000000ff 5%</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">#00000000</span>"<span style="color: blue;"> </span>
+                 <span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style=
 "color: blue;">=</span>'<span style="color: blue;">20% 58%</span>'<span style="color: blue;"> </span><span style="color: red;">s:extent</span><span style="color: blue;">=</span>'<span style="color: blue;">60% 18%</span>'<span style="color: blue;">/&gt;</span>
 <span style="color: blue;">    &lt;/</span><span style="color: #a31515;">styling</span><span style="color: blue;">&gt;</span>
 <span style="color: blue;">    &lt;</span><span style="color: #a31515;">layout</span><span style="color: blue;">&gt;</span>
@@ -782,16 +806,18 @@
 <section>
 <div data-transform='example'>Positioned style. An off-screen narrator is present and no graphics are used. Content placed in a single region in the bottom one-third of that region.</div>
 <!-- div data-include=example2.xml'></div -->
-<pre class='example' style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">
-<span style="color: blue;">&lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">bottomMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">black 1px</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">transparent</span>"<span style="color: blue;"> </span><span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style="color: blue;">=</span>'<span style=
+<pre class='example' style="font-family: monospace; font-size: 10pt; color: black; background: white;">
+<span style="color: blue;">&lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">bottomMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">black 1px</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">transparent</span>"<span style="color: blue;"> </span>
+       <span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style="color: blue;">=</span>'<span style=
 "color: blue;">20% 58%</span>'<span style="color: blue;"> </span><span style="color: red;">s:extent</span><span style="color: blue;">=</span>'<span style="color: blue;">60% 18%</span>'<span style="color: blue;">/&gt;</span>
-<span style="color: blue;">&lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">topMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">black 1px</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">transparent</span>"<span style="color: blue;"> </span><span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style="color: blue;">=</span>'<span style=
+<span style="color: blue;">&lt;</span><span style="color: #a31515;">style</span><span style="color: blue;"> </span><span style="color: red;">xml:id</span><span style="color: blue;">=</span>"<span style="color: blue;">topMidStyle</span>"<span style="color: blue;"> </span><span style="color: red;">s:textAlign</span><span style="color: blue;">=</span>"<span style="color: blue;">center</span>"<span style="color: blue;"> </span><span style="color: red;">s:textOutline</span><span style="color: blue;">=</span>"<span style="color: blue;">black 1px</span>"<span style="color: blue;"> </span><span style="color: red;">s:backgroundColor</span><span style="color: blue;">=</span>"<span style="color: blue;">transparent</span>"<span style="color: blue;"> </span>
+       <span style="color: red;">s:color</span><span style="color: blue;">=</span>"<span style="color: blue;">#ffffffff</span>"<span style="color: blue;"> </span><span style="color: red;">s:origin</span><span style="color: blue;">=</span>'<span style=
 "color: blue;">20% 10%</span>'<span style="color: blue;"> </span><span style="color: red;">s:extent</span><span style="color: blue;">=</span>'<span style="color: blue;">60% 18%</span>'<span style="color: blue;">/&gt;</span>
 </pre></section>
 <section>
 <div data-transform='example'>Moving regions. Content is positioned based on location of speaker, visible in the bottom two lines individually positioned in region(s) so as to avoid background content..</div>
 <!-- div data-include=example3.xml'></div -->
-<pre class='example' style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">
+<pre class='example' style="font-family: monospace; font-size: 10pt; color: black; background: white;">
 <span style="color: blue;">&lt;?</span><span style="color: #a31515;">xml</span><span style="color: blue;"> </span><span style="color: red;">version</span><span style="color: blue;">=</span>"<span style="color: blue;">1.0</span>"<span style="color: blue;"> </span><span style="color: red;">encoding</span><span style="color: blue;">=</span>"<span style="color: blue;">utf-8</span>"<span style="color: blue;">?&gt;</span>
 <span style="color: blue;">&lt;</span><span style="color: #a31515;">tt</span><span style="color: blue;"> </span><span style="color: red;">xml:lang</span><span style="color: blue;">=</span>"<span style="color: blue;">en-us</span>"<span style="color: blue;"> </span><span style="color: red;">xmlns</span><span style="color: blue;">=</span>"<span style="color: blue;">http://www.w3.org/ns/ttml</span>"<span style="color: blue;"> </span><span style="color: red;">xmlns:s</span><span style="color: blue;">=</span>'<span style="color: blue;">http://www.w3.org/ns/ttml#styling</span>'<span style="color: blue;">&gt;</span>
 <span style="color: blue;">  &lt;</span><span style="color: #a31515;">head</span><span style="color: blue;">&gt;</span>
@@ -866,18 +892,18 @@
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
-<div data-transform='constraint'>The document MUST use the tts:fontFamily attribute using only the following values:</div>
+<div data-transform='constraint'>A document MUST NOT specify a <code>tts:fontFamily</code> attribute whose value is not one of the following:</div>
 <ul>
-<li>default</li>
-<li>monospaceSerif</li>
-<li>proportionalSerif</li>
-<li>monospaceSansSerif</li>
-<li>proportionalSansSerif</li>
-<li>casual</li>
-<li>cursive</li>
-<li>smallCaps</li>
+<li><code>default</code></li>
+<li><code>monospaceSerif</code></li>
+<li><code>proportionalSerif</code></li>
+<li><code>monospaceSansSerif</code></li>
+<li><code>proportionalSansSerif</code></li>
+<li><code>casual</code></li>
+<li><code>cursive</code></li>
+<li><code>smallCaps</code></li>
 </ul>
-<div class='note'><p>Values of tts:fontFamily that do not not correspond to generic font family names in [[!TTML10]], such as <code>casual</code>, <code>cursive</code> and <code>smallCaps</code>, may be used. These are to be interpreted as local font names, which, if not available, the <code>default</code> font family is to be used.</p></div>
+<div class='note'><p>Values of <code>tts:fontFamily</code> that do not not correspond to generic font family names in [[!TTML10]], such as <code>casual</code>, <code>cursive</code> and <code>smallCaps</code>, may be used. These are to be interpreted as local font names, which, if not available, the <code>default</code> font family is to be used.</p></div>
 <div data-transform='constraint'>A presentation processor MUST map the generic font names to fonts as follows:</div>
 <table>
 <tr>
@@ -926,8 +952,14 @@
 <td>Similar to Engravers Gothic</td>
 </tr>
 </table>
-<div data-transform='constraint'>The presentation processor MUST allow the user to specify a generic fontFamily for the document using the values shown in the preceding table.</div>
-<div data-transform='constraint'>The presentation processor MUST allow the user to specify character edge attributes and types for the generic fontFamily names for the values shown in the preceding table.</div>
+<p></p>
+<div data-transform='constraint'>The presentation processor MUST allow the user to specify a generic font family for the document using the values shown in the preceding table.</div>
+<p class=issue>The phrase <em>the user</em> above is probably incorrect.</p>
+<p class=issue>The phrase <em>for the document</em> above is probably incorrect.</p>
+<p class=issue>The above requirement appears to be redundant with R0023 and its preceding prologue.</p>
+<div data-transform='constraint'>The presentation processor MUST allow the user to specify character edge attributes and types for the generic font family names for the values shown in the preceding table.</div>
+<p class=issue>The phrase <em>the user</em> above is probably incorrect.</p>
+<p class=issue>The phrase <em>character edge attributes</em> above needs to point at a definition since this is not a TTML concept.</p>
 <div class='note'><p>Presentation processor and Unicode code point support is defined in <a href="#code-points">Code Point support</a></p></div>
 <div class='note'><p>Text outline can be specified using a style property to apply to characters selected for specific areas for content flowed into a region. Text outline applies a specific character edge to content. For example, when the textOutline style property is used, a type of shadow or thickness can be applied to content.</p></div>
 </section>
@@ -954,14 +986,15 @@
 <td>&#160;</td>
 </tr>
 </table>
+<p class=issue>What does <em>(root)</em> mean in the Scope column of the above table?</p>
 </section>
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
-<div data-transform='constraint'>A document MUST NOT specify <code>tts:fontSize</code> using a value that is not one of 50%, 75%, 100%, 150% or 200%.</div>
-<div class='note'><p>Use of a fontSize of less than 75% (i.e. 50%) may result in unreadable content for a user.</p></div>
-<div class='note'><p>Specifying a fontSize is used for a document could allow the user to select a preferred fontSize.</p></div>
-<div class='note'><p>If a specific fontSize is not supported, then, follow the semantics for a presentation processor defined in [[!TTML10]], Section 8.2.9.</p></div>
+<div data-transform='constraint'>A document MUST NOT specify a <code>tts:fontSize</code> attribute using a value that is not one of 50%, 75%, 100%, 150% or 200%.</div>
+<div class='note'><p>Use of a font size of less than 75% (i.e. 50%) may result in unreadable content for a user.</p></div>
+<div class='note'><p>Specifying a font size is used for a document could allow the user to select a preferred font size.</p></div>
+<div class='note'><p>If a specific font size is not supported, then, follow the semantics for a presentation processor defined in [[!TTML10]], Section 8.2.9.</p></div>
 <div class='note'><p>Constraining the root container extent to the active video area means that the default
 font size of 1c and the default cell grid of 32 x 15 (as specified in TTML 1.0) implies an initial font height of 6.67% of the video height.</p></div>
 </section>
@@ -992,6 +1025,7 @@
 <h4>Constraints</h4>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
 <div data-transform='constraint'>The capability MUST exist for the user to specify the italic style for the font families identified in this profile.</div>
+<p class=issue>The phrase <em>the user</em> above is probably incorrect.</p>
 </section>
 </section>
 <section id='Constrained_TTML_Feature_length_percentage'>
@@ -1020,8 +1054,8 @@
 <h4>Constraints</h4>
 <p>None</p>
 <section>
-<div data-transform='example'>Using 10% for the tts:extent of the root container region (for example, of an 720x640 region), the equivalence to pixel units (px) could be obtained. For example, using this snippet:</div>
-<pre class='example' style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">
+<div data-transform='example'>Using 10% for the <code>tts:extent</code> of the root container region (for example, of an 720x640 region), the equivalence to pixel units (px) could be obtained. For example, using this snippet:</div>
+<pre class='example' style="font-family: monospace; font-size: 10pt; color: black; background: white;">
 <span style="color:blue;">&lt;</span><span style="color:#a31515;">style</span><span style="color:blue;"> </span><span style="color:red;">xml:id</span><span style="color:blue;">=</span>"<span style="color:blue;">topLeftStyle</span>"<span style="color:blue;"> </span><span style="color:red;">s:fontSize</span><span style="color:blue;">=</span>"<span style="color:blue;">150%</span>"<span style="color:blue;"> </span><span style="color:red;">s:textAlign</span><span style="color:blue;">=</span>"<span style="color:blue;">left</span>"<span style="color:blue;"> </span><span style="color:red;">s:backgroundColor</span><span style="color:blue;">=</span>"<span style="color:blue;">#ffffffff</span>"<span style="color:blue;"> </span><span style="color:red;">s:color</span><span style="color:blue;">=</span>"<span style="color:blue;">#ff0000ff</span>"<span style="color:blue;"> </span><span style="color:red;">s:origin</span><span style="color:blue;">=</span>'<span style=
 "color:blue;">10% 10%</span>'<span style="color:blue;"> </span><span style="color:red;">s:extent</span><span style="color:blue;">=</span>'<span style="color:blue;">40% 18%</span>'<span style="color:blue;">/&gt;</span>
 </pre>
@@ -1087,9 +1121,14 @@
 <h4>Constraints</h4>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
 <div data-transform='constraint'>Styles MUST be applied either by reference or through use of inline styling.</div>
-<div data-transform='constraint'>Styles MUST be applied with a single style element using the style attribute.</div>
+<p class=issue>The phrase <em>MUST be applied</em> above is not well defined.</p>
+<p class=issue>The above requirement appears to be redundant with R0005.</p>
+<div data-transform='constraint'>Styles MUST be applied with a single <code>style</code> element using the <code>style</code> attribute.</div>
+<p class=issue>The phrase <em>MUST be applied</em> above is not well defined.</p>
+<p class=issue>The above requirement needs to be elaborated in terms of markup usage.</p>
 <div data-transform='constraint'>Style elements MUST NOT reference other styles.</div>
-<div data-transform='constraint'>Style elements MUST NOT be child elements of region elements.</div>
+<p class=issue>The phrase <em>reference other styles</em> above is not well defined.</p>
+<div data-transform='constraint'>A <code>region</code> element MUST NOT contain a child <code>style</code> element.</div>
 <div class='note'><p>The constraints in this section result in a document that contains style blocks that are complete and self-contained.</p></div>
 </section>
 </section>
@@ -1199,8 +1238,11 @@
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
-<div data-transform='constraint'>The tts:textDecoration-under attribute MUST support the constraints identified in this profile.</div>
+<div data-transform='constraint'>The <code>tts:textDecoration-under</code> attribute MUST support the constraints identified in this profile.</div>
+<p class=issue>The phrase <em>attribute MUST support</em> above is probably incorrect.</p>
+<p class=issue>There is no such thing as a tts:textDecoration-under attribute. In any case, this requirement should actually specify a requirement.</p>
 <div data-transform='constraint'>The capability MUST exist for the user to specify the underline decoration for the font families identified in this profile.</div>
+<p class=issue>The phrase <em>the user</em> above is probably incorrect.</p>
 </section>
 </section>
 <section id='Constrained_TTML_Feature_textOutline_unblurred'>
@@ -1229,9 +1271,16 @@
 <h4>Constraints</h4>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
 <div data-transform='constraint'>Character edge attributes MUST be expressed using textOutline-unblurred based on the settings identified in CEA-708-D, Section 8.5.8.</div>
+<p class=issue>Not well defined.</p>
+<p class=issue>The phrase <em>character edge attributes</em> above needs to point at a definition since this is not a TTML concept.</p>
 <div data-transform='constraint'>A text outline MUST be expressed using textOutline-unblurred of up to 10% thickness.</div>
-<div data-transform='constraint'>The user MUST be able to specify character edge and type attributes using tts:textOutline attribute.</div>
+<p class=issue>Not well defined.</p>
+<div data-transform='constraint'>The user MUST be able to specify character edge and type attributes using <code>tts:textOutline</code> attribute.</div>
+<p class=issue>The phrase <em>the user</em> above is probably incorrect.</p>
+<p class=issue>The phrase <em>character edge attributes</em> above needs to point at a definition since this is not a TTML concept.</p>
 <div data-transform='constraint'>The user SHOULD be able to specify the rendering of character edge types of: none, raised, depressed, uniform or drop shadowed edges.</div>
+<p class=issue>The phrase <em>the user</em> above is probably incorrect.</p>
+<p class=issue>The phrase <em>character edge attributes</em> above needs to point at a definition since this is not a TTML concept.</p>
 <div class='note'><p>This requirement targets the capabilities of a presentation processor.</p></div>
 </section>
 </section>
@@ -1326,11 +1375,11 @@
 <div data-transform='constraint'>If the aspect ratio of the root container is 4:3 (16:9), then, respectively, more than 152 (168) characters MUST NOT be
 present in all displayed text lines.</div>
 <div class='note'><p>These requirements accommodate content originated in Europe but displayed in the US, as well as content displayed using 16:9 format.</p></div>
-<div data-transform='constraint'>At most one p element MUST be selected into a region at a time.</div>
+<div data-transform='constraint'>More than one <code>p</code> element MUST NOT be selected into a region in any synchronic intermediate document.</div>
 <div class='note'><p>The style properites of region and the content selected for the region impact how selected text flows into a region (i.e. selected text may flow outside of the region such as on a mobile device).</p></div>
-<div class='note'><p>Constraining one p element to a region logically places content from two different speakers to different region(s).</p></div>
-<div class='note'><p>When a document author wants to construct a single phrase from a speaker with more than one line in a region, the br within a p element can be used. This construction adheres to the constraints in this section. For example for one speaker with more than one line:</p></div>
-<pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">
+<div class='note'><p>Constraining one <code>p</code> element to a region logically places content from two different speakers to different region(s).</p></div>
+<div class='note'><p>When a document author wants to construct a single phrase from a speaker with more than one line in a region, the <code>br</code> element within a <code>p</code> element can be used. This construction adheres to the constraints in this section. For example for one speaker with more than one line:</p></div>
+<pre class="example" style="font-family: monospace; font-size: 10pt; color: black; background: white;">
 <span style="color:blue;">&lt;</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span> I always get the fuzzy end<span style="color:blue;">&lt;</span><span style="color:#a31515;">br</span><span style="color:blue;">/&gt;</span>of the lollipop<span style="color:blue;">&lt;/</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span>
 </pre></section>
 </section>
@@ -1363,28 +1412,32 @@
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
-<div data-transform='constraint'>Timing MUST be expressed in the hh:mm:ss.ms or hh:mm:ss:ff format used in the timeExpression.</div>
+<div data-transform='constraint'>Timing MUST be expressed in either the <code>hh:mm:ss.ms</code> or the <code>hh:mm:ss:ff</code> format used in a time expression.</div>
 <div data-transform='constraint'>Timing MUST be expressed in the same format throughout the document.</div>
-<div data-transform='constraint'>Presentation processors MUST support durations (dur) on the p and span elements, and MAY (but need not) support on other element types;
-as such, a document SHOULD NOT use a duration on an element type other than p or span.</div>
-<div data-transform='constraint'>For timing in hh:mm:ss.ms, the following format MUST be used:</div>
+<p class=issue>The phrase <em>in the same format</em> above needs elaboration.</p>
+<div data-transform='constraint'>Presentation processors MUST support durations (<code>dur</code>) on the <code>p</code> and <code>span</code> elements, and MAY (but need not) support on other element types;
+as such, a document SHOULD NOT use a duration on an element type other than <code>p</code> or <code>span</code>.</div>
+<div data-transform='constraint'>For time expressions that use the <code>hh:mm:ss.ms</code> format, the following constraints apply:</div>
 <ul>
 <li>Exactly 2 digits MUST be used in each of the hours, minutes, and second components (include leading zeros).</li>
 <li>Exactly 3 decimal places MUST be used for the milliseconds component (include zeros).</li>
 </ul>
-<pre class='example' style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">
+<div class='note'><p>The phrase <em>milliseconds component</em> above refers to a particular use of the <code>fraction</code> of a <code>clock-time</code> time expression as defined by [[!TTML10]] Section 10.3.1.</p></div>
+<pre class='example' style="font-family: monospace; font-size: 10pt; color: black; background: white;">
 <span style="color:blue;">&lt;</span><span style="color:#a31515;">p</span><span style="color:blue;"> </span><span style="color:red;">begin</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:01.000</span>'<span style="color:blue;"> </span><span style="color:red;">end</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:11.123</span>'<span style="color:blue;"> </span><span style="color:red;">region</span><span style="color:blue;">=</span>"<span style="color:blue;">r1</span>"<span style="color:blue;"> &gt;</span>Test<span style="color:blue;">&lt;/</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span>
 </pre>
-<div data-transform='constraint'>For timing in hh:mm:ss.ms, the following format MUST be used:</div>
+<div data-transform='constraint'>For time expressions that use the <code>hh:mm:ss:ff</code> format, the following constraints apply:</div>
 <ul>
 <li>Exactly 2 digits MUST be used in each of the hours, minutes, second, and frame components (include leading zeros).</li>
-<li>A ttp:frameRate attribute MUST be present on the root element.</li>
-<li>A ttp:frameRateMultiplier attribute MAY be present on the root element.</li>
+<li>A <code>ttp:frameRate</code> attribute MUST be present on the <code>tt</code> element.</li>
+<li>A <code>ttp:frameRateMultiplier</code> attribute MAY be present on the <code>tt</code> element.</li>
 </ul>
 <p></p>
-<pre class='example' style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">
+<pre class='example' style="font-family: monospace; font-size: 10pt; color: black; background: white;">
 <span style="color:blue;">&lt;</span><span style="color:#a31515;">p</span><span style="color:blue;"> </span><span style="color:red;">begin</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:01:00</span>'<span style="color:blue;"> </span><span style="color:red;">end</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:11:22</span>'<span style="color:blue;"> </span><span style="color:red;">region</span><span style="color:blue;">=</span>"<span style="color:blue;">r1</span>"<span style="color:blue;"> &gt;</span>Test<span style="color:blue;">&lt;/</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span>
-</pre></section>
+</pre>
+<p class=issue>The above example should also show a <code>tt</code> element with a <code>ttp:frameRate</code> attribute.</p>
+</section>
 </section>
 <section id='Constrained_TTML_Feature_time_offset'>
 <h2>Use of Constrained TTML Feature <span data-transform='term'>time-offset</span></h2>
@@ -1411,11 +1464,11 @@
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <p>None</p>
-<div class='note'><p>Since the ttp:timebase attribute is outside of this profile, the implicit timebase used here is media as specified in [[!TTML10]].</p></div>
+<div class='note'><p>Since the <code>ttp:timeBase</code> attribute is not supported by this profile, the implicit timebase is <code>media</code> as specified in [[!TTML10]].</p></div>
 </section>
 </section>
 <section id='frameRate'>
-<h2>Use of Constrained TTML Feature <span data-transform='term'>frameRate and frameRateMultiplier</span></h2>
+<h2>Use of Constrained TTML Feature <span data-transform='term'>ttp:frameRate and ttp:frameRateMultiplier</span></h2>
 <p></p>
 <section class='Usage_Scenario'>
 <h4>Usage Scenario</h4>
@@ -1436,7 +1489,7 @@
 <td>&#160;</td>
 </tr>
 </table>
-<div class='note'><p>Use of the #frameRateMultiplier feature is optional in a document (see <a href="#Features_in_TTML_1.0_Used">Features in TTML1.0 Used in This Profile</a>).</p></div>
+<div class='note'><p>Use of the <code>#frameRateMultiplier</code> feature is optional in a document (see <a href="#Features_in_TTML_1.0_Used">Features in TTML1.0 Used in This Profile</a>).</p></div>
 </section>
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
@@ -1468,11 +1521,13 @@
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
-<div data-transform='constraint'>The set element MUST only animate the region or span element.</div>
-<div data-transform='constraint'>The use of set elements applied to a region element MUST only animate the tts:display, tts:origin or tts:extent attribute.</div>
-<div data-transform='constraint'>The use of set elements applied to a span element MUST only animate the tts:color attribute.</div>
-<div data-transform='constraint'>No more than 6 set elements MUST be used within a given element.</div>
-<div class='note'><p>Animation is constrained to the scenarios where the region needs to be moved &#8211; i.e. when the &#8220;snap&#8221; display effect is required.</p></div>
+<div data-transform='constraint'>The <code>set</code> element MUST only animate the <code>region</code> or <code>span</code> element.</div>
+<p class=issue>Does the above requirement mean that <code>set</code> must not appear as a child of any element other than region or span elements?</p>
+<div data-transform='constraint'>The use of <code>set</code> elements applied to a <code>region</code> element MUST only animate the <code>tts:display</code>, <code>tts:origin</code> or <code>tts:extent</code> attribute.</div>
+<div data-transform='constraint'>The use of <code>set</code> elements applied to a <code>span</code> element MUST only animate the <code>tts:color</code> attribute.</div>
+<div data-transform='constraint'>More than six (6) <code>set</code> child elements MUST NOT be specified within a given element.</div>
+<div class='note'><p>Animation is constrained to the scenarios where the region needs to be moved, e.g., when a <em>snap</em> display effect is desired.</p></div>
+<p class=issue>The phrase <em>snap display effect</em> is not defined.</p>
 <div class='note'><p>Animation is constrained to the scenarios to change the foreground color of content when flashing text is required.</p></div>
 </section>
 </section>
@@ -1521,7 +1576,7 @@
 </section>
 <section id='Features_in_TTML_1.0_Used'>
 <h2>Features in TTML 1.0 Used in This Profile</h2>
-<pre style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;">
+<pre style="font-family: monospace; font-size: 10pt; color: black; background: white;">
 <span style="color: blue;">&lt;?</span><span style="color: #a31515;">xml</span><span style="color: blue;"> </span><span style="color: red;">version</span><span style="color: blue;">=</span>"<span style="color: blue;">1.0</span>"<span style="color: blue;"> </span><span style="color: red;">encoding</span><span style="color: blue;">=</span>"<span style="color: blue;">utf-8</span>"<span style="color: blue;">?&gt;</span>
 <span style="color: blue;">&lt;?</span><span style="color: #a31515;">xml</span><span style="color: blue;"> </span><span style="color: red;">version</span><span style="color: blue;">=</span>"<span style="color: blue;">1.0</span>"<span style="color: blue;"> </span><span style="color: red;">encoding</span><span style="color: blue;">=</span>"<span style="color: blue;">utf-8</span>"<span style="color: blue;">?&gt;</span>
 <span style="color: blue;">&lt;</span><span style="color: #a31515;">profile</span><span style="color: blue;"> </span><span style="color: red;">xmlns</span><span style="color: blue;">=</span>"<span style="color: blue;">http://www.w3.org/ns/ttml#parameter</span>"<span style="color: blue;">&gt;</span>
@@ -1588,7 +1643,7 @@
 <section class='appendix' id='future_needs'>
 <h2>Future Needs for TTML next for Simple Delivery</h2>
 <section class='appendix' id='Section2'>
-<h3>Values for fontFamily support</h3>
+<h3>Values for font family support</h3>
 <p>The casual, cursive and smallCaps generic font families are expected to be considered for inclusion in a future version of TTML.</p>
 </section>
 <section class='appendix' id='Section3'>
@@ -1663,20 +1718,20 @@
 </table>
 <p>TTML Mandatory Features</p>
 <ul>
-<li>core</li>
-<li>content</li>
-<li>presentation</li>
-<li>structure</li>
-<li>time-offset</li>
-<li>timing</li>
+<li><code>#core</code></li>
+<li><code>#content</code></li>
+<li><code>#presentation</code></li>
+<li><code>#structure</code></li>
+<li><code>#time-offset</code></li>
+<li><code>#timing</code></li>
 </ul>
 <p>TTML Features Required That Support Other Requirements</p>
 <ul>
-<li>styling</li>
-<li>styling-referential</li>
-<li>styling-inline</li>
-<li>styling-inheritance-content</li>
-<li>styling-inheritance-region</li>
+<li><code>#styling</code></li>
+<li><code>#styling-referential</code></li>
+<li><code>#styling-inline</code></li>
+<li><code>#styling-inheritance-content</code></li>
+<li><code>#styling-inheritance-region</code></li>
 </ul>
 <p></p>
 </section>
@@ -2701,7 +2756,7 @@
 Presentation processors may also provide Glyph coverage for additional Unicode code points
 <section class='color_values'>
 <h2>Color values</h2>
-<p>For color values of the form #rrggbbaa, presentation processors MUST support combinations where the rr, gg, bb components may be either 00 or ff; and the aa component may be 00, 54, A8 or FF. e.g: #00ffff54. Additionally presentation processors SHOULD support values for rr, gg, and bb of 54 or A8, and MAY support all possible values between 00 to ff.</p>
+<p>For color values of the form <code>#rrggbbaa</code>, presentation processors MUST support combinations where the red, green, and blue components may be either <code>00</code> or <code>FF</code>; and the alpha component may be <code>00</code>, <code>54</code>, <code>A8</code> or <code>FF</code>, e.g, #00FFFF54. Additionally presentation processors SHOULD support values for red, green, and blue of <code>54</code> or <code>A8</code>, and MAY support all possible values between <code>00</code> and <code>FF</code>.</p>
 <table>
 <tr>
 <th>Color</th>
ttml

Hosted by W3C Systems Team, please report bugs to sysreq@w3.org