Re: [xsl] Where is 'intersect' Operator Defined in XPath 3?

Subject: Re: [xsl] Where is 'intersect' Operator Defined in XPath 3?
From: "Christophe Marchand cmarchand@xxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 17 Aug 2022 07:01:57 -0000
Waouh ! This quickRef, and others in the same folder are just marvelous !

Thanks for this pointer, Wendell, and congrats to all authors !

Please, on which license are these materials shared ?

Best regards,
Christophe

Le 15/08/2022 C  16:34, Wendell Piez wapiez@xxxxxxxxxxxxxxx a C)critB :
> Friends, I am coming in late (after a week by scenicB Lake Otsego, 
> without email), with apologies --
>
> Of course, the solution is an updated QuickRef such as Mulberry's 
> Quick References (back in the day), and yes, good examples of this 
> kind of thing are works of art. I hesitate to mention this only 
> because I am not volunteering to do any actual work this time. :-)
>
> But a hand-held printable "Dungeon master's guide" cheat sheet to go 
> with whatever Norm is working on, would be fantabulous (wouldn't it)?
>
> BTW to this day most XPathers do not know you can do 
> key('a',@b)/key('c',@d) ... for this reason a good Quick Ref has examples
>
> https://mulberrytech.com/quickref/xpath2.pdf (by Sam, me, Debbie and 
> Tommie?) - evidently, both page-printable and online-browsable forms 
> present actual design problems. Think about how it should look on a 
> handheld device, for example.
>
> Cheers, Wendell
>
>
>
>
> On Fri, Aug 12, 2022 at 3:36 AM Norm Tovey-Walsh ndw@xxxxxxxxxx 
> <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>     > In my abundant ignorance of the editorial process I assumed that at
>     > least each function (nd other component) of the language would
>     have a
>     > few paras of explanation; but specifically would occupy
>     something like
>     > a <sect*> to itself at some level, with the name of the function in
>     > the <title>, or perhaps as the xml:id.B  It is then trivial to list
>     > them all, with a view to indexing, checking, assigning to
>     > subcommittees, etc. But perhaps I have been working with structured
>     > document systems for too long :-)
>
>     Thatbs certainly the case, therebs a lot of valuable information
>     in the
>     markup that we can use to improve access to the specs.
>
>     B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  Be seeing you,
>     B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  B  norm
>
>     --
>     Norman Tovey-Walsh <ndw@xxxxxxxxxx>
>     https://nwalsh.com/
>
>     > Science is not a tradition, it is the organized use of evidence from
>     > the real world to make inferences about the real worldbmeaning
>     the real
>     > universe, which is, in Carl Saganbs words, all that is, or ever
>     was, or
>     > ever will be.--Richard Dawkins
>
>
>
> -- 
> ...Wendell Piez... ...wendell -at- nist -dot- gov...
> ...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org...
> ...github.com/wendellpiez. <http://github.com/wendellpiez.>.. 
> ...gitlab.coko.foundation/wendell...
> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/2837134> 
> (by email <>)

Current Thread