Mark Birbeck wrote: > Hi Ben, > >> The reason I'm a lot less comfortable with @href completing hanging >> triples is that, when a triple hangs, there's simply no way to write an >> @href inside that element and *not* have it complete the triple. Plus, >> there are relatively easy ways to write the same thing without @href >> completing hanging triples. > > Not wishing to preempt our discussion, but when I was replying to the > @rel="license" question earlier it struck me that in my model, @rel="" > would have the effect of preventing @href from completing any > incomplete triples: > > <div about="#ben" rel="foaf:knows"> > <a href="#ivan">Ivan</a> > <a rel="" href="next-page.html">Click here for more</a> > </div> > > Just a thought. :) > Is that correct? Well it is in the sense that the second @href is indeed switched off, but isn't it true that you would get a <#ben> foaf:knows [] . triple instead? The existence of @rel means that (in the second <a>) the [new subject] will be set to the BNode sent down from <div> (representing the hanging @rel) which will then complete it... I may be wrong, though. Ivan > Regards, > > Mark > -- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Thursday, 10 January 2008 15:43:20 UTC