--- a/ttml1/spec/ttml1-changes.html	Fri Aug 23 12:28:30 2013 -0600
+++ b/ttml1/spec/ttml1-changes.html	Fri Aug 23 18:22:19 2013 -0600
@@ -45,12 +45,14 @@
   first version of TTML. [The next version of TTML is expected to be called TTML2.]
 * In 1.2, add note explaining that use of <p/> element may be presentational or semantic
   according to intentions of author.
+* In 2.2, remove definitions of "Content Profile" and "Processor Profile" due to
+  inadequate definition and lack of reference. [Expected to be redefined in TTML2.]
 * In 2.2, change the definition of "Related Media Object Region" to not imply that a
   TTML presentation processor is responsible for presenting the related media object.
 * In 3.2.1, change "TTML Content profile" to "TTML profile", since TTML profiles are not
-  presently defined as content profiles but as processor profiles.
+  presently defined as content profiles or as processor profiles as such.
 * In 6.1.1, change "TTML Content profile" to "TTML profile", since TTML profiles are not
-  presently defined as content profiles but as processor profiles.
+  presently defined as content profiles or as processor profiles as such.
 * In 8.1.2, remove erroneous sentence stating that style element takes metadata children (this
   support was removed in the sytnax definition and schema before REC was published, but this
   sentence was inadvertently left in the text).
@@ -62,6 +64,10 @@
 * In 8.2.9, improve compatibility with CSS and XSL-FO implementations by interpreting
   'normal' line height as 120% (1.2 multiplier) of relevant font size instead of 100%
   (1.0 multiplier).
+* In 8.2.9, elaborate semantics for resolving percentage font size on region element,
+  in which case computed cell size is used as a reference.
+* In 8.2.9, elaborate note that explains use of single cell-based length to also include
+  case of two cell-based lengths.
 * In 8.2.12, correct typo where "initial" value was written, but "computed" value
   intended.
 * In 8.2.12, clarify that the interpretation of "normal" is scoped by descendants in a

--- a/ttml1/spec/ttml1.xml	Fri Aug 23 12:28:30 2013 -0600
+++ b/ttml1/spec/ttml1.xml	Fri Aug 23 18:22:19 2013 -0600
@@ -569,13 +569,6 @@
 </def>
 </gitem>
 <gitem>
-<label>Content Profile</label>
-<def>
-<p>A collection of features and extensions that are (or may be) employed by
-Timed Text Markup Language content.</p>
-</def>
-</gitem>
-<gitem>
 <label>Content Region</label>
 <def>
 <p>A logical region into which rendered content is placed when modeling or
@@ -596,7 +589,7 @@
 <def>
 <p>The implied context or environment external to a <emph>Content Processor</emph> in
 which document interchange occurs, and in which out-of-band protocols or specifications
-may define certain behavioral defaults, such as an implied <emph>Content Profile</emph>.</p>
+may define certain behavioral defaults, such as an implied profile.</p>
 </def>
 </gitem>
 <gitem>
@@ -618,8 +611,7 @@
 <gitem>
 <label>Exchange Profile</label>
 <def>
-<p>A content profile that serves a set of needs
-for content interchange.</p>
+<p>A profile of content that serves a set of needs for content interchange.</p>
 </def>
 </gitem>
 <gitem>
@@ -653,13 +645,6 @@
 </def>
 </gitem>
 <gitem>
-<label>Processor Profile</label>
-<def>
-<p>A collection of features and extensions that must or may be implemented (supported) by
-a content processor.</p>
-</def>
-</gitem>
-<gitem>
 <label>Profile Definition Document</label>
 <def>
 <p>A document that defines a specific collection of features and extensions
@@ -1082,8 +1067,7 @@
 associated <emph>Abstract Document Type</emph>.</p>
 <note>
 <p>While a conformant processor may not <emph>a priori</emph> reject a
-conformant <emph>Document Instance</emph> that adheres to a
-supported content profile, a given <emph>Document Instance</emph> may be
+conformant <emph>Document Instance</emph>, a given <emph>Document Instance</emph> may be
 constrained by the author or authoring tool to satisfy a more
 restrictive definition of validity.</p>
 </note>
@@ -1297,14 +1281,14 @@
 <loc href="#parameter-vocabulary-profile"><el>ttp:profile</el></loc>
 element is present in a <emph>Document Instance</emph>, and if the <emph>Document
 Interchange Context</emph> does not make an implicit or explicit
-reference to a pre-defined Content Profile or does not specify a <emph>Profile Definition
+reference to a pre-defined profile or does not specify a <emph>Profile Definition
 Document</emph> or another equivalent set of feature designations,
 then the DFXP Transformation profile applies.</p>
 <note role="elaboration">
-<p>It is not a requirement on a conformant <emph>Document Instance</emph> that a <emph>Content Profile</emph> be internally
+<p>It is not a requirement on a conformant <emph>Document Instance</emph> that a profile be internally
 defined by use of a <el>ttp:profile</el> element or internally referenced by a
 <att>ttp:profile</att> attribute. More specifically, it is permitted that the <emph>Document
-Interchange Context</emph> determines the applicable <emph>Content Profile</emph> through private
+Interchange Context</emph> determines the applicable profile through private
 agreement, out-of-band protocol, or common use (between sender and receiver) of a profile defined
 by an external specification.</p>
 </note>
@@ -4249,7 +4233,9 @@
 </tr>
 <tr>
 <td><emph>Percentages:</emph></td>
