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

RE: Accessing values from another sub-tree

Subject: RE: Accessing values from another sub-tree
From: "Vun Kannon, David" <dvunkannon@xxxxxxxx>
Date: Thu, 7 Jan 1999 17:13:51 -0500
kannon david
	I thought so. Of course href is then a misnomer. The unfortunate
thing is that the source document becomes littered with id attributes on all
the elements which are in effect the full navigation path (to preserve
uniqueness) to that element. I am forced into naming with ids instead of
pointing with references. "Where to go" is not "How to get there". What gets
lost in that, for example, is the fact that the key part href is a local
reference, which used to be explicit. I think we need uri() as James Clark
described generalising it (so it can subsume the functionality of id() as
well), and wouldn't it be nice to agree on a syntax in the bargain.
Cheers,
David vun Kannon

> -----Original Message-----
> From:	David Schach [SMTP:davidsch@xxxxxxxxxxxxx]
> Sent:	Thursday, January 07, 1999 2:28 PM
> To:	'xsl-list@xxxxxxxxxxxxxxxx'
> Subject:	RE: Accessing values from another sub-tree
> 
> Yes, this can be accomplished within the XSL spec. If you change your data
> so that it uses id/idrefs then you do not need the follow() function.
> I've
> highlighted the attributes that should become ididrefs. For example,
> 
> 	<Class name="Customer">
> 		<Property name="FirstName" datatype="String"/>
> 		<Property name="LastName" datatype="String"/>
> 		<Property name="CustID" datatype="Integer"/>
> 		<Key primary="true">
> 			<Part href="CustID'" />
> 	</Key>
> 
> 	<Class name="Address">
> 		<Property name="Street" datatype="String"/>
> 		<Property name="City" datatype="String"/>
> 		<Property name="ZIP" datatype="String"/>
> 		<Property name="State" datatype="String"/>
> 		<Key primary="true">
> 			<Part href="../Property/@name='Zip'" />
> 			<Part href="../Property/@name='Street'" />
> 		</Key>
> </Class>
> 	...
> 	<Association name="AccessibleAt">
> 		<AssociationEnd href="Customer'" role="theCustomer"
> 	cardinality="*"/>
> 		<AssociationEnd href="Address'" role="theAddress"
> 	cardinality="*"/>
> </Association>
> 
> Then the XSL becomes
> 				<xsl:for-each
> select="id(@href)/Key[@primary='true']/Part">
> 
> Note: This feature is not available in the IE5b2 but it will be available
> in
> the final release of IE5.  
> 


 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.