removed closed Issues, added plenary-approved reqs, as per ACTION-206

profiles/index.html

@@ -161,10 +161,6 @@ <h2>Related work and examples of existing profiles</h2>
     <p>
       <em>profiling</em> is an activity that has been undertaken by many communities with a range of formalisms.
     </p>
-    <div class="issue" data-number="366">
-      (Antoine:) This section was recommended here in https://github.com/w3c/dxwg/issues/242#issuecomment-408916364. I now have doubts about the it, as it breaks the flow between two crucial (normative) sections on DXWG recommendations. As an alternative, I suggest to try to fit this in (a subsection of) the introduction if it can be short enough. Otherwise we could put it as appendix and refer to it from the introduction.
-    </div>
-    <div class="issue" data-number="419"></div>
     <div class="note">
       (Karen:) I had thought of this as showing examples of TYPES of profiles. There are profiles like DCAT that take place within a community, make primary use of a base metadata schema, but add or remove based on local need. There are profiles like ODRL that have a very formal meaning (legal license) and are in essence cumulative, with the base standard elements assumed and specific rules for over-riding. There are profiles that use only the namespace of the base profile, but are defined subsets (BIBFRA.ME, but any other example of this would be fine - that's the one I know). And then we could perhaps find a profile that has no strong base profile (ADMS perhaps?) but combines elements as needed from a variety of sources and is independent of any existing vocabulary. The idea would be to show a range of profile motivations, designs, and community involvement.
     </div>
@@ -310,12 +306,8 @@ <h2>Definitions</h2>
           <p><em>Source: deliberations of the DXWG. See <a href="https://www.w3.org/2017/dxwg/wiki/ProfileContext">ProfileContext wiki page</a>.</em></p>
         </dd>
       </dl>
-      <div class="issue" data-number="372">(Nick:)</div>
-      <div class="issue" data-number="373">
-        (Nick:) Extend the second paragraph of 'profile' to indicate data use, not just metadata
-      </div>
+      <div class="issue" data-number="448"></div>
       <div class="issue" data-number="418"></div>
-      <div class="issue" data-number="420"></div>
     </section>
 
     <section id="relatedworkdefns" class="appendix">
@@ -342,22 +334,22 @@ <h2>Requirements</h2>
       <p>
         Here listed are the individual requirements addressed by the Working Group in the formulation of this document.
       </p>
+      <div class="issue" data-number="73"></div>
+      <div class="issue" data-number="238"></div>
       <div class="issue" data-number="255"></div>
+      <div class="issue" data-number="268"></div>
       <div class="issue" data-number="275"></div>
       <div class="issue" data-number="276"></div>
       <div class="issue" data-number="277"></div>
       <div class="issue" data-number="278"></div>
+      <div class="issue" data-number="279"></div>
       <div class="issue" data-number="280"></div>
       <div class="issue" data-number="281"></div>
       <div class="issue" data-number="282"></div>
       <div class="issue" data-number="283"></div>
     </section>
   </section>
 
-  <div class="issue" data-number="375">
-    (Nick:) Determine references for a 'Normative references' subsection
-  </div>
-
   <script class="remove" src="config.js"></script>
   <script class="remove" src="https://www.w3.org/Tools/respec/respec-w3c-common"></script>
 </body>