- From: Antoine Isaac <aisaac@few.vu.nl>
- Date: Fri, 6 Jan 2012 15:55:39 +0100
- To: <public-esw-thes@w3.org>
On 1/6/12 3:45 PM, Sean Bechhofer wrote: > > On Jan 4, 2012, at 6:09 PM, Antoine Isaac wrote: > >> Dear Dominique, >> >>> >>> Le 4 janv. 2012 à 15:26, Antoine Isaac a écrit : >>> >>> I'm currently developing a little thesaurus management web application, this point is important for me too >>> >>>> Indeed, the original idea is that the vocabulary providers would start publish assertions with skos:broader/narrower. >>> >>> Who do you call the "vocabulary providers" ? >> >> >> Sorry, "publisher of SKOS data" is maybe clearer. >> >> >>> If I'm creating a SKOS thesaurus from scratch, using a web GUI that allows me to state either kind of relation, and I know that two concepts have a broaderTransitive relation, what prevents me in the SKOS specification to qualify this relation directly as broaderTransitive ? >> >> >> Well, nothing prevents you from doing that, but then you have lost some information. Despite the property names, asserting a skos:broader is indeed *more precise* than asserting a skos:broaderTransitive. Because the former implies the latter (mathematically speaking, the skos:broaderTransitive is the transitive closure of the skos:broader relation, http://en.wikipedia.org/wiki/Transitive_closure) > > Not quite. The definitions give us that skos:broaderTransitive _includes_ the transitive closure of skos:broader, but it's not an equivalence. > Agreed, well spotted, Sean. Luckily, this should not change anything to my "Because the former implies the latter" :-) Antoine
Received on Friday, 6 January 2012 14:51:06 UTC