- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 27 Feb 2009 23:49:18 +0100
- To: Ben Adida <ben@adida.net>
- CC: noah_mendelsohn@us.ibm.com, Henri Sivonen <hsivonen@iki.fi>, Mark Nottingham <mnot@mnot.net>, HTMLWG WG <public-html@w3.org>, RDFa mailing list <public-rdf-in-xhtml-tf@w3.org>, public-xhtml2@w3.org, "www-tag@w3.org WG" <www-tag@w3.org>
Ben Adida wrote: > Julian Reschke wrote: >>> how @rel is interpreted. You can't interpret @rel blindfolded. >> But I'd like to. > > I don't think RDFa is the technology that's stopping you here. The > existing state of the web and HTML is already preventing it. > >> WRT profile; I see how this can work for a single profile URI, but it >> does not scale, so I'm not sure how this is supposed to help with mixing >> relations from several profiles (namespaces) in a single document. > > Far be it from me to defend the @profile approach to web-scale data :) > But, to be fair, @profile does allow for a space-separated list of values. Yes, but how does this help in this case? If I have <head profile="http://example.com/ http://example.org/"> and <a rel="foobar"> ...how do I find out which profile/namespace foobar belongs to? It doesn't solve the disambiguation problem. >> No, that's fine. What's controversial is how many different >> language-dependent interpretations there should be for the HTML family >> of languages. I think that number needs to be 1. > > I would love to see that happen, too. That's why we're working hard with > the HTML5 team to try to convince them :) I think it would be easier to convince them if you wouldn't have unilaterally changed the semantics for the rel attribute (note that I have less problems with CURIEs in *new* attributes). Best regards, Julian
Received on Friday, 27 February 2009 22:50:05 UTC