Skip to content

Commit

Permalink
Merge branch 'gh-pages' into dcat-closed-issues-links-html-daveb
Browse files Browse the repository at this point in the history
  • Loading branch information
davebrowning committed Jan 28, 2019
2 parents 5d95400 + c64b2e3 commit 5700bb6
Show file tree
Hide file tree
Showing 6 changed files with 145 additions and 95 deletions.
File renamed without changes
11 changes: 10 additions & 1 deletion dcat/config.js
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ var respecConfig = {
"publisher":"ISO",
"status":"International Standard",
"date":"2012"
},
},
"DDI" : {
href : "http://www.ddialliance.org/explore-documentation",
title : "Data Documentation Initiative",
Expand Down Expand Up @@ -183,6 +183,15 @@ var respecConfig = {
publisher:"Hydra W3C Community Group",
status:"Unofficial Draft"
},
"LDP": {
authors: [
"Leigh Dodds",
"Ian Davis"
],
href:"http://patterns.dataincubator.org/book/",
title:"Linked Data Patterns",
date:"31 May 2012"
},
"ODRS": {
authors: [
"Leigh Dodds"
Expand Down
83 changes: 68 additions & 15 deletions dcat/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1212,7 +1212,7 @@ <h4>Property: qualified relation</h4>
</table>

<p>
This DCAT property follows the pattern of <a href="https://www.w3.org/TR/prov-o/#description-qualified-terms">Qualification Properties</a> defined in [[PROV-O]].
This DCAT property follows the common <a href="#qualified-forms">qualified relation pattern</a> .
</p>

<p class="note">
Expand Down Expand Up @@ -1308,7 +1308,7 @@ <h4>Property: qualified attribution</h4>
</table>

<p>
This DCAT property follows the pattern of <a href="https://www.w3.org/TR/prov-o/#description-qualified-terms">Qualification Properties</a> defined in [[PROV-O]].
This DCAT property follows the common <a href="#qualified-forms">qualified relation pattern</a> .
</p>

<p class="note">
Expand Down Expand Up @@ -2138,7 +2138,7 @@ <h3>Class: Concept Scheme</h3>
<tr><td class="prop">See also:</td><td><a href="#Property:catalog_themes">catalog themes</a>, <a href="#Property:resource_theme">dataset theme</a></td></tr>
</tbody>
</table>
</section>
</section> <!-- end class Concept_Scheme -->

<section id="Class:Concept">
<h3>Class: Concept</h3>
Expand All @@ -2151,7 +2151,7 @@ <h3>Class: Concept</h3>
<tr><td class="prop">See also:</td><td><a href="#Property:catalog_themes">catalog themes</a>, <a href="#Property:resource_theme">dataset theme</a></td></tr>
</tbody>
</table>
</section>
</section> <!-- end class Concept -->

<section id="Class:Organization_Person">
<h3>Class: Organization/Person</h3>
Expand All @@ -2162,7 +2162,7 @@ <h3>Class: Organization/Person</h3>
<tr><td class="prop">Usage note:</td><td>[[!FOAF]] provides sufficient properties to describe these entities.</td></tr>
</tbody>
</table>
</section>
</section> <!-- end class Person -->

<section id="Class:Relationship">
<h3>Class: Relationship</h3>
Expand Down Expand Up @@ -2204,7 +2204,7 @@ <h4>Property: hadRole</h4>
<tbody>
<tr><td class="prop">Definition:</td><td>The function of an entity or agent with respect to another entity or resource.</td></tr>
<tr><td class="prop">Domain:</td><td><code><a href="http://www.w3.org/ns/prov#Attribution"><code>prov:Attribution</code></a> or <a href="#Class:Relationship"><code>dcat:Relationship</code></a></code></td></tr>
<tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/prov#Role"><code>prov:Role</code></a></td></tr>
<tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/prov#Role"><code>dcat:Role</code></a></td></tr>
<tr><td class="prop">Usage note:</td><td>May be used in a qualified-attribution to specify the role of an Agent with respect to an Entity. It is recommended that the value be taken from a controlled vocabulary of agent roles, such as <a href="http://registry.it.csiro.au/def/isotc211/CI_RoleCode">ISO 19115 CI_RoleCode</a>.</td></tr>
<tr><td class="prop">Usage note:</td><td>May be used in a qualified-relation to specify the role of an Entity with respect to another Entity. It is recommended that the value be taken from a controlled vocabulary of entity roles.</td></tr>
</tbody>
Expand All @@ -2221,6 +2221,32 @@ <h4>Property: hadRole</h4>

</section> <!-- end class Relationship -->

<section id="Class:Role">
<h3>Class: Role</h3>

<table class="definition">
<thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/ns/dcat#Role">dcat:Role</a></th></tr></thead>
<tbody>
<tr><td class="prop">Definition:</td><td>A role is the function of a resource or agent with respect to another resource, in the context of resource attribution or resource relationships.</td></tr>
<tr><td class="prop">Sub class of:</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept"><code>skos:Concept</code></a></td></tr>
<tr><td class="prop">Usage note:</td><td>Used in a qualified-attribution to specify the role of an Agent with respect to an Entity. It is recommended that the values be managed as a controlled vocabulary of agent roles, such as <a href="http://registry.it.csiro.au/def/isotc211/CI_RoleCode">ISO 19115 CI_RoleCode</a> </td></tr>
<tr><td class="prop">Usage note:</td><td>Used in a qualified-relation to specify the role of an Entity with respect to another Entity.
It is recommended that the values be managed as a controlled vocabulary of entity roles such as
<br/>- <a href="http://registry.it.csiro.au/def/isotc211/DS_AssociationTypeCode">ISO 19115 DS_AssociationTypeCode</a>
<br/>- <a href="https://www.iana.org/assignments/link-relation">IANA Registry of Link Relations</a>
<br/>- DataCite metadata schema [[DataCite]]
<br/>- <a href="https://id.loc.gov/vocabulary/relators">MARC relators</a> </td></tr>
</tbody>
</table>
<p>
This DCAT class complements <a href="http://www.w3.org/ns/prov#Role"><code>prov:Role</code></a> which provides the function of an entity or agent with respect to an activity.
</p>

<p class="note">
Property added in this revision of DCAT.
</p>
</section> <!-- end class Role -->

</section>


Expand Down Expand Up @@ -2650,15 +2676,41 @@ <h3>Conformance test results</h3>
</section>
</section>

<section id="qualified-forms">
<h2>Qualified relations</h2>

<p class="issue" data-number="79">
Provision of a general pattern for qualified relationships was identified as a requirement for this revision of DCAT.
</p>
<p>
DCAT includes elements to support description of many aspects of datasets and data-services. Nevertheless, additional information is required in order to fully express the semantics of some relationships. An example is that, while Dublin Core [[DC11]] provides the standard roles <b>creator</b>, <b>contributor</b> and <b>publisher</b> for attribution of a resource to a responsible party or agent, there are many other potential roles, see for example the CI_RoleCode values from [[ISO-19115-1]]. Similarly, while Dublin Core and [[PROV-O]] provide some properties to capture relationships between resources, including <b>was derived from</b>, <b>was quoted from</b>, <b>is version of</b>, <b>references</b> and several others, many additional concerns are seen in the list of <a href="http://registry.it.csiro.au/def/isotc211/DS_AssociationTypeCode">ISO 19115 DS_AssociationTypeCodes</a>, the <a href="https://www.iana.org/assignments/link-relation">IANA Registry of Link Relations</a>, the DataCite metadata schema [[DataCite]]
<br/> and the <a href="https://id.loc.gov/vocabulary/relators">MARC relators</a>. While these relations could be captured with additional sub-properties of <code>dct:relation</code>, <code>dct:contributor</code>, etc, this would lead to an explosion in the number of properties, and anyway the full set of potential roles and relationships is unknown.
</p>
<p>
A common approach for meeting these kinds of requirement is to introduce an additional resource to carry parameters that qualify the relationship. Precedents are the <a href="https://www.w3.org/TR/prov-o/#description-qualified-terms">qualified terms</a> in [[PROV-O]] and the <a href="https://www.w3.org/TR/vocab-ssn/#Sample_Relations">sample relations</a> in the Semantic Sensor Network ontology [[VOCAB-SSN]]. The general <a href="http://patterns.dataincubator.org/book/qualified-relation.html">Qualified Relation pattern</a> is described in [[LDP]].
</p>
<p>
Many of the qualified terms from [[PROV-O]] are relevant to the description of resources in catalogs but these are incomplete due to the activity-centric viewpoint taken by PROV-O. Addressing some of the gaps, additional forms are included in the DCAT vocabulary to satisfy requirements that do not involve explicit Activities. These are summarized in the <a href="#fig2">following figure</a>:
</p>

<figure id="fig2"><img alt="UML model of DCAT qualified relationships" src="UML/DCAT-Relationships.png">
<figcaption>
Qualified relationships support an extensible set of roles relating resources to agents or to other resources
</figcaption>
</figure>

<p>
Note that, while the focus of these qualified forms is to allow for additional <i>roles</i> on a relationship, other aspect of the relationships, such as the applicable time interval, are easily attached when a specific node is used to describe the relationship like this (e.g. see the <a href="https://www.w3.org/TR/prov-o/#qualified-terms-figure">chart of Influence relations</a> in [[PROV-O]] for some examples).
</p>
<section id="qualified-attribution">
<h2>Attribution roles</h2>
<h3>Relationships between datasets and agents</h3>
<p>
The standard Dublin Core properties <a href="http://purl.org/dc/terms/contributor"><code>dct:contributor</code></a>, <a href="http://purl.org/dc/terms/creator"><code>dct:creator</code></a> and <a href="http://purl.org/dc/terms/publisher"><code>dct:publisher</code></a>, and the generic <a href="https://www.w3.org/TR/prov-o/#wasAttributedTo"><code>prov:wasAttributedTo</code></a> from [[PROV-O]], support basic associations of responsible agents with a catalogued resource.
However, there are many other roles of importance in relation to datasets and services - e.g. funder, distributor, custodian, editor.
Some of these roles are enumerated in the CI_RoleCode values from [[ISO-19115-1]], in the [[DataCite]] metadata schema, and included within the <a href="https://id.loc.gov/vocabulary/relators">MARC relators</a>.
</p>
<p>
A general method for assigning an agent to a resource with a specified relationship is provided by using the qualified form <a href="https://www.w3.org/TR/prov-o/#qualifiedAttribution"><code>prov:qualifiedAttribution</code></a> from [[PROV-O]].
A general method for assigning an agent to a resource with a specified role is provided by using the qualified form <a href="https://www.w3.org/TR/prov-o/#qualifiedAttribution"><code>prov:qualifiedAttribution</code></a> from [[PROV-O]].
The following provides an illustration:
</p>
<pre id="ex-qualified-attribution" class="example nohighlight turtle" aria-busy="false" aria-live="polite">
Expand All @@ -2678,7 +2730,7 @@ <h2>Attribution roles</h2>
</pre>

<p>
In this example the roles are taken from [[ISO-19115-1]] which are available as linked data in a <a href="http://registry.it.csiro.au/def/isotc211/CI_RoleCode">discrete list</a>.
In this example the roles are taken from [[ISO-19115-1]] which are available as linked data in a <a href="http://registry.it.csiro.au/def/isotc211/CI_RoleCode">code list</a>.
</p>

<aside class="note">
Expand All @@ -2688,7 +2740,7 @@ <h2>Attribution roles</h2>
</section>

<section id="qualified-relationship">
<h2>Relationships between datasets and other catalogued resources</h2>
<h3>Relationships between datasets and other resources</h3>
<p>
The standard Dublin Core properties <a href="http://purl.org/dc/terms/relation">dct:relation</a> and sub-properties such as
<a href="http://purl.org/dc/terms/hasPart">dct:hasPart</a>/<a href="http://purl.org/dc/terms/isPartOf">dct:isPartOf</a>,
Expand All @@ -2705,8 +2757,7 @@ <h2>Relationships between datasets and other catalogued resources</h2>
A general method for relating a resource to another resource with a specified role is provided by using the qualified form <a href="#Property:resource_qualifiedRelation">dcat:qualifiedRelation</a>.
The following provides illustrations:
</p>
<div class="example">
<pre class="nohighlight turtle" aria-busy="false" aria-live="polite">
<pre id="ex-dataset-resource" class="example nohighlight turtle" aria-busy="false" aria-live="polite">
ex:Test987
a dcat:Dataset ;
dcat:qualifiedRelation [
Expand All @@ -2725,14 +2776,16 @@ <h2>Relationships between datasets and other catalogued resources</h2>
] ;
.
</pre>
</div>

<p class="note">
Note: The property <a href="#Property:resource_qualifiedRelation">dcat:qualifiedRelation</a> and association-class <a href="#Class:Relationship">dcat:Relationship</a> follow the pattern established in W3C [[PROV-O]] and described in the section <a href="https://www.w3.org/TR/prov-o/#description-qualified-terms">Qualified Terms</a>.
However, PROV-O is activity-centric, and does not support Entity-Entity relations except for the single case of 'was derived from', thus necessitating the new elements shown here to support the general case.
</p>
</section>

</section>


<section id="prov-patterns">

<h2>Provenance patterns</h2>
Expand Down Expand Up @@ -2871,9 +2924,9 @@ <h3>Schema.org</h3>
Schema.org [[SCHEMA-ORG]] includes a number of types and properties based on the original DCAT work (see <a href="https://schema.org/Dataset">schema:Dataset</a> as a starting point),
and the index for Google's <a href="https://g.co/datasetsearch">Dataset Search service</a> relies on structured description in web pages about datasets based on both
<a href="https://developers.google.com/search/docs/data-types/dataset">schema.org and DCAT</a>.
A comparison of the DCAT backbone, showed in <a href="#vocabulary-overview">Figure 1. above</a> with related classes from [[SCHEMA-ORG]] shows the similarity:
A comparison of the <a href="#fig1">DCAT backbone</a> with related classes from [[SCHEMA-ORG]] in <a href="#fig3">the following figure</a> shows the similarity:
</p>
<figure id="fig2"><img alt="UML model of schema.org classes and properties related to dataset catalogs" src="UML/schema.org-dataset.png">
<figure id="fig3"><img alt="UML model of schema.org classes and properties related to dataset catalogs" src="UML/schema.org-dataset.png">
<figcaption>
schema.org support for dataset catalogs, showing a selection of schema.org properties that have the classes shown within their domain and range
</figcaption>
Expand Down
Loading

0 comments on commit 5700bb6

Please sign in to comment.