clean links to drop into full version.
authorcharles
Wed, 19 Mar 2014 13:00:59 +0100
changeset 95 881ab929e726
parent 94 6d59bee616e9
child 96 e2d162dfd842
clean links to drop into full version.
tr.html
--- a/tr.html	Wed Mar 19 12:58:56 2014 +0100
+++ b/tr.html	Wed Mar 19 13:00:59 2014 +0100
@@ -30,12 +30,12 @@
     <h1>W3C Process Document</h1>
     <h2 id="Reports">7 W3C Technical Report Development Process</h2>
     <p>The W3C technical report development process is the set of steps and
-      requirements followed by W3C <a href="http://www.w3.org/2005/10/Process-20051014/groups#GroupsWG">Working
+      requirements followed by W3C <a href="groups#GroupsWG">Working
         Groups</a> to standardize Web technology. The W3C technical report
       development process is designed to </p>
     <ul>
       <li>support multiple specification development methodologies</li>
-      <li>maximize <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-consensus"
+      <li>maximize <a href="policies.html#def-consensus"
           rel="glossary" title="Definition of Consensus"><span class="dfn-instance">consensus</span></a>
         about the content of stable technical reports</li>
       <li>ensure high technical and editorial quality</li>
@@ -46,7 +46,7 @@
     </ul>
     <p>See also the licensing goals for W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section
         2</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
-        Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].
+        Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>].
       </p>
     <h3>Table of Contents</h3>
     <ul id="mozToc">
@@ -195,7 +195,7 @@
       in maturity level, requiring a Working Group to conduct further work, and
       <em class="rfc2119">may</em> require the specification to return to a
       lower <a href="#maturity-level">maturity level</a>. The Director <em class="rfc2119">must</em>
-      inform the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
+      inform the <a href="organization.html#AC">Advisory
         Committee</a> and Working Group Chairs when a Working Group's request
       for a specification to advance in maturity level is declined and the
       specification is returned to a Working Group for further work.</p>
@@ -227,7 +227,7 @@
       </dd>
       <dd class="new"><strong>Note:</strong> Candidate Recommendation is the
         state referred to in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
-          Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>]
+          Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>]
         as "Last Call Working Draft"</dd>
       <dd><strong>Note:</strong> Candidate Recommendations are expected to be
         acceptable as Recommendations. Announcement of a different next step <em
@@ -255,7 +255,7 @@
         longer endorses. See also clause 10 of the licensing requirements for
         W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section
           5</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
-          Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].</dd>
+          Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>].</dd>
     </dl>
     <p>Working Groups and Interest Groups <em class="rfc2119">may</em> make
       available "Editor's drafts". Editor's drafts have no official standing
@@ -267,7 +267,7 @@
       Reports</h4>
     <p>Every document published as part of the technical report development
       process <em class="rfc2119 old">must</em> be a public document. The <a href="http://www.w3.org/TR/">index
-        of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-doc-list">PUB11</a>]
+        of W3C technical reports</a> [<a href="refs.html#ref-doc-list">PUB11</a>]
       is available at the W3C Web site. W3C strives to make archival documents
       indefinitely available at their original address in their original form.</p>
     <p>Every document published as part of the technical report development
@@ -305,7 +305,7 @@
       and the Advisory Committee of any changes to these rules.</p>
     <p>The primary language for W3C Technical Reports is English. W3C encourages
       the translation of its Technical Reports. <a href="http://www.w3.org/Consortium/Translation/">Information
-        about translations of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-translations">PUB18</a>]
+        about translations of W3C technical reports</a> [<a href="refs.html#ref-translations">PUB18</a>]
       is available at the W3C Web site.</p>
     <h4 id="transition-reqs">7.2.2 Advancement on the Recommendation Track</h4>
     <p>For <em>all</em> requests to advance a specification to a new maturity
@@ -317,11 +317,11 @@
       <li><em class="rfc2119 ">must</em> provide public documentation of all <a
           href="#substantive-change">substantive changes</a> to the technical
         report since the previous publication.</li>
-      <li><em class="rfc2119">must</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
+      <li><em class="rfc2119">must</em> <a href="policies.html#formal-address">formally
           address</a> all issues raised about the document since the previous
         maturity level.</li>
       <li><em class="rfc2119">must</em> provide public documentation of any <a
