- From: Sjoerd Visscher <sjoerd@w3future.com>
- Date: Thu, 09 Jun 2005 10:13:25 +0200
- To: Dan Brickley <danbri@w3.org>
- CC: public-rdf-in-xhtml-tf@w3.org, www-html@w3.org
Dan Brickley wrote: > On Wed, 2005-06-08 at 20:27 +0200, Sjoerd Visscher wrote: >>How about using N3? For example: >> >><div >> id="titanic" >> properties="label:hasClassification age:twelve; foo:duration bar:015"> >> <span property="dc:title" class="title">Titanic</span> >> <a href="titanic.mov">See the movie</a> >></div> >> >>The syntax would be that of N3, starting at rule "propertylist": >>http://www.w3.org/2000/10/swap/grammar/n3-report.html#propertylist > > > Interesting idea, but I don't think it will fly. Creating > micro-syntaxes inside attribute values is tempting, but with each > step it takes us away from the world of generic XML processing (XSLT, > XPath, DOM etc). XML simply doesn't have "complex type" attributes, it's something we have to live with. I think it worked out very well in previous cases: XPath in XSLT and Path data in SVG (or even the style attribute in HTML) And in this case there are more advantages: - It might be a choice between having information in a micro-syntax, or not having the information at all. - N3 already seems to be the preferred syntax for RDF It's not that hard to create a complete N3 document from a "properties" attribute (add namespace prefix declarations, set the base uri, prefix the value of the about attribute in <> and append a dot.) Then use N3 tools to either get the triples or RDF/XML. -- Sjoerd Visscher http://w3future.com/weblog/
Received on Thursday, 9 June 2005 08:13:55 UTC