Subscribe to the XSL-List Blog in XML format
RSS 2.0
Atom 0.3

The XSL-LIST Blog

The XSL-List Blog's mission is to increase the level of XSL knowledge and usage in the software development community. It's a service by Mulberry Technologies, and the list is by far the most popular XSL development forum in the world — in fact, some of the inventors of XSL hang out there and respond to questions. Got a stylesheet emergency? Want to contribute to the XSL community? visit the XSL-List blog today!


How to Parse String with Escaped XML Markup?

Posted 1/15/2021 2:57:55 PM

I researched this question in this list but I didn't find a recent response so I'm asking it again. My specific requirement is to take the value of an Oxygen deleted content processing instruction and parse it back into elements in the context of an XSLT 3 transform. The PI is: <?oxy_delete a . . . Read full entry »


Re: XPath expression to get the string following the o

Posted 1/14/2021 4:33:19 PM

I guess the problem is that this is an attribute value The parses all of that away, I am afraid The attribute value is abc the " would be gone after parsing attribute boundaries can be " or ' if you really need either " or ' and the difference is important, I am afraid you would nee . . . Read full entry »


Re: XPath expression to get the string following the o

Posted 1/14/2021 4:17:58 PM

On 14.01.2021 17:14, Roger L Costello costello@xxxxxxxxx wrote: Here are sample input strings: ="abc" = "abc" = "abc" That is, an equals, zero or more whitespaces, quote, value, quote I want everything after the first quote. My neural network thinks that sound . . . Read full entry »


XPath expression to get the string following the open

Posted 1/14/2021 4:14:00 PM

Hi Folks, Here are sample input strings: ="abc" = "abc" = "abc" That is, an equals, zero or more whitespaces, quote, value, quote I want everything after the first quote. What XPath expression yields the desired result? For all of the above inputs, the resu . . . Read full entry »


Re: XSLT repetition constructs comparison

Posted 1/14/2021 11:31:05 AM

On Thu, Jan 14, 2021 at 3:58 PM Martin Honnen martin.honnen@xxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Last, for the use with the variable, don't forget that > `xsl:perform-sort` can be directly applied to result constructed by > nested XSLT so you could also use > . . . Read full entry »


Re: XSLT repetition constructs comparison

Posted 1/14/2021 11:04:10 AM

On Thu, Jan 14, 2021 at 2:49 PM Michael Kay mike@xxxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > <xsl:iterate select="sort(student, (), function($s){$s/(fName, lName))">... > Thanks for this suggestion. I'll surely try this (at least to learn). or if . . . Read full entry »


Re: XSLT repetition constructs comparison

Posted 1/14/2021 10:28:38 AM

Am 14.01.2021 um 10:05 schrieb Mukul Gandhi mukulg@xxxxxxxxxxxxxxxxx: Hi all, B B I'm comparing the functionality of, XSLTB repetition constructs xsl:for-each and xsl:iterate (versions 2.0 & 3.0). Below is my example use case, and the corresponding XSLT solutions from my side, XML input docum . . . Read full entry »


Re: XSLT repetition constructs comparison

Posted 1/14/2021 9:19:30 AM

I would personally only use xsl:iterate where you need something that xsl:for-each can't do, such as early exit, or accumulation of parameter values. But an xsl:iterate with no parameters, no xsl:break, no xsl:on-completion is equivalent to xsl:for-each so there's no intrinsic reason to prefer one . . . Read full entry »


XSLT repetition constructs comparison

Posted 1/14/2021 9:05:29 AM

Hi all, I'm comparing the functionality of, XSLT repetition constructs xsl:for-each and xsl:iterate (versions 2.0 & 3.0). Below is my example use case, and the corresponding XSLT solutions from my side, XML input document: <?xml version="1.0"?> <students> <stude . . . Read full entry »


Re: xpath versions comparison

Posted 1/2/2021 3:01:18 PM

> > 1) XPath 2.0 has introduced sequences, > > right, and the nodes are now typed. > Thanks, for reminding me about this. That's also a fundamental change between XPath 1.0 and 2.0/3.1. Interestingly, for the non schema-aware variant of XPath 2.0, element nodes in the XPath data mo . . . Read full entry »


Re: xpath versions comparison

Posted 1/2/2021 7:44:48 AM

On Sat, 2021-01-02 at 06:01 +0000, Mukul Gandhi mukulg@xxxxxxxxxxxxxxxxx wrote: > Hi all, > B B B As we all know, currently we've following versions of XPath > language: > 1.0, 2.0 & 3.1. > > I've been trying to think that, what are the major differences > between the > . . . Read full entry »


xpath versions comparison

Posted 1/2/2021 6:00:07 AM

Hi all, As we all know, currently we've following versions of XPath language: 1.0, 2.0 & 3.1. I've been trying to think that, what are the major differences between the above mentioned XPath versions. Below are my thoughts, 1) Since XPath 2.0, the XPath data model has fundamentally change . . . Read full entry »


XSL-List Guidelines

Posted 1/1/2021 5:10:12 PM

This information is posted to the XSL-List (and the XSL-List Digest) at intervals under the subject line "XSL-List guidelines". INTRODUCTION TO XSL-LIST XSL-List hosts discussion of XSL itself, XSL applications and implementation, and XSL user questions. XSL-List is open to everyone, us . . . Read full entry »


Re: [ANN] upcoming courses on XSLT 3, Accessibility,

Posted 12/23/2020 2:32:58 PM

On 22.12.2020 01:33, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx wrote: Upcoming courses from Delightful Computing, delivered with live video from Pointy Bracket Farm in rural South-East Ontario... * XProc Three, it's the pipeline language for me! Three glorious, fabulous, wonderful days. Availab . . . Read full entry »


SciELO

Posted 12/22/2020 2:27:17 AM

Any luck on SciELO? -dal ================================================================ Deborah A Lapeyre mailto:dalapeyre@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Phone: 301-315-9631 (USA) Suite 207 . . . Read full entry »


[ANN] upcoming courses on XSLT 3, Accessibility, Sche

Posted 12/22/2020 12:33:30 AM

Upcoming courses from Delightful Computing, delivered with live video from Pointy Bracket Farm in rural South-East Ontario... The courses are mostly scheduled on demand, so feel free to contact me; if someone has booked a course at a particular date, i'll advertise those dates. The courses are for . . . Read full entry »


Re: XSLT code that implements the Point-in-a-Polygon

Posted 12/11/2020 7:33:38 PM

Just looking at the code, wondering why it's using xsl:choose: could you not do all of it in a single XPath expression, even in XSLT 2? Cheers, E. -- Eliot Kimber http://contrext.com o;?On 12/10/20, 1:22 PM, "Roger L Costello costello@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxx . . . Read full entry »


Re: XSLT code that implements the Point-in-a-Polygon

Posted 12/11/2020 6:12:48 AM

Roger, I'm enjoying reading/experimenting with this code. Minor things: It looks like you could dispense with $N, no? Data types: the function should take doubles as input (with error checks for odd inputs) and return a boolean, no? And in XSLT 3.0 you could use xsl:iterate, which could facili . . . Read full entry »


XSLT code that implements the Point-in-a-Polygon probl

Posted 12/10/2020 7:22:52 PM

Hi Folks, I implemented XSLT code to determine if a point p is inside or outside a polygon. See below. Admittedly, the tests that I've done thus far are really simple. See the template rule. I would appreciate it if you see a bug in the code or see where the code can be improved, you would let me . . . Read full entry »


[Ann] Oxygen XML Editor Saxon Add-on Update

Posted 12/10/2020 2:58:06 PM

Hi everyone, New versions for "Saxon XSLT and XQuery Transformer" add-on are now available to install for Oxygen 23.0. They integrate the latest available engine versions for Saxon 9.9 and 10 (9.9.1.8 and 10.3 respectively). Best Regards, Octavian -- Octavian Nadolu <oXygen/> X . . . Read full entry »


Re: Do you have XSLT code that solves the Point-in-a-

Posted 12/9/2020 12:11:50 AM

On Tue, Dec 8, 2020 at 11:30 PM Roger L Costello costello@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > The Point-in-a-Polygon problem is this: > > Given: v = a lat/long value > p = a series of (lat,long) pairs representing a polygon > > Determine i . . . Read full entry »


Do you have XSLT code that solves the Point-in-a-Polyg

Posted 12/8/2020 6:00:19 PM

Hi Folks, The Point-in-a-Polygon problem is this: Given: v = a lat/long value p = a series of (lat,long) pairs representing a polygon Determine if v is within p. Question: Do you have XSLT code which solves the Point-in-a-Polygon problem? /Roger . . . Read full entry »


