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

Move Linked Data Platform into Appendix #873

Merged
merged 9 commits into from Apr 18, 2019
39 changes: 21 additions & 18 deletions dcat/index.html
Expand Up @@ -2121,7 +2121,7 @@ <h3>Class: Data Service</h3>
<tr><td class="prop">Sub class of:</td><td><a href="#Class:Resource">dcat:Resource</a></td></tr>
<tr><td class="prop">Sub class of:</td><td><a href="http://purl.org/dc/dcmitype/Service">dctype:Service</a></td></tr>
<tr><td class="prop">Usage note:</td><td>If a <a href="#Class:Data_Service"><code>dcat:DataService</code></a> is bound to one or more specified Datasets, they are indicated by the dcat:servesDataset property.</td></tr>
<tr><td class="prop">Usage note:</td><td>The kind of service can be indicated using the <a href="http://purl.org/dc/terms/type">dct:type</a> property. Its value may be taken from a controlled vocabulary such as the <a href="https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/">INSPIRE spatial data service type vocabulary</a></td></tr>.
<tr><td class="prop">Usage note:</td><td>The kind of service can be indicated using the <a href="http://purl.org/dc/terms/type">dct:type</a> property. Its value may be taken from a controlled vocabulary such as the <a href="https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/">INSPIRE spatial data service type vocabulary</a>.</td></tr>
</tbody>
</table>

Expand Down Expand Up @@ -3153,38 +3153,39 @@ <h2>Security and Privacy</h2>
</p>
</section>

<section id="other-w3c-recommendations">
<section class="appendix" id="other-w3c-recommendations">

<h2>Relation to other W3C Recommendations</h2>

<p class="issue" data-number="254">
DCAT should be aligned with other recent Linked Data based Recommendations.
</p>

<section id="ldp">
<section id="ldp" class="informative">
<h3>Linked Data Platform (<abbr title="Linked Data Platform">LDP</abbr>)</h3>

<p>
DCAT provides a data model for representation of metadata about datasets in the form of Linked Data, but it does not specify how this metadata can be accessed or modified.
The DCAT compatible metadata can be viewed as collections of Catalog Records, Datasets and Data Services contained in a Catalog, and a collection of Distributions contained in a Dataset.
The Linked Data Platform [[!LDP]] specification deals with access to and modification of Linked Data Platform Containers (<abbr title="Linked Data Platform Containers">LDPCs</abbr>).
The Linked Data Platform [[?LDP]] specification deals with access to and modification of Linked Data Platform Containers (<abbr title="Linked Data Platform Containers">LDPCs</abbr>).
This section provides guidance on how to represent DCAT metadata as LDP Containers, which supports namely the implementation of <a href="https://solid.mit.edu/" title="Solid">Solid</a> based DCAT catalogs.
</p>

<p>
First, we will present an example of a LDPC for datasets in a catalog.
There is one catalog with one dataset.
The dataset is contained in the <code>&lt;/datasets/&gt;</code> LDP Direct Container.
To ensure the <abbr title="Linked Data Platform Container">LDPC</abbr> discovery, we connect it to the Catalog using the <code>dcat:datasets</code> predicate.
To ensure the <abbr title="Linked Data Platform Container">LDPC</abbr> discovery, we connect it to the Catalog using the <code>dcat-ld:datasets</code> predicate.
</p>
<pre id="ex-ldpc-dataset" class="example nohighlight turtle" aria-busy="false" aria-live="polite">
@prefix dcat: &lt;http://www.w3.org/ns/dcat#&gt; .
@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
@prefix dcat-ld: &lt;http://www.w3.org/ns/dcat-ld#&gt; .

@base &lt;https://example.org/resource/catalog&gt; .

&lt;&gt; a dcat:Catalog ;
dcat:datasets &lt;/datasets/&gt; ;
dcat-ld:datasets &lt;/datasets/&gt; ;
dcat:dataset &lt;/datasets/001&gt; .

&lt;/datasets/&gt; a ldp:Container, ldp:DirectContainer ;
Expand All @@ -3194,18 +3195,19 @@ <h3>Linked Data Platform (<abbr title="Linked Data Platform">LDP</abbr>)</h3>

&lt;/datasets/001&gt; a dcat:Dataset .</pre>

<p>In the second example, we add LDPCs <code>&lt;/records/&gt;</code> for Catalog Records and <code>&lt;/services/&gt;</code> for Data Services, discoverable using <code>dcat:records</code> and <code>dcat:services</code> predicates from the Catalog:
<p>In the second example, we add LDPCs <code>&lt;/records/&gt;</code> for Catalog Records and <code>&lt;/services/&gt;</code> for Data Services, discoverable using <code>dcat-ld:records</code> and <code>dcat-ld:services</code> predicates from the Catalog:
</p>
<pre id="ex-ldpc-record" class="example nohighlight turtle" aria-busy="false" aria-live="polite">
@prefix dcat: &lt;http://www.w3.org/ns/dcat#&gt; .
@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
@prefix dcat-ld: &lt;http://www.w3.org/ns/dcat-ld#&gt; .

