- From: Oliver Becker <obecker@informatik.hu-berlin.de>
- Date: Wed, 4 Feb 2004 10:55:59 +0100 (MET)
- To: mhk@mhk.me.uk, davidc@nag.co.uk
- Cc: public-qt-comments@w3.org
David,
> Basing the model for regexp matching on that of template matching
> was the basic idea of an early post of mine to this list (or rather, its
> predecessor) before the drafts had any usable regexp support at all.
>
> http://lists.w3.org/Archives/Public/xsl-editors/2002JanMar/0083.html
Ah, I see. Excellent contribution.
My recent improvement proposal matches your V3. The priority would by
implicitely given by the order of the xsl:matching-substring elements,
so an extra priority attribute is not necessary.
> Actually once the current draft mechanism was introduced, although it
> seemed to be simpler I could do most of my use cases just as well,
> although sometimes explictly requiring more passes,
Of course you are right that the current draft allows already regular
expression matching and replacing. I simply believe that instead of this
rather cumbersome
<xsl:analyze-string select= regex= >
<xsl:matching-substring>
...
</>
<xsl:non-matching-substring>
<xsl:analyze-string select="." regex= >
<xsl:matching-substring>
...
</>
<xsl:non-matching-substring>
<xsl:analyze-string select="." regex= >
etc
</>
</>
</>
</>
</>
the syntax could be slightly changed and thus in this case strongly simplified.
(See also your use cases RE-4, RE-7)
I am not requesting a generally new feature, just a simple adjustment
of the current draft. I think it is worth to consider this idea.
Cheers,
Oliver
/-------------------------------------------------------------------\
| ob|do Dipl.Inf. Oliver Becker |
| --+-- E-Mail: obecker@informatik.hu-berlin.de |
| op|qo WWW: http://www.informatik.hu-berlin.de/~obecker |
\-------------------------------------------------------------------/
Received on Wednesday, 4 February 2004 04:57:41 UTC