[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Style Matters - A class act

Subject: RE: Style Matters - A class act
From: "Didier PH Martin" <martind@xxxxxxxxxxxxx>
Date: Sat, 5 Feb 2000 14:40:42 -0500
david m when style matters
Hi David,

David said:
I'm of the opinion that a more general solution is the creation of a
set of Xlink elements during transformation. This set of links captures
exactly which nodes of the source document(s) influenced the creation of
exactly which nodes in the result. Ideally, I think this link document would
be a separate document from the source and result documents. Ideally, this
link document would be produced automatically by the XSL engine, via command
line switch or input parameter, because it is far easier for the engine to
do than for the stylesheet writer to do. Whenever the engine is about to
emit a result tree node, emit a link to the link fork/document/database
which specifies the context nodes from the source and the result nodes being
emitted.
	This will work between any XML sources and any XLinkable result. In
particular, a direct manipulation GUI needs to drill down through the
presentation layer to the semantic content over and over, traversing these
links to get at individual characters of content at times. In such usage
scenarios, industrial strength linking between source and result is a
necessity.

	I hope my suggestion of automatic link output is taken seriously by
XSLT engine authors. Even as a debugging tool, it would be valuable.

Didier replies:
In fact, when I wrote the article I got two things in mind:
a) debugging (as you mentionned)
b) the usage of templates (I am not taking here of XSLT templates but more
template as used by products like red dots, NCompass, GoLive, etc...)

In both cases, it is useful to have a back linkage from the result of the
transformation(i.e. rendition language) ito the original model (i.e. XML
document).

I agree, my suggestion to use the "class" attribute cannot be adapted to a
template matched to an attribute. Therefore, the usage of xlink is more
powerful since we can practically address any node. This is a very good
suggestion David. I'll keep it in my notebook.

Cheers
Didier PH Martin
----------------------------------------------
Email: martind@xxxxxxxxxxxxx
Conferences: Web New York (http://www.mfweb.com)
Book: XML Pro published by Wrox Press
Products: http://www.netfolder.com


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.