Binary file ttml2/spec/rnc/schema.zip has changed

--- a/ttml2/spec/rnc/ttml2-parameter-items.rnc	Thu Sep 05 00:23:28 2013 -0600
+++ b/ttml2/spec/rnc/ttml2-parameter-items.rnc	Thu Sep 05 17:02:48 2013 -0600
@@ -13,8 +13,9 @@
 
 TTAF.parameters.profile.attlist &=
   TTAF.id.attrib,
-  attribute use { TTAF.Profile.datatype }?,
-  attribute combine { TTAF.ProfileCombine.datatype }?
+  attribute combine { TTAF.ProfileCombine.datatype }?,
+  attribute designator { TTAF.Profile.datatype }?,
+  attribute use { TTAF.Profile.datatype }?
 
 TTAF.parameters.profile.content.extra = empty
 TTAF.parameters.profile.content =

--- a/ttml2/spec/ttml2-changes.html	Thu Sep 05 00:23:28 2013 -0600
+++ b/ttml2/spec/ttml2-changes.html	Thu Sep 05 17:02:48 2013 -0600
@@ -45,6 +45,9 @@
 * In 6.1.1, add 'combine' attribute to ttp:profile element, including normative
   processing semantics.
 
+* In 6.1.1, add 'designator' attribute to ttp:profile element in order to
+  normatively associate a profile designator with a profile definition.
+
 * In 6.1.3, add 'prohibited' value to 'value' attribute of ttp:feature element,
   including normative processing semantics.
 

--- a/ttml2/spec/ttml2.xml	Thu Sep 05 00:23:28 2013 -0600
+++ b/ttml2/spec/ttml2.xml	Thu Sep 05 17:02:48 2013 -0600
@@ -1890,6 +1890,7 @@
 <eg xml:space="preserve">
 &lt;ttp:profile
   combine = (replace|union|intersection) : replace
+  designator = string
   use = string
   <loc href="#content-attribute-id">xml:id</loc> = ID
   {<emph>any attribute not in default or any TT namespace</emph>}&gt;
@@ -1900,19 +1901,6 @@
 </tr>
 </tbody>
 </table>
-<p>If specified, the <att>use</att> attribute must adhere to the
-<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-&sect;3.2.17, and, furthermore, must denote a profile designator in
-accordance with <specref ref="vocabulary-profiles"/>. In this case,
-the profile designator must refer to (1) a standard, predefined
-<loc href="#terms-profile-definition-document">profile definition document</loc> as defined by <specref ref="profiles"/>,
-or (2) a feasibly dereferenceable resource representing a valid <emph>Profile Definition
-Document</emph> instance. In either case, the referenced profile serves as the
-baseline profile of the specifying <el>ttp:profile</el> element.</p>
-<p>If the <att>use</att> attribute is not specified, then the baseline
-profile of the <el>ttp:profile</el> element must be considered to be
-the empty (null) profile, i.e., a profile definition containing no
-feature or extension specifications.</p>
 <p>The <att>combine</att> attribute may be used to specify how
 feature or extension specifications are combined in the case that
 multiple specifications apply to the same feature or extension, respectively.
@@ -1929,6 +1917,32 @@
 <date>2013-07-10</date>
 <edtext>Need to elaborate semantics of union and intersection combination methods.</edtext>
 </ednote>
+<p>If specified, the <att>designator</att> attribute must (1) adhere to the
+<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
+&sect;3.2.17 and (2) express an absolute URI that denotes a profile designator in
+accordance with <specref ref="vocabulary-profiles"/>.</p>
+<p>A <att>designator</att> attribute may
+be specified on a <el>ttp:profile</el> element that appears in a TTML
+<loc href="#terms-document-instance">document instance</loc>, and, if not specified,
+the defined profile is considered to be an anonymous (undesignated) profile.
+A <att>designator</att> attribute should
+be specified on a <el>ttp:profile</el> element that appears in a TTML
+<loc href="#terms-profile-definition-document">profile definition document</loc> instance,
+and, if not specified, the defining context (e.g., an external specification) must specify
+a designator in its accompanying definition text.</p>
+<p>If specified, the <att>use</att> attribute must adhere to the
+<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
+&sect;3.2.17, and, furthermore, must denote a profile designator in
+accordance with <specref ref="vocabulary-profiles"/>. In this case,
+the profile designator must refer to (1) a standard, predefined
+<loc href="#terms-profile-definition-document">profile definition document</loc> as defined by <specref ref="profiles"/>,
+or (2) a feasibly dereferenceable resource representing a valid <emph>Profile Definition
+Document</emph> instance. In either case, the referenced profile serves as the
+baseline profile of the specifying <el>ttp:profile</el> element.</p>
+<p>If the <att>use</att> attribute is not specified, then the baseline
+profile of the <el>ttp:profile</el> element must be considered to be
+the empty (null) profile, i.e., a profile definition containing no
+feature or extension specifications.</p>
 <p>The collection of features and extensions of a profile are determined according
 to the following ordered rules:</p>
 <olist>
