Skip to content

Commit

Permalink
Merge branch 'gh-pages' into dcat-AdjustingConfigForFPWD
Browse files Browse the repository at this point in the history
  • Loading branch information
andrea-perego committed Nov 17, 2020
2 parents bc872ae + f9f4c80 commit 89e2a6e
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions dcat/index.html
Expand Up @@ -3333,13 +3333,16 @@ <h2>Version information</h2>
<p>Two typical examples are (a) a textual description of the changes between the current and the previous version of a resource, and (b) whether the new version of the resource is backward compatible or not with the previous version (this is particularly relevant when the resource is used by given applications, so it is fundamental to know if the new version can be also used with them).</p>

<div class="issue" data-number="1258"></div>

<!--
<aside class="issue">
<a href="https://www.w3.org/TR/2012/REC-owl2-syntax-20121211/#Ontology_Annotations">Section 3.5 in OWL 2 specification</a> suggests <code>owl:backwardCompatibleWith</code> / <code>owl:incompatibleWith</code> properties on entities other than ontologies is discouraged. Should we consider any other valuable alternatives? (see <a href="https://github.com/w3c/dxwg/issues/1258">issue 1258</a>)
</aside>
-->
<p>For these purposes, it is recommended to use, respectively, property <a data-cite="VOCAB-ADMS#adms-versionnotes"><code>adms:versionNotes</code></a> (for a textual description of the changes) and properties <code>owl:backwardCompatibleWith</code> / <code>owl:incompatibleWith</code> (for specifying (in)compatibility).</p>

<div class="issue" data-number="1280"></div>

For indicating the version release date and identifier, the use of, respectively, <code>dct:issued</code> and <code>owl:versionInfo</code> is recommended.
</section>

Expand Down

0 comments on commit 89e2a6e

Please sign in to comment.