Skip to content

Commit

Permalink
Added citation keys for cited specs
Browse files Browse the repository at this point in the history
  • Loading branch information
@andrea-perego
andrea-perego committed Jan 26, 2019
1 parent 5261d93 commit 2c93571
Showing 1 changed file with 12 additions and 12 deletions.
24 changes: 12 additions & 12 deletions ucr/index.html
View file
Expand Up @@ -315,9 +315,9 @@ <h2>Responses can conform to multiple, modular profiles [ID3]</h2>
</p>
<p>
Similarly, the response of a server can conform to multiple profiles.
For example, a profile X could demand that all persons are described with the FOAF vocabulary,
For example, a profile X could demand that all persons are described with the [[FOAF]] vocabulary,
and a profile Y could demand that all books are described with the Schema.org vocabulary.
Then, a response which uses FOAF for people and Schema.org for books,
Then, a response which uses [[FOAF]] for people and [[SCHEMA-ORG]] for books,
clearly conforms to both profiles.
And in contrast to content types,
it is informative to list both profiles,
Expand Down Expand Up @@ -2284,13 +2284,13 @@ <h2>Vocabulary constraints [ID41]</h2>
<li> what dependencies exist between elements of the vocabulary</li>
<li> etc.</li>
</ul>
<p>It would be ideal if the profile could be translated into a validation language (such as ShEx or SHACL). If not, it should at least be able to link to such a language.</p>
<p>It would be ideal if the profile could be translated into a validation language (such as [[ShEx]] or [[SHACL]]). If not, it should at least be able to link to such a language.</p>
</p>
<p class="existing_approaches">
<ul>
<li><a href="http://dublincore.org/documents/dc-dsp/">Dublin Core Description Set Profiles</a> - This has many of the needed factors, but not the dependencies</li>
<li><a href="http://shex.io">Shape Expressions</a> - a validation language.</li>
<li>SHACL Shapes Constraint Language - a validation language [[SHACL]]</li>
<li>[[DCDSP]]]] has many of the needed factors, but not the dependencies</li>
<li>Shape Expressions [[ShEx]] - a validation language.</li>
<li>Shapes Constraint Language [[SHACL]] - a validation language</li>
<li><a href="https://github.com/SEMICeu/dcat-ap_shacl/">OWL/SHACL expression for European DCAT-AP v1.1</a> </li>
</ul>
</p>
Expand Down Expand Up @@ -2570,7 +2570,7 @@ <h2>Profile relation to validation [ID48]</h2>
</p>
<p>
There needs to be a way to coordinate the profile and the validation function. This could be a matter
of basing the profile on a defined validation language (SHACL or ShEx or Schematron...), or of deriving
of basing the profile on a defined validation language ([[SHACL]] or [[ShEx]] or [[SCHEMATRON]]...), or of deriving
the validation rules from the profile. Note, though, that the existing validation languages are quite
atomistic and so far there has not been a demonstration of creating a usable profile from a validation language.
In any case, the relationship between these two related languages needs to be clarified.
Expand All @@ -2583,7 +2583,7 @@ <h2>Profile relation to validation [ID48]</h2>
</li>
<li>BIBFRAME Profiles: <a href="http://www.loc.gov/bibframe/docs/bibframe-profiles.html#grammar">Grammar</a>
</li>
<li> <a href="http://shex.io">ShEx</a>
<li> [[ShEx]]
</li>
<li> [[SHACL]]
</li>
Expand Down Expand Up @@ -2906,7 +2906,7 @@ <h2>Qualitative information</h2>
<section class="requirement" id="RUN">
<h3>Usage notes [RUN]</h3>
<p>Ability to provide information on how to use the data.</p>
<p class="note">Should this also apply to specific distributions?</p>
<p class="ednote">Should this also apply to specific distributions?</p>
<p class="relatedRequirements">
<!-- <a href="#RPFL"></a> -->
<a href="#RDSAT"></a>
Expand Down Expand Up @@ -3432,7 +3432,7 @@ <h3>Global rules for descriptive content [RPGRDC]</h3>

<section class="requirement" id="RPFVALID">
<h3>Data validation [RPFVALID]</h3>
<p>A profile may be (partially) "implemented" by "schemas" (in OWL, SHACL, XML Schema...) that allow different levels of data validation</p>
<p>A profile may be (partially) "implemented" by "schemas" (in [[OWL-REF]], [[SHACL]] [[XMLSCHEMA11-1]]...) that allow different levels of data validation</p>
<p class="relatedUseCases"><a href="#ID37"></a></p>
<span class="source"><a target="_blank" href="https://github.com/w3c/dxwg/issues/273">github:issue/273</a></span>
<div class="note">This requirement, which is a bit redundant
Expand Down Expand Up @@ -3498,14 +3498,14 @@ <h2>Profiles &#8212; Profile distributions</h2>
<h3>Profile documentation [RPFDOCU]</h3>
<p>A profile should have human-readable documentation that expresses for humans the main components
of a profile, which can also be available as machine-readable resources (ontology or schema files,
SHACL files, etc). This includes listing of elements in the profile, instructions and recommendations
[[SHACL]] files, etc). This includes listing of elements in the profile, instructions and recommendations
on how to use them, constraints that determine what data is valid according to the profile, etc.</p>
<span class="source"><a target="_blank" href="https://github.com/w3c/dxwg/issues/272">github:issue/272</a></span>
</section>

<section class="requirement" id="RPFSCHEMAS">
<h3>Schema implementations [RPFSCHEMAS]</h3>
<p>Profiles may be written in or may link to a document or schema in a validation language (ShEx, SHACL, XMLschema).</p>
<p>Profiles may be written in or may link to a document or schema in a validation language ([[ShEx]], [[SHACL]], [[XMLSCHEMA11-1]]).</p>
<p class="relatedRequirements"><a href="#RPFVALID"></a></p>
<p class="relatedUseCases"><a href="#ID41"></a></p>
<span class="source"><a target="_blank" href="https://github.com/w3c/dxwg/issues/279">github:issue/279</a></span>
Expand Down

0 comments on commit 2c93571

Please sign in to comment.