- From: Ivan Herman <ivan@w3.org>
- Date: Fri, 13 Jul 2007 11:01:38 +0200
- To: Ben Adida <ben@adida.net>
- Cc: RDFa <public-rdf-in-xhtml-tf@w3.org>, SWD WG <public-swd-wg@w3.org>
- Message-ID: <46973F72.9010908@w3.org>
Ben Adida wrote: > > Hi all, > > Today, we discussed the @src attribute on IMG, though as pointed out by > Shane we should consider what happens on SCRIPT, STYLE, and OBJECT, too. > Let's attempt to approach this generically, where X in {SCRIPT, STYLE, > OBJECT, IMG}. > Just to be pedantic: in the case of <object> we are talking about the @data and not @src, right? > > The remaining question is what to do for contained content inside > <OBJECT>. <SCRIPT> and <STYLE> can't contain HTML elements, so we don't > need to worry about them right now. > > Since the contents of <OBJECT> are typically parameters given to the > object, nothing that is rendered, I propose that we postpone this > decision, effectively not parsing RDFa inside <OBJECT>. I can see > arguments both ways for setting @src as the subject or not, and I'd > rather not bias the future of RDFa one way or the other. > Actually, your argument is not correct. My standard usage of <object> is as an alternative image representation for an svg element. <object data="xxx.svg" ...> <img src="xxx.png"/></object> to give an image alternative if the browser cannot handle SVG... I am not sure what the best solution is, and we may leave it open, but I see a valid case where I want to add additional triples to the contained elements... Ivan > Thoughts? > > -Ben > -- Ivan Herman, W3C Semantic Web Activity Lead URL: http://www.w3.org/People/Ivan/ PGP Key: http://www.cwi.nl/%7Eivan/AboutMe/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Friday, 13 July 2007 14:19:36 UTC