Merged the changes
authorcharles
Fri, 28 Feb 2014 17:26:00 +0100
changeset 12 2b4b49c893c5
parent 11 68efbad8ae7c (current diff)
parent 10 53c648cd06d8 (diff)
child 13 056c065b1abb
Merged the changes
longdesc/exitCrit.html
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/longdesc/TODO.html	Fri Feb 28 17:26:00 2014 +0100
@@ -0,0 +1,127 @@
+<!DOCTYPE html>
+<html lang="en">
+    <head>
+        <meta charset="utf-8">
+        <meta name="viewport" content="width=device-width, initial-scale=1.0">
+        <title>
+            Longdesc TODO
+        </title>
+        <link rel="stylesheet" title="base CSS" href="http://www.w3.org/StyleSheets/TR/base.css">
+    </head>
+    <body>
+        <p>
+            <a href="http://www.w3.org/"><img src="https://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a>
+        </p>
+        <h1 id="title">
+            Longdesc Transition Prep
+        </h1>
+        <h2 id="emails">
+            Emails
+        </h2>
+        <ul>
+            <li>Reply to <a href="http://lists.w3.org/Archives/Public/public-html-a11y/2013Sep/0037.html">EOWG</a> Chaals
+            </li>
+            <li>Reply to <a href="http://lists.w3.org/Archives/Public/public-html-a11y/2014Jan/0068.html">UAWG</a> Chaals
+            </li>
+        </ul>
+        <h2 id="publication">
+            Publication
+        </h2>
+        <h3 id="before-tf">
+            Before going to the TF
+        </h3>
+        <ul>
+            <li>Write Document Status Section
+            </li>
+            <li>Write Exit Criteria (Mark is Drafting) But chaals wrote a draft and shared it w/ Mark.
+            </li>
+        </ul>
+        <h3 id="tf">
+            In the Task Force
+        </h3>
+        <ul>
+            <li>Get TF then WG approval of the exit criteria
+            </li>
+            <li>Record Decision to request WG request the transition
+            </li>
+        </ul>
+        <h3 id="tf-agreement">
+            When the TF has agreed
+        </h3>
+        <ul>
+            <li>Get WG to request the transition
+            </li>
+            <li>Schedule Meeting with Director, HTML chairs as needed
+            </li>
+        </ul>
+        <h3 id="director">
+            Needed for Director's meeting
+        </h3>
+        <ul>
+            <li>Report of important changes to the document
+            </li>
+            <li>Record Objections
+            </li>
+            <li>Patent disclosures
+            </li>
+            <li>Verify no open exclusion opportunities
+            </li>
+            <li>Evidence that the document satisfies group's requirements
+            </li>
+            <li>Evidence that dependencies with other groups are met
+            </li>
+            <li>Evidence that the document has- received wide review
+            </li>
+            <li>Evidence that issues have been formally addressed
+            </li>
+            <li>Implementation Report (Mark is Drafting)
+            </li>
+            <li>Prepare Spec to pass pubrules
+            </li>
+            <li>Verify that transition requirements have been met
+            </li>
+            <li>Send Transition Request
+            </li>
+            <li>Create Agenda (This should just be "step through the transition request" which has all the things that need to get checked)
+            </li>
+            <li>Reserve Teleconference Bridge
+            </li>
+            <li>Transition Meeting Prep/Practice (Don't bother with this. The "director" who sounds a lot like Ralph will check through the things required, which should be in the transition request, and if we're good, says "OK". If you are really concerned, ask PLH to have a quick look first).
+            </li>
+            <li>Transition Meeting
+            </li>
+        </ul>
+        <h3 id="approved">
+            When we are approved for Proposed Rec
+        </h3>
+        <ul>
+            <li>Create a Publication Schedule
+            </li>
+            <li>The Team Contact reviews the&nbsp;(Team-only) pre-publication steps.
+            </li>
+            <li>Send a pub request
+            </li>
+            <li>install the document in its final location
+            </li>
+            <li>Meeting with Shawn to do WAI messaging
+            </li>
+            <li>Send DRAFT transition announcement to Comm Team
+            </li>
+            <li>Public Mailing List
+            </li>
+            <li>Team Only Mailing List
+            </li>
+            <li>The Facilitators fwd announcement to WG and TF-
+            </li>
+        </ul>
+        <h2 id="done">
+            DONE
+        </h2>
+        <ul>
+            <li>Reply to <a href="http://lists.w3.org/Archives/Public/public-html-a11y/2013Dec/0083.html">Matt Turvey</a> Chaals
+            </li>
+            <li>Chaals will scribe transition call.
+            </li>
+        </ul>
+    </body>
+</html>
--- a/longdesc/exitCrit.html	Fri Feb 28 17:19:09 2014 +0100
+++ b/longdesc/exitCrit.html	Fri Feb 28 17:26:00 2014 +0100
@@ -1,7 +1,13 @@
 <html>
   <head>
