-
Notifications
You must be signed in to change notification settings - Fork 55
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'gh-pages' into dcat-issue119
- Loading branch information
Showing
4 changed files
with
299 additions
and
306 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,183 @@ | ||
| <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" 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>). | ||
| 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></datasets/></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-ldp:datasets</code> predicate. | ||
| </p> | ||
| <pre id="ex-ldpc-dataset" class="example nohighlight turtle"> | ||
| @prefix dcat: <http://www.w3.org/ns/dcat#> . | ||
| @prefix ldp: <http://www.w3.org/ns/ldp#> . | ||
| @prefix dcat-ldp: <http://www.w3.org/ns/dcat-ldp#> . | ||
|
|
||
| @base <https://example.org/resource/catalog> . | ||
|
|
||
| <> a dcat:Catalog ; | ||
| dcat-ldp:datasets </datasets/> ; | ||
| dcat:dataset </datasets/001> . | ||
|
|
||
| </datasets/> a ldp:Container, ldp:DirectContainer ; | ||
| ldp:membershipResource <> ; | ||
| ldp:hasMemberRelation dcat:dataset ; | ||
| ldp:contains </datasets/001> . | ||
|
|
||
| </datasets/001> a dcat:Dataset .</pre> | ||
|
|
||
| <p>In the second example, we add LDPCs <code></records/></code> for Catalog Records and <code></services/></code> for Data Services, discoverable using <code>dcat-ldp:records</code> and <code>dcat-ldp:services</code> predicates from the Catalog: | ||
| </p> | ||
| <pre id="ex-ldpc-record" class="example nohighlight turtle"> | ||
| @prefix dcat: <http://www.w3.org/ns/dcat#> . | ||
| @prefix ldp: <http://www.w3.org/ns/ldp#> . | ||
| @prefix dcat-ldp: <http://www.w3.org/ns/dcat-ldp#> . | ||
|
|
||
| @base <https://example.org/resource/catalog> . | ||
|
|
||
| <> a dcat:Catalog ; | ||
| dcat-ldp:records </records/> ; | ||
| dcat-ldp:datasets </datasets/> ; | ||
| dcat-ldp:services </services/> ; | ||
| dcat:dataset </datasets/001> . | ||
|
|
||
| </records/> a ldp:Container, ldp:DirectContainer ; | ||
| ldp:membershipResource <> ; | ||
| ldp:hasMemberRelation dcat:record ; | ||
| ldp:contains </records/001> . | ||
|
|
||
| </datasets/> a ldp:Container, ldp:DirectContainer ; | ||
| ldp:membershipResource <> ; | ||
| ldp:hasMemberRelation dcat:dataset ; | ||
| ldp:contains </datasets/001> . | ||
|
|
||
| </services/> a ldp:Container, ldp:DirectContainer ; | ||
| ldp:membershipResource <> ; | ||
| ldp:hasMemberRelation dcat:service ; | ||
| ldp:contains </services/001> . | ||
|
|
||
| </records/001> a dcat:CatalogRecord ; | ||
| foaf:primaryTopic </datasets/001> . | ||
|
|
||
| </datasets/001> a dcat:Dataset ; | ||
|
|
||
| </services/001> a dcat:DataService .</pre> | ||
|
|
||
| <p>Each dataset has its own LDPC for its distributions. | ||
| In the third example, we show the LDPC <code></datasets/001/distributions/></code> for distributions of a single dataset, <code></datasets/001></code>, discoverable through the <code>dcat-ldp:distributions</code> predicate.</p> | ||
| <pre id="ex-ldpc-distribution" class="example nohighlight turtle"> | ||
|
|
||
| @prefix dcat: <http://www.w3.org/ns/dcat#> . | ||
| @prefix ldp: <http://www.w3.org/ns/ldp#> . | ||
| @prefix dcat-ldp: <http://www.w3.org/ns/dcat-ldp#> . | ||
|
|
||
| @base <https://example.org/resource/catalog> . | ||
|
|
||
| </datasets/001> a dcat:Dataset ; | ||
| dcat-ldp:distributions </datasets/001/distributions/> ; | ||
| dcat:distribution </datasets/001/distributions/001> . | ||
|
|
||
| </datasets/001/distributions/> a ldp:Container, ldp:DirectContainer ; | ||
| ldp:membershipResource </datasets/001> ; | ||
| ldp:hasMemberRelation dcat:distribution ; | ||
| ldp:contains </datasets/001/distributions/001> . | ||
|
|
||
| </datasets/001/distributions/001> a dcat:Distribution .</pre> | ||
|
|
||
| <p class="note">For catalogs with many datasets, catalog records, data services or distributions, | ||
| the Linked Data Platform Paging mechanism [[?LDP-Paging]] SHOULD be used to provide access to them.</p> | ||
|
|
||
| <p> | ||
| In the next sections we formally define the additional properties used for discovery of LDP containers. | ||
| </p> | ||
|
|
||
| <section id="Property:catalog_datasets"> | ||
| <h4>Property: datasets</h4> | ||
|
|
||
| <table class="definition"> | ||
| <thead><tr><th>RDF Property:</th><th><code>dcat-ldp: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> | ||
| <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/ldp#DirectContainer"><code>ldp:DirectContainer</code></a></td></tr> | ||
| </tbody> | ||
| </table> | ||
| </section> | ||
|
|
||
| <section id="Property:catalog_records"> | ||
| <h4>Property: catalog records</h4> | ||
|
|
||
| <table class="definition"> | ||
| <thead><tr><th>RDF Property:</th><th><code>dcat-ldp: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> | ||
| <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/ldp#DirectContainer"><code>ldp:DirectContainer</code></a></td></tr> | ||
| </tbody> | ||
| </table> | ||
| </section> | ||
|
|
||
| <section id="Property:catalog_services"> | ||
| <h4>Property: data services</h4> | ||
|
|
||
| <table class="definition"> | ||
| <thead><tr><th>RDF Property:</th><th><code>dcat-ldp: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> | ||
| <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/ldp#DirectContainer"><code>ldp:DirectContainer</code></a></td></tr> | ||
| </tbody> | ||
| </table> | ||
| </section> | ||
|
|
||
| <section id="Property:dataset_distributions"> | ||
| <h4>Property: distributions</h4> | ||
|
|
||
| <table class="definition"> | ||
| <thead><tr><th>RDF Property:</th><th><code>dcat-ldp: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> | ||
| <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/ldp#DirectContainer"><code>ldp:DirectContainer</code></a></td></tr> | ||
| </tbody> | ||
| </table> | ||
| </section> | ||
|
|
||
| </section> | ||
|
|
||
| <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. | ||
| Any resource can have an LDN Inbox. | ||
| In the following example we show a dataset <code></datasets/001></code> as an LDN Target with an LDN Inbox. | ||
| </p> | ||
| <pre id="ex-ldn-dataset" class="example nohighlight turtle"> | ||
| @prefix dcat: <http://www.w3.org/ns/dcat#> . | ||
| @prefix ldp: <http://www.w3.org/ns/ldp#> . | ||
|
|
||
| @base <https://example.org/resource/catalog> . | ||
|
|
||
| </datasets/001> a dcat:Dataset ; | ||
| ldp:inbox </datasets/001/inbox/> . | ||
|
|
||
| </datasets/001/inbox/> ldp:contains </datasets/001/inbox/001> .</pre> | ||
|
|
||
| </section> | ||
|
|
||
| </section> |
Oops, something went wrong.