Merge pull request #1279 from w3c/andrea-perego-dcat-add-links-to-new…

…-issues

Add links to newly created issues

dcat/index.html

@@ -3285,12 +3285,14 @@ <h2>Versioning</h2>
 <p>The following sections briefly discuss some key versioning aspects, and how they can be specified in DCAT records.</p>
 
 <aside class="ednote">
-<p>TBD: revising <a href="#qualified-relationship"></a> and <a href="#examples-dataset-provenance"></a> in order to include aspects more specific to versioning.</p>
+<p><a href="#qualified-relationship"></a> and <a href="#examples-dataset-provenance"></a> should be revised in order to include aspects more specific to versioning.</p>
 </aside>
 
 <section id="version-types">
 <h2>Version types</h2>
 
+<div class="issue" data-number="1277"></div>    
+
 <p>The creation of a version of a resource may have different motivations and purposes. For instance, the resource contains errors to be fixed, there may be new content to be added, or there may be a need to make the resource available in a different representation or language. Moreover, a new version may or may not replace the original resource.</p>
 <p>Depending on these aspects, it is possible to identify different version types, which may correspond to different relationships. By following the approach used in the library domain, version types can be classified as follows:</p>
 
@@ -3301,7 +3303,7 @@ <h2>Version types</h2>
 </ol>
 
 <aside class="ednote">
-<p>The second type is partially related to the notion of dataset series.</p>
+<p>The second type is partially related to the notion of dataset series (<a href="#dataset-series"></a>).</p>
 </aside>
 
 <p>These version types are not necessarily mutually exclusive, and they may overlap - especially, the first and the second ones. So, the relationship(s) used to link resource versions depends on which aspect is relevant for the specific use case. E.g.:</p>