Deployed a3aae55 with MkDocs version: 1.5.3

Author: Crashedmind

cwe/cwe_views/index.html

@@ -1209,6 +1209,15 @@
     <nav class="md-nav" aria-label="Research View (View-1000)">
       <ul class="md-nav__list">
 
+          <li class="md-nav__item">
+  <a href="#repeatability" class="md-nav__link">
+    <span class="md-ellipsis">
+      Repeatability
+    </span>
+  </a>
+  
+</li>
+        
           <li class="md-nav__item">
   <a href="#visualization" class="md-nav__link">
     <span class="md-ellipsis">
@@ -1850,6 +1859,15 @@
     <nav class="md-nav" aria-label="Research View (View-1000)">
       <ul class="md-nav__list">
 
+          <li class="md-nav__item">
+  <a href="#repeatability" class="md-nav__link">
+    <span class="md-ellipsis">
+      Repeatability
+    </span>
+  </a>
+  
+</li>
+        
           <li class="md-nav__item">
   <a href="#visualization" class="md-nav__link">
     <span class="md-ellipsis">
@@ -1954,10 +1972,24 @@ <h2 id="example-using-cwe-798-use-of-hard-coded-credential">Example using <a hre
 </ol>
 <h2 id="research-view-view-1000_2">Research View (<a href="https://cwe.mitre.org/data/definitions/1000.html">View-1000</a>)<a class="headerlink" href="#research-view-view-1000_2" title="Permanent link">&para;</a></h2>
 <p>The Research Concepts view (<abbr title="CWE Common Weakness Enumeration">CWE</abbr>-1000) organizes all weakness CWEs by the method through which an exploitation can occur.</p>
-<p>Research View (<a href="https://cwe.mitre.org/data/definitions/1000.html">View-1000</a>) contains all CWEs and uses a deep hierarchical organization, with more levels of abstraction than other classification schemes.</p>
+<p>Research View (<a href="https://cwe.mitre.org/data/definitions/1000.html">View-1000</a>) contains all CWEs and uses a deep hierarchical organization, with <strong>more levels of abstraction than other classification schemes.</strong></p>
 <ul>
 <li>While Software Assurance Trends View (<a href="https://cwe.mitre.org/data/definitions/1400.html">View-1400</a>) contains all CWEs, it is only 2 levels deep.</li>
 </ul>
+<p>The Research view was built to maximize mutual exclusivity, repeatability and clarity — it’s the canonical, theory-driven taxonomy.</p>
+<div class="admonition quote">
+<p class="admonition-title">Quote</p>
+<p>The Research view is mainly organized according to abstractions of software behaviors and the resources that are manipulated by those behaviors, which aligns with MITRE's research into vulnerability theory. In addition to classification, the Research view explicitly models the inter-dependencies between weaknesses, which have not been a formal part of past classification efforts. The main examples are chains and composites.</p>
+<p>The view uses multiple deep hierarchies as its organization structure, with more levels of abstraction than other classification schemes. </p>
+<p><a href="https://cwe.mitre.org/documents/views/view-evolution.html">https://cwe.mitre.org/documents/views/view-evolution.html</a></p>
+</div>
+<h3 id="repeatability">Repeatability<a class="headerlink" href="#repeatability" title="Permanent link">&para;</a></h3>
+<div class="admonition quote">
+<p class="admonition-title">Quote</p>
+<p>the Research view seeks to achieve repeatability, although strong technical knowledge and an understanding of chains is required. Repeatability has been informally verified in many situations in which two separate <abbr title="CWE Common Weakness Enumeration">CWE</abbr> team members classified issues the same way. However, there are limits - ambiguous classification can still happen because of perspective issues or incomplete parts of the hierarchy.</p>
+<p>In the case of the Development view, it is hoped that the large number of navigation categories will make it easier for people to reach the desired weakness ID. However, with so many categories, there is a risk of incomplete or incorrect mappings if one user follows one path of the tree, and another mapper follows a different path.</p>
+<p><a href="https://cwe.mitre.org/documents/views/view-comparison.html#Repeatable">https://cwe.mitre.org/documents/views/view-comparison.html#Repeatable</a></p>
+</div>
 <h3 id="visualization">Visualization<a class="headerlink" href="#visualization" title="Permanent link">&para;</a></h3>
 <p>MITRE <abbr title="CWE Common Weakness Enumeration">CWE</abbr> provides visualizations on <a href="https://cwe.mitre.org/data/pdfs.html">https://cwe.mitre.org/data/pdfs.html</a>.</p>
 <ul>

