Subject: Re: [xsl] modeling relationships for efficent XSL processing|
From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 26 Feb 2004 12:03:18 -0500
At 2004-02-26 07:13 -0800, James A. Robinson wrote:So I've got databases which don't depend on anything, features which depend on a database type, and sites which depend on features and the specific database of the type required by the each feature. I find myself wanting to model things using XPATH notation:
But just how flexible do you need these XPath addresses to be?
Could you say:
and then within the handling of require_db hardwire the rest of the XPath:
Could you say:
<ref_database dbserver="oracle1" dbname="wsj_subscribers"/>
and then within the handling of ref_database hardwire the rest of the XPath:
<xsl:value-of select="/dbservers/dbserver[@name=current()/@dbserver]/ /dbname[@name=current()/@dbname]"/>
That way you would have an element type for each of your (I suspect limited set of) possible XPath hardwired addresses where the soft components needed for lookup are supplied as attributes of the element.
But it would only work if you did, indeed, have a limited set of possible XPaths and it was not totally generalizable.
I hope this helps.
-- US XSL training: Washington,DC March 15; San Francisco,CA March 22 World-wide on-site corporate, government & user group XML training G. Ken Holman mailto:gkholman@xxxxxxxxxxxxxxxxxxxx Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995) Male Breast Cancer Awareness http://www.CraneSoftwrights.com/s/bc
|<- Previous||Index||Next ->|
|Re: [xsl] modeling relationships fo, G. Ken Holman||Thread||Re: [xsl] modeling relationships fo, James A. Robinson|
|Re: [xsl] Unable to resolve the XSL, Agnes Kielen||Date||Re: [xsl] Embedded Xsl, Dipesh Khakhkhar|