Update references and advisement

Author: csarven

ED/qa.html

@@ -741,7 +741,7 @@ <h3 property="schema:name">Test Report Description</h3>
                     <li>Zero or one <code>dcterms:description</code> property to include additional notes about the report from the submitter.</li>
                   </ul>
 
-                  <p class="issue">Additional notes about the report can be expressed as a Web Annotation (<code>oa:Annotation</code>).</p>
+                  <p class="issue" about="" id="test-suite-implementation-earl" rel="spec:advisement" resource="#test-suite-implementation-earl"><span property="spec:statement">Additional notes about the report <span rel="spec:advisementLevel" resource="spec:Can">can</span> be expressed as a Web Annotation (<code>oa:Annotation</code>).</span></p>
 
                   <p class="issue">Agent (person or software) that had a role in the production of the test report can be expressed as a PROV-O activity association (<code>prov:wasAssociatedWith</code>).</p>
 
@@ -1128,9 +1128,9 @@ <h3 property="schema:name">Normative References</h3>
                     <dt id="bib-rfc8174">[RFC8174]</dt>
                     <dd><cite><a href="https://datatracker.ietf.org/doc/html/rfc8174" rel="cito:citesAsAuthority">Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</a></cite>. B. Leiba.  IETF. May 2017. Best Current Practice. URL: <a href="https://datatracker.ietf.org/doc/html/rfc8174">https://datatracker.ietf.org/doc/html/rfc8174</a></dd>
                     <dt id="bib-rfc9110">[RFC9110]</dt>
-                    <dd><cite><a href="https://www.rfc-editor.org/rfc/rfc9110" rel="cito:citesAsAuthority">HTTP Semantics</a></cite>. R. Fielding, M. Nottingham, J. Reschke, Editors.  IETF. June 2022. Internet Standard. URL: <a href="https://www.rfc-editor.org/rfc/rfc9110">https://www.rfc-editor.org/rfc/rfc9110</a></dd>
+                    <dd><cite><a href="https://www.rfc-editor.org/rfc/rfc9110" rel="cito:citesAsAuthority">HTTP Semantics</a></cite>. R. Fielding, M. Nottingham, J. Reschke, Ed..  IETF. June 2022. Internet Standard. URL: <a href="https://www.rfc-editor.org/rfc/rfc9110">https://www.rfc-editor.org/rfc/rfc9110</a></dd>
                     <dt id="bib-rfc9113">[RFC9113]</dt>
-                    <dd><cite><a href="https://www.rfc-editor.org/rfc/rfc9113" rel="cito:citesAsAuthority">HTTP/2</a></cite>. M. Thomson, C. Benfield, Editors.  IETF. June 2022. Internet Standard. URL: <a href="https://www.rfc-editor.org/rfc/rfc9113">https://www.rfc-editor.org/rfc/rfc9113</a></dd>
+                    <dd><cite><a href="https://www.rfc-editor.org/rfc/rfc9113" rel="cito:citesAsAuthority">HTTP/2</a></cite>. M. Thomson, C. Benfield, Ed..  IETF. June 2022. Internet Standard. URL: <a href="https://www.rfc-editor.org/rfc/rfc9113">https://www.rfc-editor.org/rfc/rfc9113</a></dd>
                     <dt id="bib-qa-glossary">[qa-glossary]</dt>
                     <dd><cite><a href="https://www.w3.org/QA/glossary" rel="cito:citesAsAuthority">Quality Assurance glossary</a></cite>. K. Dubost, M. Skall  W3C. 28 April 2005. W3C Quality Assurance and Conformance activity. URL: <a href="https://www.w3.org/QA/glossary">https://www.w3.org/QA/glossary</a></dd>
                     <dt id="bib-skos-reference">[skos-reference]</dt>
@@ -1158,11 +1158,11 @@ <h3 property="schema:name">Informative References</h3>
                     <dt id="bib-qaframe-spec">[qaframe-spec]</dt>
                     <dd><cite><a href="https://www.w3.org/TR/qaframe-spec/" rel="cito:citesAsPotentialSolution">QA Framework: Specification Guidelines</a></cite>. Karl Dubost; Lynne Rosenthal; Dominique Hazaël-Massieux; Lofton Henderson et al.  W3C. 17 August 2005. W3C Recommendation. URL: <a href="https://www.w3.org/TR/qaframe-spec/">https://www.w3.org/TR/qaframe-spec/</a></dd>
                     <dt id="bib-security-privacy-questionnaire">[SECURITY-PRIVACY-QUESTIONNAIRE]</dt>
-                    <dd><cite><a href="https://www.w3.org/TR/security-privacy-questionnaire/" rel="cito:citesAsPotentialSolution">Self-Review Questionnaire: Security and Privacy</a></cite>. Theresa O'Connor; Peter Snyder.  W3C. 23 March 2021. W3C Note. URL: <a href="https://www.w3.org/TR/security-privacy-questionnaire/">https://www.w3.org/TR/security-privacy-questionnaire/</a></dd>
+                    <dd><cite><a href="https://www.w3.org/TR/security-privacy-questionnaire/" rel="cito:citesAsPotentialSolution">Self-Review Questionnaire: Security and Privacy</a></cite>. Theresa O'Connor; Peter Snyder.  W3C. 16 December 2021. W3C Group Note. URL: <a href="https://www.w3.org/TR/security-privacy-questionnaire/">https://www.w3.org/TR/security-privacy-questionnaire/</a></dd>
                     <dt id="bib-solid-technical-reports">[SOLID-TECHNICAL-REPORTS]</dt>
                     <dd><cite><a href="https://solidproject.org/TR/" rel="cito:citesAsRelated">Solid Technical Reports</a></cite>. Sarven Capadisli.  W3C Solid Community Group. 16 March 2024. Living Document. URL: <a href="https://solidproject.org/TR/">https://solidproject.org/TR/</a></dd>
                     <dt id="bib-w3c-process">[W3C-PROCESS]</dt>
-                    <dd><cite><a href="https://www.w3.org/Consortium/Process/" rel="cito:citesAsRelated">W3C Process Document</a></cite>. Elika J. Etemad (fantasai); Florian Rivoal.  W3C. 12 June 2023. URL: <a href="https://www.w3.org/Consortium/Process/">https://www.w3.org/Consortium/Process/</a></dd>
+                    <dd><cite><a href="https://www.w3.org/Consortium/Process/" rel="cito:citesAsPotentialSolution">W3C Process Document</a></cite>. Elika J. Etemad / fantasai; Florian Rivoal;  W3C Process Community Group. 3 November 2023. URL: <a href="https://www.w3.org/Consortium/Process/">https://www.w3.org/Consortium/Process/</a></dd>
                   </dl>
                 </div>
               </section>