Changed the "status section" to status information to provide more flexibility in how it is managed, although it is still subject to pubrules. ISSUE-51
--- a/tr.html Tue Dec 03 23:04:46 2013 +0100
+++ b/tr.html Thu Dec 05 08:16:31 2013 +0100
@@ -237,7 +237,8 @@
process <em class="rfc2119 old">must</em> <span class="from">(was in
7.8)</span> clearly indicate its <a href="#maturity-levels">maturity
level</a>, and <em id="DocumentStatus" class="rfc2119">must</em>
- include a section about the status of the document. The status section</p>
+ include information about the status of the document. This status
+ information</p>
<ul>
<li><em class="rfc2119">must</em> be unique each time a specification is
published,<br>
@@ -263,7 +264,7 @@
<p>The Team is <em class="rfc2119">not required</em> to publish a Technical
Report that does not conform to the Team's <a href="http://www.w3.org/Guide/pubrules">Publication
Rules</a> (e.g., for <a name="DocumentName" id="DocumentName">naming</a>,
- style, and <a name="document-copyright" id="document-copyright">copyright
+ status information, style, and <a name="document-copyright" id="document-copyright">copyright
requirements</a>). These rules are subject to change by the Team from
time to time. The Team <em class="rfc2119">must</em> inform group Chairs
and the Advisory Committee of any changes to these rules.</p>