Merge pull request #440 from w3c/dcat-issue434-simon

Improve documentation of dcat:Distribution

dcat/index.html

@@ -1793,7 +1793,7 @@ <h3>Class: Distribution</h3>
 		<b>Applications consuming DCAT should be aware that catalogues designed using DCAT-2014 might use dcat:Distribution to represent both services and representations.</b>
 	</p>
 	<p>
-		Under the revised scope, instances of type dcat:Distribution <em title="SHOULD" class="rfc2119">SHOULD</em> be limited to <i>representations</i> of datasets which might be transported as files, and <em title="SHOULD NOT" class="rfc2119">SHOULD NOT</em> be used for data <i>services</i> such as APIs or feeds. Data services including APIs and feeds <em title="SHOULD" class="rfc2119">SHOULD</em> be described using instances of type <a href="#Class:Data_Service">dcat:DataService</a> or <a href="#Class:Data_Distribution_Service">dcat:DataDistributionService</a>.
+		Under the revised scope, instances of type dcat:Distribution <em title="SHOULD" class="rfc2119">SHOULD</em> be limited to <i>representations</i> of datasets which might be transported as files, and <em title="SHOULD NOT" class="rfc2119">SHOULD NOT</em> be used for data <i>services</i> such as APIs or feeds. Data services including APIs and feeds <em title="SHOULD" class="rfc2119">SHOULD</em> be described using instances of type <a href="#Class:Data_Service">dcat:DataService</a> whose sub-class <a href="#Class:Data_Distribution_Service">dcat:DataDistributionService</a> <em title="MAY" class="rfc2119">MAY</em> serve <a href="#Class:Data_Distribution">dcat:Distributions</a>. 
 	</p>
 	<p>
 		Links between a dcat:Distribution and services or web addresses where it can be accessed are expressed using <a href="#Property:distribution_accessurl">dcat:accessURL</a>, <a href="#Property:distribution_accessservice">dcat:accessService</a>, <a href="#Property:distribution_downloadurl">dcat:downloadURL</a>, as shown in <a href="#fig1">Figure 1</a> and described in the definitions below.