Subject: RE: Questions on the new XSL spec (section 2.6) From: David Schach <davidsch@xxxxxxxxxxxxx> Date: Wed, 30 Dec 1998 17:41:28 -0800 |
Comments and questions below. > -----Original Message----- > From: James Clark [SMTP:jjc@xxxxxxxxxx] > Sent: Monday, December 28, 1998 9:52 PM > To: xsl-list@xxxxxxxxxxxxxxxx > Subject: Re: Questions on the new XSL spec (section 2.6) > > Steve Dahl wrote: > > > > In section 2.6, the new pattern rules seem confusing to me: > > > > Can '.', '..', ancestor(), ancestor-or-self(), and id() appear in > > match patterns, or only in select patterns? > > Yes. > > > What does it mean when they occur in a match pattern, if that's > > permitted? > > See 2.6.2 under Matching, second paragraph. These are kind of confusing > when used as match patterns; one case is definitely useful: > [David] - Can you be more specific. What does it mean to use ancestor in a match pattern? > id("foo") > > matches an element with ID "foo". > > > Can these patterns appear in a SubtreeExpr? In other words, can they > > appear as a "child" of another pattern? For example, is > > 'a/b/ancestor(c)/d' a permitted pattern? > > Yes. > [David] - This construct is not permitted in the Microsoft XSL implementation. The ancestor must be on the left side of the /. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Questions on the new XSL spec (, James Clark | Thread | Re: Questions on the new XSL spec (, James Clark |
Re: Questions on the new XSL spec (, James Clark | Date | Re: How do In preserve '<' and '>' , James Clark |
Month |