Subject: Re: [xsl] Implementing XPointer Resolution Withsaxon:evaluate() From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Tue, 13 Aug 2002 19:13:55 -0400 |
> Yet if they contain all the same information, using a node-set extension > couldn't you query into them and find the further information you need to > continue along your chain?
No--I need the *the same node*, not a copy of the node.
That is, an XPointer addresses a thing and I need the resolution of that XPointer to return the thing, not a copy of the thing.
It's not about the information in the element, it's about the element itself. For example, I must be able to navigate from the element returned to its parent--I can't do this if what I get back is a copy of the node.
Cheers, Wendell
====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Implementing XPointer Res, Jeni Tennison | Thread | RE: [xsl] Implementing XPointer Res, Dion Houston |
Re: [xsl] Implementing XPointer Res, Jeni Tennison | Date | [xsl] position accross multiple nod, Jeff Barrett |
Month |