Cary:
Yeah, I figured your simplified example was extremely, well, simple.  After
my post I realized that you're the author of "Optimizing Oracle
Performance."  http://www.oreilly.com/catalog/optoraclep/index.html
I was wondering why an Oracle guru would want to change the object's state
just to denote whether it's been read.
I am very much a neophyte, and have received some wonderful help in these
newsgroups, whether through replies to my posts, or just lurking and reading
other people's questions, and the responses they receive.  So I try to
answer an easy question or two a week, to give back to the group.  At first
glance your question seemed like an easy one.

Since you don't know the what the list looks like at authorship-time, can
you pass in a parameter to your stylesheet at run-time and just do the
<xsl:template> bit from my post?  I would be very interested in an outline
of your solution.

I've been fortunate so far in that I generate both the XML and XSL for my
apps.  And now that the client I work for has finally upgraded their Oracle
from 8.0 to 9i, I am looking forward to sinking my teeth into XML inside the
database.  Up until now I've had my packages generate my XML through
frelling string concatenation.

Thank you for your time,
Dave


"Cary Millsap" <cary.millsap@h...> wrote in message
news:10bvqcp7p41d153@c......
> Dave,
>
> Thank you. My situation is complicated in such a manner that this solution
> won't work as well as I'd like. The list L is supplied from an external
> source, so I don't have the luxury of authorship-time knowledge of what L
> looks like. I have figured out a recursive solution, though, in spite of
> that. If anyone's interested, respond to this posting, and I can post an
> outline of how it works.
>
> Cary
>
>
> "David Carnes" <davidc@N...> wrote in message
> news:uR3m3nXSEHA.3988@t......
> > Cary:
> > I think <xsl:template> and <xsl:apply-templates> will work for you.
> >
> > Given this XML:
> > <data>
> >   <thing name="a"/>
> >   <thing name="d"/>
> >   <thing name="a"/>
> > </data>
> >
> > ...and this XSL:
> > <xsl:stylesheet version="1.0"
> > xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> >  <xsl:output method='text' indent='yes' omit-xml-declaration='yes' />
> >   <xsl:template name="data" match="data">
> >     <xsl:apply-templates select="thing[@name='a']"/>
> >     <xsl:apply-templates select="thing[@name!='a']"/>
> >   </xsl:template>
> >
> >   <xsl:template match="thing[@name='a']">
> >     thing 1
> >   </xsl:template>
> >
> >   <xsl:template match="thing[@name!='a']">
> >     thing 2
> >   </xsl:template>
> >   </xsl:stylesheet>
> >
> > ...will yield:
> >
> >     thing 1
> >
> >     thing 1
> >
> >     thing 2
> >
> > I leave the implementation up to you.  Have fun!
> > Oh, BTW, download Xselerator; it's a great tool.
> > http://www.marrowsoft.com/
> >
> > Ciao,
> > Dave
> >
> >
> > "Cary Millsap" <cary.millsap@h...> wrote in message
> > news:10bs84hh6vspd63@c......
> > > I have a list L that contains values that are @name attribute values
in
> > > elements of the input document. In my application, I need to traverse
L,
> > > processing input document elements whose @name attribute values match
> > items
> > > from L. However, L doesn't contain all the names in the input
document.
> > > Therefore, when I'm finished traversing L, I need to walk the input
> > document
> > > to process all the elements that weren't processed during the
traversal
> of
> > > L. (There's a simplified example below my signature.)
> > >
> > > I can think of two ways to approach this problem, but I'm not sure
which
> > is
> > > a more elegant XSL answer (or even if a way I'm not considering would
be
> a
> > > smarter way to go):
> > >
> > > a) Attach an @has-been-processed attribute to the input document
> elements
> > as
> > > they're processed during the pass through L. (Is it even possible to
do
> > this
> > > in XSL?)
> > >
> > > b) Whenever I process a set of elements in the input document, append
> > those
> > > elements' @id values in a separate data structure and then (somehow
that
> I
> > > have yet to figure out) add a predicate that says "...and the
element's
> > @id
> > > value is not in the already-processed list."
> > >
> > > Thank you very much for your advice.
> > >
> > >
> > > Cary Millsap
> > >
> > >
> > > Simplified example:
> > >
> > > - L contains the names "a" and "b".
> > > - Input document contains the following elements:
> > >     <thing name="a" .../>
> > >     <thing name="d" .../>
> > >     <thing name="a" .../>
> > >
> > > Step 1: For each element in L, process the input document's elements
> with
> > > that name. This pass will pick up the two 'a' elements. (I have
figured
> > out
> > > already how to avoid emitting anything for 'b', since it is not
> > represented
> > > in the input document.)
> > > Step 2: For the input document elements that are left over, process
> those
> > > elements. This pass will pick up the 'd' element that was not
addressed
> in
> > > Step 1.
> > >
> > >
> >
> >
>
>