+<<<<<<< local
     <meta content="text/html; charset=UTF-8" http-equiv="content-type">
     <style>em.rfc2119 { 
+=======
+    <meta charset="UTF-8">
+    <link rel="stylesheet" title="base CSS" href="http://www.w3.org/StyleSheets/TR/base.css">
+    <style>em.rfc2119 {
+>>>>>>> other
     text-transform:     lowercase;
     font-variant:       small-caps;
     font-style:         normal;
@@ -10,8 +16,15 @@
     <title>longdesc exit criteria</title>
   </head>
   <body>
+    <p>
+        <a href="http://www.w3.org/">
+          <img src="https://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72">
+        </a>
+    </p>
+
     <h1>HTML Image Description Extension (longdesc)</h1>
     <h2>Exit Criteria for Candidate Recommendation</h2>
+<<<<<<< local
     <p>Preconditions:</p>
     <ul>
       <li>There is a <a href="@@">test suite</a>. </li>
@@ -21,7 +34,34 @@
         whether an implementation that passes the "required" test also passes
         the relevant dependent tests. </li>
     </ul>
+=======
+
+    <p><em>
+      The following DRAFT is under consideration by the HTML Accessibility
+      Task Force (Task Force).  The agreed upon text will be submitted to the
+      HTML Working Group and the Protocols and Formats Working Group for
+      approval.
+    </em></p>
+
+    <p>
+      The Task Force has developed a <a href="@@">suite of tests</a> to measure
+      support for all normative absolute (RFC2119 "MUST") requirements stated in
+      the specification. The TF agrees that the tests
+      marked "dependent" are sufficient to show whether an implementation that
+      passes the "required" test also passes the relevant dependent tests. The
+      TF agrees that there are sufficient tests for requirements in the
+      specification labelled should.
+    </p>
+
+    <p>
+      For the <a href="http://www.w3.org/TR/html-longdesc/">HTML 5 Image
+      Description Extension</a> to be advanced to a W3C Proposed Recommendation,
+      the following conditions are to be met:
+    </p>
+
+>>>>>>> other
     <ol>
+<<<<<<< local
       <li>At least two independent "release" implementations of a user agent
         pass each "required" test.</li>
       <li>At least two independent "release" implementations of an authoring
@@ -32,6 +72,25 @@
         dependent tests.</li>
       <li>At least 50 pages on the Web which are not developed as examples
         implement each content requirement.</li>
+=======
+      <li>For each test in the test suite that is for a
+        <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#normative-def">
+          normative</a> feature, there exist atleast two independent
+          <a href="http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html#implementation">
+          implementations</a> of a user agent that pass.</li>
+      <li>For each test in the test suite that is for a normative feature, there
+        exist at least two independent implementations of an authoring tool that
+        pass.</li>
+      <li>For each test in the test suite that is for a normative feature, there
+        exists at least one validator that can successfully test whether content
+        passes.</li>
+      <li>For each test in the test suite that depends on another test, at least
+        one implementation that passes the test depended on passes the dependent
+        test.</li>
+      <li>For each requirement on authors in the specification there exist at
+        least 50 pages on the Web that implement this, and which are not
+        developed as examples.</li>
+>>>>>>> other
     </ol>
   </body>
 </html>