Hi Scott,

XML is great for representing hierarchical data structures,
so why use strings to do the same job? If possible, I suggest
you change the input document format to be something like:

<masterdoc> 
  <namespace name="System"> 
    <class name="Object"/> 
    <class name="Array"/> 
    <namespace name="Collections"> 
      <class name="ArrayList"/> 
      <class name="Comparer"/> 
      <namespace name="Overkill"> 
        <class name="Grimey"/> 
      </namespace> 
    </namespace> 
    <namespace name="Runtime"> 
      <namespace name="Serialization"> 
         <class name="Formatter"/> 
      </namespace> 
      <namespace name="Remoting"> 
         <class name="ObjectHandle"/> 
      </namespace> 
    </namespace> 
  </namespace> 
  <namespace name="Other"> 
    <namespace name="SubAPI"> 
      <class name="Garbage"/> 
    </namespace> 
  </namespace> 
</masterdoc> 

This will make you problem considerably easier to solve.

Regards,

Dan.

-- 
Danny Yates
Technical Architect
Abbey National Treasury Services
E-mail: Danny.Yates@[...].uk
Phone: +44 20 7612 4017
Fax: +44 20 7612 4342


-----Original Message-----
From: Scott Bronson [mailto:bronson@[...].com]
Sent: 14 October 2002 10:36
To: xsl-list@[...].com
Subject: [xsl] Hierearchy navigation in XSL


Hello.  I've solved most of this problem, but the last tiny bit has me
stumped.  I'm hoping someone can tell me how to fix this.

Here's some input:


<masterdoc> 
  <class name="Object"       namespace="System"/> 
  <class name="Array"        namespace="System"/> 
  <class name="ArrayList"    namespace="System.Collections"/> 
  <class name="Comparer"     namespace="System.Collections"/> 
  <class name="Grimey"       namespace="System.Collections.Overkill"/> 
  <class name="Formatter"    namespace="System.Runtime.Serialization"/> 
  <class name="ObjectHandle" namespace="System.Runtime.Remoting"/> 
  <class name="Garbage"      namespace="Other.SubAPI"/> 
</masterdoc> 


My script accepts a parameter that tells where it is in the hierarchy. 
It then outputs all immediate child nodes at that level in the
hierarchy.

Some examples: if we're at "System", the script should output
"Collections" and "Runtime".  If we're at "System.Collections", it
should output "Overkill".  If we're at "", it should output "System" and
"Other".  If at "Other", output "SubAPI".  Seems a fairly easy problem,
right?



Here's my script right now:


<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0"> 
<xsl:output method="text"/> 
<xsl:param name="ns"/> 
<xsl:key name='uniq' match='class' use='@namespace'/> 

<xsl:template match="/masterdoc"> 
  <xsl:for-each
select="class[generate-id()=generate-id(key('uniq',@namespace)[1])]"> 
    <xsl:sort select="@namespace"/> 
    <xsl:choose> 
      <xsl:when test="string-length($ns)=0"> 
        <xsl:value-of select="@namespace"/> 
      </xsl:when> 
      <xsl:when test="starts-with(@namespace,concat($ns,'.'))"> 
        <xsl:value-of
select="substring(@namespace,string-length($ns)+2)"/> 
      </xsl:when> 
    </xsl:choose> 
<xsl:text> 
</xsl:text> 
  </xsl:for-each> 
</xsl:template> 

</xsl:stylesheet> 



Here are some example runs of this script:

xalan -Q -XSL samp1.xsl -IN sample.xml -PARAM ns "'System.Collections'"
Overkill

xalan -Q -XSL samp1.xsl -IN sample.xml -PARAM ns "'System'"
Collections
Collections.Overkill
Runtime.Remoting
Runtime.Serialization


The last one illustrates the problem.  It should have output only
"Collections" and "Runtime".

I picture the algorithm being something like:
   if(not(already copied string-before("Runtime.Remoting", "."))
      then copy string-before("Runtime.Remoting", ".") to output

I've tried various combinations of preceding, preceding sibling, and
position to try to figure out what I've already output.  I even tried
key() and using IDs to navigate the parent.  All has resulted in
frustration.

Does anyone have any idea of what I can do?  I'm out of ideas.

Thank you!

    - Scott





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


***************************************************************************
This communication (including any attachments) contains confidential information.  If you ar
e not the intended recipient and you have received this communication in error, you should d
estroy it without copying, disclosing or otherwise using its contents.  Please notify the se
nder immediately of the error.

Internet communications are not necessarily secure and may be intercepted or changed after t
hey are sent.  Abbey National Treasury Services plc does not accept liability for any loss y
ou may suffer as a result of interception or any liability for such changes.  If you wish to
 confirm the origin or content of this communication, please contact the sender by using an 
alternative means of communication.

This communication does not create or modify any contract and, unless otherwise stated, is n
ot intended to be contractually binding.

Abbey National Treasury Services plc. Registered Office:  Abbey National House, 2 Triton Squ
are, Regents Place, London NW1 3AN.  Registered in England under Company Registration Number
: 2338548.  Regulated by the Financial Services Authority (FSA).
***************************************************************************


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