Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Merge pull request #201 from aisaac/gh-pages
Changes in Vocab section to implement resolutions to ISSUE-166
  • Loading branch information
aisaac committed Sep 24, 2015
2 parents db1852c + 1133626 commit 2ab1b5b
Showing 1 changed file with 14 additions and 14 deletions.
28 changes: 14 additions & 14 deletions bp.html
Expand Up @@ -1524,13 +1524,13 @@ <h3>Data Vocabularies</h3>
allows applications to localize their display of their search
depending on the language of the user. </p>
<p>According to W3C, <a href="http://www.w3.org/standards/semanticweb/ontology">vocabularies</a>
define the concepts and relationships (also referred to as “terms”)
define the concepts and relationships (also referred to as “terms” or “attributes”)
used to describe and represent an area of concern. Vocabularies are
used to classify the terms that can be used in a particular
application, characterize possible relationships, and define possible
constraints on using those terms. Several categories of vocabularies
have been coined, for example, ontology, controlled vocabularies,
thesaurus, taxonomy, semantic network.</p>
have been coined, for example, ontology, controlled vocabulary,
thesaurus, taxonomy, code list, semantic network.</p>
<p>There is no strict division between the artifacts referred to by
these names. “Ontology” tends however to denote the vocabularies of
classes and properties that structure the descriptions of resources in
Expand Down Expand Up @@ -1563,15 +1563,15 @@ <h3>Data Vocabularies</h3>
be used to provide metadata</p>
<section class="axioms">
<p class="subhead">Why</p>
<p>The need for standardized terms for describing metadata is to
<p>The need for code lists and other commonly used terms for describing metadata is to
avoid as much as possible ambiguity and clashes in the terms
chosen for metadata information. The key reason is to be able to
refer to the standardized body/organization which defines the term
refer to the standardized body/organization which defines the term or code
as a clear reference.</p>
<p></p>
<section class="outcome">
<p class="subhead">Intended Outcome</p>
<p>The benefit of using standardized terms is to enable
<p>The benefit of using standardized code lists and other commonly used terms is to enable
interoperability and consensus among data publishers and
consumers. </p>
<p></p>
Expand All @@ -1590,7 +1590,7 @@ <h3>Data Vocabularies</h3>
</aside>
</section>
<section class="test"><span style="font-weight: bold;">How to Test </span>
<p>Check that the terms to be used are defined in a standard
<p>Check that the terms or codes to be used are defined in a standard
organization/working group of body such as IETF, OGC, W3C, etc.</p>
<p></p>
<section class="ucr">
Expand All @@ -1601,7 +1601,7 @@ <h3>Data Vocabularies</h3>
</section>
</div>
<!-- begin of Document Vocabularies -->
<div class="practice">
<!--<div class="practice">
<p><span id="DocumentVocabularies" class="practicelab"> Document
vocabularies </span></p>
<p class="practicedesc">Vocabularies <em class="rfc2119">should</em>
Expand Down Expand Up @@ -1642,10 +1642,10 @@ <h3>Data Vocabularies</h3>
<p><span>Relevant requirements</span>: <a href="http://www.w3.org/TR/dwbp-ucr/#R-VocabDocum">R-VocabDocum</a>
</p>
</section>
</div>
</div>-->
<!-- end of Document Vocabularies BP -->
<!-- begin of Share Open Vocabularies BP -->
<div class="practice">
<!--<div class="practice">
<p><span id="ShareOpenVocabularies" class="practicelab"> Share
vocabularies in an open way </span></p>
<p class="practicedesc"> Vocabularies <em class="rfc2119">should</em>
Expand Down Expand Up @@ -1683,10 +1683,10 @@ <h3>Data Vocabularies</h3>
<p class="subhead">Evidence</p>
<p><span>Relevant requirements</span>: <a href="http://www.w3.org/TR/dwbp-ucr/#R-VocabOpen">R-VocabOpen</a></p>
</section>
</div>
</div>-->
<!-- end of Share Open Vocabularies BP -->
<!-- begin of Versioning Vocabularies BP -->
<div class="practice">
<!--<div class="practice">
<p><span id="VersioningVocabularies" class="practicelab"> Vocabulary
versioning </span></p>
<p class="practicedesc">Vocabularies <em class="rfc2119">should</em>
Expand Down Expand Up @@ -1730,7 +1730,7 @@ <h3>Data Vocabularies</h3>
<p><span>Relevant requirements</span>:<a href="http://www.w3.org/TR/dwbp-ucr/#R-VocabVersion">R-VocabVersion</a>
</p>
</section>
</div>
</div>-->
<!-- end of BP -->
<!-- begin of re-use Vocabularies BP -->
<div class="practice">
Expand Down Expand Up @@ -1761,7 +1761,7 @@ <h3>Data Vocabularies</h3>
</section>
<section class="test">
<p class="subhead">How to Test</p>
<p>Check that terms used do not replicate those defined by
<p>Check that terms or attributes used do not replicate those defined by
vocabularies in common use within the same domain.</p>
<!--
<p>Verify whether for any new vocabulary developed an analog reference one may already be publicly available on the Web.</p> <ol> <li>Vocabularies Search tools: <a href="http://ws.nju.edu.cn/falcons/objectsearch/index.jsp"> Falcons</a>, <a href="http://watson.kmi.open.ac.uk/WatsonWUI/">Watson</a>, <a href="http://sindice.com/">Sindice</a>, <a href="http://swoogle.umbc.edu/">Swoogle</a>, <a href="http://vocab.org">vocab.org</a> or others</li> <li>Vocabularies Repositories: <a href="http://lov.okfn.org/dataset/lov/">LOV</a>, <a href="http://bioportal.bioontology.org/">BioPortal</a>, and <a href="https://joinup.ec.europa.eu/catalogue/repository">JoinUp</a>; </li> <li>Inventories: <a href="http://www.w3.org/standards/">W3C Standards</a> or domain-specific inventories like this <a href="http://www.w3.org/2005/Incubator/lld/XGR-lld-vocabdataset/">Library Linked Data Incubator Group report</a>. </li> </ol> <p>Verify that when no analog reference vocabulary may already be available at least core elements from base vocabularies, such as the <a href="http://dublincore.org/documents/dcmi-terms/">DCMI Metadata Terms</a>, <a href="http://xmlns.com/foaf/spec/">FOAF</a>, <a href="http://rdfs.org/sioc/spec/">SIOC</a>, <a href="http://www.w3.org/TR/vcard-rdf/">vCard</a>, the <a href="http://www.w3.org/ns/locn">Location Core Vocabulary</a>, the <a href="http://www.w3.org/2003/01/geo/wgs84_pos">W3C WGS84 Geo Positioning vocabulary</a> or the <a href="http://creativecommons.org/ns">Creative Commons Rights Expression Language</a>, are re-used instead of re-defined.</p> -->
Expand Down

0 comments on commit 2ab1b5b

Please sign in to comment.