This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: xlink implementation - html link choice
- From: "Mark Wonsil" <wonsil at 4m-ent dot com>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Thu, 23 May 2002 11:06:44 -0400
- Subject: RE: [xsl] xlink implementation - html link choice
- Reply-to: xsl-list at lists dot mulberrytech dot com
Michael Kay writes:
> You don't need XLink to do this. Either client-side or
> server-side, you
> can write a stylesheet that constructs a menu containing all the links
> available and allows the user to click on any one of them,
> which in turn
> causes the relevant XML document to be rendered.
While this is true, would there be a benefit to using XLink syntax? E.g.
the role attribute could be used to render a document differently depending
on the device, the context attribute would tell the XSLT processor to
include JavaScript for a new browser window, etc.. Then when (if?) the time
comes that there is an XLink aware browser (well popular support anyway)
then you're all set.
Just wondering out loud...
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list