- From: Antoine Isaac <Antoine.Isaac@KB.nl>
- Date: Tue, 24 Feb 2009 08:38:28 +0100
- To: "Pat Hayes" <phayes@ihmc.us>, <public-esw-thes@w3.org>
- Message-ID: <68C22185DB90CA41A5ACBD8E834C5ECD053E12C1@goofy.wpakb.kb.nl>
Dear Pat, Thank you for taking the time to report on this. That's much appreciated! Indeed we certainly want to avoid any misleading. I propose to rewrite the sentence as: [ In particular, there is no logical dependency between skos:inScheme and owl:imports: the use of owl:imports will not result in the presence of any skos:inScheme statements other than the ones already asserted in the imported graph." ] Do you think that would be better? Best regards, Antoine -------- Message d'origine-------- De: public-esw-thes-request@w3.org de la part de Pat Hayes Date: lun. 23/02/2009 18:27 À: public-esw-thes@w3.org Objet : misleading sentence in the SKOS primer The excellent "SKOS Primer" has one sentence in it which may be misleading. When discussing owl:imports, it states: "In particular, there is no logical dependency between skos:inScheme and owl:imports: the use of owl:imports will not result in the presence of any additional skos:inScheme statements." Well, no. It might, if the imported file itself contained some skos:inScheme statements. What is meant here, as becomes clear when one follows the example given, is that if A imports B, then the triples in B should not be counted as being skos:inScheme in scheme A. A minor point, but it caught my attention because when I read this for the first time (carelessly) it seemed like SKOS was denying the OWL semantics for owl:imports. Pat Hayes ------------------------------------------------------------ IHMC (850)434 8903 or (650)494 3973 40 South Alcaniz St. (850)202 4416 office Pensacola (850)202 4440 fax FL 32502 (850)291 0667 mobile phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes
Received on Tuesday, 24 February 2009 07:39:10 UTC