Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

embed issue links in DCAT draft #129

Merged
merged 6 commits into from
Feb 21, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
120 changes: 116 additions & 4 deletions dcat/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -303,11 +303,20 @@ <h2>

<p>The (revised) DCAT vocabulary is available in RDF <a href="https://raw.githubusercontent.com/w3c/dxwg/gh-pages/dcat/rdf/dcat.ttl">here</a>.</p>

<p class="note">From DCAT 1.0</p>
<p class="note">From DCAT 1.0 except where indicated.</p>

<p>
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="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>

<section id="class-catalog">
<h3>Class: Catalog</h3>
<p>The following properties are recommended for use on this class:
Expand All @@ -325,6 +334,11 @@ <h3>Class: Catalog</h3>
<a href="#Property:catalog_title">title</a>,
<a href="#Property:catalog_update_date">update date</a>
</p>

<p class="issue" data-number="105">
The use of guarded constraints (existence, cardinality, range-type) to control the usage of the recommended properties in the context of a class is being considered as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/ns/dcat#Catalog">dcat:Catalog</a></th></tr></thead>
<tbody>
Expand Down Expand Up @@ -441,6 +455,11 @@ <h4>Property: spatial/geographic </h4>

<section id="Property:catalog_themes">
<h4>Property: themes</h4>

<p class="issue" data-number="119">
The axiomatization of dcat:themeTaxonomy is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#themeTaxonomy">dcat:themeTaxonomy</a></th></tr></thead>
<tbody>
Expand Down Expand Up @@ -483,6 +502,11 @@ <h4>Property: rights</h4>

<section id="Property:catalog_dataset">
<h4>Property: dataset</h4>

<p class="issue" data-number="117">
The axiomatization of dcat:dataset is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#dataset">dcat:dataset</a></th></tr></thead>
<tbody>
Expand All @@ -496,6 +520,11 @@ <h4>Property: dataset</h4>

<section id="Property:catalog_catalog_record">
<h4>Property: catalog record</h4>

<p class="issue" data-number="118">
The axiomatization of dcat:record is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#record">dcat:record</a></th></tr></thead>
<tbody>
Expand All @@ -517,6 +546,28 @@ <h3>Class: Catalog record</h3>
<a href="#Property:record_update_date">update date</a>
</p>

<p class="issue" data-number="128">
A number of requirements identify the need to provide better support for Dataset and Record provenance - see
<a href="https://github.com/w3c/dxwg/issues/77">Issue #78</a>,
<a href="https://github.com/w3c/dxwg/issues/77">Issue #77</a>,
<a href="https://github.com/w3c/dxwg/issues/76">Issue #76</a>,
<a href="https://github.com/w3c/dxwg/issues/71">Issue #71</a>,
<a href="https://github.com/w3c/dxwg/issues/66">Issue #66</a>,
<a href="https://github.com/w3c/dxwg/issues/66">Issue #63</a>,
<a href="https://github.com/w3c/dxwg/issues/57">Issue #57</a>,
.
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>,
.
</p>

<p class="issue" data-number="105">
The use of guarded constraints (existence, cardinality, range-type) to control the usage of the recommended properties in the context of a class is being considered as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/ns/dcat#CatalogRecord">dcat:CatalogRecord</a></th></tr></thead>
<tbody>
Expand Down Expand Up @@ -626,22 +677,32 @@ <h3>Class: Dataset</h3>
<a href="#Property:dataset_update_date">update date</a>,
</p>

<p class="issue" data-number="77">
A number of requirements identify the need to provide better support for Dataset provenance - see
<p class="issue" data-number="128">
A number of requirements identify the need to provide better support for Dataset and Record provenance - see
<a href="https://github.com/w3c/dxwg/issues/77">Issue #78</a>,
<a href="https://github.com/w3c/dxwg/issues/77">Issue #77</a>,
<a href="https://github.com/w3c/dxwg/issues/76">Issue #76</a>,
<a href="https://github.com/w3c/dxwg/issues/71">Issue #71</a>,
<a href="https://github.com/w3c/dxwg/issues/66">Issue #66</a>,
<a href="https://github.com/w3c/dxwg/issues/66">Issue #63</a>,
<a href="https://github.com/w3c/dxwg/issues/57">Issue #57</a>,
.
It has been suggested that many of the requirements can be satisfied by using the [[prov-o]] ontology,
in particular by making dcat:Dataset a sub-class of <a href="http://www.w3.org/ns/prov#Entity">prov:Entity</a>.
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>,
.
</p>

