removed a closed Issue

profilesont/index.html

@@ -217,27 +217,20 @@ <h2>Conceptual Model</h2>
     </a>
     <figcaption>OWL [[OWL2-OVERVIEW]] overview diagram of this vocabulary</figcaption>
   </figure>
-    <p>
-      This vocabulary is for describing relationships between standards/specifications, profiles of them and supporting artifacts such as validating resources.
-    </p>
-    <p>
-      The model takes the <code><a href="http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-Standard">dct:Standard</a></code> Class as a starting point and defines a specialization, a <code>Profile</code>, which is a <code>dct:Standard</code> that <em>profiles</em> a <code>dct:Standard</code> or another <code>Profile</code>. <code>Standards</code>s or <code>Profile</code>s can have <code>Resource Descriptor</code>s associated with
-    them that define rules for implementation, provide guidance on how to implement, or play some other role. <code>Resource Descriptor</code>s must indicate the role they
-    play (to guide, to validate etc.), the formalism they adhere to (<code><a href="http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-format">dct:format</a></code>)
-    and any <code>dct:Standard</code> that they themselves conform to (<code><a href="http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-conformsTo">dct:conformsTo</a></code>).
-  </p>
   <p>
-    A extensible vocabulary of <code>Resource Role</code>s is provided alongside this vocabulary.
+    This vocabulary is for describing relationships between standards/specifications, profiles of them and supporting artifacts such as validating resources.
   </p>
-  <ul>
-    <li><a href="https://w3c.github.io/dxwg/profilesont/resource_roles.html">Resource Roles Vocabulary</a></li>
-  </ul>
+  <p>
+    The model takes the <code><a href="http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-Standard">dct:Standard</a></code> Class as a starting point and defines a specialization, a <code>Profile</code>, which is a <code>dct:Standard</code> that <em>profiles</em> a <code>dct:Standard</code> or another <code>Profile</code>. <code>Standards</code>s or <code>Profile</code>s can have <code>Resource Descriptor</code>s associated with
+  them that define rules for implementation, provide guidance on how to implement, or play some other role. <code>Resource Descriptor</code>s must indicate the role they
+  play (to guide, to validate etc.), the formalism they adhere to (<code><a href="http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-format">dct:format</a></code>)
+  and any <code>dct:Standard</code> that they themselves conform to (<code><a href="http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-conformsTo">dct:conformsTo</a></code>).
+</p>
   <p>
     <em>The remainder of this section is informative.</em>
   </p>
   <section id="initial-example">
     <h3>Initial Example</h3>
-    <div class="issue" data-number="695"></div>
     <p>
       The example below illustrates the use of most parts of PROF and indicates how non-PROF profile metadata is stored alongside PROF metadata.
     </p>