• To: xml-dev@l...
• Subject: Re: Type-based design patterns
• From: Norman Walsh <ndw@n...>
• Date: Thu, 03 Oct 2002 07:09:45 -0400
• In-reply-to: <001f01c26ab3$c3517160$6401a8c0@pcukmka> ("Michael Kay"'smessage of "Thu, 3 Oct 2002 09:06:22 +0100")
• References: <001f01c26ab3$c3517160$6401a8c0@pcukmka>
• User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.1 (i686-pc-linux-gnu)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

/ "Michael Kay" <michael.h.kay@n...> was heard to say:
|> As I think about 2 though, I'm struck that I'm going to need 
|> the equivalent of "next-match" in order for it to be useful.
|> 
|
| I think you're probably right. Interestingly, "next-match" is about the
| only requirement on the XSLT 2.0 requirements list that we haven't yet
| tackled.

Yep. One of a small number of things I actually *wanted* in XSLT 1.x/2.0...
I think I even wrote a proposal for it, I'll go dig through the archives, I guess.

                                        Be seeing you,
                                          norm

- -- 
Norman.Walsh@S...    | Man's great misfortune is that he has no
XML Standards Architect | organ, no kind of eyelid or brake, to mask or
Sun Microsystems, Inc.  | block a thought, or all thought, when he
                        | wants to.--Valéry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE9nCV5OyltUcwYWjsRAg2DAKCbV3klFqn4QG8oYn+QpmQwJYlLwACfZgGY
aP1c69uUEN4mB/2FgTdThBU=
=hb7O
-----END PGP SIGNATURE-----

• References:
  • RE: Type-based design patterns
    • From: "Michael Kay" <michael.h.kay@n...>

• Prev by Date: RE: xsd validation was RE: XPath/XSLT 2.0 concerns
• Next by Date: RE: xsd validation was RE: XPath/XSLT 2.0 concerns
• Previous by thread: RE: Type-based design patterns
• Next by thread: Re: Type-based design patterns
• Index(es):
  • Date
  • Thread