clarifying working of qb:HCL in response to Franck Cotton comments
authorDave Reynolds <dave@epimorphics.com>
Fri, 12 Apr 2013 16:51:00 +0100
changeset 455 62edc0d49759
parent 453 edc70db3377c
child 456 2d325bab0d34
clarifying working of qb:HCL in response to Franck Cotton comments
data-cube/index.html
--- a/data-cube/index.html	Fri Apr 12 08:03:53 2013 +0100
+++ b/data-cube/index.html	Fri Apr 12 16:51:00 2013 +0100
@@ -1319,8 +1319,11 @@
 <p>Thus a <code><a>qb:HierarchicalCodeList</a></code>
 is similar to a <code>skos:ConceptScheme</code> in which <code><a>qb:hierarchyRoot</a></code> plays the same
 role as <code>skos:hasTopConcept</code>, and the value of <code><a>qb:parentChildProperty</a></code> plays
-the same role as <code>skos:narrower</code>.  In the case where a code list is already available as a SKOS concept scheme or collection
-then those SHOULD be used directly;  <code><a>qb:HierarchicalCodeList</a></code> is provided for cases where the
+the same role as <code>skos:narrower</code>.  In the case where a code
+  list is already available as a SKOS concept scheme or collection, or
+  could reasonable me made so, then those SHOULD be used
+  directly. <code><a>qb:HierarchicalCodeList</a></code> is provided
+  for cases where the 
 terms are not available as SKOS but are available in some other RDF representation suitable for reuse.
 </p>