<p class="issue" data-number="104">
The option of allowing license and rights information to be associated with a dcat:Dataset, as well as dcat:Distribution, is being considered as part of the revision of DCAT.
</p>

<p class="issue" data-number="105">
The use of guarded constraints (existence, cardinality, range-type) to control the usage of the recommended properties in the context of a class is being considered as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/ns/dcat#Dataset">dcat:Dataset</a></th></tr></thead>
<tbody>
Expand Down Expand Up @@ -757,6 +818,11 @@ <h4>Property: frequency</h4>

<section id="Property:dataset_identifier">
<h4>Property: identifier</h4>

<p class="issue" data-number="53">
The desirability of dereferenceable identifiers has been raised as an item for consideration in the revision of DCAT. dct:identifier has limited expressivity for this. It has been suggested that ADMS identifier, or a property from another ontology might be recruited to help DCAT in this area.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/identifier">dct:identifier</a></th></tr></thead>
<tbody>
Expand Down Expand Up @@ -793,6 +859,10 @@ <h4>Property: temporal coverage</h4>
<section id="Property:dataset_theme">
<h4>Property: theme/category</h4>

<p class="issue" data-number="123">
The axiomatization of dcat:theme is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#theme">dcat:theme</a></th></tr></thead>
<tbody>
Expand Down Expand Up @@ -844,6 +914,10 @@ <h4>Property: type/genre</h4>
<section id="Property:dataset_keyword">
<h4>Property: keyword/tag</h4>

<p class="issue" data-number="121">
The axiomatization of dcat:keyword is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#keyword">dcat:keyword</a></th></tr></thead>
<tbody>
Expand All @@ -863,6 +937,10 @@ <h4>Property: contact point</h4>
see <a href="https://github.com/w3c/dxwg/issues/95">Issue #95</a>.
</p>

<p class="issue" data-number="109">
The axiomatization of dcat:contactPoint is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#contactPoint">dcat:contactPoint</a></th></tr></thead>
<tbody>
Expand All @@ -874,6 +952,11 @@ <h4>Property: contact point</h4>

<section id="Property:dataset_distribution">
<h4>Property: dataset distribution</h4>

<p class="issue" data-number="120">
The axiomatization of dcat:distribution is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#distribution">dcat:distribution</a></th></tr></thead>
<tbody>
Expand All @@ -886,6 +969,11 @@ <h4>Property: dataset distribution</h4>

<section id="Property:dataset_landingpage">
<h4>Property: landing page</h4>

<p class="issue" data-number="122">
The axiomatization of dcat:landingPage is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#landingPage">dcat:landingPage</a></th></tr></thead>
<tbody>
Expand Down Expand Up @@ -918,6 +1006,10 @@ <h3>Class: Distribution</h3>
<a href="#Property:distribution_update_date">update date</a>
</p>

<p class="issue" data-number="105">
The use of guarded constraints (existence, cardinality, range-type) to control the usage of the recommended properties in the context of a class is being considered as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/dcat#Distribution">dcat:Distribution</a></th></tr></thead>
<tbody>
Expand Down Expand Up @@ -1012,6 +1104,11 @@ <h4>Property: rights</h4>

<section id="Property:distribution_accessurl">
<h4>Property: access URL</h4>

<p class="issue" data-number="124">
The axiomatization of dcat:accessURL is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#accessURL">dcat:accessURL</a></th></tr></thead>
<tbody>
Expand All @@ -1037,6 +1134,11 @@ <h4>Property: access URL</h4>

<section id="Property:distribution_downloadurl">
<h4>Property: download URL</h4>

<p class="issue" data-number="126">
The axiomatization of dcat:downloadURL is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#downloadURL">dcat:downloadURL</a></th></tr></thead>
<tbody>
Expand All @@ -1053,6 +1155,11 @@ <h4>Property: download URL</h4>

<section id="Property:distribution_size">
<h4>Property: byteSize</h4>

<p class="issue" data-number="125">
The axiomatization of dcat:byteSize is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#size">dcat:byteSize</a></th></tr></thead>
<tbody>
Expand All @@ -1066,6 +1173,11 @@ <h4>Property: byteSize</h4>

<section id="Property:distribution_media_type">
<h4>Property: media type</h4>

<p class="issue" data-number="127">
The axiomatization of dcat:mediaType is being re-evaluated as part of the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#mediaType">dcat:mediaType</a></th></tr></thead>
<tbody>
Expand Down