- From: Liam R E Quin <liam@w3.org>
- Date: Fri, 14 Jun 2013 16:58:34 -0400
- To: public-xmlhypermedia@w3.org
On Fri, 2013-06-14 at 19:31 +0000, Rushforth, Peter wrote: > XLink starts there and gets a lot more complicated, which in itself is a problem. > It offers many features that are useful to few applications, and few features > that are useful to many applications. The two "killer" features for XLink are (1) being as easy as html (href), and (2) link templates, so that I can declare that <qv ref="newton-sir-isaac">Sir Isaac Newton</qv> is a link to "../n/newton-sir-isaac.html" XLink actually has neither of these. I can't say that the longdesc attribute on an img element is a link, for example. Even on a small site like words.fromoldbooks.org, though, it would cost me real money to move from HTML to XML today. So the XML stays server side and I serve up XHTML with embedded adverts, which I can't do in XML (no equivalent of <script type="text/javascript" src="googleads.js" />) Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
Received on Friday, 14 June 2013 20:58:36 UTC