-<td>relative to parent element's font size</td>
+<td>if not <loc href="#content-vocabulary-span"><el>region</el></loc> element,
+then relative to parent element's font size; otherwise, relative to the
+<emph>Computed Cell Size</emph></td>
 </tr>
 <tr>
 <td><emph>Animatable:</emph></td>
@@ -4283,7 +4269,10 @@
 <p>The expression <code>1c</code> means one cell, where <code>'c'</code> expresses
 the <emph>cell</emph> length unit as defined by <specref ref="style-value-length"/>.
 When a single &lt;length&gt; is expressed using cell units, then it refers to the height of
-the <emph>Computed Cell Size</emph>.</p>
+the <emph>Computed Cell Size</emph>.
+When two &lt;length&gt; values are expressed using cell units, then the first refers to the width of
+the <emph>Computed Cell Size</emph>, and the second refers to the height of the
+<emph>Computed Cell Size</emph>.</p>
 </note>
 <p>The <att>tts:fontSize</att> style is illustrated by the following example.</p>
 <table id="style-attribute-fontSize-example-1" role="example">

--- a/ttml2/spec/ttml2.xml	Fri Aug 23 12:28:30 2013 -0600
+++ b/ttml2/spec/ttml2.xml	Fri Aug 23 18:22:19 2013 -0600
@@ -573,6 +573,11 @@
 <def>
 <p>A collection of features and extensions that are (or may be) employed by
 Timed Text Markup Language content.</p>
+<ednote>
+<name>Content Profile</name>
+<date>2013-08-23</date>
+<edtext>Need to update and elaborate definition of content profile based on new profiling mechanisms.</edtext>
+</ednote>
 </def>
 </gitem>
 <gitem>
@@ -596,7 +601,7 @@
 <def>
 <p>The implied context or environment external to a <emph>Content Processor</emph> in
 which document interchange occurs, and in which out-of-band protocols or specifications
-may define certain behavioral defaults, such as an implied <emph>Content Profile</emph>.</p>
+may define certain behavioral defaults, such as an implied profile.</p>
 </def>
 </gitem>
 <gitem>
@@ -618,8 +623,7 @@
 <gitem>
 <label>Exchange Profile</label>
 <def>
-<p>A content profile that serves a set of needs
-for content interchange.</p>
+<p>A profile of content that serves a set of needs for content interchange.</p>
 </def>
 </gitem>
 <gitem>
@@ -657,6 +661,11 @@
 <def>
 <p>A collection of features and extensions that must or may be implemented (supported) by
 a content processor.</p>
+<ednote>
+<name>Processor Profile</name>
+<date>2013-08-23</date>
+<edtext>Need to update and elaborate definition of processor profile based on new profiling mechanisms.</edtext>
+</ednote>
 </def>
 </gitem>
 <gitem>
@@ -1082,8 +1091,7 @@
 associated <emph>Abstract Document Type</emph>.</p>
 <note>
 <p>While a conformant processor may not <emph>a priori</emph> reject a
-conformant <emph>Document Instance</emph> that adheres to a
-supported content profile, a given <emph>Document Instance</emph> may be
+conformant <emph>Document Instance</emph>, a given <emph>Document Instance</emph> may be
 constrained by the author or authoring tool to satisfy a more
 restrictive definition of validity.</p>
 </note>
@@ -1297,14 +1305,14 @@
 <loc href="#parameter-vocabulary-profile"><el>ttp:profile</el></loc>
 element is present in a <emph>Document Instance</emph>, and if the <emph>Document
 Interchange Context</emph> does not make an implicit or explicit
-reference to a pre-defined Content Profile or does not specify a <emph>Profile Definition
+reference to a pre-defined profile or does not specify a <emph>Profile Definition
 Document</emph> or another equivalent set of feature designations,
 then the DFXP Transformation profile applies.</p>
 <note role="elaboration">
-<p>It is not a requirement on a conformant <emph>Document Instance</emph> that a <emph>Content Profile</emph> be internally
+<p>It is not a requirement on a conformant <emph>Document Instance</emph> that a profile be internally
 defined by use of a <el>ttp:profile</el> element or internally referenced by a
 <att>ttp:profile</att> attribute. More specifically, it is permitted that the <emph>Document
-Interchange Context</emph> determines the applicable <emph>Content Profile</emph> through private
+Interchange Context</emph> determines the applicable profile through private
 agreement, out-of-band protocol, or common use (between sender and receiver) of a profile defined
 by an external specification.</p>
 </note>
@@ -4299,7 +4307,9 @@
 </tr>
 <tr>
 <td><emph>Percentages:</emph></td>
-<td>relative to parent element's font size</td>
+<td>if not <loc href="#content-vocabulary-span"><el>region</el></loc> element,
+then relative to parent element's font size; otherwise, relative to the
+<emph>Computed Cell Size</emph></td>
 </tr>
 <tr>
 <td><emph>Animatable:</emph></td>
@@ -4333,7 +4343,10 @@
 <p>The expression <code>1c</code> means one cell, where <code>'c'</code> expresses
 the <emph>cell</emph> length unit as defined by <specref ref="style-value-length"/>.
 When a single &lt;length&gt; is expressed using cell units, then it refers to the height of
-the <emph>Computed Cell Size</emph>.</p>
+the <emph>Computed Cell Size</emph>.
+When two &lt;length&gt; values are expressed using cell units, then the first refers to the width of
+the <emph>Computed Cell Size</emph>, and the second refers to the height of the
+<emph>Computed Cell Size</emph>.</p>
 </note>
 <p>The <att>tts:fontSize</att> style is illustrated by the following example.</p>
 <table id="style-attribute-fontSize-example-1" role="example">