@@ -2962,6 +2976,13 @@
 </tr>
 </tbody>
 </table>
+<p></p>
+<ednote>
+<name>Possibly change ttp:version to ttm:version</name>
+<date>2013-09-05</date>
+<edtext>Unless normative processing or conformance language makes use of <att>ttp:version</att> then it
+should be changed to live in the TT Metadata Namespace, i.e., as <att>ttm:version</att>.</edtext>
+</ednote>
 <p>A <att>ttp:version</att> attribute must be specified on the root <el>tt</el>
 element of a <loc href="#terms-document-instance">document instance</loc> if it
 requires support for a <loc href="#terms-feature">feature</loc> not defined by <bibref ref="ttml1"/>.</p>
@@ -3459,6 +3480,13 @@
 <bibref ref="xmlid"/>.</p>
 <p>The <att>xml:id</att> attribute may be used with any element in the
 core vocabulary catalog.</p>
+<ednote>
+<name>Deprecating xml:id in favor of unqualified id</name>
+<date>2013-09-05</date>
+<edtext>Consider deprecating <att>xml:id</att>, using unqualified <att>id</att> instead. If deprecated, then require
+a document to only use <att>xml:id</att> or <att>id</att>, i.e., mixed use to be prohibited. See
+<loc href="https://www.w3.org/AudioVideo/TT/tracker/issues/205">Issue 205</loc>.</edtext>
+</ednote>
 </div3>
 <div3 id="content-attribute-lang">
 <head>xml:lang</head>
@@ -7192,6 +7220,13 @@
 <item><p><loc href="#semantics-style-inheritance-content">content style inheritance</loc></p></item>
 <item><p><loc href="#semantics-style-inheritance-content">region style inheritance</loc></p></item>
 </ulist>
+<ednote>
+<name>Layout Style Inheritance</name>
+<date>2013-09-05</date>
+<edtext>Regions should be able to inherit styles from a common ancestor in order to prevent
+having to full populate region styles. <loc href="https://www.w3.org/AudioVideo/TT/tracker/issues/277">Issue 277</loc> proposes
+inheritance from the layout element.</edtext>
+</ednote>
 <p>For the purpose of determining inherited styles, the element hierarchy of
 an intermediate synchronic document form of a <loc href="#terms-document-instance">document instance</loc> must be used, where
 such intermediate forms are defined by <specref ref="semantics-region-layout-step-1"/>.</p>
@@ -8625,6 +8660,12 @@
 </tbody>
 </table>
 <p></p>
+<ednote>
+<name>Change xlink:href to href</name>
+<date>2013-09-05</date>
+<edtext>The SVG WG is deprecating xlink:href, in favor of using an unqualified href attribute. See
+<loc href="http://www.w3.org/Graphics/SVG/WG/wiki/Href">SVG Wiki: Href</loc>. We should probably just specify the use of unqualified href.</edtext>
+</ednote>
 <p>Except for the constraints or variations enumerated below, the semantics of the <el>animate</el> element and its attributes
 enumerated above are defined to be those specified by <bibref ref="svg11"/>, &sect;19.2.12:</p>
 <olist>
@@ -8750,6 +8791,12 @@
 </tbody>
 </table>
 <p></p>
+<ednote>
+<name>Change xlink:href to href</name>
+<date>2013-09-05</date>
+<edtext>The SVG WG is deprecating xlink:href, in favor of using an unqualified href attribute. See
+<loc href="http://www.w3.org/Graphics/SVG/WG/wiki/Href">SVG Wiki: Href</loc>. We should probably just specify the use of unqualified href.</edtext>
+</ednote>
 <p>Except for the constraints or variations enumerated below, the semantics of the <el>set</el> element and its attributes
 enumerated above are defined to be those specified by <bibref ref="svg11"/>, &sect;19.2.13:</p>
 <olist>

Binary file ttml2/spec/xsd/schema.zip has changed

--- a/ttml2/spec/xsd/ttml2-parameter-items.xsd	Thu Sep 05 00:23:28 2013 -0600
+++ b/ttml2/spec/xsd/ttml2-parameter-items.xsd	Thu Sep 05 17:02:48 2013 -0600
@@ -12,8 +12,9 @@
   <xs:include schemaLocation="ttml2-parameter-attribs.xsd"/>
   <xs:attributeGroup name="profile.attlist">
     <xs:attributeGroup ref="tt:Core.ID.attrib.class"/>
+    <xs:attribute name="combine" type="ttd:profileCombine"/>
+    <xs:attribute name="designator" type="ttd:profile"/>
     <xs:attribute name="use" type="ttd:profile"/>
-    <xs:attribute name="combine" type="ttd:profileCombine"/>
     <xs:anyAttribute namespace="##other" processContents="lax"/>
   </xs:attributeGroup>
   <xs:attributeGroup name="features.attlist">