XSL-LIST Mailing List Archive by date - December, 2019

• Re: Re: [saxon] Questions about the `saxon:threads` extension attribute, Dimitre Novatchev dnovatchev@xxxxxxxxx - 29 Dec 2019 02:17:10 -0000
  
• Re: [saxon] Questions about the `saxon:threads` extension attribute, Michael Kay mike@xxxxxxxxxxxx - 28 Dec 2019 20:58:24 -0000
  
• Re: Re: [saxon] Questions about the `saxon:threads` extension attribute, Dimitre Novatchev dnovatchev@xxxxxxxxx - 28 Dec 2019 05:15:40 -0000
  
• Re: [saxon] Questions about the `saxon:threads` extension attribute, Michael Kay mike@xxxxxxxxxxxx - 28 Dec 2019 01:20:40 -0000
  
• Questions about the `saxon:threads` extension attribute, Dimitre Novatchev dnovatchev@xxxxxxxxx - 27 Dec 2019 05:18:31 -0000
  
• Re: Group handling of multiple IDREFS, Peter Flynn peter@xxxxxxxxxxx - 20 Dec 2019 01:30:18 -0000
  
• Re: Group handling of multiple IDREFS, Michael Kay mike@xxxxxxxxxxxx - 19 Dec 2019 23:50:51 -0000
  
• Group handling of multiple IDREFS, Peter Flynn peter@xxxxxxxxxxx - 19 Dec 2019 23:42:27 -0000
  
• Re: Suggestions for filtering algorithm, Rick Quatro rick@xxxxxxxxxxxxxx - 18 Dec 2019 16:32:55 -0000
  
• Re: Suggestions for filtering algorithm, Martin Honnen martin.honnen@xxxxxx - 18 Dec 2019 16:11:23 -0000
  
• Re: Suggestions for filtering algorithm, Rick Quatro rick@xxxxxxxxxxxxxx - 18 Dec 2019 15:29:50 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Trevor Nicholls trevor@xxxxxxxxxxxxxxxxxx - 18 Dec 2019 03:13:34 -0000
  
• Suggestions for filtering algorithm, Rick Quatro rick@xxxxxxxxxxxxxx - 18 Dec 2019 03:08:06 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Rolf Kleef rolf@xxxxxxxxxxx - 16 Dec 2019 14:43:52 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Christophe Marchand cmarchand@xxxxxxxxxx - 16 Dec 2019 10:43:09 -0000
  
• [no subject], Unknown - Mon Dec 16 00:25:18 2019
  
• Re: Running the same transformation on many input files, optimisation possible?, Michael Kay mike@xxxxxxxxxxxx - 16 Dec 2019 00:20:15 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 15 Dec 2019 23:00:42 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Michael Kay mike@xxxxxxxxxxxx - 15 Dec 2019 22:50:07 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 15 Dec 2019 22:35:21 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Michael Kay mike@xxxxxxxxxxxx - 15 Dec 2019 22:12:21 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx - 15 Dec 2019 19:31:12 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 15 Dec 2019 19:07:28 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 15 Dec 2019 17:49:37 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Graydon graydon@xxxxxxxxx - 15 Dec 2019 17:37:11 -0000
  
• Re: command line invocation issue, Andre Cusson akhu01@xxxxxxxxx - 15 Dec 2019 10:25:21 -0000
  
• Re: command line invocation issue, Pieter Masereeuw pieter@xxxxxxxxxxxx - 15 Dec 2019 10:11:06 -0000
  
• Re: command line invocation issue, Andre Cusson akhu01@xxxxxxxxx - 15 Dec 2019 10:00:22 -0000
  
• Re: command line invocation issue, Andre Cusson akhu01@xxxxxxxxx - 15 Dec 2019 09:48:00 -0000
  
• Re: Running the same transformation on many input files, optimisation possible?, Martin Honnen martin.honnen@xxxxxx - 15 Dec 2019 09:35:29 -0000
  
• Re: command line invocation issue, Martin Honnen martin.honnen@xxxxxx - 15 Dec 2019 09:25:49 -0000
  
• Running the same transformation on many input files, optimisation possible?, Trevor Nicholls trevor@xxxxxxxxxxxxxxxxxx - 15 Dec 2019 09:02:56 -0000
  
• Re: command line invocation issue, Dave Pawson dave.pawson@xxxxxxxxx - 15 Dec 2019 08:38:00 -0000
  
• command line invocation issue, Andre Cusson akhu01@xxxxxxxxx - 15 Dec 2019 08:21:45 -0000
  
• Re: XSLT code for XML to JSON conversion?, Richard Fozzard richard.fozzard@xxxxxxxx - 13 Dec 2019 22:50:40 -0000
  
• Re: XSLT code for XML to JSON conversion?, Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx - 13 Dec 2019 15:28:06 -0000
  
