You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>This specification uses the RDF language to describe technical reports, test reports, test suites, and test cases. Implementers are encouraged to produce human-visible and machine-readable representations with RDFa in host languages such as HTML and SVG.</p>
640
+
<pabout="" id="human-machine-readable" rel="spec:advisement" resource="#human-machine-readable"><spanproperty="spec:statement">This specification uses the RDF language to describe technical reports, test reports, test suites, and test cases. Implementers are <spanrel="spec:advisementLevel" resource="spec:Encouraged">encouraged</span> to produce human-visible and machine-readable representations with RDFa in host languages such as HTML and SVG.</span></p>
641
641
</div>
642
642
</section>
643
643
</div>
@@ -672,17 +672,17 @@ <h3 property="schema:name skos:prefLabel">Classes of Products</h3>
672
672
<pproperty="skos:definition">The <spanabout="" rel="spec:classesOfProducts" resource="#classes-of-products">Solid QA</span> identifies the following <cite><ahref="https://www.w3.org/TR/qaframe-spec/#cop-def" rel="dcterms:subject" resource="spec:ClassesOfProducts">Classes of Products</a></cite> for conforming implementations. These products are referenced throughout this specification.</p>
<ddabout="#TechnicalReport" property="skos:definition">A <ahref="#TechnicalReport">Technical Report</a> is a document outlining recommendations and the level of conformance that various classes of products, processes, or services can achieve [<cite><aclass="bibref" href="#bib-qa-glossary">QA GLOSSARY</a></cite>].</dd>
<ddabout="#TestCase" property="skos:definition">A <ahref="#TestCase">Test Cases</a> is an individual test with a purpose that maps to measurable or testable behaviours, actions, or conditions in a <ahref="#TechnicalReport" rel="skos:related">Technical Report</a> [<cite><aclass="bibref" href="#bib-qa-glossary">QA GLOSSARY</a></cite>].</dd>
<ddabout="#TestReport" property="skos:definition">A <ahref="#test-report"rel="rdfs:seeAlso"><em>Test Report</em></a> is a resource that describes the level of conformance of a project’s tests against <ahref="#TestCase">Test Cases</a> [<cite><aclass="bib-ref" href="#bib-test-metadata">test-metadata</a></cite>].</dd>
<ddabout="#TestReport" property="skos:definition">A <ahref="#test-report">Test Report</a> is a resource that describes the level of conformance of a project’s tests against <ahref="#TestCase"rel="skos:related">Test Cases</a>.</dd>
<ddabout="#TestSuite" property="skos:definition" rel="skos:broadMatch" resource="spec:ProducerOfContent">A <ahref="#TestSuite">Test Suite</a> is collection of documents and software designed to verify an implementation's degree of conformance by using <ahref="#TechnicalReport"rel="skos:related">Technical Reports</a> and <ahref="#TestCase"rel="skos:related">Test Cases</a>, and it generates <ahref="#TestReport" rel="skos:related">Test Reports</a> [<cite><aclass="bibref" href="#bib-qa-glossary">QA GLOSSARY</a></cite>].</dd>
686
686
</dl>
687
687
</div>
688
688
</section>
@@ -764,9 +764,9 @@ <h4 property="schema:name"><span>Note</span>: Test Report Description: Descripti
<p>The subject of the <code>doap:Project</code> for Test Report Description coincides with the object of the <code>earl:subject</code> in <ahref="#test-assertion-description">Test Assertion Description</a>.</p>
766
766
767
-
<p>To help distinguish project releases in test reports, it is encouraged to use versioned URIs for projects.</p>
767
+
<pabout="" id="project-versioned-uri" rel="spec:advisement" resource="#project-versioned-uri"><spanproperty="spec:statement">To help distinguish project releases in test reports, it is <spanrel="spec:advisementLevel" resource="spec:Encouraged">encouraged</span> to use versioned URIs for projects.</span></p>
768
768
769
-
<p>While some information about the project can be accompanied with the test report, it is encouraged that projects are <ahref="https://www.w3.org/2001/tag/doc/selfDescribingDocuments" rel="cito:citesAsInformation">self-describing documents</a>.</p>
769
+
<pabout="" id="project-self-describing-document" rel="spec:advisement" resource="#project-self-describing-document"><spanproperty="spec:statement">While some information about the project can be accompanied with the test report, it is <spanrel="spec:advisementLevel" resource="spec:Encouraged">encouraged</span> that projects are <ahref="https://www.w3.org/2001/tag/doc/selfDescribingDocuments" rel="cito:citesAsInformation">self-describing documents</a>.</span></p>
770
770
</div>
771
771
</div>
772
772
@@ -781,9 +781,9 @@ <h4 property="schema:name"><span>Note</span>: Test Report Description: Descripti
<p>To help distinguish test criteria, it is encouraged to use versioned URIs for criteria.</p>
784
+
<pabout="" id="test-criteria-versioned-uri" rel="spec:advisement" resource="#test-criteria-versioned-uri"><spanproperty="spec:statement">To help distinguish test criteria, it is <spanrel="spec:advisementLevel" resource="spec:Encouraged">encouraged</span> to use versioned URIs for criteria.</span></p>
785
785
786
-
<p>To convey association between a test criterion and its reviews, it is encouraged to use the <ahref="https://www.w3.org/TR/annotation-vocab/">Web Annotation Vocabulary</a> with the <code>oa:assessing</code> motivation.</p>
786
+
<pabout="" id="test-criterion-review-assessing-motivation" rel="spec:advisement" resource="#test-criterion-review-assessing-motivation"><spanproperty="spec:statement">To convey association between a test criterion and its reviews, it is <spanrel="spec:advisementLevel" resource="spec:Encouraged">encouraged</span> to use the <ahref="https://www.w3.org/TR/annotation-vocab/">Web Annotation Vocabulary</a> with the <code>oa:assessing</code> motivation.</span></p>
787
787
</div>
788
788
</div>
789
789
@@ -809,7 +809,7 @@ <h3 property="schema:name">Test Case Description</h3>
809
809
810
810
<pclass="issue"><code>spec:testScript</code> may need to be <code>rdfs:subPropertyOf</code><code>td:input</code> or <code>td:informationResourceInput</code>, or use those properties instead.</p>
811
811
812
-
<pclass="note">When referencing a requirement with <code>spec:requirementReference</code>, it is strongly encouraged to use versioned URLs of technical reports where available with preference to URLs covered by a persistence policy.</p>
812
+
<pclass="note"about="" id="test-report-requirement-versioned-uri" rel="spec:advisement" resource="#test-report-requirement-versioned-uri"><spanproperty="spec:statement">When referencing a requirement with <code>spec:requirementReference</code>, it is <spanrel="spec:advisementLevel" resource="spec:StronglyEncouraged">strongly encouraged</span> to use versioned URLs of technical reports where available with preference to URLs covered by a persistence policy.</span></p>
<p>Test assertions MUST use the <cite><ahref="https://www.w3.org/TR/EARL10-Schema/" rel="cito:citesAsAuthority">Evaluation and Report Language 1.0 Schema</a></cite> [<cite><aclass="bibref" href="#bib-earl10-Schema">EARL10-Schema</a></cite>].</p>
837
837
838
-
<p>Test Suite implementers are encouraged to follow the <cite><ahref="https://www.w3.org/TR/EARL10-Guide/" rel="cito:citesAsPotentialSolution">Developer Guide for Evaluation and Report Language 1.0</a></cite> [<cite><aclass="bibref" href="#bib-earl10-guide">EARL10-Guide</a></cite>].</p>
838
+
<pabout="" id="test-suite-implementation-earl" rel="spec:advisement" resource="#test-suite-implementation-earl"><spanproperty="spec:statement">Test Suite implementers are <spanrel="spec:advisementLevel" resource="spec:Encouraged">encouraged</span> to follow the <cite><ahref="https://www.w3.org/TR/EARL10-Guide/" rel="cito:citesAsPotentialSolution">Developer Guide for Evaluation and Report Language 1.0</a></cite> [<cite><aclass="bibref" href="#bib-earl10-guide">EARL10-Guide</a></cite>].</span></p>
0 commit comments