Re: Creating ZIP archive from folder

Posted 11/28/2020 4:46:54 PM

Okay, Below is my little Saturday joy. A few notes: * I have not tested this on Windows. * I moved the namespace declarations to the functions to increase portability. * I read about saxon:do in https://www.saxonica.com/documentation9.9/index.html#!extensions/functions/ex path and used it when wri . . . Read full entry »


Re: [xml-dev] Community Group for QT4 specs

Posted 11/27/2020 11:36:43 PM

I'm humbled to be one of the first persons, to reply to this thread. Just quickly, scanned through the qt4cg github repos (particularly the XSLT 4.0 editor's draft). The work seems useful and timely. I hope to interact, further bit through the XSLT 4.0 development process. On Fri, Nov 27, 2020 at . . . Read full entry »


Re: Creating ZIP archive from folder

Posted 11/27/2020 7:56:16 PM

On 27.11.2020 20:31, Michael MC<ller-Hillebrand mmh@xxxxxxxxx wrote: Before I start digging deep, I would hope that someone used these features to create a function which creates a ZIP archive from a a list of root elements and collecting all contained files automatically. My XSLT create a lot . . . Read full entry »


Re: Creating ZIP archive from folder

Posted 11/27/2020 7:37:33 PM

On Fri, Nov 27, 2020 at 07:31:14PM -0000, Michael M|ller-Hillebrand mmh@xxxxxxxxx scripsit: > Before I start digging deep, I would hope that someone used these > features to create a function which creates a ZIP archive from a a > list of root elements and collecting all contained files &g . . . Read full entry »


Creating ZIP archive from folder

Posted 11/27/2020 7:31:07 PM

Dear colleagues, I have used the expath-file extension to copy files. And I see there is also expath-archive supported by Saxon. Before I start digging deep, I would hope that someone used these features to create a function which creates a ZIP archive from a a list of root elements and collectin . . . Read full entry »


Community Group for QT4 specs

Posted 11/27/2020 5:18:12 PM

I have established a W3C community group to work on extensions to the XSLT/XPath/XQuery 3.x specs, and invite participation. There have been initial proposals on the EXPath-ng forum, in my XML Prague 2020 paper, and more recently I have published some proposals in W3C spec format. I've forked the . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 3:47:20 PM

> For example: > > *$myConcat := function($s1, $s2)* > *{ *> *$s1 || '&' || $s2* > *}*> > *return* >* $myConcat('month', 'august')* > > produces > *month&august* produces: *month&august* Gmail is tricky when one wants to highlight t . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 3:31:36 PM

