Merge branch 'gh-pages' into dcat-sdo-annexe

dcat/index.html

@@ -1745,10 +1745,6 @@ <h3>Class: Distribution</h3>
             </p>
         </div>
 
-        <p class="issue" data-number="411">
-            The intention of the phrase "informationally equivalent" needs to be clarified, in particular as different serializations may have different expressivity.
-        </p>
-
         <section id="Property:distribution_title">
             <h4>Property: title</h4>
             <table class="definition">
@@ -2536,10 +2532,6 @@ <h2>Quality information</h2>
         </p>
     </aside>
 
-    <p class="issue" data-number="252">
-        We might want to include examples of quality documentation related to services.
-    </p>
-
     <section id="quality-example1">
         <h2>Providing quality information</h2>
 
@@ -3109,9 +3101,9 @@ <h2>DCAT Profiles</h2>
         an application profile extends one of the DCAT extensions themselves.
     </p>
 
-    <p>
-        Some of the DCAT application profiles are:
-        <ul>
+	<p>Some of the DCAT application profiles are:</p>
+
+	<ul>
             <li>DCAT-AP [[?DCAT-AP]]: the DCAT application profile for data portals in Europe</li>
             <li>GeoDCAT-AP [[?GeoDCAT-AP]]: the geo-spatial extension to DCAT-AP</li>
             <li>StatDCAT-AP [[?StatDCAT-AP]]: Statistical extension to DCAT-AP</li>
@@ -3122,15 +3114,17 @@ <h2>DCAT Profiles</h2>
             <li>DCAT-BE [[?DCAT-BE]]: Belgian extension to DCAT-AP</li>
             <li>DCAT-AP-SE [[?DCAT-AP-SE]]: Swedish extension to DCAT-AP</li>
         </ul>
-    </p>
 
 </section>
 
 <section id="security_and_privacy">
     <h2>Security and Privacy</h2>
-    <p class="issue" data-number="691">
-        This section will describe security and privacy considerations relevant to the DCAT revision.
-    </p>
+    <p>
+    The DCAT vocabulary supports the attribution of data and metadata to various participants such as resource <a href="#Property:resource_creator">creators</a>, <a href="#Property:resource_publisher">publishers</a> and other parties or agents via <a href="#qualified-forms">qualified relations</a>, 
+	    and as such defines terms that may be related to personal information.  In addition, it also supports the association of <a href="#Property:resource_rights">rights</a> and <a href="#Property:resource_license">licenses</a> with cataloged Resources and Distributions. 
+	    These rights and licences could potentially include or reference sensitive information such as user and asset identifiers as <a href="https://www.w3.org/TR/odrl-vocab/#privacy-consideration">described</a> in [[!ODRL-VOCAB]].   Implementations that produce, maintain, publish or 
+	    consume such vocabulary terms must take steps to ensure security and privacy considerations are addressed at the application level.
+    </p>  	
 </section>
 
 <section id="other-w3c-recommendations">

profiles/index.html

@@ -102,7 +102,7 @@ <h3>Definitions</h3>
     <p>
 			We recognise that the term 'profile' occurs in several domains, and that there are a range of definitions 
 			available from different communities. We have taken this variability into account but for the purpose of this document we 
-			are using the following definitions:
+			are using the following definition:
     <p>
       <dl>
         <dt><dfn>profile</dfn></dt>
@@ -119,14 +119,6 @@ <h3>Definitions</h3>
           </p>
           <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>
-        <dt><dfn>profiling</dfn></dt>
-        <dd>
-          <p>
-            The act of creating a profile  - an activity that has been undertaken by many communities with a range of formalisms.
-          </p>
-				</dd>
-      </dl>
       <div class="issue" data-number="448"></div>
     </section>
 
@@ -147,7 +139,7 @@ <h3>The motivation for profiles</h3>
       has identified typical use cases for profiles, such as:
     </p>
     <ul>
-      <li><a href="https://w3c.github.io/dxwg/ucr/#ID7">support associating fine-grained semantics for datasets and resources within a dataset</a></li>
+      <li><a href="https://w3c.github.io/dxwg/ucr/#ID7">associating fine-grained semantics for datasets and resources within a dataset</a></li>
       <li><a href="https://w3c.github.io/dxwg/ucr/#ID41">expression of vocabulary constraints</a>, and</li>
       <li><a href="https://w3c.github.io/dxwg/ucr/#ID46">support for input functions</a></li>
     </ul>
@@ -224,8 +216,11 @@ <h2>Diving into profiles</h2>
 
    <div class="note">
     <p>
-      The terminology in this section is still under discussion, e.g. <a href="https://github.com/w3c/dxwg/issues/747">here</a> or 
-      <a href="https://github.com/w3c/dxwg/issues/795">here</a>
+      The idea of the previous paragraph is to have a set of links to various sections, as done in the SKOS Primer at 
+	    https://www.w3.org/TR/skos-primer/#secsimple. 
+	    It needs to be re-written considering the final structure of the document. 
+	    Also, the terminology in this section is still under discussion, e.g. <a href="https://github.com/w3c/dxwg/issues/747">here</a> or 
+      <a href="https://github.com/w3c/dxwg/issues/795">here</a>.
     </p>
   </div>
 
@@ -666,6 +661,14 @@ <h2>Appendices</h2>
 
     <section id="appendix-definitions">
       <h3>Definitions</h3>
+       <dl>
+        <dt><dfn>profiling</dfn></dt>
+        <dd>
+          <p>
+            The act of creating a profile  - an activity that has been undertaken by many communities with a range of formalisms.
+          </p>
+	</dd>
+      </dl>
       <dl>
         <dt><dfn>formalism</dfn></dt>
         <dd>