Generlizing 19b to allow nested skos collections
authorDave Reynolds <dave@epimorphics.com>
Fri, 08 Mar 2013 13:48:36 +0000
changeset 367 fd984093d4e1
parent 366 d750a9a276e5
child 368 d394eeeb9bf4
Generlizing 19b to allow nested skos collections
data-cube/index.html
--- a/data-cube/index.html	Fri Mar 08 13:46:34 2013 +0000
+++ b/data-cube/index.html	Fri Mar 08 13:48:36 2013 +0000
@@ -2066,10 +2066,10 @@
 definition of the code list as well as the Data Cube to be checked. In the case
 of a <code>skos:ConceptScheme</code> then each concept must be linked to the scheme using
 <code>skos:inScheme</code>. In the case of a <code>skos:Collection</code> then the
-collection must link to each concept using <code>skos:member</code> (i.e. if the
+collection must link to each concept or nested collection using <code>skos:member</code> (i.e. if the
 collection uses <code>skos:memberList</code> then the entailment of <code>skos:member</code>
 values defined by <a href="http://www.w3.org/TR/2009/REC-skos-reference-20090818/#S36">S36</a>
-in [[!SKOS-REFERENCE]] must be materialized).</p>
+in [[!SKOS-REFERENCE]] must be materialized). </p>
 
 <table class="bordered-table">
   <tbody>
@@ -2089,7 +2089,7 @@
         qb:codeList ?list .
     ?list a skos:Collection .
     ?obs ?dim ?v .
-    FILTER NOT EXISTS { ?list skos:member ?v }
+    FILTER NOT EXISTS { ?list skos:member+ ?v }
 }
     </td></pre></tr>
   </tbody>