@base &lt;https://example.org/resource/catalog&gt; .

&lt;&gt; a dcat:Catalog ;
dcat:records &lt;/records/&gt; ;
dcat:datasets &lt;/datasets/&gt; ;
dcat:services &lt;/services/&gt; ;
dcat-ld:records &lt;/records/&gt; ;
dcat-ld:datasets &lt;/datasets/&gt; ;
dcat-ld:services &lt;/services/&gt; ;
dcat:dataset &lt;/datasets/001&gt; .

&lt;/records/&gt; a ldp:Container, ldp:DirectContainer ;
Expand All @@ -3231,15 +3233,16 @@ <h3>Linked Data Platform (<abbr title="Linked Data Platform">LDP</abbr>)</h3>
&lt;/services/001&gt; a dcat:DataService .</pre>

<p>Each dataset has its own LDPC for its distributions.
In the third example, we show the LDPC <code>&lt;/datasets/001/distributions/&gt;</code> for distributions of a single dataset, <code>&lt;/datasets/001&gt;</code>, discoverable through the <code>dcat:distributions</code> predicate.</p>
In the third example, we show the LDPC <code>&lt;/datasets/001/distributions/&gt;</code> for distributions of a single dataset, <code>&lt;/datasets/001&gt;</code>, discoverable through the <code>dcat-ld:distributions</code> predicate.</p>
<pre id="ex-ldpc-distribution" class="example nohighlight turtle" aria-busy="false" aria-live="polite">
@prefix dcat: &lt;http://www.w3.org/ns/dcat#&gt; .
@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
@prefix dcat-ld: &lt;http://www.w3.org/ns/dcat-ld#&gt; .

@base &lt;https://example.org/resource/catalog&gt; .

&lt;/datasets/001&gt; a dcat:Dataset ;
dcat:distributions &lt;/datasets/001/distributions/&gt; ;
dcat-ld:distributions &lt;/datasets/001/distributions/&gt; ;
dcat:distribution &lt;/datasets/001/distributions/001&gt; .

&lt;/datasets/001/distributions/&gt; a ldp:Container, ldp:DirectContainer ;
Expand All @@ -3260,7 +3263,7 @@ <h3>Linked Data Platform (<abbr title="Linked Data Platform">LDP</abbr>)</h3>
<h4>Property: datasets</h4>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#datasets">dcat:datasets</a></th></tr></thead>
<thead><tr><th>RDF Property:</th><th><code>dcat-ld:datasets</code></th></tr></thead>
<tbody>
<tr><td class="prop">Definition:</td><td>Connects a catalog to the LDP container of its datasets.</td></tr>
<tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/dcat#Catalog"><code>dcat:Catalog</code></a></td></tr>
Expand All @@ -3273,7 +3276,7 @@ <h4>Property: datasets</h4>
<h4>Property: catalog records</h4>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#records">dcat:records</a></th></tr></thead>
<thead><tr><th>RDF Property:</th><th><code>dcat-ld:records</code></th></tr></thead>
<tbody>
<tr><td class="prop">Definition:</td><td>Connects a catalog to the LDP container of its catalog records.</td></tr>
<tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/dcat#Catalog"><code>dcat:Catalog</code></a></td></tr>
Expand All @@ -3286,7 +3289,7 @@ <h4>Property: catalog records</h4>
<h4>Property: data services</h4>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#services">dcat:services</a></th></tr></thead>
<thead><tr><th>RDF Property:</th><th><code>dcat-ld:services</code></th></tr></thead>
<tbody>
<tr><td class="prop">Definition:</td><td>Connects a catalog to the LDP container of its data services.</td></tr>
<tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/dcat#Catalog"><code>dcat:Catalog</code></a></td></tr>
Expand All @@ -3299,7 +3302,7 @@ <h4>Property: data services</h4>
<h4>Property: distributions</h4>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#distributions">dcat:distributions</a></th></tr></thead>
<thead><tr><th>RDF Property:</th><th><code>dcat-ld:distributions</code></th></tr></thead>
<tbody>
<tr><td class="prop">Definition:</td><td>Connects a dataset to the LDP container of its distributions.</td></tr>
<tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/dcat#Dataset"><code>dcat:Dataset</code></a></td></tr>
Expand All @@ -3310,11 +3313,11 @@ <h4>Property: distributions</h4>

</section>

<section id="ldn">
<section id="ldn" class="informative">
<h3>Linked Data Notifications (<abbr title="Linked Data Notifications">LDN</abbr>)</h3>

<p>
Linked Data Notifications (LDN) [[!LDN]] can be used with DCAT e.g. for feedback collection.
Linked Data Notifications (LDN) [[?LDN]] can be used with DCAT e.g. for feedback collection.
Any resource can have an LDN Inbox.
In the following example we show a dataset <code>&lt;/datasets/001&gt;</code> as an LDN Target with an LDN Inbox.
</p>
Expand Down