Merge pull request #65 from w3c/update/split-ps

Split privacy and security considerations

Author: mattgarrish

dpub-aria/index.html

@@ -6,7 +6,6 @@
     <script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
     <script src="common/script/resolveReferences.js" class="remove"></script>
     <script src="common/biblio.js" class="remove" defer="defer"></script>
-    <!-- <script src="common/script/linkFix.js" class="remove"></script> -->
     <link href="common/css/common.css" rel="stylesheet" type="text/css" />
     <script class="remove" src="common/script/ariaChild.js"></script>
     <script class="remove" src="common/script/roleInfo.js"></script>
@@ -4397,9 +4396,12 @@ <h3>Definition of Roles</h3>
       </section>
     </section>
     <section class="informative">
-      <h2>Privacy and Security Considerations</h2>
+      <h2>Security Considerations</h2>
 
       <p>This specification introduces no new security considerations.</p>
+    </section>
+    <section class="informative">
+      <h2>Privacy Considerations</h2>
 
       <p>
         In accordance with <a href="https://w3ctag.github.io/design-principles/#do-not-expose-use-of-assistive-tech">Web Platform Design Principles</a>, this specification provides no programatic
@@ -4409,32 +4411,6 @@ <h2>Privacy and Security Considerations</h2>
         technologies.
       </p>
     </section>
-    <!-- <section class="appendix informative" id="exit_criteria">
-			<h2>Candidate Recommendation Exit Criteria</h2>
-			<p>For this specification to be advanced to Proposed Recommendation, it has to be proven that roles defined
-				in this specification have sufficient usage by the target communities. More specifically, it has to be
-				documented that <em>each</em>
-				<a href="#roles">Digital Publishing Role</a> is used (at least in preliminary prototypes, not
-				necessarily in full production yet) by two, independent document author/publisher as a means to
-				structure document, where “usage” means: </p>
-
-			<ul>
-				<li>the <code>role</code> attribute value is used, as defined in this specification; or, as a
-					fallback</li>
-				<li>the <code>epub:type</code> attribute, defined for the purpose of <a
-						href="http://www.idpf.org/epub/31/spec/epub-contentdocs.html#sec-xhtml-semantic-inflection"
-						>Semantic Inflection</a> in [[EPUB-Content]], is used with the related value (when specified in
-					the detailed specification of the role) in the <a
-						href="https://idpf.github.io/epub-vocabs/structure/">EPUB Structural Semantic Vocabulary</a>
-					[[EPUB-SSV]]. </li>
-			</ul>
-
-			<p> In the case where the <code>epub:type</code> attribute is used, the author/publisher should also clearly
-				state that the plan is to replace <code>epub:type</code> by the ARIA <code>role</code> attribute when
-				this specification is published as a Recommendation. Furthermore, it is also required that at least two,
-				independent authors/publishers use a comprehensive, although not necessarily complete, set of
-					<code>role</code> attribute (as opposed to <code>epub:type</code>). </p>
-		</section>-->
     <section class="appendix informative" id="changelog">
       <h2>Change Log</h2>