-          href="http://www.w3.org/2005/10/Process-20051014/policies.html#FormalObjection">Formal
+          href="policies.html#FormalObjection">Formal
           Objections</a>.</li>
       <li><span class="rfc2119">should</span> provide public documentation of
         changes that are not substantive.</li>
@@ -339,7 +339,7 @@
       ensure the requirements have been met before Director's approval is given.</p>
     <h4 id="doc-reviews">7.2.3 Reviews and Review Responsibilities</h4>
     <p>A document is available for review from the moment it is first published.
-      Working Groups <em class="rfc2119">should</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
+      Working Groups <em class="rfc2119">should</em> <a href="policies.html#formal-address">formally
         address</a> <em>any</em> substantive review comment about a technical
       report in a timely manner. </p>
     Reviewers <em class="rfc2119">should</em> send substantive technical
@@ -447,7 +447,7 @@
     <p>Publishing the First Public Working Draft triggers a Call for Exclusions,
       per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
         4</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
-        Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].</p>
+        Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>].</p>
     <h4 id="revised-wd">7.3.2 Revising Public Working Drafts</h4>
     <p>A Working Group <em class="rfc2119">should</em> publish a Working Draft
       to the W3C Technical Reports page when there have been significant changes
@@ -482,7 +482,7 @@
     <p>Work on a technical report <em class="rfc2119">may</em> cease at any
       time. Work <em class="rfc2119 new">should</em> cease if W3C or a Working
       Group determines that it cannot productively carry the work any further.
-      If the Director <a href="http://www.w3.org/2005/10/Process-20051014/groups.html#GeneralTermination">closes
+      If the Director <a href="groups.html#GeneralTermination">closes
         a Working Group</a> W3C <em class="rfc2119">must </em> publish any
       unfinished specifications on the Recommendation track as <a href="#Note">Working
         Group Notes</a>. If a Working group decides, or the Director requires,
@@ -519,11 +519,11 @@
       begin an Advisory Committee Review of the specification.</p>
     <p> A Candidate Recommendation corresponds to a "Last Call Working Draft" as
       used in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
-        Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].
+        Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>].
       Publishing a Candidate Recommendation triggers a Call for Exclusions, per
       <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
         4</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
-        Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].</p>
+        Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>].</p>
     <p>Possible next steps:</p>
     <ul>
       <li>Return to <a href="#hb-wd">Working Draft</a></li>
@@ -532,10 +532,10 @@
         next step)</li>
       <li><a href="#Note">Working Group Note</a></li>
     </ul>
-    <p>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"
+    <p>If there was any <a href="policies.html#def-Dissent"
         rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>&nbsp;to
-      the Working Group decision to request advancement <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
-        Committee</a> representatives <em class="rfc2119">may</em> <a href="http://www.w3.org/2005/10/Process-20051014/acreview.html#ACAppeal">appeal</a>
+      the Working Group decision to request advancement <a href="organization.html#AC">Advisory
+        Committee</a> representatives <em class="rfc2119">may</em> <a href="acreview.html#ACAppeal">appeal</a>
       the decision to advance the technical report.</p>
     <h4 id="revised-cr">7.4.1 Revising a Candidate Recommendation</h4>
     <p>If there are any <a href="#substantive-change">substantive changes</a>
@@ -545,7 +545,7 @@
       Recommendation. This is because substantive changes will generally require
       a new Exclusion Opportunity per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
         4</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
-        Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].
+        Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>].
       Note that approval is <em>expected</em> to be fairly simple compared to
       getting approval for a transition to Candidate Recommendation.</p>
     <p>In addition the Working Group:</p>
@@ -580,7 +580,7 @@
         Proposed Recommendation and <em class="rfc2119">should</em> be at least
         10 days after the end of the last Exclusion Opportunity per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
           4</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
-          Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].</li>
+          Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>].</li>
     </ul>
     <p>A Working Group:</p>
     <ul>
@@ -591,7 +591,7 @@
       <li><em class="rfc2119">must</em> show that all issues raised during the
         Candidate Recommendation review period other than by Advisory Committee
         representatives acting in their formal AC representative role have been
-        <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
+        <a href="policies.html#formal-address">formally
           addressed</a>,</li>
       <li><em class="rfc2119">must </em>identify any substantive issues raised
         since the close of the Candidate Recommendation review period by parties
