Skip to content

Commit

Permalink
Merge branch 'gh-pages' into conneg-ap-merge-list-tokens
Browse files Browse the repository at this point in the history
  • Loading branch information
Nicholas Car committed Mar 19, 2019
2 parents 28e8a8d + c476b6e commit 08820ef
Show file tree
Hide file tree
Showing 3 changed files with 41 additions and 59 deletions.
9 changes: 6 additions & 3 deletions conneg-by-ap/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -37,10 +37,13 @@ <h1>Introduction</h1>
<p>
Content delivered by dereferencing Internet identifiers can be negotiated for in different
ways. When using the HTTP protocol [[RFC7230]], a client may set one or more headers:
<ul><li>an <code>Accept</code> header specifying preferred Media Types which the server may or may not supply</li>
</p>
<ul>
<li>an <code>Accept</code> header specifying preferred Media Types which the server may or may not supply</li>
<li>an <code>Accept-Encoding</code> header to request that a specific content encoding system be used</li>
<li>an <code>Accept-Language</code> header to indicate a preferred language</li>
</ul>
</ul>
<p>
However, clients have not had a
defined way to negotiate for content based on its adherence to an information model - a standard, a specification or
a <a>profile</a> - and this document addresses this functionality.
Expand Down Expand Up @@ -190,7 +193,7 @@ <h4>Using Accept/Content Type together with the profile parameter</h4>
such as the JSON-LD profiles "expanded" (<code>http://www.w3.org/ns/json-ld#expanded</code>) or
"flattened" (<code>http://www.w3.org/ns/json-ld#flattened</code>).
In order to signal the use of media-type-independent profiles,
the http header fields </code>Accept-Profile</code> and <code>Content-Profile</code> are to be used.</p>
the http header fields <code>Accept-Profile</code> and <code>Content-Profile</code> are to be used.</p>
<h4>Using a Link-header with rel=”profile” (RFC 6906)</h4>
<p>The HTTP Link header field [[RFC 8288]] relates a web resource (Link Context)
to a target resource (Link Target
Expand Down
36 changes: 20 additions & 16 deletions dcat/config.js
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,10 @@ var respecConfig = {
edDraftURI: "https://w3c.github.io/dxwg/dcat/",
// issueBase: "https://github.com/w3c/dxwg/issues/", -- Not needed when github used
editors: [{
name: "Alejandra Gonzalez Beltran",
company: "Oxford eResearch Centre, Engineering Science, University of Oxford",
url: "https://www.oerc.ox.ac.uk/people/alejandra",
companyURL: "http://www.oerc.ox.ac.uk/"
name: "Riccardo Albertoni",
company: "CNR - Consiglio Nazionale delle Ricerche, Italy",
url: "http://www.imati.cnr.it/joomla/index.php/people/8-curricula/178-riccardo-albertoni",
companyURL: "http://www.cnr.it/"
},{
name: "Dave Browning",
company: "Refinitiv",
Expand All @@ -23,24 +23,28 @@ var respecConfig = {
company: "CSIRO",
url: "http://people.csiro.au/Simon-Cox",
companyURL: "https://www.csiro.au/"
},{
name: "Alejandra Gonzalez Beltran",
company: "Oxford eResearch Centre, Engineering Science, University of Oxford",
url: "https://www.oerc.ox.ac.uk/people/alejandra",
companyURL: "http://www.oerc.ox.ac.uk/"
},{
name: "Andrea Perego",
company: "European Commission, Joint Research Centre (JRC)",
url: "https://joinup.ec.europa.eu/user/14209",
companyURL: "https://ec.europa.eu/jrc/"
},{
name: "Peter Winstanley",
company: "Scottish Government",
companyURL: "http://www.gov.scot/"
}],
otherLinks: [{
// key: "Contributors",
// data: [{
// value: "Makx Dekkers",
// href: "http://www.makxdekkers.com"
// },{
// value: "Antoine Isaac, Europeana Foundation",
// href: "https://pro.europeana.eu/person/antoine-isaac"
// },{
// value: "Andrea Perego, European Commission",
// href: "https://ec.europa.eu/jrc/"
// }]
// },{
key: "Contributors",
data: [{
value: "Makx Dekkers",
href: "http://www.makxdekkers.com"
}]
},{
key: "Editors of previous version",
data: [{
value: "Fadi Maali, DERI",
Expand Down
55 changes: 15 additions & 40 deletions dcat/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ <h2>Introduction</h2>

<section id="motivation" class="informative"><h2>Motivation for change</h2>
<p>The original Recommendation [[?VOCAB-DCAT-20140116]], published in January 2014, provided the basic framework for describing datasets. Importantly, it made the distinction between a dataset as an abstract idea and a distribution as a manifestation of the dataset. Although DCAT has been widely adopted, it has become clear that the original specification lacked a number of essential features that were added either through application profiles, such as the European Commission's DCAT-AP [[?DCAT-AP]], or the development of larger vocabularies that, to a greater or lesser extent, built upon the base standard, such as the Healthcare and Life Sciences Community Profile [[?HCLS-Dataset]], the Data Tag Suite [[?DATS]] and more. This version of DCAT has been developed to address the specific shortcomings that have come to light through the experiences of different communities, the aim being, of course, to improve interoperability between the outputs of these larger vocabularies.
For example, in this new DCAT version, we provide classes, properties and guidance to address <a href="Dereferenceable-identifiers">identifiers</a>, <a href="#quality-information">quality information</a>, <a href="#data-citation">data citation</a> issues.</p>
For example, in this new DCAT version, we provide classes, properties and guidance to address <a href="#Dereferenceable-identifiers">identifiers</a>, <a href="#quality-information">quality information</a>, <a href="#data-citation">data citation</a> issues.</p>
<p>This draft includes re-writing of the specification throughout. Significant changes from the 2014 Recommendation are marked within the text using "Note" sections, as well as being described in the <a href="#changes">Change History</a>.</p>

</section>
Expand Down Expand Up @@ -953,16 +953,18 @@ <h4>Property: contact point</h4>
<section id="Property:resource_creator">
<h4>Property: resource creator</h4>

<p class="note">
<div class="note">
<p>
New property added in this revision of DCAT, specifically added when considering the data citation requirement and
added to the <a href="#Class:Resource"><code>dcat:Resource</code></a> class, as the Dataset superclass. For more details, see
the <a href="data-citation">data citation</a> section.
</p>
the <a href="#data-citation">data citation</a> section.
</p>

<p class="issue" data-number="80">
<p>
The use of the [[?PROV-O]] qualified-attribution pattern is <a href="#qualified-attribution">described below</a>.
`dct:creator` corresponds with a general attribution with the role 'creator'.
</p>
</p>
</div>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/creator">dct:creator</a></th></tr></thead>
Expand Down Expand Up @@ -1053,7 +1055,7 @@ <h4>Property: language</h4>
<section id="Property:resource_publisher">
<h4>Property: publisher</h4>

<p class="issue" data-number="80">
<p class="note">
The use of the [[?PROV-O]] qualified-attribution pattern is <a href="#qualified-attribution">described below</a>.
`dct:publisher` corresponds with a general attribution with the role 'publisher'.
</p>
Expand Down Expand Up @@ -1169,11 +1171,6 @@ <h4>Property: resource relation</h4>
<a href="http://purl.org/dc/terms/relation"><code>dct:relation</code></a> is a super-property of a number of more specific properties which express more precise relationships, so use of <code>dct:relation</code> is not inconsistent with a subsequent reclassification with more specific semantics, though the more specialized sub-properties <em title="SHOULD" class="rfc2119">SHOULD</em> be used to link a dataset to component and supplementary resources if possible.
</p>

<p class="issue" data-number="81">
The general need to describe relationships between datasets has been identified as a requirement to be satisfied in the revision of DCAT.
Guidance on the use of more specific relationship predicates is required, particularly in the context of the <code>dcat:Dataset</code> sub-class.
</p>

<p class="note">
Use of this Dublin Core Terms property in this context added in this revision of DCAT.
</p>
Expand Down Expand Up @@ -1487,10 +1484,6 @@ <h3>Class: Dataset</h3>
</p>


<p class="issue" data-number="59">
The need to more formally encode access restrictions for both datasets and distributions has been identified as a requirement to be satisfied in the revision of DCAT.
</p>

<p class="issue" data-number="60">
The need to provide richer descriptions of dataset aspects (e.g. instrument/sensor used, spatial feature, observable property, quantity kind) has been identified as a requirement to be satisfied in the revision of DCAT.
</p>
Expand All @@ -1511,9 +1504,6 @@ <h3>Class: Dataset</h3>
<p class="issue" data-number="86">
The need to be able to provide usage notes for a dataset or distribution has been identified as a requirement to be satisfied in the revision of DCAT.
</p>
<p class="issue" data-number="433">
The need to be able to provide citations for a distribution has been identified as a potential requirement to be satisfied in 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>
Expand Down Expand Up @@ -1550,11 +1540,6 @@ <h4>Property: dataset distribution</h4>
</table>
</section>

<p class="issue" data-number="81">
<a href="https://github.com/w3c/dxwg/issues/81">Issue #81</a> concerns the general need to describe relationships between datasets.
Guidance on the use of specializations of <code>dct:relation</code> is required in the context of <code>dcat:Dataset</code>.
</p>

<section id="Property:dataset_frequency">
<h4>Property: frequency</h4>
<table class="definition">
Expand All @@ -1568,11 +1553,11 @@ <h4>Property: frequency</h4>
</tbody>
</table>

<div class="example">

<p>
For example, a 15-minute time-series that is published daily could be described
</p>
<pre id="ex-frequency" class="example nohighlight turtle" aria-busy="false" aria-live="polite">
<pre id="ex-freq-daily" class="example nohighlight turtle" aria-busy="false" aria-live="polite">
&lt;ds913&gt;
a dcat:Dataset ;
dct:accrualPeriodicity &lt;http://purl.org/cld/freq/daily&gt; ;
Expand All @@ -1583,14 +1568,14 @@ <h4>Property: frequency</h4>
<p>
A dataset composed of items added hourly and published immediately could be described
</p>
<pre id="ex-frequency" class="example nohighlight turtle" aria-busy="false" aria-live="polite">
<pre id="ex-freq-hourly" class="example nohighlight turtle" aria-busy="false" aria-live="polite">
&lt;ds782&gt;
a dcat:Dataset ;
dct:accrualPeriodicity &lt;http://purl.org/cld/freq/continuous&gt; ;
dcat:temporalResolution "PT1H"^^xsd:duration ;
.
</pre>
</div>


</section>

Expand Down Expand Up @@ -1731,14 +1716,6 @@ <h3>Class: Distribution</h3>
<a href="#Property:distribution_update_date">update/modification date</a>,
</p>

<p class="issue" data-number="54">
The packaging of files in a <code>dcat:Distribution</code> is being considered as part of the revision of DCAT.
</p>

<p class="issue" data-number="59">
The need to more formally encode access restrictions for both datasets and distributions has been identified as a requirement to be satisfied in 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 @@ -1984,10 +1961,8 @@ <h4>Property: spatial resolution</h4>
<p class="note">
New property in this context in this revision of DCAT.
</p>
</tbody>
</table>

</section>
</section>

<section id="Property:distribution_temporalresolution">
<h4>Property: temporal resolution</h4>
Expand Down Expand Up @@ -4241,7 +4216,7 @@ <h3>Changes since the W3C Recommendation of 16 January 2014</h3>
</li>

<li>
<a href="#Property:resource_relation">Property: resource relation</a>: The property <code>dct:relation</code> is recommended for use in the context of a catalogued resource to capture general relationships, including the case where the package of resources associated with a catalogued item includes a mixture of representations, parts, documentation and other elements which are not strictly 'distributions' of a dataset - see <a href="https://github.com/w3c/dxwg/issues/253">Issue #253</a>.
<a href="#Property:resource_relation">Property: resource relation</a>: The property <code>dct:relation</code> is recommended for use in the context of a catalogued resource to capture general relationships, including the case where the package of resources associated with a catalogued item includes a mixture of representations, parts, documentation and other elements which are not strictly 'distributions' of a dataset - see <a href="https://github.com/w3c/dxwg/issues/253">Issue #253</a>. The more general use of <code>dct:relation</code> is driven by the requirement documented in <a href="https://github.com/w3c/dxwg/issues/81">Issue #81</a>.
</li>


Expand Down

0 comments on commit 08820ef

Please sign in to comment.