Skip to content

Commit

Permalink
fixing broken HTML identified by HTML validator
Browse files Browse the repository at this point in the history
  • Loading branch information
Nicholas Car committed Mar 27, 2019
1 parent de8090c commit c98defa
Showing 1 changed file with 19 additions and 19 deletions.
38 changes: 19 additions & 19 deletions profilesont/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -41,12 +41,14 @@ <h2>Introduction</h2>
development was triggered by the appearance of multiple profiles of the Dataset Catalog Vocabulary (DCAT)
[[VOCAB-DCAT-20140116]] and examples of profiles including the Guidelines for Dublin Core Application Profiles [[DCAP]] and various profiles of OpenGeospatial Consortium specifications.
</p>
<p>The Profiles Vocabulary is an RDF vocabulary to describe the resources that define and implement a profile. A profile is defined as "A named set of constraints on one or more identified base specifications or other profiles, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function." These resources may be human-readable documents (PDFs, textual documents), vocabularies or ontologies (XSD, RDF), resources specific to validation tools (SHACL, ShEx, Schematron), or any other files or resources that support the profile. Each resource is defined as having a role that defines its function within the profile.
<p>
The Profiles Vocabulary is an RDF vocabulary to describe the resources that define and implement a profile. A profile is defined as "A named set of constraints on one or more identified base specifications or other profiles, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function." These resources may be human-readable documents (PDFs, textual documents), vocabularies or ontologies (XSD, RDF), resources specific to validation tools (SHACL, ShEx, Schematron), or any other files or resources that support the profile. Each resource is defined as having a role that defines its function within the profile.
</p>
This vocabulary also provides for the description of relationships between such profiles and the standards to which they conform. A standard in this case can be a vocabulary or it can be another profile from which the described profile is a derivation, expansion, or selection. This vocabulary provides a standardized, machine readable formalism for describing the context of profiles. The basis of this vocabulary is a specialization of <code><a href="http://www.dublincore.org/documents/dcmi-terms/#terms-Standard">dct:Standard</a></code>, allowing the use of the <code><a href="http://www.dublincore.org/documents/dcmi-terms/#terms-conformsTo">dct:conformsTo</a></code> predicate to specify conformance to a profile.
<p>
This vocabulary also provides for the description of relationships between such profiles and the standards to which they conform. A standard in this case can be a vocabulary or it can be another profile from which the described profile is a derivation, expansion, or selection. This vocabulary provides a standardized, machine readable formalism for describing the context of profiles. The basis of this vocabulary is a specialization of <code><a href="http://www.dublincore.org/documents/dcmi-terms/#terms-Standard">dct:Standard</a></code>, allowing the use of the <code><a href="http://www.dublincore.org/documents/dcmi-terms/#terms-conformsTo">dct:conformsTo</a></code> predicate to specify conformance to a profile.
</p>
A "profile" here is represented by the <a href="#Class:Profile">Profile class definition</a> in the
<a href="#specification">Vocabulary Specification</a> with the following definition: "A named set of constraints on one or more identified base specifications or other profiles, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function."
<p>
A "profile" here is represented by the <a href="#Class:Profile">Profile class definition</a> in the <a href="#specification">Vocabulary Specification</a> with the following definition: "A named set of constraints on one or more identified base specifications or other profiles, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function."
</p>
<p>
Profiles aim to increase interoperability within a community of users by introducing
Expand Down Expand Up @@ -358,7 +360,7 @@ <h4>Class: Profile</h4>
<tr><td class="prop">Source:</td><td><a href="https://www.w3.org/2017/dxwg/wiki/ProfileContext">https://www.w3.org/2017/dxwg/wiki/ProfileContext</a></td></tr>
</tbody>
</table>
<div class=issue" data-number="521"></div>
<div class="issue" data-number="521"></div>
<section id="Property:hasResource" class="property">
<h4>Property: hasResource</h4>
<table class="definition">
Expand Down Expand Up @@ -687,7 +689,6 @@ <h4>Class: ResourceRole</h4>
<tr><td class="prop">Sub class of:</td><td><a href="https://www.w3.org/TR/skos-reference/#Concept">skos:Concept</a></td></tr>
<tr><td class="prop">Usage note:</td><td>Specific terms must come from a vocabulary. Such a vocabulary is provided alongside this ontology and that list is extensible: <a href="https://w3c.github.io/dxwg/profilesont/resource_roles.html">Resource Roles Vocabulary</a></td></tr>
</tbody>
</a>
</table>
<div class="issue" data-number="452"></div>
</section>
Expand Down Expand Up @@ -1569,19 +1570,18 @@ <h2>Security and Privacy</h2>
</section>
<section id="changes" class="informative">
<h2>Changes</h2>
<p>Changes since the <a href="https://www.w3.org/TR/2018/WD-dx-prof-20181218/">First Public Working Draft</a> are:
<ul>
<li>Removed BaseSpecification class (<a href="https://github.com/w3c/dxwg/issues/641">Issue 641</a>)</li>
<li>Changed name to Profiles Vocabulary (<a href="https://github.com/w3c/dxwg/issues/758">Issue 758</a>)</li>
<li>Added a set of common roles to the vocabulary (<a href="https://github.com/w3c/dxwg/issues/758">Issue 758)</a></li>
<li>Improved introduction to clarify scope</li>
<li>Improved examples (<a href="https://github.com/w3c/dxwg/issues/658">Issue 658</a>)</li>
<li>Improved diagrams (<a href="https://github.com/w3c/dxwg/issues/697">#697</a>, <a href="https://github.com/w3c/dxwg/issues/689">#689</a>, <a href="https://github.com/w3c/dxwg/issues/731">#731</a>)</li>
</ul>
</p>
<p>
A <em>comments disposition document</em> is in preparation and will be available from the <a href="https://www.w3.org/2017/dxwg/wiki/Main_Page">Data Exchange Working Group</a> home page.
</p>
<p>Changes since the <a href="https://www.w3.org/TR/2018/WD-dx-prof-20181218/">First Public Working Draft</a> are:</p>
<ul>
<li>Removed BaseSpecification class (<a href="https://github.com/w3c/dxwg/issues/641">Issue 641</a>)</li>
<li>Changed name to Profiles Vocabulary (<a href="https://github.com/w3c/dxwg/issues/758">Issue 758</a>)</li>
<li>Added a set of common roles to the vocabulary (<a href="https://github.com/w3c/dxwg/issues/758">Issue 758)</a></li>
<li>Improved introduction to clarify scope</li>
<li>Improved examples (<a href="https://github.com/w3c/dxwg/issues/658">Issue 658</a>)</li>
<li>Improved diagrams (<a href="https://github.com/w3c/dxwg/issues/697">#697</a>, <a href="https://github.com/w3c/dxwg/issues/689">#689</a>, <a href="https://github.com/w3c/dxwg/issues/731">#731</a>)</li>
</ul>
<p>
A <em>comments disposition document</em> is in preparation and will be available from the <a href="https://www.w3.org/2017/dxwg/wiki/Main_Page">Data Exchange Working Group</a> home page.
</p>
</section>
<section class="appendix" id="appendices">
<h2>Appendices</h2>
Expand Down

0 comments on commit c98defa

Please sign in to comment.