> CONSTRUCT > {?x skos:minimalBroader ?y} > > WHERE > { > ?x skos:broader ?z. > ?z skos:broader ?y. > FILTER (!bound(?z)) > } > I think you would want to do... CONSTRUCT { ?x skos:minimalBroader ?y } WHERE { ?x skos:broader ?y OPTIONAL { ?x skos:broader ?z . ?z skos:broader ?y . } FILTER (!bound(?z)) } ...? > The above computing can pinpoint those exceptions. And then up to the > vocabulary manager to figure if they are bugs or features ... This is a crucial point. In some vocabularies this could be a deliberate feature. Hence <http://www.w3.org/TR/2008/WD-skos-reference-20080609/#L2518>. Interesting idea... Cheers, Al. -- Alistair Miles Senior Computing Officer Image Bioinformatics Research Group Department of Zoology The Tinbergen Building University of Oxford South Parks Road Oxford OX1 3PS United Kingdom Web: http://purl.org/net/aliman Email: alistair.miles@zoo.ox.ac.uk Tel: +44 (0)1865 281993Received on Wednesday, 30 July 2008 10:11:41 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:39:00 GMT