• Re: XSLT code for XML to JSON conversion?, Michael Kay mike@xxxxxxxxxxxx - 13 Dec 2019 10:26:57 -0000
  
• Re: XSLT code for XML to JSON conversion?, O'Neil Delpratt oneil@xxxxxxxxxxxx - 13 Dec 2019 10:11:44 -0000
  
• Re: XSLT code for XML to JSON conversion?, Steven D. Majewski steve.majewski@xxxxxxxxx - 12 Dec 2019 22:37:30 -0000
  
• Re: XSLT code for XML to JSON conversion?, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx - 12 Dec 2019 22:08:34 -0000
  
• XSLT code for XML to JSON conversion?, Richard Fozzard richard.fozzard@xxxxxxxx - 12 Dec 2019 21:31:53 -0000
  
• Re: Suggestion for handling an endless loop, Mark Giffin m1879@xxxxxxxxxxxxx - 11 Dec 2019 00:06:23 -0000
  
• Re: What are the possible vendor-options to pass to fn:transform() in the case of Saxon?, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx - 10 Dec 2019 02:34:12 -0000
  
• Re: What are the possible vendor-options to pass to fn:transform() in the case of Saxon?, Steven D. Majewski steve.majewski@xxxxxxxxx - 9 Dec 2019 20:55:27 -0000
  
• What are the possible vendor-options to pass to fn:transform() in the case of Saxon?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 9 Dec 2019 19:34:29 -0000
  
• Re: How to call an XSLT function whose name isn't known till run-time?, Michael Kay mike@xxxxxxxxxxxx - 8 Dec 2019 00:48:26 -0000
  
• Re: Aw: URI collection select?, Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx - 7 Dec 2019 23:23:04 -0000
  
• Aw: URI collection select?, Martin Honnen martin.honnen@xxxxxx - 7 Dec 2019 23:00:01 -0000
  
• URI collection select?, dvint@xxxxxxxxx - 7 Dec 2019 22:51:28 -0000
  
• Re: How to call an XSLT function whose name isn't known till run-time?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 7 Dec 2019 17:04:14 -0000
  
• Re: How to call an XSLT function whose name isn't known till run-time?, Michael Kay mike@xxxxxxxxxxxx - 7 Dec 2019 08:59:20 -0000
  
• Re: How to call an XSLT function whose name isn't known till run-time?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 7 Dec 2019 01:44:55 -0000
  
• Re: How to call an XSLT function whose name isn't known till run-time?, Michael Kay mike@xxxxxxxxxxxx - 6 Dec 2019 23:50:45 -0000
  
• Re: How to call an XSLT function whose name isn't known till run-time?, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx - 6 Dec 2019 20:13:15 -0000
  
• Re: best practices for using XSLT modes, Wendell Piez wapiez@xxxxxxxxxxxxxxx - 6 Dec 2019 19:46:15 -0000
  
• Re: How to call an XSLT function whose name isn't known till run-time?, Martin Honnen martin.honnen@xxxxxx - 6 Dec 2019 19:35:56 -0000
  
• Re: best practices for using XSLT modes, Eliot Kimber ekimber@xxxxxxxxxxxx - 6 Dec 2019 18:25:36 -0000
  
• Re: How to call an XSLT function whose name isn't known till run-time?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 6 Dec 2019 17:32:01 -0000
  
• Re: How to call an XSLT function whose name isn't known till run-time?, Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx - 6 Dec 2019 17:30:10 -0000
  
• Re: How to call an XSLT function whose name isn't known till run-time?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 6 Dec 2019 17:28:59 -0000
  
• How to call an XSLT function whose name isn't known till run-time?, Costello, Roger L. costello@xxxxxxxxx - 6 Dec 2019 17:20:52 -0000
  
• Re: best practices for using XSLT modes, Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx - 6 Dec 2019 17:13:15 -0000
  
• Re: best practices for using XSLT modes, Eliot Kimber ekimber@xxxxxxxxxxxx - 6 Dec 2019 15:53:48 -0000
  
• Re: best practices for using XSLT modes, Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx - 6 Dec 2019 15:00:06 -0000
  
• Re: user defined data elements in stylesheets, Mukul Gandhi gandhi.mukul@xxxxxxxxx - 6 Dec 2019 11:20:21 -0000
  
• Re: user defined data elements in stylesheets, Geert Bormans geert@xxxxxxxxxxxxxxxxxxx - 6 Dec 2019 11:11:35 -0000
  
• Re: user defined data elements in stylesheets, Martin Honnen martin.honnen@xxxxxx - 6 Dec 2019 11:05:49 -0000
  
• user defined data elements in stylesheets, Mukul Gandhi gandhi.mukul@xxxxxxxxx - 6 Dec 2019 10:55:42 -0000
  
• Re: best practices for using XSLT modes, Mukul Gandhi gandhi.mukul@xxxxxxxxx - 6 Dec 2019 05:42:29 -0000
  
