W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > October 2008

Re: On the interpretation of match=

From: mozer <xmlizer@gmail.com>
Date: Sun, 5 Oct 2008 19:30:16 +0200
Message-ID: <21d9ade60810051030p3697f4ceofb53e700c7adcaea@mail.gmail.com>
To: "Florent Georges" <fgeorges@fgeorges.org>
Cc: "Norman Walsh" <ndw@nwalsh.com>, public-xml-processing-model-comments@w3.org

On Sun, Oct 5, 2008 at 7:18 PM, Florent Georges <fgeorges@fgeorges.org> wrote:
>
> 2008/10/5 Norman Walsh wrote:
>
>> I think the shortest argument why is that the BNF for an XSLT 2.0
>> Pattern[2] (which we call an XSLTMatchPattern and still need to cite a
>> little more carefully) cannot be empty.
>
>  I would second that for the same reason.

+1

>
>  But I have a little question about your example:
>
>>  <p:rename match="//item" new-name="foo"/>
>
>  Do we agree this is equivalent to the following? (note the descendent axis) :
>
>    <p:rename match="item" new-name="foo"/>

Sure : this is an XSLT Match Pattern !

>
>> The matched node is a comment and rename cannot
>> target comments.
>
>  About this example (matching a comment node), would it be an error
> if the match expression matched both comment and element nodes?

No I would be an error ONLY because it is matching a comment

If it was matching both an element and an PI then it would be ok

Xmlizer
Received on Sunday, 5 October 2008 17:30:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:25 UTC