On Wed, Nov 25, 2020 at 6:48 AM Michael Kay mike@xxxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > > > *let $makeElement := function($k, $v) { parse-xml('<' || $k || '>' || $v > || '</' || $k || '>' ) } return $makeElement('month', . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 3:03:44 PM

> As for this particular example, I suspect that building an XML document incrementally from a sequence of single elements will have performance implications -- similar to concatenating to a string many times. > It's true that bottom-up construction of a tree can be very expensive because of . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 2:48:47 PM

> let $makeElement := function($k, $v) { > parse-xml('<' || $k || '>' || $v || '</' || $k || '>' ) > } > return $makeElement('month', 'August') > > There is nothing to be escaped in the above expression! This is XPath, not XML. Well, $makeElement('menu', 'ba . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 2:39:50 PM

> I think having actual node constructors in XPath would be helpful. Having my own XPath function library > introduces all sorts of maintenance and portability problems customers are generally savvy enough to spot and complain about. > (and my employer is _certainly_ savvy enough to spot a . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 2:29:56 PM

I wrote this last night just before going to bed, the correct expression is: *let $makeElement := function($k, $v) { parse-xml('<' || $k || '>' || $v || '</' || $k || '>' ) } return $makeElement('month', 'August')* and it produces the expected result as can be seen in the X . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 1:31:21 PM

On Wed, Nov 25, 2020 at 07:00:29AM -0000, Willem Van Lishout willemvanlishout@xxxxxxxxx scripsit: > In Saxon 10 there is an extension function saxon:new-element(). > https://www.saxonica.com/documentation/index.html#!functions/saxon/new-element Very interesting! thank you! (Here's hoping S . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 1:29:00 PM

On Wed, Nov 25, 2020 at 04:56:06AM -0000, Dimitre Novatchev dnovatchev@xxxxxxxxx scripsit: > > works, but while this is doubtless a question of aesthetic bias I don't > > consider this solution more elegant than (or preferable to) the XSLT version [snip] > *As for elegance*, one can . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 1:24:23 PM

On Wed, Nov 25, 2020 at 10:07:15AM -0000, Michael Kay mike@xxxxxxxxxxxx scripsit: > I've recently proposed that we should have a library of XPath functions for constructing nodes: see https://www.saxonica.com/~mike/builder.html This was motivated by this kind of use case, and I'm now wondering w . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 10:10:31 AM

> let $makeElement := function($k, $v) { > parse-xml('<' || $k '>' || $v '</' || $k '>' ) We really shouldn't be encouraging anyone to construct lexical XML by string concatenation, in any language. We see so many StackOverflow problems caused by people doing it wrong, specific . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 10:07:09 AM

I've recently proposed that we should have a library of XPath functions for constructing nodes: see https://www.saxonica.com/~mike/builder.html This was motivated by this kind of use case, and I'm now wondering whether such functions should go into the core (though there's an interesting question a . . . Read full entry »


Re: Future of XSL 1.0 support

Posted 11/25/2020 9:57:48 AM

Just as if the system was written in COBOL or Fortran, you should be aware that you're using old technology that (a) won't be around for ever, and (b) will get more difficult to support over time. That doesn't necessarily mean you need to do anything about it right now, but relying on old technolog . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 7:00:22 AM

In Saxon 10 there is an extension function saxon:new-element(). https://www.saxonica.com/documentation/index.html#!functions/saxon/new-elemen t On Wed, Nov 25, 2020 at 3:04 AM Graydon graydon@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > So if I have a sequence of maps, . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 6:14:08 AM

Sent from my iPhone > On Nov 24, 2020, at 9:15 PM, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > o;?On Wed, 2020-11-25 at 04:56 +0000, Dimitre Novatchev > dnovatchev@xxxxxxxxx wrote: >> >> >> *The pure XPath solution . . . Read full entry »


Re: Future of XSL 1.0 support

Posted 11/25/2020 6:05:37 AM

On Wed, 2020-11-25 at 02:53 +0000, Charles Muller acmuller@xxxxxxxxxxxxxxx wrote: > > The system was built by Michael Beddow, who passed away last year, :-( :-( I believe i met him. > so > the XSLT version is not being updated. > > Do you think this is a matter that should . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 5:15:18 AM

On Wed, 2020-11-25 at 04:56 +0000, Dimitre Novatchev dnovatchev@xxxxxxxxx wrote: > > > *The pure XPath solution is also an XQuery solution*, as XQuery is a > superset of XPath. However, the results may differ in terms of in-scope namespaces, i think. I'd probably write an XSLT funct . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 4:56:00 AM

> works, but while this is doubtless a question of aesthetic bias I don't consider this solution more elegant than (or preferable to) the XSLT version The problem stated in the initial post was that: "This isn't allowed, because map:for-each() takes an XPath function, rather than an XQue . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 4:03:48 AM

On Wed, Nov 25, 2020 at 03:30:12AM -0000, Dimitre Novatchev dnovatchev@xxxxxxxxx scripsit: > > So if I have a sequence of maps, such as one gets from using > > collection() with the metadata flag set in Saxon, and I want to > > serialize the result just to see what is in there, I' . . . Read full entry »


Re: XSLT 4: map serialization

Posted 11/25/2020 3:30:04 AM

> So if I have a sequence of maps, such as one gets from using collection() with the metadata flag set in Saxon, and I want to serialize the result just to see what is in there, I'd like to be able to use: Demonstrated how to do this in pure XPath 7 years ago at the Balisage 2013 conference: . . . Read full entry »


Future of XSL 1.0 support

Posted 11/25/2020 2:52:51 AM

Dear XSLT'ers, Having followed the recent thread on oXygen 23 which ended up dealing with the issue of ongoing support for XSL 1.0, I'm guessing that I should be concerned. I know the basics of XSLT, but I wouldn't really call myself a programmer. I manage an online dictionary (www.buddhism-di . . . Read full entry »


XSLT 4: map serialization

Posted 11/25/2020 2:03:39 AM

So if I have a sequence of maps, such as one gets from using collection() with the metadata flag set in Saxon, and I want to serialize the result just to see what is in there, I'd like to be able to use: <xsl:sequence select="$fileArchive ! map:for-each(.,function($k,$v){element{$k}{$v}})& . . . Read full entry »


Re: Append to a file on output?

Posted 11/24/2020 6:55:05 PM

Ibll try that Willem, tks. Thanks Martin - not seen that one. On Tue, 24 Nov 2020 at 15:51, Willem Van Lishout willemvanlishout@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Or just using the command line: > > <willemvanlishout@xxxxxxxxx> > java -jar saxon . . . Read full entry »


Re: Append to a file on output?

Posted 11/24/2020 3:51:35 PM

Or just using the command line: <willemvanlishout@xxxxxxxxx> java -jar saxon.jar -xsl: ... >> myFile.txt On Tue, Nov 24, 2020 at 4:43 PM Martin Honnen martin.honnen@xxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > On 24.11.2020 16:40, Dave Pawson dave.pawson@xxxxx . . . Read full entry »


Re: Append to a file on output?

Posted 11/24/2020 3:43:12 PM

On 24.11.2020 16:40, Dave Pawson dave.pawson@xxxxxxxxx wrote: Processing an xml file each day. Wraps up each month (cron job). Suggestions please - I want the transform to append to a plain text file. Is that possible with xslt 2 (or 3) please? With the EXPath file module http://expath.org/spec/fi . . . Read full entry »


Append to a file on output?

Posted 11/24/2020 3:39:49 PM

Processing an xml file each day. Wraps up each month (cron job). Suggestions please - I want the transform to append to a plain text file. Is that possible with xslt 2 (or 3) please? If not, any suggestions as to a reasonably elegant way of doing it? TiA -- Dave Pawson XSLT XSL-FO FAQ. Docb . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/24/2020 2:57:15 PM

As an aside re IBM System 360 in today's world: I learned the other day that a friend has taken a new job building a system that generates modern Web applications that replace existing System 360 applications, even going so far as to emulate to some degree the look and feel of old 3270 display UIs. . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/24/2020 7:30:30 AM

Hello Tommie, The projects are updated automatically when you switch to a new version. There should be no problem when you switch from one version to other. There have probably been some problems in the past, but I hope they have all been resolved. We do not have a topic in documentation that d . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/24/2020 6:52:26 AM

Hi Geert, Thanks for your feedback. I will add an issue to analyze the feedback that we get on the deprecated processors. For XSLT 1.0 debuggingB you can use Xalan or Saxon 6.5.5, but you can also use Saxon 9 or 10 in XSLT 1.0 compatibility mode. Best Regards, Octavian On 23.11.2020 16:26, Ge . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/24/2020 5:58:40 AM

Hi all, Thank you all for your feedback, it is really helpful! I want to clarify some things from the oXygen perspective: * We never considered removing XSLT 1.0 support in oXygen. * We did not remove any processors, we just marked some very old ones as "deprecated". This will incre . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 10:55:40 PM

I think this is really true, and itbs why XML and XSLT is still so relevant. The story about replacing the IT Departmentbs concept of blegacyb (that is, tools that the business spends money on in order generate revenue, but that are no longer current) with the core business idea of how the bus . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 10:52:24 PM

I think a huge part of the problem is a) for many users, these systems are ancillary - theybre not part of the core revenue generation system - and thus the emphasis is on cost minimisation, rather than investment in the return they generate (ie, they donbt generate a return); and b) so many of . . . Read full entry »


Re: MORE Re: [Ann] Oxygen XML Editor version 23 releas

Posted 11/23/2020 10:14:00 PM

On 23/11/2020 18:56, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx wrote: On Mon, 2020-11-23 at 16:57 +0000, Graydon graydon@xxxxxxxxx wrote: On Mon, Nov 23, 2020 at 03:13:27PM -0000, B Tommie Usdin btusdin@xxxxxxxxxxxxxxxxx scripsit: If support for XSLT 1.0 goes away the user is faced with a significant t . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 9:57:21 PM

Hi, I agree with all the disagreements so far. To return to the beginning of the thread, it seems fair to say that there is a reasonable use case for oXygen in continuing to maintain XSLT 1.0 support alongside with XSLT 2.0, for the sake both of crusty old systems and their maintainers who do not . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 9:29:53 PM

I have a requirement to use Xalan to debug XSLT 1.0 because that is the built-in transformer to a database software that my company uses. There is a capability run an XSLT on export from the database software. It uses Xalan. This restricts me to writing 1.0 transformations and debugging them with X . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 8:29:12 PM

> By the way, Geert, I don't think MSXML supports debugging, at least in my Oxygen version it switches to Saxon when I try that. Visual Studio has had an XSLT Debugger since VS 2008. I think it is based on the .NET XSLTransform, but the behavior of the two XSLT processors is almost identical ( . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 7:43:59 PM

> AND, there are things tool vendors can to do make updating easier. For example, providing guidance on how to "fix" things that "break" in such an upgrade. I've recently been trying to help a Saxon user who's managed to get about 10 major releases behind, and it isn't prett . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 7:11:54 PM

>> So it's not a question of like or dislike, fun or no fun, it's a >> question of economics, of minimising the lifetime costs of your >> system. Of course, the calculations will come out differently for >> different projects. > > I agree. But it is also a question of . . . Read full entry »


Re: MORE Re: [Ann] Oxygen XML Editor version 23 releas

Posted 11/23/2020 6:55:56 PM

On Mon, 2020-11-23 at 16:57 +0000, Graydon graydon@xxxxxxxxx wrote: > On Mon, Nov 23, 2020 at 03:13:27PM -0000, B Tommie Usdin > btusdin@xxxxxxxxxxxxxxxxx scripsit: > > If support for XSLT 1.0 goes away the user is faced with a > > significant testing chore and a possibly signifi . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 6:54:36 PM

On Mon, 2020-11-23 at 16:54 +0000, Wegmann, Frank frank.wegmann@xxxxxxxxxxxxxx wrote: > > Unfortunately, there are vendors of Windows-based software relying on > .NET and can only offer, what Microsoft has to offer in .NET Core. > And that is XSLT 1.0. I donbt know the .NET business g . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 5:32:23 PM

> On Nov 23, 2020, at 12:15 PM, Michael Kay mike@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > >> >> I don't see what is unfortunate about people using XSLT 1.0. I don't see why people dislike the fact that others are using it. > > You're building up . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 5:15:15 PM

> I don't see what is unfortunate about people using XSLT 1.0. I don't see why people dislike the fact that others are using it. You're building up technical debt. The concept here is that you can spend $N every year on updating and refreshing the technology you are using, or you can depreciate . . . Read full entry »


Re: MORE Re: [Ann] Oxygen XML Editor version 23 releas

Posted 11/23/2020 4:56:31 PM

On Mon, Nov 23, 2020 at 03:13:27PM -0000, B Tommie Usdin btusdin@xxxxxxxxxxxxxxxx scripsit: > If support for XSLT 1.0 goes away the user is faced with a significant testing chore and a possibly significant amount of maintenance programming. Is anybody actively maintaining an XSLT 1.0 processor? . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 4:53:55 PM

Thank you for sharing this. Rethinking current systems and procedures should happen on a continuous basis. At some point in time then it could be appropriate to ensure that revenues are coming in using a modernized system, and maybe even in a more efficient and more maintainable way. Undoubtedly, . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 4:29:39 PM

I don't see what is unfortunate about people using XSLT 1.0. I don't see why people dislike the fact that others are using it. It may be more fun to write in newer versions of the language. There are certainly useful capabilities in XSLTs 2 and 3, and for new applications that need those capabilit . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 3:53:55 PM

> By the way, Geert, I don't think MSXML supports debugging, at least in my Oxygen version it switches to Saxon when I try that. True, thanks for pointing that out On Nov 23, 2020, at 15:26, "Geert Bormans geert@xxxxxxxxxxxxxxxxxxx" < [ mailto:xsl-list-service@xxxxxxxxxxxxxxxxxx . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 3:43:38 PM

I have to agree with the others. XSLT 1.0 is unfortunately still very prevalent, and I sometimes need to use MSXML to see what quirks it produces. (There's quite a few of them!) If you are really keen on removing them, I would at least consider making them available as easily installable plugins. . . . Read full entry »


Re: MORE Re: [Ann] Oxygen XML Editor version 23 releas

Posted 11/23/2020 3:38:54 PM

Yes, yes, so much yes. Thank you! Michele -----Original Message----- From: B Tommie Usdin btusdin@xxxxxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Sent: Monday, November 23, 2020 10:14 AM To: xsl-list <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Cc: Tommie Usdin <btusdin@xxxxxxxxxx . . . Read full entry »


Re: MORE Re: [Ann] Oxygen XML Editor version 23 releas

Posted 11/23/2020 3:31:59 PM

B Tommie Usdin btusdin@xxxxxxxxxxxxxxxx wrote on 2020-11-23 09:13: > And yes, people*are* using XSLT1.0 to run their business systems. They are also using > DTDs. No, they aren't Luddites, they are people running real businesses, using tools > that work for their needs, and preferring to . . . Read full entry »


MORE Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 3:13:20 PM

> On Nov 23, 2020, at 8:41 AM, Octavian Nadolu octavian_nadolu@xxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: ... > But we will maintain the XSLT 1.0 support in Oxygen. Also, you can configure them as external processors. > How many of you are using this processors? This . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 3:05:23 PM

Hello Octavian -- Is there a place in the documentation that describes how to move projects that were developed in one version of Oxygen into the next version? Or at least a list of the things that might stop working and some clues on how to solve these problems? Some of our clients are quite anx . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 2:26:09 PM

Hi Octavian, Thanks for the update As much as I don't like it... some customers can not or don't want to migrate to an XSLT version higher than 1.0, and I am not always in a position to change that (and that will continue to be so for a long while I am afraid) So I guess I will be needing de . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 1:41:06 PM

Hello, Thanks for your feedback. We intend to update the Saxon 9 and 10 plugins for the Oxygen XML Editor 23.0. Because this are provided separately as plugins, we can updated them also after the release. We decided to deprecate some of the XSLT processors (Xalan, MSXML 4.0, MSXML .NET, .NET . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/23/2020 8:45:44 AM

On Sun, Nov 22, 2020 at 12:44 PM Mukul Gandhi gandhi.mukul@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > I can see that, at the preferences oXygen page, XSLT 1.0 dropdown shows > Xalan as deprecated. It seems to me that, in a future oXygen version, when > Xalan would . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/22/2020 7:13:56 AM

On Fri, Nov 20, 2020 at 8:37 PM Martin Honnen martin.honnen@xxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: With all the deprecating mentioned in > > > *The Apache Xalan XSLT processor is now deprecated and will be > > completely removed from the code in the next majo . . . Read full entry »


Re: [Ann] Oxygen XML Editor version 23 release

Posted 11/20/2020 3:07:49 PM

On 20.11.2020 15:08, Octavian Nadolu octavian_nadolu@xxxxxxx wrote: We are happy to announce that Oxygen XML Author/Editor version 23 is available! Congrats to the new release. I am kind of surprised that the Saxon 9 and 10 engines were not updated (e.g.9.9.1.8 and 10.2 or 10.3). With all the . . . Read full entry »


[Ann] Oxygen XML Editor version 23 release

Posted 11/20/2020 2:07:49 PM

Hello, We are happy to announce that Oxygen XML Author/Editor version 23 is available! Here is a subset of the released features that might be of interest to the XSLT community: * The required attributes in an XSLT 3.0 stylesheet are now automatically added when elements are inserted from the . . . Read full entry »


Pluralsight Free Weekend: Friday 11/20 - Sunday 11/22

Posted 11/19/2020 2:38:50 PM

Pluralsight announced this *Free Weekend <https://www.pluralsight.com/offer/2020/november-free-weekend>*: https://www.pluralsight.com/offer/2020/november-free-weekend Watch for free all my courses on XSLT (3.0, 2.0 and 1.0) and XPath 3.0, and any of the 7000+ courses developed in Pluralsigh . . . Read full entry »


Re: document( URI ) with accented chars fails

Posted 11/19/2020 11:12:43 AM

On Wed, Nov 18, 2020 at 12:16:01PM -0000, Martynas JuseviD ius martynas@xxxxxxxxxxxxx wrote: > We use this in bash scripts: > > urlencode() > { > python -c 'import urllib, sys; print urllib.quote(sys.argv[1] if > len(sys.argv) > 1 else sys.stdin.read()[0:-1])' "$1&quo . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/19/2020 12:15:12 AM

On Wed, Nov 18, 2020 at 09:50:31PM -0000, Wendell Piez wapiez@xxxxxxxxxxxxxxx scripsit: > So maybe today a solution is to pad with extra {''} around your string > literal (escaping ')? > > <xsl:analyze-string regex="{ '\{.*?\}' }"> ... > > With trepidation (forgi . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/18/2020 9:50:24 PM

Hi, So maybe today a solution is to pad with extra {''} around your string literal (escaping ')? <xsl:analyze-string regex="{ '\{.*?\}' }"> ... With trepidation (forgive me if this has already been suggested), Wendell On Wed, Nov 18, 2020 at 3:47 PM Liam R. E. Quin liam@xxxxxx . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/18/2020 8:47:18 PM

On Tue, 2020-11-17 at 13:58 +0000, Michael Kay mike@xxxxxxxxxxxx wrote: > A suggestion that I've thought about from time to time: > > If an attribute in XSLT expects an expression or an AVT, then a > leading undoubled "}" in the attribute value indicates that is to be > tr . . . Read full entry »


Re: [ANN] Web Accessibility course, online

Posted 11/18/2020 4:30:06 PM

I would definitely be interested in such a course. Cheers, E. -- Eliot Kimber http://contrext.com o;?On 11/18/20, 2:04 AM, "Liam R. E. Quin liam@xxxxxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: I'm looking at developing a Web Accessibility course for XML . . . Read full entry »


Re: document( URI ) with accented chars fails

Posted 11/18/2020 12:16:00 PM

We use this in bash scripts: urlencode() { python -c 'import urllib, sys; print urllib.quote(sys.argv[1] if len(sys.argv) > 1 else sys.stdin.read()[0:-1])' "$1" } On Wed, Nov 18, 2020 at 12:32 PM Alexandre HoC/de alexandre.hoide@xxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxx . . . Read full entry »


Re: document( URI ) with accented chars fails

Posted 11/18/2020 11:32:38 AM

On Tue, Nov 17, 2020 at 10:51:25PM -0000, Alexandre HoC/de alexandre.hoide@xxxxxxxxxx wrote: > On Tue, Nov 17, 2020 at 09:26:23PM -0000, Michael Kay mike@xxxxxxxxxxxx wrote: > > The document() function expects a URI, not a filename, and URIs never contain accented characters. > > &g . . . Read full entry »


[ANN] Web Accessibility course, online

Posted 11/18/2020 8:04:25 AM

I'm looking at developing a Web Accessibility course for XML people and publishing people. Are you interested? Attendees should have some basic HTML and CSS knowledge; topics will (probably) include - * short intro with talking points for why accessibility matters, and universal access * the We . . . Read full entry »


Re: document( URI ) with accented chars fails

Posted 11/17/2020 10:51:25 PM

On Tue, Nov 17, 2020 at 09:26:23PM -0000, Michael Kay mike@xxxxxxxxxxxx wrote: > The document() function expects a URI, not a filename, and URIs never contain accented characters. > > XSLT 2.0+ has functions to escape special characters using %HH escapes so you can turn arbitrary filename . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 9:58:02 PM

On Tue, 2020-11-17 at 21:18 +0000, David Carlisle d.p.carlisle@xxxxxxxxx wrote: > > > We might get there this time > https://w3c.github.io/charter-drafts/math-2020.html Yes - i reviewed the charter although the comments i made might have bounced. Pleased to see Bert Bos listed. > . . . Read full entry »


Re: document( URI ) with accented chars fails

Posted 11/17/2020 9:26:23 PM

The document() function expects a URI, not a filename, and URIs never contain accented characters. XSLT 2.0+ has functions to escape special characters using %HH escapes so you can turn arbitrary filenames into valid URIs. For xsltproc you'll need some processor-specific solution and I can't help . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 9:17:07 PM

On Tue, 17 Nov 2020 at 20:29, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > I'd like to see presentation mathml integrated through CSS into Web > browsers, so that one could simply declare an element to have a left > brace, or fence a . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 8:29:35 PM

On Tue, 2020-11-17 at 13:08 +0000, Martin Honnen martin.honnen@xxxxxx wrote: > > On 17.11.2020 13:43, Don Smith dsmith_lockesmith@xxxxxxxxxx wrote: > > <text>In the be{opthyphen}gin{opthyphen}ning</text> > > > The curly braces need to be escaped as \{ and \} Or . . . Read full entry »


document( URI ) with accented chars fails

Posted 11/17/2020 8:28:40 PM

Hello ! I have a little problem : URI inside a bdocument()bB9 is ignored when the filename contains accented (UTF-8) character(s). When applying the XSLT on the source with the sample 2 files below, with the following command ~~~{Command line} $ xsltproc multifiles.xsl files-list.xml ~~~ . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 4:19:03 PM

> Weird Mike - looks plain ugly... > Logical, but weird <grin/> > Digressing: the odd thing is that our expectation that curly braces will only be used in matching pairs is a very recent notion. Go back to pre-computer typography, and vertical braces were often used singly. Traditio . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 4:18:26 PM

Thank you Martin for the solution. Thank you Dr. Kay for the summary reminder: To cope with the specialness in AVTs, double them, To cope with the specialness in regexes, backslash-escape them. So regex = "\{{[a-z]+\}}" Don On Tuesday, November 17, 2020, 07:43:44 AM CST, Michael Kay . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 3:27:17 PM

On Tue, 17 Nov 2020 at 13:57, Michael Kay mike@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > <xsl:param name="x" select="}O'Reilly"/> > > indicates that the default value is the string "O'Reilly" > > and in an AVT > > . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 3:07:25 PM

On Tue, Nov 17, 2020 at 02:59:17PM -0000, Wendell Piez wapiez@xxxxxxxxxxxxxxx scripsit: > Hi, > > <xsl:analyze-string regex="\{.+?\}" interpret-attributes-as-avt="no"> .. > > samish as? > > <xsl:analyze-string regex-string="\{.+?\}"> . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 2:59:10 PM

Hi, <xsl:analyze-string regex="\{.+?\}" interpret-attributes-as-avt="no"> .. samish as? <xsl:analyze-string regex-string="\{.+?\}"> ... whereas the current @regex is a @regex-avt ... Cheers, Wendell On Tue, Nov 17, 2020 at 9:31 AM Graydon graydon@xxx . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 2:31:04 PM

On Tue, Nov 17, 2020 at 01:57:30PM -0000, Michael Kay mike@xxxxxxxxxxxx scripsit: > A suggestion that I've thought about from time to time: > > If an attribute in XSLT expects an expression or an AVT, then a leading undoubled "}" in the attribute value indicates that is to be tr . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 2:26:30 PM

Too quirky. Cheers, E. -- Eliot Kimber http://contrext.com o;?On 11/17/20, 8:04 AM, "Michael Kay mike@xxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: A suggestion that I've thought about from time to time: If an attribute in XSLT expects an expression or . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 2:10:20 PM

On Tue, 17 Nov 2020 at 13:57, Michael Kay mike@xxxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > A suggestion that I've thought about from time to time: > > If an attribute in XSLT expects an expression or an AVT, then a leading > undoubled "}" in the att . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 1:57:25 PM

A suggestion that I've thought about from time to time: If an attribute in XSLT expects an expression or an AVT, then a leading undoubled "}" in the attribute value indicates that is to be treated as a plain string. So for an expression <xsl:param name="x" select="}O' . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 1:43:37 PM

Curly braces are special in AVTs and they are special in regexes. To cope with the specialness in AVTs, double them, To cope with the specialness in regexes, backslash-escape them. So regex = "\{{[a-z]+\}}" should do the trick; or as Martin suggests, remove the AVT problem by using a . . . Read full entry »


Re: Analyze-string Regex to Match Content within Curly

Posted 11/17/2020 1:08:02 PM

On 17.11.2020 13:43, Don Smith dsmith_lockesmith@xxxxxxxxx wrote: <text>In the be{opthyphen}gin{opthyphen}ning</text> The curly braces need to be escaped as \{ and \} B <xsl:param name="pattern" as="xs:string">\{([a-z]+)\}</xsl:param> B <xsl:temp . . . Read full entry »


Analyze-string Regex to Match Content within Curly Bra

Posted 11/17/2020 12:43:16 PM

Once again I find myself at a loss when trying to write a regex in analyze-string that matches on an open/close curly brace combination. I'm using XSLT 2.0 and Saxon PE-9.6.0.7. Here's an example of the text content: <text>In the be{opthyphen}gin{opthyphen}ning</text> I need to match a . . . Read full entry »


XSLT 4?

Posted 11/15/2020 11:04:44 AM

https://www.saxonica.com/qt4specs/ Mike's thinking ahead! regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/13/2020 1:47:31 AM

> This all leads me to think that a non-deterministic fn:refresh-document() function might be useful in certain circumstances, > but that we would be well advised to leave the plain-vanilla document() > function (and its ilk such as doc() and unparsed-text()) deterministic. They are alread . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/13/2020 1:26:42 AM

Hi again, On Thu, Nov 12, 2020 at 8:02 PM Mukul Gandhi gandhi.mukul@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Trying to answer the original question. > > Given the requirements, I find the answer suggested by Dimitre to be > useful, to use web service to get . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/13/2020 1:02:17 AM

Trying to answer the original question. Given the requirements, I find the answer suggested by Dimitre to be useful, to use web service to get the UUID generated. Something like, unparsed-text("https://uuid_service"). That should be portable for deployment. On Tue, Nov 10, 2020 at 10: . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/12/2020 11:04:01 PM

On Thu, 2020-11-12 at 15:41 +0000, Dave Pawson dave.pawson@xxxxxxxxx wrote: > Is this the internet messing with functional programming definitions > / terms? > B For UUID it would seem that is wanted (if not needed), either via an > extension > as Mike has done, or via a non-function . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/12/2020 9:10:16 PM

> This all leads me to think that a non-deterministic fn:refresh-document() function might be useful in certain circumstances, > but that we would be well advised to leave the plain-vanilla document() function (and its ilk such as doc() and unparsed-text()) deterministic. > They are alread . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/12/2020 8:33:30 PM

Hi, Norm has it right (I think) that following this rule and being able to trust that a processor should follow this rule (even when it does not), is an important stabilizing factor in XSLT development, enabling a very useful separation of concerns whose boundaries run close to the governance boun . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/12/2020 4:39:22 PM

> I don't expect that anyone wrote XSLT code that relies on these functions > being deterministic. I would be very reluctant to endorse that claim. I have relied on this *all the time* in as much as Ibve never given a moment of thought to whether or not fn:doc() could possibly return a diff . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/12/2020 4:36:02 PM

On Thu, 12 Nov 2020 at 16:28, Dimitre Novatchev dnovatchev@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Do you think fn:unparsed-text() should be different with respect to > > determinism than fn:doc() (and fn:document(), come to that)? Or do you > > thin . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/12/2020 4:28:21 PM

> Do you think fn:unparsed-text() should be different with respect to > determinism than fn:doc() (and fn:document(), come to that)? Or do you > think they should also be nondeterministic? There is no reason why doc() and document() should be "more deterministic" than unparsed-t . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/12/2020 4:14:28 PM

> I think these functions should not be deterministic. Informally, and going all the way back to 1.0, I think the XSLT view is that the world doesnbt change while the transformation is running. Consider, for example, that fn:current-dateTime() is fixed! This simplifies *a lot* of things. Ima . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/12/2020 3:40:52 PM

Is this the internet messing with functional programming definitions / terms? For UUID it would seem that is wanted (if not needed), either via an extension as Mike has done, or via a non-functional call (same as non-deterministic?). Has this never come up in WG discussions? A really interesting . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/12/2020 2:59:47 PM

In my opinion, all those functions that depend on external things, as existence or non-existence of a file, content return by an http request can not be specified as deterministic, as implementors are not responsible of the returned value. If specification defines these function as deterministi . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/12/2020 10:26:26 AM

Dimitre Novatchev dnovatchev@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> writes: > It seems to me that tagging the function unparsed-text() as "deterministic" > was rather inaccurate... And definitely not useful, if we need hacks as > workarounds for its limitations . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 11:50:37 PM

> This is the view of the InternetArchive <https://archive.org/web/>, but this is also too simplistic. What about load-balancers, caches and replicas, just to name a few? Indeed, now you mention it, the ads I see on a page are the result of some complex algorithm whose inputs we don't eve . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 11:35:49 PM

> I don't know how FP purists model this, but it seems to me that the content of a web page is a function of two things: the URL, and the time This is the view of the *InternetArchive* <https://archive.org/web/>, but this is also too simplistic. What about load-balancers, caches and repl . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 10:35:50 PM

I don't know how FP purists model this, but it seems to me that the content of a web page is a function of two things: the URL, and the time. So probably we should be treating unparsed-text() as if there is an implicit parameter timestamp() which is potentially different on each call; though since . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 10:03:26 PM

> According to the spec, unparsed-text() is deterministic, which means that two calls with the same argument should return the same result. You're relying on a Saxon non-conformance, I fear! It seems to me that tagging the function unparsed-text() as "deterministic" was rather inaccur . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 9:53:41 PM

> Dimitre, I don't know! XSLT too can be beautiful in its way don't you think? Absolutely, however when solving a non-XML-processing problem, using XPath (a functional, expression language) seems much more elegant to me. A matter of taste, of course. Cheers, Dimitre On Wed, Nov 11, 2020 at . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 9:35:20 PM

Dimitre, I don't know! XSLT too can be beautiful in its way don't you think? Cheers, Wendell On Wed, Nov 11, 2020 at 4:12 PM Dimitre Novatchev dnovatchev@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi Wendell, > > > Meanwhile an XSLT implementation of UUID v4 . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 9:12:00 PM

Hi Wendell, > Meanwhile an XSLT implementation of UUID v4 was not as fearsome as I had supposed it would be. (We'll see how it stands up.) I would aim at a pure XPath implementation, XSLT is not interesting enough p Thanks, Dimitre On Wed, Nov 11, 2020 at 1:06 PM Wendell Piez wapiez@xxxx . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 9:05:58 PM

Hi Dimitre, Yes indeed and I am glad to have all of these in the kit. This would be a much simpler question if I could guarantee anything about the users ... however not only may they be unable to call Java, they might also be off line at runtime. So I have to be able to offer options. Meanwhile . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 8:35:07 PM

Hi Wendell, Dimitre, suggesting the web service option, offers > for $i in 1 to $N > return unparsed-text("https://uuidgen.org/api/v/4") > > I'll try this ... but what prevents an XSLT engine giving me the same result each time? (Oh I see.) Dr. Kay suggested a fix that . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 8:19:38 PM

Hi, Dimitre, suggesting the web service option, offers for $i in 1 to $N return unparsed-text("https://uuidgen.org/api/v/4") I'll try this ... but what prevents an XSLT engine giving me the same result each time? (Oh I see.) Update since yesterday -- I've had some apparent success . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 7:44:04 PM

> Except that if you make the call in a loop, Saxon will probably loop-lift it, thus becoming conformant and making your code deliver a stream of identical UUIDs. Oxygen's XPath/XQuery Builder, when running with XPath 3.1 SA, produces all different results when evaluating this: for $i in 1 to . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 7:29:37 PM

> I was using the XPath/XQuery Builder tool and it indeed produces a new result on each invocation. I was using the *Oxygen *XPath/XQuery Builder tool and it indeed produces a new result on each invocation. On Wed, Nov 11, 2020 at 11:28 AM Dimitre Novatchev <dnovatchev@xxxxxxxxx> wrot . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 7:28:33 PM

That's a great explanation, Dr. Kay! I was using the XPath/XQuery Builder tool and it indeed produces a new result on each invocation. Thanks, Dimitre On Wed, Nov 11, 2020 at 11:19 AM Michael Kay mike@xxxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > According to the spe . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 7:19:39 PM

According to the spec, unparsed-text() is deterministic, which means that two calls with the same argument should return the same result. You're relying on a Saxon non-conformance, I fear! Except that if you make the call in a loop, Saxon will probably loop-lift it, thus becoming conformant and ma . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 7:16:23 PM

On 11.11.2020 19:32, Dimitre Novatchev dnovatchev@xxxxxxxxx wrote: > how can I go about producing random UUIDs, in dozens or hundreds, inside an XSLT pipeline, without extension functions in Saxon. This is actually very easy and doesn't require the use of any extension functions: */unparsed-tex . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 6:32:19 PM

> how can I go about producing random UUIDs, in dozens or hundreds, inside an XSLT pipeline, without extension functions in Saxon. This is actually very easy and doesn't require the use of any extension functions: *unparsed-text("https://uuidgen.org/api/v/4 <https://uuidgen.org/api/v/ . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/11/2020 7:53:06 AM

We've been very reluctant to define impure functions. It would be interesting to know how SPARQL solves this problem. Michael Kay Saxonica > On 10 Nov 2020, at 22:09, Martynas JuseviD ius martynas@xxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Maybe XSLT could h . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/10/2020 10:09:02 PM

Maybe XSLT could have a built-in function? SPARQL has functions UUID() and STRUUID(): https://www.w3.org/TR/sparql11-query/#func-uuid On Tue, Nov 10, 2020 at 9:56 PM Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > XSL-List, > > &g . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/10/2020 8:56:31 PM

XSL-List, Thanks everyone for your answers so far. Very illuminating. The good news seems to be as Dimitre reassures us that this is certainly possible in some form. An extension function of some kind may be in order. I like both of Mike Kaybs ideas. At its essence, however, this isnbt really a . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/10/2020 8:24:40 PM

Hi Wendell, This question has definite answers even for XSLT 1.0, see for example this SO question: XSLT generate UUID <https://stackoverflow.com/questions/8126963/xslt-generate-uuid> And we have had pure XSLT 1.0 random sequence generators since 2002 (FXSL): Casting the Dice with FXSL: Ra . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/10/2020 7:14:27 PM

On Tue, 2020-11-10 at 16:37 +0000, Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx wrote: > XSL Friends - > > Today I write from the day job, where I am researching the question > of how can I go about producing random UUIDs, in dozens or hundreds, > inside an XSLT pipeline, without ex . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/10/2020 6:28:20 PM

I was wondering about this requirement a few days ago, as it happens. One approach might be to add an extra "method" to the object returned by fn:random-number-generator. If you don't like extension functions then an alternative now we have first-class functions is to construct an XDM f . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/10/2020 5:06:46 PM

On 10/11/2020 16:51, Martin Honnen martin.honnen@xxxxxx wrote: HE 10 with higher-order function support (which is not available in HE 9.8 and 9.9) has at least support for fn:random-number-generator, Saxon JS 2 also supports that function. SaxonJS2 does support fn:random-number-generator, based on . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/10/2020 4:56:00 PM

> Java randomUUID() function works nicely when it's available, but I > need to distribute the capability for SaxonHE and eventually SaxonJS. If youbre willing to do a little more work, you can write extension functions that you can call from SaxonHE. There are a few in https://github.com/do . . . Read full entry »


Re: Random UUID in pure XSLT?

Posted 11/10/2020 4:50:53 PM

On 10.11.2020 17:36, Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx wrote: Today I write from the day job, where I am researching the question of how can I go about producing random UUIDs, in dozens or hundreds, inside an XSLT pipeline, without extension functions in Saxon. The Java randomUUID() fun . . . Read full entry »


Random UUID in pure XSLT?

Posted 11/10/2020 4:36:18 PM

XSL Friends - Today I write from the day job, where I am researching the question of how can I go about producing random UUIDs, in dozens or hundreds, inside an XSLT pipeline, without extension functions in Saxon. The Java randomUUID() function works nicely when it's available, but I need to distr . . . Read full entry »


Re: HTML5 and MathML and namespaces, oh my

Posted 11/6/2020 2:57:53 PM

Hi, On Thu, Nov 5, 2020 at 10:18 PM Liam R. E. Quin liam@xxxxxxxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > On Fri, 2020-11-06 at 01:13 +0000, Chris Papademetrious > christopher.papademetrious@xxxxxxxxxxxx wrote: > > > > <xsl:template xmlns="htt . . . Read full entry »


Re: HTML5 and MathML and namespaces, oh my

Posted 11/6/2020 2:31:38 PM

Thanks to everyone that helped me solve my namespace issues! Indeed, I broke my posted testcase in the process of simplifying it. (I hate when I change something from properly broken to improperly broken.) With your guidance, I have it working now. I posted the solution on stackoverflow.com to mak . . . Read full entry »


Re: HTML5 and MathML and namespaces, oh my

Posted 11/6/2020 12:59:04 PM

On Fri, 6 Nov 2020 at 12:56, David Carlisle d.p.carlisle@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > > <p> fires, but the template for MathML <mi> does not. What am I doing > wrong? > > The template for mi does match, > Actually not, as L . . . Read full entry »


Re: HTML5 and MathML and namespaces, oh my

Posted 11/6/2020 12:56:18 PM

> <p> fires, but the template for MathML <mi> does not. What am I doing wrong? The template for mi does match, but you never applied templates to the mi, so the template isn't used. Your template on the parent p is using copy-of select=. so copies the source and doesn't apply templa . . . Read full entry »


Re: HTML5 and MathML and namespaces, oh my

Posted 11/6/2020 3:18:14 AM

On Fri, 2020-11-06 at 01:13 +0000, Chris Papademetrious christopher.papademetrious@xxxxxxxxxxxx wrote: > > B <xsl:template xmlns="http://www.w3.org/1998/Math/MathML" > match="mi"> i think you want, <xsl:template xmlns:m="http://www.w3.org/1998/Math/Math . . . Read full entry »


Re: building a mental model for the "current node" be

Posted 11/6/2020 2:24:10 AM

Thank you, Christophe, for still having that diagram available readily as a web page! Back in 2014 I released my PDF books (on which I had based my training) for free, including the one on XSLT/XPath and the one on XSL-FO. They are available both in US-letter and A4 page sizes here: http://www.cran . . . Read full entry »


Re: HTML5 and MathML and namespaces, oh my

Posted 11/6/2020 1:12:34 AM

Hi Wendell, all, My bxpath-default-namespace" solution worked when I modified only MathML content, but it failed when I tried to modify both MathML and HTML content. :( Your note that XSLT documents themselves follow XML namespace rules got me thinkingb& and I also came across the Novem . . . Read full entry »


Re: building a mental model for the "current node" be

Posted 11/5/2020 10:04:27 PM

On 05.11.2020 22:13, David Carlisle d.p.carlisle@xxxxxxxxx wrote: On Thu, 5 Nov 2020 at 14:46, Martin Honnen martin.honnen@xxxxxx <mailto:martin.honnen@xxxxxx> <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx <mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>> wrote: Am 05.11.2020 um . . . Read full entry »


Re: building a mental model for the "current node" be

Posted 11/5/2020 9:13:17 PM

On Thu, 5 Nov 2020 at 14:46, Martin Honnen martin.honnen@xxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Am 05.11.2020 um 15:11 schrieb Chris Papademetrious > christopher.papademetrious@xxxxxxxxxxxx: > > Ibm trying to better my understanding of bcurrent nodeb behavi . . . Read full entry »


Re: building a mental model for the "current node" be

Posted 11/5/2020 8:59:41 PM

New host, but yes, I found that diagram very useful. Regards On Thu, 5 Nov 2020 at 19:52, Christophe Marchand cmarchand@xxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > You mean that one : > > https://our.umbraco.com/documentation/reference/templating/macros/xslt/xpa . . . Read full entry »


Re: building a mental model for the "current node" be

Posted 11/5/2020 7:52:00 PM

You mean that one : https://our.umbraco.com/documentation/reference/templating/macros/xslt/xpath-axes-and-their-shortcuts ? Christophe Le 05/11/2020 C 17:50, Dave Pawson dave.pawson@xxxxxxxxx a C)critB : On Thu, 5 Nov 2020 at 14:46, Martin Honnen martin.honnen@xxxxxx <xsl-list-service@xxxxx . . . Read full entry »


Re: Resolving xsl:import href on different base URIs

Posted 11/5/2020 6:28:55 PM

> On 5 Nov 2020, at 16:28, Pieter Lamers pieter.lamers@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > interesting. can we also do > > <xsl:apply-templates _mode="{$my-mode}"/> with a parametrized mode? > Sure. So long as $my-mode is a STAT . . . Read full entry »


Re: building a mental model for the "current node" be

Posted 11/5/2020 4:50:18 PM

On Thu, 5 Nov 2020 at 14:46, Martin Honnen martin.honnen@xxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Am 05.11.2020 um 15:11 schrieb Chris Papademetrious > > As a novice, I get confused remembering when the current node > > does/doesnbt change. Therebs also . . . Read full entry »


Re: Resolving xsl:import href on different base URIs

Posted 11/5/2020 4:27:59 PM

interesting. can we also do <xsl:apply-templates _mode="{$my-mode}"/> with a parametrized mode? -p On 04/11/2020 22:24, Martynas JuseviD ius martynas@xxxxxxxxxxxxx wrote: Thanks for all the suggestions! A static parameter and a shadow attribute did the trick for me: <xsl: . . . Read full entry »


Re: building a mental model for the "current node" be

Posted 11/5/2020 2:46:39 PM

Am 05.11.2020 um 15:11 schrieb Chris Papademetrious christopher.papademetrious@xxxxxxxxxxxx: Im trying to better my understanding of current node behavior in XSLT, and I have a couple questions. 1. Which stylesheet elements select the current node .? The dot is used or usable in any XPath expr . . . Read full entry »


building a mental model for the "current node" behavio

Posted 11/5/2020 2:11:21 PM

I'm trying to better my understanding of "current node" behavior in XSLT, and I have a couple questions. 1. Which stylesheet elements select the current node "."? "How XPath Context Is Initialized" at https://www.lenzconsulting.com/how-xslt-works/ states that asid . . . Read full entry »


Re: HTML5 and MathML and namespaces, oh my

Posted 11/4/2020 10:00:52 PM

Thanks Wendell! When I first learned about XSLT and namespaces, I figured, bIbll be thankful for this when I have mixed-namespace content.b I am relieved that indeed, the complexity helps avoid even more complexity! I am learning XSLT and namespaces at the same time. My background is perl/Tcl/ . . . Read full entry »


Re: Resolving xsl:import href on different base URIs

Posted 11/4/2020 9:23:53 PM

Thanks for all the suggestions! A static parameter and a shadow attribute did the trick for me: <xsl:param name="apl:baseUri" as="xs:anyURI" static="yes"/> <xsl:import _href="{resolve-uri('static/com/atomgraph/linkeddatahub/xsl/bootstrap/2.3.2/l . . . Read full entry »


Re: Resolving xsl:import href on different base URIs

Posted 11/4/2020 5:29:19 PM

Two further tricks: (a) when you load the top-level stylesheet using new StreamSource(stream, systemId), the systemId becomes the base URI of the top-level stylesheet module, and this doesn't need to reflect the actual location of the source code. (b) don't forget that you can set xml:base=" . . . Read full entry »


Re: Resolving xsl:import href on different base URIs

Posted 11/4/2020 4:56:30 PM

On Tue, 2020-11-03 at 22:37 +0000, Martynas JuseviD ius martynas@xxxxxxxxxxxxx wrote: > Hi, > > I have a stylesheet that I want to deploy on different setups that > have different base URIs. That impacts the relative URI of the > imports > of that stylesheet. For example, in one . . . Read full entry »


Re: HTML5 and MathML and namespaces, oh my

Posted 11/4/2020 4:12:05 PM

Chris, Awesome. You have about cracked the namespace conundrum. Part of the key is to see that the XSLT is also an XML document and follows all the same rules as any other XML document as to its namespaces. So: > Why would the XSLT serializer write explicit namespace references that arenbt n . . . Read full entry »


Re: HTML5 and MathML and namespaces, oh my

Posted 11/4/2020 1:04:14 PM

Hi Martin, Thanks for taking the time to reply! The :mml namespace was a vestigial declaration from earlier experiments. I didn't realize its presence would cause problems. After deleting it, I get ... <math xmlns="http://www.w3.org/1998/Math/MathML"> <mrow> . . . Read full entry »


Re: HTML5 and MathML and namespaces, oh my

Posted 11/4/2020 12:49:16 PM

Am 04.11.2020 um 13:44 schrieb Chris Papademetrious christopher.papademetrious@xxxxxxxxxxxx: Hi all, I have an HTML5-namespaced document containing MathML-namespaced <math> content: <!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <head> < . . . Read full entry »


HTML5 and MathML and namespaces, oh my

Posted 11/4/2020 12:43:48 PM

Hi all, I have an HTML5-namespaced document containing MathML-namespaced <math> content: <!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Equations</title> </head> <body> <math xmlns="http:/ . . . Read full entry »


Re: Resolving xsl:import href on different base URIs

Posted 11/4/2020 11:19:54 AM

On 3.11.2020 23:36, Martynas JuseviD ius martynas@xxxxxxxxxxxxx wrote: > The rest is identical. I'd like to avoid having to duplicate > stylesheets just because of this URI difference. > > Is there some clever URI resolution trick I'm not seeing, or some XSLT > 3.0 static features t . . . Read full entry »


Re: Resolving xsl:import href on different base URIs

Posted 11/3/2020 10:42:56 PM

On 03.11.2020 23:36, Martynas JuseviD ius martynas@xxxxxxxxxxxxx wrote: I have a stylesheet that I want to deploy on different setups that have different base URIs. That impacts the relative URI of the imports of that stylesheet. For example, in one case <xsl:import href="../../../xsl/ . . . Read full entry »


Resolving xsl:import href on different base URIs

Posted 11/3/2020 10:36:35 PM

Hi, I have a stylesheet that I want to deploy on different setups that have different base URIs. That impacts the relative URI of the imports of that stylesheet. For example, in one case <xsl:import href="../../../xsl/bootstrap/2.3.2/layout.xsl"/> and in the other case & . . . Read full entry »


XSL-List Guidelines

Posted 11/1/2020 10:48:11 PM

This information is posted to the XSL-List (and the XSL-List Digest) at intervals under the subject line "XSL-List guidelines". INTRODUCTION TO XSL-LIST XSL-List hosts discussion of XSL itself, XSL applications and implementation, and XSL user questions. XSL-List is open to everyone, us . . . Read full entry »


Re: Ungready Flag on Regex

Posted 10/23/2020 8:03:14 AM

First, I've try to change all xsl:non-matching-substring TVT with xsl:sequence, and that was worst. Then, I've changed only pt:replaceTextDollar xsl:non-matcing-substring TVT to a xsl:sequence, without success. The problem was my test was not correctly written. I now have written all test case . . . Read full entry »


Re: Ungready Flag on Regex

Posted 10/23/2020 1:01:23 AM

Christophe, Have you tried Martin's solution? It solves the issue and it doesn't create atomic values instead of text nodes. You need to see that you've been smashing the results of the inner function invocations to text nodes, no matter whether elements have been created by these functions i . . . Read full entry »


Re: Ungready Flag on Regex

Posted 10/22/2020 10:50:50 PM

That's not the problem. Changing to <xsl:sequence .../> is worse, it creates some pseudo-atomic-values instead of text() nodes. Christophe Le 22/10/2020 C 23:48, Martin Honnen martin.honnen@xxxxxx a C)critB : On 22.10.2020 23:14, Christophe Marchand cmarchand@xxxxxxxxxx wrote: For sure, r . . . Read full entry »


Re: Ungready Flag on Regex

Posted 10/22/2020 9:53:36 PM

On 22.10.2020 23:48, Martin Honnen martin.honnen@xxxxxx wrote: I think the issue is your use of text value templates <xsl:non-matching-substring>{pt:replaceTextArobase(.)}</xsl:non-matching-subs tring> that strips any elements; you need to use B <xsl:non-matching-substring> . . . Read full entry »


Re: Ungready Flag on Regex

Posted 10/22/2020 9:47:51 PM

On 22.10.2020 23:14, Christophe Marchand cmarchand@xxxxxxxxxx wrote: For sure, regex are strange to me, even if I think they are really usefull. So, when a regex king give me the right regex to do exactly what I want, I take this regex, and I adapt it to other similar use-cases. My first problem w . . . Read full entry »


Re: Ungready Flag on Regex

Posted 10/22/2020 9:14:02 PM

For sure, regex are strange to me, even if I think they are really usefull. So, when a regex king give me the right regex to do exactly what I want, I take this regex, and I adapt it to other similar use-cases. My first problem was with comments, and I've adapted it to other kind of markers : . . . Read full entry »


Re: Grouping

Posted 10/21/2020 6:07:11 PM

Thank you Martin! This is the perfect solution for the overall stylesheet. Even if it's not as readable as the solution with a function, it requires no knowledge about the special grouping logic when applying templates somewhere in the rest of the stylesheet. And it's _way_ more understandable . . . Read full entry »


Re: Grouping

Posted 10/21/2020 4:37:50 PM

Am 21.10.2020 um 17:57 schrieb Christoph Naber pentium120mhz@xxxxxxxxx: The group-wrap should be performed for sequences of <points> of @type = '1'. <Points> of other types and completeley other nodes should not be grouped. Another approach not using grouping with for-each-group is t . . . Read full entry »


Re: Grouping

Posted 10/21/2020 4:05:46 PM

Am 21.10.2020 um 17:57 schrieb Christoph Naber pentium120mhz@xxxxxxxxx: The group-wrap should be performed for sequences of <points> of @type = '1'. <Points> of other types and completeley other nodes should not be grouped. The "group-adjacent" solution seemes obvious but I h . . . Read full entry »


Re: Grouping

Posted 10/21/2020 3:42:22 PM

Am 21.10.2020 um 17:25 schrieb Christoph Naber pentium120mhz@xxxxxxxxx: the question of Charlie brought me to thinking about a problem and solution that I came up with a few years ago. A few words upfront: - This is a _very_ stripped down example which doesn't reflect the complete structure. I hop . . . Read full entry »


Grouping

Posted 10/21/2020 3:25:17 PM

Hello xsl-list, the question of Charlie brought me to thinking about a problem and solution that I came up with a few years ago. A few words upfront: - This is a _very_ stripped down example which doesn't reflect the complete structure. I hope that I was able to retain all relevant structural attr . . . Read full entry »


[ANN] XSLT Two to Three Course, December

Posted 10/21/2020 2:04:50 AM

Hello! Delightful Computing will be holding an XSLT 3 course in December aimed at people who already use XSLT 2. The course will be online, with a live instructorm but it's essentially the same course i've run before, organized into two days plus an optional third day for XSLT streaming. See htt . . . Read full entry »


Re: Grouping?

Posted 10/20/2020 1:22:57 PM

Hello Charlie, I came up with this XSLT2.0 solution: <?xml version="1.0"?> <xsl:stylesheet version="2.0" xmlns:xsl=" http://www.w3.org/1999/XSL/Transform" xmlns:fn="my.functions"> <xsl:output indent="no" method="text" e . . . Read full entry »


Re: possible grouping problem.

Posted 10/20/2020 9:23:08 AM

I'm sorry for posting to early... After having double checked the structure as well as the Mail from Liam Quin, I apologize for my mistake. The rules seem to remain a mystery. Am Di., 20. Okt. 2020 um 11:17 Uhr schrieb Christoph Naber pentium120mhz@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxx . . . Read full entry »


Re: possible grouping problem.

Posted 10/20/2020 9:17:07 AM

It looks like the resulting CSV-file should simply copy the structure of the input ids, without any regard to the type of surrounding elements. <work_package id="M01"> <eqpcond> <targetfile id="O01"/> </eqpcond> <eqpcond> <targetf . . . Read full entry »


Re: possible grouping problem.

Posted 10/20/2020 8:24:13 AM

Spare a thought for your readers! This problem would be so much easier to understand if you reduced the id's to simple values like M01 and O22, and if you reduced the number of elements so the XML fits on one screen without scrolling. You're much more likely to get a response if the problem is clea . . . Read full entry »


Re: Grouping?

Posted 10/20/2020 7:51:37 AM

On Tue, 2020-10-20 at 06:15 +0000, Martin Honnen martin.honnen@xxxxxx wrote: > Am 20.10.2020 um 04:40 schrieb Charlie0 charlieo0@xxxxxxxxxxx: [...] Let's see if interleaving input and output helps. > > <work_package id="M2183892350419"> > > B B B <eqpcond> &g . . . Read full entry »


Re: Grouping?

Posted 10/20/2020 6:14:07 AM

Am 20.10.2020 um 04:40 schrieb Charlie0 charlieo0@xxxxxxxxxxx: Greetings, I have an issue that I think is a grouping problem but I just can't seem to figure it out. I have no code to show as I'm that lost on this. Using XSLT 2.0 with Oxygen 18.1. I have the following XML that needs to transform to . . . Read full entry »


Re: possible grouping problem.

Posted 10/19/2020 10:01:31 PM

Two bits of clarification needed: 1. What version of XSLT can you use? XSLT 2? XSLT 3? 2. Can you describe the rules? That is, what is the conceptual algorithm that gets you from the input to the output? Cheers, E. -- Eliot Kimber http://contrext.com o;?On 10/19/20, 4:15 PM, "Charlie0 cha . . . Read full entry »


possible grouping problem.

Posted 10/19/2020 9:15:28 PM

Greetings, I have an issue that I think is a grouping problem but I just can't seem to figure it out. I have no code to show as I'm that lost on this. I have the following XML that needs to transform to a comma delimited text file. See text after the XML. Any assistance to get me in the right . . . Read full entry »


Re: tokenizing and counting with xsl:analyze-string

Posted 10/18/2020 4:31:53 AM

On Sat, 17 Oct, 2020, 10:45 PM Martin Honnen martin.honnen@xxxxxx, < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: Without having any "as" attribute your variable is a document fragment node containing the content constructed by the sequence constructor; of course if you use fun . . . Read full entry »



PURCHASE STYLUS STUDIO ONLINE TODAY!!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Learn Stylus Studio in 6 Minutes

Can six minutes change your life? A new action-packed online video demonstration covers how to use Stylus Studio in just six minutes! Watch this video and change the way you develop XML applications forever!

Ask Someone You Know

Does your company use Stylus Studio? Do your competitors? Engineers from over 100,000 leading companies use Stylus Studio, and now you can ask someone from your own organization about their experiences using Stylus Studio.

 
Free Stylus Studio XML Training:
W3C Member