Added requirements for Status of Doc to be unique for each publication, and to identify whether a Rec is provisional or Formally Approved. ISSUE-48
authorcharles
Fri, 18 Oct 2013 02:20:38 +0200
changeset 42563e36863a36
parent 41 23a28177f938
child 43 ac8cd60df842
Added requirements for Status of Doc to be unique for each publication, and to identify whether a Rec is provisional or Formally Approved. ISSUE-48
tr.html
     1.1 --- a/tr.html	Fri Oct 18 02:02:38 2013 +0200
     1.2 +++ b/tr.html	Fri Oct 18 02:20:38 2013 +0200
     1.3 @@ -240,6 +240,9 @@
     1.4          class="from">(was in 7.8.1)</span> include a section about the status of
     1.5        the document. The status section</p>
     1.6      <ul>
     1.7 +      <li><em class="rfc2119 changed">must</em> be unique each time a
     1.8 +        specification is published<br>
     1.9 +        <em class="rfc2119 changed"></em></li>
    1.10        <li><em class="rfc2119 changed">must</em> <span class="from">(was should
    1.11            in 7.8.1)</span> state who developed the specification, </li>
    1.12        <li><em class="rfc2119 changed">must</em> <span class="from">(was should
    1.13 @@ -659,7 +662,10 @@
    1.14            Committee</a> <em class="rfc2119">may</em> <a href="http://www.w3.org/2005/10/Process-20051014/acreview.html#ACAppeal">appeal</a>
    1.15          the decision.</li>
    1.16        <li>The Director <em class="rfc2119">must</em> announce the publication
    1.17 -        of a W3C Recommendation to other W3C groups and to the public. </li>
    1.18 +        of a W3C Recommendation to other W3C groups and to the public.</li>
    1.19 +      <li>The "Status of the Document" <em class="rfc2119 changed">must</em>
    1.20 +        reflect whether it is provisionally approved, or published as a W3C
    1.21 +        Recommendation.</li>
    1.22      </ul>
    1.23      <p>Possible next steps:</p>
    1.24      <ul>