Skip to content

Commit

Permalink
Merge pull request #143 from w3c/simon-dcat-doc-issues
Browse files Browse the repository at this point in the history
Align 'issue' links in document with progress on issues in GitHub
  • Loading branch information
davebrowning committed Mar 5, 2018
2 parents 22f4cff + 6fca539 commit 5d1b19a
Showing 1 changed file with 15 additions and 19 deletions.
34 changes: 15 additions & 19 deletions dcat/index.html
Expand Up @@ -20,7 +20,7 @@
<p>
This revised version of DCAT was developed by the <a href="https://www.w3.org/2017/dxwg/wiki/Main_Page">Dataset Exchange Working Group</a> in response to a new set of <a href="https://www.w3.org/TR/dcat-ucr/">Use Cases and Requirements</a> submitted on the basis of experience since the original version, and new applications not originally considered.
</p>
<p>DCAT incorporates terms from pre-existing vocabularies, where stable terms with appropriate meanings could be found, such as foaf:homepage and dct:title. Informal summary definitions of these terms are included here for convenience, while complete definitions are available in the provided authoritative references. Changes to definitions in those references, if any, will supersede the summaries given in this specification. Note that conformance to DCAT (Section 3) concerns usage of only the terms in the DCAT namespace itself, so possible changes to the external definitions will not affect conformance of DCAT implementations.</p>
<p>DCAT incorporates terms from pre-existing vocabularies, where stable terms with appropriate meanings could be found, such as foaf:homepage and dct:title. Informal summary definitions of the externally defined terms are included here for convenience, while authoritative definitions are available in the normative references. Changes to definitions in the references, if any, supersede the summaries given in this specification. Note that conformance to DCAT (Section 4) concerns usage of only the terms in the DCAT namespace itself, so possible changes to the external definitions will not affect conformance of DCAT implementations.</p>
<p>
Please see the Working Group's <a href="http://www.w3.org/2011/gld/wiki/DCAT_Implementations">implementation
report</a>.
Expand Down Expand Up @@ -309,20 +309,21 @@ <h2>
The definitions (including domain and range) of terms outside the dcat namespace are provided here only for convenience and must not be considered normative. The authoritative definitions of these terms are in the corresponding specifications: [[!dc11]], [[!foaf]], [[!rdf-schema]], [[!skos-reference]], [[!xmlschema11-2]] and [[!vcard-rdf]].
</p>

<p class="issue" data-number="65">
Guidance on the use DCAT in a weakly axiomatized environment, such as schema.org, has been identified as a requirement to be satisfied in the revision of DCAT.
</p>
<div class="issue" data-number="65">
<p>
Guidance on the use DCAT in a weakly axiomatized environment, such as schema.org, has been identified as a requirement to be satisfied in the revision of DCAT.
</p>
<p>
An <a href="https://github.com/w3c/dxwg/blob/gh-pages/dcat/rdf/schema.ttl">RDF graph containing an alignment of DCAT with schema.org</a> is available.
</p>
</div>

<p class="issue" data-number="110">
The axiomatization of DCAT v1 used global domain and range constraints for many of the properties defined in the DCAT namespace. This makes quite strong ontological commitments, some of which are now being reconsidered - see individual issues noted inline below.
</p>

<p class="issue" data-number="131">
Changes to the domain and range definitions of DCAT properties might be considered to be semantic changes to the vocabulary. The implications for such changes for backward compatibility must be considered, including the continued use of the same RDF namespace.
</p>

<p class="issue" data-number="134">
Modularization of the DCAT RDF representation into more than one file or graph is being considered as a way to facilitate users being able to access a version of DCAT with the level of axiomatization and alignments that they need. Also see <a href="https://github.com/w3c/dxwg/issues/94">Issue #94</a>.
<p class="note">
The DCAT RDF representation is modularized into several files or graphs to facilitate users being able to access a version of DCAT with the alignments that they need. This mechanism may also be used to capture different levels of axiomatization, though the status of such proposals has not been finalized. See <a href="https://github.com/w3c/dxwg/issues/134">Issue #134</a>.
</p>

<section id="class-catalog">
Expand Down Expand Up @@ -587,10 +588,7 @@ <h3>Class: Catalog record</h3>
.
It has been suggested that many of the requirements can be satisfied by using the [[prov-o]] ontology,
in particular by making dcat:Dataset and/or dcat:CatalogRecord a sub-class of <a href="http://www.w3.org/ns/prov#Entity">prov:Entity</a>.
However, the best way of introducing PROV-O capabilities into DCAT is not clear - see discussion at
<a href="https://github.com/w3c/dxwg/issues/77">Issue #77</a>,
<a href="https://github.com/w3c/dxwg/pull/94">Pull #94</a>,
.
A preliminary <a href="https://github.com/w3c/dxwg/blob/gh-pages/dcat/rdf/prov.ttl">alignment of DCAT with PROV-O is available</a>.
</p>

<table class="definition">
Expand Down Expand Up @@ -739,7 +737,8 @@ <h3>Class: Dataset</h3>
</p>

<p class="issue" data-number="76">
The need provide a more comprehensive method for describing dataset provenance has been identified as a requirement to be satisfied in the revision of DCAT.
The need provide a more comprehensive method for describing dataset provenance has been identified as a requirement to be satisfied in the revision of DCAT. A preliminary <a href="https://github.com/w3c/dxwg/blob/gh-pages/dcat/rdf/prov.ttl">alignment of DCAT with PROV-O is available</a>.

</p>

<p class="issue" data-number="77">
Expand Down Expand Up @@ -786,10 +785,7 @@ <h3>Class: Dataset</h3>
.
It has been suggested that many of the requirements can be satisfied by using the [[prov-o]] ontology,
in particular by making dcat:Dataset and/or dcat:CatalogRecord a sub-class of <a href="http://www.w3.org/ns/prov#Entity">prov:Entity</a>.
However, the best way of introducing PROV-O capabilities into DCAT is not clear - see discussion at
<a href="https://github.com/w3c/dxwg/issues/77">Issue #77</a>,
<a href="https://github.com/w3c/dxwg/pull/94">Pull #94</a>,
.
A preliminary <a href="https://github.com/w3c/dxwg/blob/gh-pages/dcat/rdf/prov.ttl">alignment of DCAT with PROV-O is available</a>.
</p>

<table class="definition">
Expand Down

0 comments on commit 5d1b19a

Please sign in to comment.