Skip to content

Commit

Permalink
Merge branch 'gh-pages' into gh-pages-add-issue505-cneg3PWD
Browse files Browse the repository at this point in the history
  • Loading branch information
@rob-metalinkage
rob-metalinkage committed Nov 19, 2019
2 parents b731888 + 643295b commit 5ad47a6
Show file tree
Hide file tree
Showing 3 changed files with 39 additions and 48 deletions.
8 changes: 4 additions & 4 deletions connegp/config.js
View file
@@ -1,12 +1,12 @@
var respecConfig = {
specStatus: "ED",
shortName: "dx-prof-conneg",
edDraftURI: "https://w3c.github.io/dxwg/conneg-by-ap/",
edDraftURI: "https://w3c.github.io/dxwg/connegp/",
previousPublishDate: "2019-04-30",
previousMaturity: "PWD",
prevRecURI: "https://www.w3.org/TR/2019/WD-dx-prof-conneg-20190430/",
testSuiteURI: "https://github.com/w3c/conneg-prof-testing",
implementationReportURI: "https://github.com/w3c/conneg-prof-testing",
testSuiteURI: "https://github.com/w3c/prof-conneg-testing",
implementationReportURI: "https://github.com/w3c/prof-conneg-testing",
canonicalURI: "TR",
editors: [{
name: "Lars G. Svensson",
Expand All @@ -18,7 +18,7 @@ var respecConfig = {
{
name: "Rob Atkinson",
company: "Metalinkage, Open Geospatial Consortium",
companyURL: "http://www.opengeospatial.org/",
companyURL: "http://www.opengeospatial.org",
orcid: "0000-0002-7878-2693"
},
{
Expand Down
7 changes: 5 additions & 2 deletions connegp/extra.css
View file
Expand Up @@ -17,9 +17,13 @@ th, td {
}

.codelisting {
padding:0 5px 5px 5px;
padding: 5px;
background-color: #eee;
border-left: solid 0.5em #999;
display: block;
font-family: Menlo, Consolas, "DejaVu Sans Mono", Monaco, monospace;
font-size: 0.9em;
white-space: pre;
}

.codelisting-title {
Expand All @@ -28,5 +32,4 @@ th, td {
line-height: 1.5;
text-transform: none;
color: #666;
margin-top: -1em;
}
72 changes: 30 additions & 42 deletions connegp/index.html
View file
Expand Up @@ -114,7 +114,7 @@ <h2>Definitions</h2>
A basis for comparison; a reference point against which other things can be evaluated.
</p>
<p>
<em>Source: DCMI Metadata Terms [[DCTERMS]]'s definition for a <code><a href="http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-Standard">Standard</a></code>.</em>
<em>Source: DCMI Metadata Terms [[DCTERMS]]'s definition for a <code><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-Standard">Standard</a></code>.</em>
</p>
</dd>
<dt><dfn data-lt="data specification">data specification</dfn></dt>
Expand Down Expand Up @@ -206,7 +206,7 @@ <h2>Motivation</h2>
(classes and properties) available to use for their content's information model. When a client initiates a request
for an Internet resource, such as an HTTP GET to retrieve a resource's representation, the client and server must have a standardized way to exchange information on how the transmitted resource
will be structured according to DTDs, XML Schema, vocabularies or other standards, specifications or
<a href="#dfn-data-profile">profiles</a>. When using non-HTTP content negotiation, methods such as URIs with Query String
<a>profiles</a>. When using non-HTTP content negotiation, methods such as URIs with Query String
Arguments have been previously implemented,
such as the
<abbr title="Open Archives Initiative - Protocol for Metadata Harvesting">OAI-PMH</abbr> [[OAI-PMH]] and
Expand Down Expand Up @@ -352,14 +352,14 @@ <h3>Linked Data APIs</h3>
Query String Arguments (QSAs). Two examples are the
<a href="http://epimorphics.github.io/elda/current/index.html">ELDA tool by Epimorphics</a>, an
implementation of the <a href="https://github.com/UKGovLD/linked-data-api/blob/wiki/Specification.md">Linked
Data API</a> specification created by the government of the United Kingdom, and <a href="https://pypi.org/project/pyLDAPI/">pyLDAPI</a>, a
Data API</a> specification created by the government of the United Kingdom, and <a href="https://pypi.org/project/pyldapi/">pyLDAPI</a>, a
Linked Data API implementation by <a href="https://www.csiro.au/">CSIRO</a> in the Python programming language. Both of these tools allow for the
listing of <em>views</em> and <em>formats</em> available for a resource by dereferencing a URL created by
adding the <code>_view=alternates</code> <abbr title='Query String Argument'>QSA</abbr> to the resource URI. The
<em>view</em> named <em>alternates</em> is a special view available for all resources that lists all other views.
</p>
<p>
What these tools call a <em>view</em> is analogous to a <a href="#dfn-data-profile">profile</a>
What these tools call a <em>view</em> is analogous to a <a>data profile</a>
and a <em>format</em> is analogous to an HTTP Media Type.
</p>
<p>
Expand Down Expand Up @@ -412,7 +412,7 @@ <h2>Abstract Model</h2>
</p>
<p>
Implementations of this Abstract Model for different environments are called
<a href="#dfn-functional-profile"><em>Functional Profiles</em></a>.
<a><em>Functional Profiles</em></a>.
To be a valid functional profile they MUST implement these Abstract Model functions.
How they do this will be environment-specific.
</p>
Expand Down Expand Up @@ -701,10 +701,10 @@ <h4>get resource by profile</h4>
profiles of others in the set), the server SHOULD indicate indicate conformance to each independent profile.
</p>
<p>
For example, using the HTTP Functional Profile, a response from a server that conforms to both [[?GeoDCAT-AP]] and also [[?STATDCAT-AP]], given
For example, using the HTTP Functional Profile, a response from a server that conforms to both [[?GeoDCAT-AP]] and also [[?STATDCAT-AP]], given
that neither profiles the other and thus no single indication of conformance will suffice for both, (note they
both do profile [[?DCAT-AP]], see the <a href="https://www.w3.org/TR/dx-prof/#eg-hierarchy">DCAT-AP Hierarchy
example in [[?DX-PROF]]</a>), a response using profile URIs for [[?GeoDCAT-AP]] and [[?STATDCAT-AP]] could be:
example</a> in [[?DX-PROF]]), a response using profile URIs for [[?GeoDCAT-AP]] and [[?STATDCAT-AP]] could be:
</p>
<p>
<code>Content-Profile: &lt;https://joinup.ec.europa.eu/release/geodcat-ap-v10>, &lt;https://joinup.ec.europa.eu/release/statdcat-ap/101></code>
Expand Down Expand Up @@ -815,13 +815,13 @@ <h3>Functional Profiles of this specification</h3>
</thead>
<tbody>
<tr>
<td><code><a href="http://www.w3.org/ns/dx/conneg/profile/http">cnpr:http</a></code></td>
<td><code>cnpr:http</code></td>
<td>HTTP Headers Functional Profile</td>
<td>For conformance with the functional profile presented in <a href="#http"></a>.</td>
<td>To be used if a resource conforms to the HTTP Headers Functional Profile</td>
</tr>
<tr>
<td><code><span style="white-space: nowrap"><a href="http://www.w3.org/ns/dx/conneg/profile/qsa">cnpr:qsa</a></span></code></td>
<td><code><span style="white-space: nowrap">cnpr:qsa</span></code></td>
<td>QSA Functional Profile</td>
<td>For conformance with the functional profile presented in <a href="#qsa"></a>.</td>
<td>
Expand All @@ -830,7 +830,7 @@ <h3>Functional Profiles of this specification</h3>
</td>
</tr>
<tr>
<td><code><span style="white-space: nowrap"><a href="http://www.w3.org/ns/dx/conneg/profile/qsa-alt">cnpr:qsa-alt</a></span></code></td>
<td><code><span style="white-space: nowrap">cnpr:qsa-alt</span></code></td>
<td>QSA Alternate Keywords Functional Profile</td>
<td>For conformance with the functional profile presented in <a href="#qsa"></a>.</td>
<td>
Expand All @@ -839,7 +839,7 @@ <h3>Functional Profiles of this specification</h3>
</td>
</tr>
<tr>
<td><code><span style="white-space: nowrap"><a href="http://www.w3.org/ns/dx/conneg/profile/rrd">cnpr:rrd</a></span></code></td>
<td><code><span style="white-space: nowrap">cnpr:rrd</span></code></td>
<td>Resource Representation Description</td>
<td>For conformance with <a href="#getresourcebyprofile"></a>.</td>
<td>
Expand Down Expand Up @@ -1272,7 +1272,7 @@ <h4>QSA Functional Profile description</h4>
</p>
<div class="note">
Conformance of a system to any one, or perhaps multiple, of these functional profiles may be demonstrated as per
<a href="#conformancetoprofiles"></a>. Note that it is not required that a system, perhaps a server, indicate
<a href="#conformancetofunctionalprofiles"></a>. Note that it is not required that a system, perhaps a server, indicate
conformance to one or more of the functional profiles described in this specification since not all systems will
do so. Systems may also show conformance to
functional profiles in multiple ways, such as with annotated entries in a services catalogue.
Expand Down Expand Up @@ -1974,11 +1974,10 @@ <h3>Profiles Vocabulary descriptions of this specification's Functional Profiles
<em>QSA Alternate Keywords Functional Profile</em> profile which thus meets the [[?DX-PROF]] definition of what it means
to be the profile of something.
</p>
<pre id="profiles-in-prof"
<div id="profiles-in-prof"
class="codelisting nohighlight" aria-busy="false" aria-live="polite"
title="Description of this specification and its profiles according to PROF">
<div class="codelisting-title">
<a href="#profiles-in-prof">CODE LISTING 1</a>: Description of this specification and its profiles, as listed in <a href="#functional-profiles-definition"></a>
title="Description of this specification and its profiles according to PROF"><div class="codelisting-title"><a href="#profiles-in-prof">CODE LISTING 1</a>: Description of this specification and its profiles,
as listed in <a href="#functional-profiles-definition"></a>,
using the Profiles Vocabulary.
</div>
@prefix dct: &lt;http://purl.org/dc/terms/> .
Expand Down Expand Up @@ -2028,7 +2027,7 @@ <h3>Profiles Vocabulary descriptions of this specification's Functional Profiles
profile(s) it conforms to, in its appropriate functional profile,
as per the abstract specification in § 6.2.2 get resource by
profile."@en .
</pre>
</div>
<figure id="fig-profile-hierarchy">
<a href="profiles-hierarchy.svg">
<img src="profiles-hierarchy.svg" alt="Profiles hierarchy of this specification" style="width:500px;" />
Expand All @@ -2045,7 +2044,7 @@ <h4>Demonstrating system conformance to Functional Profiles</h4>
With the identification of functional profiles of this specification given in <a href="#functional-profiles-definition"></a> and
their relations described using the Profiles Vocabulary [[?DX-PROF]] in this appendix, it is possible for
systems to show conformance to this specification or any functional profile of it using [[?DX-PROF]] mechanisms.
This is done using the [[DCTERMS]] predicate <code><a href="http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-conformsTo">dct:conformsTo</a></code>
This is done using the [[DCTERMS]] predicate <code><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-conformsTo">dct:conformsTo</a></code>
so that, for example, a system identified with the URI <code>&lt;http://example.org/system/a&gt;</code> claiming to
conform to a specification or functional profile identified by URI &lt;SPEC_OR_PROFILE_URI&gt; would do so like this:
</p>
Expand All @@ -2071,11 +2070,9 @@ <h4>Demonstrating system conformance to Functional Profiles</h4>
the URI <code>http://www.w3.org/ns/dx/conneg/profile/qsa-alt</code>, identified as per
<a href="#functional-profiles-definition"></a>.
</p>
<pre id="system-conforming"
<div id="system-conforming"
class="codelisting nohighlight" aria-busy="false" aria-live="polite"
title="An example Web Service claiming conformance to the QSA Alternate Keywords Functional Profile of this specification">
<div class="codelisting-title">
<a href="#system-conforming">CODE LISTING 2</a>: An example Web Service claiming conformance to the QSA Alternate Keywords
title="An example Web Service claiming conformance to the QSA Alternate Keywords Functional Profile of this specification"><div class="codelisting-title"><a href="#system-conforming">CODE LISTING 2</a>: An example Web Service claiming conformance to the QSA Alternate Keywords
Functional Profile of this specification
</div>
&lt;http://example.com/service/xx>
Expand All @@ -2097,7 +2094,7 @@ <h4>Demonstrating system conformance to Functional Profiles</h4>
# a human- and machine-readable documentation endpoint for the service using the
# Swagger UI system
dcat:endpointDescription &lt;http://example.com/service/v2/xx/swagger> ;
</pre>
</div>
</section>
<section id="altr-detail">
<h3>Alternate Representations Data Model - Details</h3>
Expand All @@ -2113,12 +2110,9 @@ <h4>Implementations</h4>
below in <a href="#altr-owl">Code Listing 3</a>. It is also available in the file
<a href="altr.ttl">altr.ttl</a>.
</p>
<pre id="altr-owl"
<div id="altr-owl"
class="codelisting nohighlight" aria-busy="false" aria-live="polite"
title="Alternate Profiles Data Model as an OWL ontology">
<div class="codelisting-title">
<a href="#altr-owl">CODE LISTING 3</a>: Alternate Profiles Data Model as an OWL ontology
</div>
title="Alternate Profiles Data Model as an OWL ontology"><div class="codelisting-title"><a href="#altr-owl">CODE LISTING 3</a>: Alternate Profiles Data Model as an OWL ontology</div>
@prefix altr: &lt;http://www.w3.org/ns/dx/conneg/altr#> .
@prefix dct: &lt;http://purl.org/dc/terms/> .
@prefix owl: &lt;http://www.w3.org/2002/07/owl#> .
Expand Down Expand Up @@ -2214,7 +2208,7 @@ <h4>Implementations</h4>
skos:scopeNote "In the context of this mode, use this class to indicate
instances of information models that representations of
resources can conform to." .
</pre>
</div>
</section>
<section id="altr-extensions">
<h4>Extensions</h4>
Expand All @@ -2227,13 +2221,10 @@ <h4>Extensions</h4>
represented in OWL in <a href="#altr-owl">Code Listing 4</a>. <a href="#eg-altr-ext"></a> gives an example of this
extended model's use following on from the content in <a href="#eg-altr"></a>.
</p>
<pre id="altr-ontology-ext-1"
<div id="altr-ontology-ext-1"
class="codelisting nohighlight" aria-busy="false" aria-live="polite"
title="Alternate Profiles Data Model as an OWL ontology">
<div class="codelisting-title">
<a href="#altr-ontology-ext-1">CODE LISTING 4</a>: Suggested extension to this specification's Alternate Profiles Data Model in OWL to
cater for Media Type representations
</div>
title="Alternate Profiles Data Model as an OWL ontology"><div class="codelisting-title"><a href="#altr-ontology-ext-1">CODE LISTING 4</a>: Suggested extension to this specification's Alternate Profiles Data Model in OWL to
cater for Media Type representations</div>
@prefix ex: &lt;http://example.org/altr-ext#> .
@prefix dct: &lt;http://purl.org/dc/terms/> .
@prefix owl: &lt;http://www.w3.org/2002/07/owl#> .
Expand Down Expand Up @@ -2267,7 +2258,7 @@ <h4>Extensions</h4>
dct:source "http://purl.org/dc/terms/MediaType" ;
skos:scopeNote "In the context of this mode, use this class to indicate
the IANA Media Type of a resource's representation." .
</pre>
</div>
<pre id="eg-altr-ext"
class="example nohighlight" aria-busy="false" aria-live="polite"
title="Extended implementation of the Alternative Profiles data model in RDF (turtle) showing Media Type information">
Expand Down Expand Up @@ -2397,12 +2388,9 @@ <h2>Describing DCAT Distributions support of Content Negotiation by Profile</h2>
Note that DCAT 2 provides no canonical means to specify if a data service allows individual data items in the dataset it provides access to, to be accessed by identifier, so this example relates to the dataset distributed as a whole. The use of <code>dct:conformsTo</code> would nevertheless apply to data services which declare a mechanism to access individual items. This mechanism may be identified via the <code>dcat:endpointDescription</code>.
</p>
<div class="issue" data-number="1146"></div>
<pre id="dcat-example"
<div id="dcat-example"
class="codelisting nohighlight" aria-busy="false" aria-live="polite"
title="Example of describing a dataset supporting Conneg-by-P in DCAT">
<div class="codelisting-title">
<a href="#dcat-example">CODE LISTING 5</a>: Describing a DCAT Data Service supporting Content Negotiation by Profile
</div>
title="Example of describing a dataset supporting Conneg-by-P in DCAT"><div class="codelisting-title"><a href="#dcat-example">CODE LISTING 5</a>: Describing a DCAT Data Service supporting Content Negotiation by Profile</div>
@prefix ex: &lt;http://example.org#> .
@prefix dcat: &lt;http://www.w3.org/ns/dcat#> .
@prefix dct: &lt;http://purl.org/dc/terms/> .
Expand Down Expand Up @@ -2435,7 +2423,7 @@ <h2>Describing DCAT Distributions support of Content Negotiation by Profile</h2>
# Declare that the Dataset may be invoked by URI, its id, using Content
# Negotiation by Profile
dcat:endPointURL :aDataset .
</pre>
</div>
</section>
</section>
<script class="remove" src="config.js"></script>
Expand Down

0 comments on commit 5ad47a6

Please sign in to comment.