• Re: best practices for using XSLT modes, Dimitre Novatchev dnovatchev@xxxxxxxxx - 5 Dec 2019 18:05:08 -0000
  
• Re: best practices for using XSLT modes, Eliot Kimber ekimber@xxxxxxxxxxxx - 5 Dec 2019 17:39:04 -0000
  
• Re: best practices for using XSLT modes, BR Chrisman brchrisman@xxxxxxxxx - 5 Dec 2019 16:48:36 -0000
  
• Re: best practices for using XSLT modes, John Lumley john@xxxxxxxxxxxx - 5 Dec 2019 16:34:31 -0000
  
• Re: best practices for using XSLT modes, Eliot Kimber ekimber@xxxxxxxxxxxx - 5 Dec 2019 14:50:58 -0000
  
• Re: best practices for using XSLT modes, Mukul Gandhi gandhi.mukul@xxxxxxxxx - 5 Dec 2019 05:54:37 -0000
  
• Re: best practices for using XSLT modes, Dimitre Novatchev dnovatchev@xxxxxxxxx - 4 Dec 2019 19:16:57 -0000
  
• Re: best practices for using XSLT modes, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx - 4 Dec 2019 19:00:08 -0000
  
• Re: best practices for using XSLT modes, Eliot Kimber ekimber@xxxxxxxxxxxx - 4 Dec 2019 18:42:17 -0000
  
• Re: best practices for using XSLT modes, Dimitre Novatchev dnovatchev@xxxxxxxxx - 4 Dec 2019 16:58:07 -0000
  
• Re: best practices for using XSLT modes, Michael Kay mike@xxxxxxxxxxxx - 4 Dec 2019 10:43:55 -0000
  
• Re: best practices for using XSLT modes, Mukul Gandhi gandhi.mukul@xxxxxxxxx - 4 Dec 2019 09:59:27 -0000
  
• Re: best practices for using XSLT modes, Martin Honnen martin.honnen@xxxxxx - 4 Dec 2019 06:51:04 -0000
  
• best practices for using XSLT modes, Mukul Gandhi gandhi.mukul@xxxxxxxxx - 4 Dec 2019 06:42:22 -0000
  
• Re: Why does this XPath expression work fine when run inOxygen but fails when used in an XSD 1.1 assert element?, Mukul Gandhi gandhi.mukul@xxxxxxxxx - 3 Dec 2019 06:22:22 -0000
  
• Re: current() and position()?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 3 Dec 2019 01:19:36 -0000
  
• Re: current() and position()?, David Birnbaum djbpitt@xxxxxxxxx - 2 Dec 2019 23:56:34 -0000
  
• Re: Why does this XPath expression work fine when run inOxygen but fails when used in an XSD 1.1 assert element?, Michael Kay mike@xxxxxxxxxxxx - 2 Dec 2019 18:40:59 -0000
  
• Re: Why does this XPath expression work fine when run in Oxygen but fails when used in an XSD 1.1 assert element?, Michael Kay mike@xxxxxxxxxxxx - 2 Dec 2019 18:12:51 -0000
  
• Re: Why does this XPath expression work fine when run inOxygen but fails when used in an XSD 1.1 assert element?, Costello, Roger L. costello@xxxxxxxxx - 2 Dec 2019 18:12:32 -0000
  
• Re: Why does this XPath expression work fine when run in Oxygen but fails when used in an XSD 1.1 assert element?, G. Ken Holman g.ken.holman@xxxxxxxxx - 2 Dec 2019 17:50:25 -0000
  
• Re: Why does this XPath expression work fine when run in Oxygen but fails when used in an XSD 1.1 assert element?, Graydon graydon@xxxxxxxxx - 2 Dec 2019 17:47:55 -0000
  
• Why does this XPath expression work fine when run in Oxygen but fails when used in an XSD 1.1 assert element?, Costello, Roger L. costello@xxxxxxxxx - 2 Dec 2019 17:26:32 -0000
  
• Re: current() and position()?, Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx - 2 Dec 2019 16:53:39 -0000
  
• Re: current() and position()?, Michael Kay mike@xxxxxxxxxxxx - 2 Dec 2019 08:11:34 -0000
  
• XSL-List Guidelines, Tommie Usdin btusdin@xxxxxxxxxxxxxxxx - 2 Dec 2019 04:56:26 -0000
  
• Re: current() and position()?, David Birnbaum djbpitt@xxxxxxxxx - 2 Dec 2019 04:07:49 -0000
  
• Re: current() and position()?, Dimitre Novatchev dnovatchev@xxxxxxxxx - 2 Dec 2019 03:41:08 -0000
  
• current() and position()?, David Birnbaum djbpitt@xxxxxxxxx - 2 Dec 2019 01:05:11 -0000