• To: 'xml-dev' <xml-dev@l...>
• Subject: Re: XPattern Specification
• From: Karl Waclawek <karl@w...>
• Date: Mon, 17 Jan 2005 09:18:36 -0500
• In-reply-to: <20050117121740.GB14403@m...>
• References: <20050116220239.GB10592@m...> <41EBAA9F.3080204@g...> <20050117121740.GB14403@m...>
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

Alan Gutierrez wrote:

> 
>     Hmm... Okay, sorry for the verbose example, it's what I'm
>     working on right now.
>     
>     The idea is that in order to place the exploaded element, I need
>     to select:
> 
>     /request/path-info/path/text()
> 
>     And I need to match:
> 
>     /request/path-info[path]
> 
>     Or maybe even:
> 
>     path[contains(text(), '/')]
> 
>     Which strikes me as resonable, but not, to my understanding, a
>     question of look *ahead*. More like look behind.

Why not just match on /request/path-info/path and process the
accumulated character data in the end-tag event for this element?
Isn't that simple enough?

Karl

• Follow-Ups:
  • Re: XPattern Specification
    • From: Alan Gutierrez <alan-xml-dev@e...>

• References:
  • XPattern Specification
    • From: Alan Gutierrez <alan-xml-dev@e...>
  • Re: XPattern Specification
    • From: Petr Cimprich <petr@g...>
  • Re: XPattern Specification
    • From: Alan Gutierrez <alan-xml-dev@e...>

• Prev by Date: Re: XPattern Specification
• Next by Date: Re: Embedded-Grammar&Components Design Approach [Was: A bunch of components, but no mandated organization - reasonable?]
• Previous by thread: Re: XPattern Specification
• Next by thread: Re: XPattern Specification
• Index(es):
  • Date
  • Thread