@@ -604,7 +604,7 @@
     <p>The Director:</p>
     <ul>
       <li><em class="rfc2119">must</em> announce the publication of a Proposed
-        Recommendation to the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
+        Recommendation to the <a href="organization.html#AC">Advisory
           Committee</a>, and</li>
       <li><span><em class="rfc2119">may</em> approve a Proposed Recommendation
           with minimal implementation experience where there is a compelling
@@ -639,17 +639,17 @@
       <li>A Recommendation <em class="rfc2119">must not</em> include any
         substantive changes from the Proposed Recommendation on which it is
         based.</li>
-      <li>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"
+      <li>If there was any <a href="policies.html#def-Dissent"
           rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
         in Advisory Committee reviews, the Director <em class="rfc2119">must</em>
         publish the substantive content of the dissent to W3C and the general
-        public, and <em class="rfc2119">must</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
+        public, and <em class="rfc2119">must</em> <a href="policies.html#formal-address">formally
           address</a> the comment at least 14 days before publication as a W3C
-        Recommendation. In this case the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
-          Committee</a> <em class="rfc2119">may</em> <a href="http://www.w3.org/2005/10/Process-20051014/acreview.html#ACAppeal">appeal</a>
+        Recommendation. In this case the <a href="organization.html#AC">Advisory
+          Committee</a> <em class="rfc2119">may</em> <a href="acreview.html#ACAppeal">appeal</a>
         the decision,</li>
       <li>The Director <em class="rfc2119">must</em> announce the publication
-        of a W3C Recommendation to <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
+        of a W3C Recommendation to <a href="organization.html#AC">Advisory
           Committee</a>, other W3C groups and to the public.</li>
     </ul>
     <p>Possible next steps:</p>
@@ -733,7 +733,7 @@
         level the specification had before publication as a Note</li>
     </ul>
     <p>The <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent
-        Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>]
+        Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>]
       does not specify any licensing requirements or commitments for Working
       Group Notes.</p>
     <h3 id="rec-rescind">7.9 Rescinding a W3C Recommendation</h3>
@@ -741,7 +741,7 @@
       if the Recommendation contains many errors that conflict with a later
       version or if W3C discovers burdensome patent claims that affect
       implementers and cannot be resolved; see the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
-        Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>]
+        Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>]
       and in particular <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section
         5</a> (bullet 10) and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-PAG-conclude">section
         7.5</a>. A Working Group <em class="rfc2119">may</em> request the
@@ -773,7 +773,7 @@
     </ul>
     <p>The Director <em class="rfc2119">must</em> announce the proposal to
       rescind a W3C Recommendation to other W3C groups, the public, and the <a
-        href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
+        href="organization.html#AC">Advisory
         Committee</a>. The announcement <em class="rfc2119">must</em>:</p>
     <ul>
       <li>indicate that this is a Proposal to Rescind a Recommendation</li>
@@ -784,13 +784,13 @@
         Working Groups;</li>
       <li>solicit public review.</li>
     </ul>
-    <p>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"
+    <p>If there was any <a href="policies.html#def-Dissent"
         rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
       in Advisory Committee reviews, the Director <em class="rfc2119">must</em>
       publish the substantive content of the dissent to W3C <strong>and the
-        public</strong>, and <em class="rfc2119">must</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
+        public</strong>, and <em class="rfc2119">must</em> <a href="policies.html#formal-address">formally
         address</a> the comment at least 14 days before publication as a
-      Rescinded Recommendation. In this case the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
+      Rescinded Recommendation. In this case the <a href="organization.html#AC">Advisory
         Committee</a> <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a>
       the decision.</p>
     <p> A Rescinded Recommendation <em class="rfc2119">must</em> be published
@@ -801,7 +801,7 @@
         Organize a Recommendation Track Transition"</a> in the <a href="http://www.w3.org/Guide/">Member
         guide</a> for practical information about preparing for the reviews and
       announcements of the various steps, and <a href="http://www.w3.org/2002/05/rec-tips">tips
-        on getting to Recommendation faster</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-rec-tips">PUB27</a>].</p>
+        on getting to Recommendation faster</a> [<a href="refs.html#ref-rec-tips">PUB27</a>].</p>
     <div class="noprint">
       <div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id="navbar-bottom">
           <hr>
@@ -811,5 +811,6 @@
         </map>
       </div>
     </div>
+    
   </body>
 </html>