I took a look at this - very similar in nature, but I'm still trying to
translate my intent into the vocabulary you are using...

I will probably move ahead with what I am doing now...though I'm open to a
merge in the future. The only caveat is that I intend my work for donation
if it is accepted...

> ----------
> From:         Simon St.Laurent[SMTP:[EMAIL PROTECTED]]
> Reply To:     [EMAIL PROTECTED]
> Sent:         Friday, May 10, 2002 9:19 AM
> To:   [EMAIL PROTECTED]
> Cc:   Stefano Mazzocchi
> Subject:      Re: A Transformer in progress....
> 
> Regular Fragmentations does _most_ of this:
> http://regfrag.sourceforge.net/
> 
> The rules vocabulary is described at:
> http://simonstl.com/ns/fragments/
> 
> The one key pieces that's missing is the XPath support, which I've been 
> planning for a while but haven't gotten to building.  I've been building a
> 
> new and more flexible object model (http://moe.sourceforge.net/) to use 
> with RegFrag, but hopefully...
> 
> At 02:10 PM 5/10/2002 +0200, Stefano Mazzocchi wrote:
> >"Lewis, Andrew J" wrote:
> > >
> > > > I'm working on a Transformer that processes specifically text nodes
> and
> > > > using regular expressions, wraps matched portions of a node in a
> tag. I'm
> > > > really just getting started on it - I have the basics working, but
> still
> > > > need to be able to specify the rules in an external file, etc. It
> has 
> > been
> > > > an interesting excercise so far, and the intent is to be able to
> detect
> > > > things like dates, currency amounts, and units of measure in a text
> node,
> > > > and mark them for later processing.
> > > >
> > > > I am planning on allowing rules to be specified in an external file
> > > > identified at componenet configuration, or directly in the component
> > > > configuration. I am also planning on allowing the "replacement" to
> be a
> > > > complete fragement with groups from the matched expression
> referencable
> > > > (and replaced) in etiher attribute values or text nodes. (currently
> I
> > > > merely enclose the match in a tag).
> > > >
> > > > Before I move on, has anyone else already done something like this?
> Does
> > > > anyone (other than me) think it would be useful?
> > > >
> > > > Ok...now to my real question...
> > > >
> > > > Does anyone know of existing code that I can use to track and
> identify if
> > > > the current point in the SAX stream matches a simplified XPath 
> > expression?
> > > > I would really like to apply expression rule set based on an XPath 
> > subset.
> > > >
> > > > Any comments or suggestions?
> > > >
> > > > Thanks!
> >
> >I know that Simon wrote a SAX filter along the lines of this, right
> >Simon?
> >
> >I think it's going to be piece of cake to take his stuff and make it a
> >cocoon transformer.
> >
> >--
> >Stefano Mazzocchi      One must still have chaos in oneself to be
> >                           able to give birth to a dancing star.
> ><[EMAIL PROTECTED]>                             Friedrich Nietzsche
> >--------------------------------------------------------------------
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, email: [EMAIL PROTECTED]
> 
> Simon St.Laurent
> Associate Editor
> O'Reilly & Associates, Inc.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to