print_page/index.html

@@ -5075,10 +5075,24 @@ <h2 id="cwe-cwe_views-example-using-cwe-798-use-of-hard-coded-credential">Exampl
 </ol>
 <h2 id="cwe-cwe_views-research-view-view-1000_2">Research View (<a href="https://cwe.mitre.org/data/definitions/1000.html">View-1000</a>)<a class="headerlink" href="#cwe-cwe_views-research-view-view-1000_2" title="Permanent link">&para;</a></h2>
 <p>The Research Concepts view (<abbr title="CWE Common Weakness Enumeration">CWE</abbr>-1000) organizes all weakness CWEs by the method through which an exploitation can occur.</p>
-<p>Research View (<a href="https://cwe.mitre.org/data/definitions/1000.html">View-1000</a>) contains all CWEs and uses a deep hierarchical organization, with more levels of abstraction than other classification schemes.</p>
+<p>Research View (<a href="https://cwe.mitre.org/data/definitions/1000.html">View-1000</a>) contains all CWEs and uses a deep hierarchical organization, with <strong>more levels of abstraction than other classification schemes.</strong></p>
 <ul>
 <li>While Software Assurance Trends View (<a href="https://cwe.mitre.org/data/definitions/1400.html">View-1400</a>) contains all CWEs, it is only 2 levels deep.</li>
 </ul>
+<p>The Research view was built to maximize mutual exclusivity, repeatability and clarity — it’s the canonical, theory-driven taxonomy.</p>
+<div class="admonition quote">
+<p class="admonition-title">Quote</p>
+<p>The Research view is mainly organized according to abstractions of software behaviors and the resources that are manipulated by those behaviors, which aligns with MITRE's research into vulnerability theory. In addition to classification, the Research view explicitly models the inter-dependencies between weaknesses, which have not been a formal part of past classification efforts. The main examples are chains and composites.</p>
+<p>The view uses multiple deep hierarchies as its organization structure, with more levels of abstraction than other classification schemes. </p>
+<p><a href="https://cwe.mitre.org/documents/views/view-evolution.html">https://cwe.mitre.org/documents/views/view-evolution.html</a></p>
+</div>
+<h3 id="cwe-cwe_views-repeatability">Repeatability<a class="headerlink" href="#cwe-cwe_views-repeatability" title="Permanent link">&para;</a></h3>
+<div class="admonition quote">
+<p class="admonition-title">Quote</p>
+<p>the Research view seeks to achieve repeatability, although strong technical knowledge and an understanding of chains is required. Repeatability has been informally verified in many situations in which two separate <abbr title="CWE Common Weakness Enumeration">CWE</abbr> team members classified issues the same way. However, there are limits - ambiguous classification can still happen because of perspective issues or incomplete parts of the hierarchy.</p>
+<p>In the case of the Development view, it is hoped that the large number of navigation categories will make it easier for people to reach the desired weakness ID. However, with so many categories, there is a risk of incomplete or incorrect mappings if one user follows one path of the tree, and another mapper follows a different path.</p>
+<p><a href="https://cwe.mitre.org/documents/views/view-comparison.html#Repeatable">https://cwe.mitre.org/documents/views/view-comparison.html#Repeatable</a></p>
+</div>
 <h3 id="cwe-cwe_views-visualization">Visualization<a class="headerlink" href="#cwe-cwe_views-visualization" title="Permanent link">&para;</a></h3>
 <p>MITRE <abbr title="CWE Common Weakness Enumeration">CWE</abbr> provides visualizations on <a href="https://cwe.mitre.org/data/pdfs.html">https://cwe.mitre.org/data/pdfs.html</a>.</p>
 <ul>