- From: Mark Birbeck <mark.birbeck@x-port.net>
- Date: Thu, 12 Jul 2007 16:02:47 +0100
- To: "Ben Adida" <ben@adida.net>
- Cc: RDFa <public-rdf-in-xhtml-tf@w3.org>, "SWD WG" <public-swd-wg@w3.org>
Hi Ben, Back already! I'll be on the call. :) > Before you run off to your meeting..... a few questions here. > > > * @href does NOT set the subject for nested statements. > > I don't get this last point. I know you're opposed to it, but I > explained how it could work and why it makes sense. What do you think is > wrong with this approach? At the moment, I'm not totally sure, but it is a major change, and it was the main cause of problems in my original drafts, so it would need a lot more thought than simply saying it looks ok. > >> 4) @rel everywhere > >> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jul/0057 > > > > > > This is tricky. > > I've not gone into detail on this, but I don't like @rel everywhere, > > Ummm, but it was *your* proposal originally :) That wouldn't be the first time. :) I have proposed many things that I've gone back on, such as using @class for rdf:type, and having @href set the subject of the contained elements to mention but a few. ;) > > If we don't > > have @href everywhere then I think we don't need this > > But we do, for bnodes and striping, as per your proposal, right? Yes...that's what pains me. :) And also @rev is so handy that I can see it being used even with @resource. Which all taken together is why I said I won't be arguing against keeping it. Regards, Mark -- Mark Birbeck, formsPlayer mark.birbeck@x-port.net | +44 (0) 20 7689 9232 http://www.formsPlayer.com | http://internet-apps.blogspot.com standards. innovation.
Received on Thursday, 12 July 2007 15:02:53 UTC