Cart|
Home > XSL-List Blog
Subscribe to the XSL-List Blog in XML format
The XSL-LIST BlogThe 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! XSL-List GuidelinesPosted 10/1/2024 5:19:09 PMThis 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 » [ANN] XSpec v3.1.2 ReleasedPosted 9/30/2024 11:08:50 PMWe are pleased to announce the release of XSpec v3.1.2, the open source unit test and behaviour-driven development framework for XSLT, XQuery, and Schematron. You can get the latest release of XSpec and read the release notes on GitHub. https://github.com/xspec/xspec/releases/tag/v3.1.2 These are . . . Read full entry » Re: Crawl a website?Posted 9/27/2024 3:43:10 PMThanks Martynas. Easier with XML input. This is my GP surgury website, in HTML, with both internal and external links. regards On Fri, 27 Sept 2024 at 16:37, Martynas JuseviD ius martynas@xxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > I have some XSLT 3.0 code that . . . Read full entry » Re: Crawl a website?Posted 9/27/2024 3:37:14 PMI have some XSLT 3.0 code that crawls Maven's pom.xml files recursively: https://github.com/AtomGraph/POM2RDF On Fri, Sep 27, 2024 at 5:04b/PM Dave Pawson dave.pawson@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Asked to produce a map of a website (not following links . . . Read full entry » Crawl a website?Posted 9/27/2024 3:04:29 PMAsked to produce a map of a website (not following links). Has anyone done this to show pages as nodes to indicate depth please? TiA -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. . . . Read full entry » Re: XSLT 3.1 that keeps both Saxon EE and HE happy andPosted 9/26/2024 6:43:23 PMBob, How about @someAttribute ! tokenize(.)? Guessing a bit (schema-aware?), untested, Wendell -----Original Message----- From: Robert Stuart bobstuart@xxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Sent: Thursday, September 26, 2024 12:21 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: . . . Read full entry » Re: XSLT 3.1 that keeps both Saxon EE and HE happy andPosted 9/26/2024 6:25:26 PMOn Thu, 2024-09-26 at 18:18 +0000, Robert Stuart bobstuart@xxxxxxx wrote: > LOL thatbs funny I did have someone on my team suggest that and said > to myself/them people like Michael and Liam would shame me if I did > that. Ibm not into shaming people (and i donbt think Michael Kay is e . . . Read full entry » Re: XSLT 3.1 that keeps both Saxon EE and HE happy andPosted 9/26/2024 6:18:22 PMLOL thatbs funny I did have someone on my team suggest that and said to myself/them people like Michael and Liam would shame me if I did that. So in your mind is the overhead of the sad turn a list back into a string and tokenize it for EE not a bit deal maybe we go that way. I was wondering if . . . Read full entry » Re: XSLT 3.1 that keeps both Saxon EE and HE happy andPosted 9/26/2024 9:23:21 AMIf you're not worried about the slight overhead, you could do `tokenize(string(@attribute))`. Michael Kay Saxonica > On 26 Sep 2024, at 05:33, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > On Thu, 2024-09-26 at 04:21 +0000, Robert Stuart . . . Read full entry » Re: XSLT 3.1 that keeps both Saxon EE and HE happy andPosted 9/26/2024 4:32:49 AMOn Thu, 2024-09-26 at 04:21 +0000, Robert Stuart bobstuart@xxxxxxx wrote: > > tokenize(./@someAttribute) works great in HE but bombs in EE with A > sequence of more than one item is not allowed as the first argument > of fn:tokenize() Right. This is because the schema gives @someAttrib . . . Read full entry » Re: XSLT 3.1 that keeps both Saxon EE and HE happy andPosted 9/26/2024 4:32:05 AMOn Thu, Sep 26, 2024 at 04:21:07AM -0000, Robert Stuart bobstuart@xxxxxxx scripsit: > I have quite a few attributes whose values are space delimited tokens. > Saxon EE C"BB knowsC"BB they are lists of tokens since the schema does have > them a lists so they can be constrained an . . . Read full entry » XSLT 3.1 that keeps both Saxon EE and HE happy and toPosted 9/26/2024 4:20:49 AMI have quite a few attributes whose values are space delimited tokens. Saxon EE b knowsb they are lists of tokens since the schema does have them a lists so they can be constrained and validated at the XSD level. tokenize(./@someAttribute) works great in HE but bombs in EE with A sequence of more . . . Read full entry » Upcoming virtual coursesfrom Delightful ComputingPosted 9/26/2024 3:12:49 AMHello! Ibm running some XML and Web courses. Exact dates depend on the people taking the courses. All online with a live instructor. (1) Introduction to XSLT With a focus on maintaining and exploring existing XSLT. Gentle. Includes perspective/context on when to use Schematron, XSD, R . . . Read full entry » Re: Match content within Two FilesPosted 9/26/2024 3:11:51 AMOn Fri, 2024-08-23 at 12:00 +0000, Byomokesh Sahoo sahoo.byomokesh@xxxxxxxxx wrote: > Hi, > > How can I take that particular value without impacting other content > in the same line? Did you get sorted out? I donbt see replies to this. liam -- Liam Quin,B https://www.delightfulcomp . . . Read full entry » Re: [ANN] Upcoming XSpec v3.1Posted 9/10/2024 2:49:35 PMSorry for using formatted text that looks bad in a plain-text view. Trying again... --- We plan to release XSpec v3.1 during the week of September 23, 2024. Please try the release candidate, and feel free to report any bugs, feature requests, or feedback. You may be interested in these changes: . . . Read full entry » [ANN] Upcoming XSpec v3.1Posted 9/9/2024 9:33:43 PMWe plan to release XSpec v3.1 during the week of September 23, 2024. Please try the release candidate, and feel free to report any bugs, feature requests, or feedback. You may be interested in these changes: Common to Languages Under Test *XSpec is tested with Saxon 12.5, except that the detailed . . . Read full entry » Declarative Amsterdam 2024 - Register nowPosted 9/4/2024 9:15:49 AMDeclarative Amsterdam 2024 will be happening at CWI, Amsterdam Science Park on Thursday/Friday November 7 and 8, 2024. * On Thursday morning we start with tutorials on XForms, in-source testing and iXML. Make sure to bring your own device to participate optimally in the hands-on sessions. * The sy . . . Read full entry » XSL-List GuidelinesPosted 9/1/2024 4:21:28 PMThis 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: Match content within Two FilesPosted 8/23/2024 12:04:31 PMOn 23/08/2024 14:00, Byomokesh Sahoo sahoo.byomokesh@xxxxxxxxx wrote: > Hi, > > How can I take that particular value without impacting other content > in the same line? > > Example: > > <text>If, however, the payment s 22A(1) made without</text> > should be &g . . . Read full entry » Match content within Two FilesPosted 8/23/2024 11:59:49 AMHi, How can I take that particular value without impacting other content in the same line? Example: <text>If, however, the payment s 22A(1) made without</text> should be <text>If, however, the payment <strf jd="CTH" id="CTH_ACT_1975-91"> <strfact . . . Read full entry » Re: Match content within Two FilesPosted 8/22/2024 5:31:31 PM> On 22 Aug 2024, at 17:20, Byomokesh Sahoo sahoo.byomokesh@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Hi, > > Here is my code. > > EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/293509> (by email <>) And what exactly is yo . . . Read full entry » Match content within Two FilesPosted 8/22/2024 4:19:51 PMHi, Here is my code. <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="xs" version="2.0"> . . . Read full entry » Re: Scope of =>Posted 8/22/2024 2:49:23 PMThanks Michael Sent from my dish washer > On 22 Aug 2024, at 15:19, Michael Kay michaelkay90@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > o;? >> >> >> A = B => not() and (A=B) => not() >> >> Are different > > Yes, the ` . . . Read full entry » Re: Scope of =>Posted 8/22/2024 2:48:52 PMGet it, makes sense, thanks Sent from my dish washer On 22 Aug 2024, at 14:49, Alan Painter alan.painter@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: o;?The table that Martin pointed out from the specification indicates that it is in order of "lowest to highest& . . . Read full entry » Re: Scope of =>Posted 8/22/2024 1:18:36 PM> A = B => not() and (A=B) => not() > > Are different Yes, the `=>` operator has higher precedence than `=`. > > > A/B/C => distinct-values() and (A/B/C) => distinct-values() > > Are the same Yes, the `/` operator has higher precedence than `=>` . . . Read full entry » Re: Scope of =>Posted 8/22/2024 12:48:38 PMThe table that Martin pointed out from the specification indicates that it is in order of "lowest to highest", hence '=>' (line 16) has higher precedence than '=' (line 5). On Thu, Aug 22, 2024, 14:43 Leo Studer leo.studer@xxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> w . . . Read full entry » Re: Scope of =>Posted 8/22/2024 12:43:48 PM> Does https://www.w3.org/TR/xpath-31/#id-precedence-order help? Not really, I would expect A = B => not() and (A=B) => not() To be the same since = precedes => . . . Read full entry » Re: Scope of =>Posted 8/22/2024 12:35:57 PMOn 22/08/2024 14:23, Leo Studer leo.studer@xxxxxxxxxxx wrote: > Where can I find the specifics? Does https://www.w3.org/TR/xpath-31/#id-precedence-order help? . . . Read full entry » Scope of =>Posted 8/22/2024 12:23:38 PMHello I wonder about the scope of the => operator I use Oxygen with Saxon-EE 12.3 A = B => not() and (A=B) => not() Are different And A = B => not() and A= (B => not()) Are the same However A/B/C => distinct-values() and (A/B/C) => distinct-values() Are th . . . Read full entry » Re: Match content within Two FilesPosted 8/19/2024 9:14:02 PMCan you use file 2 to drive the processing flow? Find the file references in it and open file 1 to find your other details? That way file 2 drives the work flow and file 1 is just there as a lookup table.Sent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: "B . . . Read full entry » Re: Match content within Two FilesPosted 8/19/2024 7:20:04 PMWhat have you tried? Where did you get stuck? Rather than asking us to write the code for you, a good question explains what you did and how it failed, so we can help you over the next hurdle in your learning curve. Michael Kay Saxonica > On 19 Aug 2024, at 20:12, Byomokesh Sahoo sahoo.byomoke . . . Read full entry » Match content within Two FilesPosted 8/19/2024 7:12:18 PMHi, I have two files. Take the TITLE value from File 1 and match the content in file 2, then placing the tag as per file 1 including <XREFID>, and <LEGNAME>. Find the below File -1 <data> <row> <PARENTELEMENT>para0</PARENTELEMENT> <TITLE>s 588FGA</TI . . . Read full entry » Devastating News re CM Sperberg-McQueenPosted 8/19/2024 5:06:34 PMThere is no good way to start this message. There is no good way to share this news. So I'm just going to say it. Michael Sperberg-McQueen died last week. He leaves an enormous hole in many lives, many projects, many working groups, and many conferences. Balisage is hosting an online wake at: ht . . . Read full entry » Re: Processing a list of non-xml files in XSLT?Posted 8/14/2024 8:35:36 PMSorry, just noticed the use of that string is not in the original post.collection($rawditacollectionstring)Is how it was used.Sent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: "dvint dvint@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Dat . . . Read full entry » Re: Processing a list of non-xml files in XSLT?Posted 8/14/2024 8:24:01 PMIt is what you want. You use it with the collection call in the for-each. What i discovered here is the uri-collection() call for some reason doesn't use the same format which requires the escaping of the |.The select allows you to specify a selection string. In this case I'm looking for all .dita . . . Read full entry » Re: Processing a list of non-xml files in XSLT?Posted 8/14/2024 8:19:36 PMOn Wed, 2024-08-14 at 20:12 +0000, Mark Giffin m1879@xxxxxxxxxxxxx wrote: > B Changing the subject a bit, but what is this syntax > '?select=(*.dita|*.xml)' as an argument to concat()? > B > B <xsl:variable name="rawditacollectionString" > B \xA0\xA0\xA0\xA0\xA0\xA0\xA0 . . . Read full entry » Re: Processing a list of non-xml files in XSLT?Posted 8/14/2024 8:11:53 PMChanging the subject a bit, but what is this syntax '?select=(*.dita|*.xml)' as an argument to concat()? <xsl:variable name="rawditacollectionString" \xA0\xA0\xA0\xA0\xA0\xA0\xA0 select="concat($rawsrcPath, '?select=(*.dita|*.xml)')"/> I have assumed I could not get a . . . Read full entry » Re: Processing a list of non-xml files in XSLT?Posted 8/12/2024 8:52:55 PMOk, that fixed the problem.B ..danSent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: "Michael Kay michaelkay90@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: 8/12/24 1:40 PM (GMT-08:00) To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: R . . . Read full entry » Re: Processing a list of non-xml files in XSLT?Posted 8/12/2024 8:40:50 PM> Uh, it indeed seems that uri-collection behaves differently to collection: > Indeed. The URI is invalid because the vertical bar should be escaped as %7C. The collection() function is recovering from that by applying the iri-to-uri() function; the uri-collection() function should probably . . . Read full entry » Re: Aw: Re: Aw: Re: Processing a list of non-xml filesPosted 8/12/2024 7:45:48 PMOn 12/08/2024 21:20, dvint dvint@xxxxxxxxx wrote: I think I was illustrating the code that was working with that. Anyway, I have it as you show. It seems to be a bug in Saxon with the uri-collection() as I can use the select with a single file extension, as soon as I add the | and the second format . . . Read full entry » Re: Aw: Re: Aw: Re: Processing a list of non-xml filesPosted 8/12/2024 7:20:00 PMI think I was illustrating the code that was working with that. Anyway, I have it as you show. It seems to be a bug in Saxon with the uri-collection() as I can use the select with a single file extension, as soon as I add the | and the second format it fails...danSent from my Verizon, Samsung Galax . . . Read full entry » Re: Aw: Re: Aw: Re: Processing a list of non-xml filesPosted 8/12/2024 6:57:11 PMOn 12/08/2024 19:56, dvint dvint@xxxxxxxxx wrote: So it seems to be the ?select that is failing. If I just set it to a single format *.jpg it works, adding a second format *.jpg|*.png fails. In your original code and question you had B B ?select=(*.dita|*.xml) so based on that you should try B . . . Read full entry » Re: Aw: Re: Aw: Re: Processing a list of non-xml filePosted 8/12/2024 5:55:41 PMSo it seems to be the ?select that is failing. If I just set it to a single format *.jpg it works, adding a second format *.jpg|*.png fails.B Trying to figure out which version of Saxon is running in oxygen 26.0 as well as downloading 26.1 to see if it changes...danSent from my Verizon, Samsung Gal . . . Read full entry » Re: Aw: Re: Aw: Re: Processing a list of non-xml filePosted 8/12/2024 3:48:58 PMThere are no spaces, that is just the way oxygen produces the error messages.Sent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: "Martin Honnen martin.honnen@xxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: 8/12/24 8:36 AM (GMT-08:00) To . . . Read full entry » Aw: Re: Aw: Re: Processing a list of non-xml files inPosted 8/12/2024 3:36:31 PMSpaces in URIs need to be escaped -- Gesendet mit der GMX Mail AppAm 12.08.24, 17:27 schrieb "dvint@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>: That was a typo after testing different things. I still get the error, but now with the ? Invalid URI passed to uri-coll . . . Read full entry » Re: Aw: Re: Processing a list of non-xml files in XSLPosted 8/12/2024 3:27:12 PMThat was a typo after testing different things. I still get the error, but now with the ? Invalid URI passed to uri-collection: file:/Users/danvint/C"BB pubsrc/_src-data-files/C"BB asciidoc-processing/C"BB Ixia-Source/C"BB dita-files/C"BB FORMAT_sample_2_1_Early_ . . . Read full entry » Aw: Re: Processing a list of non-xml files in XSLT?Posted 8/12/2024 3:07:10 PMThe question mark b o8 seems to be missing before the "select" -- Gesendet mit der GMX Mail AppAm 12.08.24, 17:03 schrieb "dvint@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>: Thanks, I was looking for something different for base-uri() rather than somethi . . . Read full entry » Re: Processing a list of non-xml files in XSLT?Posted 8/12/2024 3:02:46 PMThanks, I was looking for something different for base-uri() rather than something to create the collection differently. I've change the for loop to this: <xsl:for-each select=" uri-collection($rawimagecollectionString)" > <xsl:variable name="FILE" select="subs . . . Read full entry » Re: Processing a list of non-xml files in XSLT?Posted 8/9/2024 9:59:24 PMOn 09/08/2024 23:52, Martin Honnen martin.honnen@xxxxxx wrote: On 09/08/2024 23:28, dvint@xxxxxxxxx wrote: Is there anything I can use directly in XSL (this one stylesheet) that will just give me the filenames of these images? I can do some other preprocessing stages and build an xml file with al . . . Read full entry » Re: Processing a list of non-xml files in XSLT?Posted 8/9/2024 9:51:50 PMOn 09/08/2024 23:28, dvint@xxxxxxxxx wrote: I've created a conversion process to take DITA to asciidoc that works pretty well overall. What I have is: - a folder with all the dita, ditamaps, and images in a flat structure - a simplified format of the map as run through the normalize process I use t . . . Read full entry » Processing a list of non-xml files in XSLT?Posted 8/9/2024 9:27:49 PMI've created a conversion process to take DITA to asciidoc that works pretty well overall. What I have is: - a folder with all the dita, ditamaps, and images in a flat structure - a simplified format of the map as run through the normalize process I use the simplified map to determine what files . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/8/2024 2:10:38 PMHi, I've been reading about node-set (and also mode), and it is a bit confusing, but I think that basically, even if I/we implement the XSLT chaining, what we need to do is going to have to kind of be similar to using XProc, in the sense, that we have to implement a kind of "overlord" XS . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/8/2024 12:37:17 PMHi, I guess I will continue this topic in this same thread then..... First, as an aside, I have asked about possibly using XProc, and am awaiting response. Also, I think most of the examples of chaining that I was able to find were using at least XSLT 1.0 (yes, I know :( !!! )... So, then, here . . . Read full entry » upcoming course - XSLT For MePosted 8/7/2024 11:26:34 PMAn introduction, or booster course. Want to level up in XSLT? Maintaining or altering style sheets and finding it hard? * Introduces the big picture concepts behind XSLT * Flow with the zen and see how to write stylesheets that are easier to maintain and change * See how XSLT fits into ecosys . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 9:49:45 PMOn Wed, 2024-08-07 at 21:09 +0000, ohaya ohaya@xxxxxxxxx wrote: > > Also, now that I think I/we've gotten past the existence of the node- > set() function, I am going to start trying to implement/test the > chaining, so I think it'd be better to start a new thread for that. The usual a . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 9:27:39 PMPaul, I did take a quick look at the xprocs link earlier - but, from my experience, the env I am in kind of discourages bringing new software in... Now that I've gotten past that exslt question, I'll try to do some checking if they would go that route, but also, meanwhile, I am going to have to gi . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 9:09:32 PMFYi, just for completeness - I did output some of the system.properties when the XSLT was run on the product, and I got this: xsl:versionB - 1xsl:vendor - Apache Software Foundationxsl:vendor-url - http://xml.apache.org/xalan-c So the product IS using XALAN-c Also, now that I think I/we've gott . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 8:53:36 PMLiam, I think I had a "brain spasm" and, for the "test" I was comparing to '' (2 single quotes), instead of just using the boolean returned by the function-available() :)....., which actually looks like it worked ;) !!B But I've changed it now to just use the boolean returned . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 8:41:44 PMOn 07/08/2024 21:44, ohaya ohaya@xxxxxxxxx wrote: > > > I don't remember mentioning Xalan, and actually THAT (which XSLT > processor was being used) was a question I had. > > > You said (in a message of the thread titled "Running xsltproc does not produce any output") . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 8:23:42 PMOn Wed, 2024-08-07 at 19:33 +0000, ohaya ohaya@xxxxxxxxx wrote: > > B B B <xsl:choose> > B B B B B B B <xsl:when test="function-available('exslt:node-set') = ''"> > B B B B B B B B B B B <xsl:message>+++++++++ exslt:node-set NOT available > ;)</xsl:m . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 7:54:28 PMOn 07/08/2024 21:44, ohaya ohaya@xxxxxxxxx wrote: > Martin, > > I don't remember mentioning Xalan, and actually THAT (which XSLT > processor was being used) was a question I had. > > I think in a previous thread it was stated that you use xsltproc to test but in your product you h . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 7:44:24 PMMartin, I don't remember mentioning Xalan, and actually THAT (which XSLT processor was being used) was a question I had. Given what I just found and posted about the testing on the product (that it worked, but with the exslt: prefix and NOT with msxsl: prefix) - can we conclude that the XSLT pro . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 7:39:30 PMHi Martin!! FYI, sorry, I wanted to let you know that I wasn't ignoring your messages on purpose :(!!B I just looked in Spam folder in Yahoo email and only then saw your messages. Again, my apologies... Jim On Wednesday, August 7, 2024 at 11:48:37 AM EDT, Martin Honnen martin.honnen@xxxxx . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 7:32:59 PMHi David (et al), Wow, this is kind of scary :( !! So I tested on xsltproc with the exlst: prefix and and it said the node-set was available.... So then I tested on the product itself, and I modified the test code to use "msxsl:" prefix and when i tested it said it was NOT available :( . . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 6:48:48 PMOn 07/08/2024 20:11, ohaya ohaya@xxxxxxxxx wrote: > I just tried (this was before your response below came in: > > > <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > B B B B B xmlns:exslt="http://exslt.org/common" > B B B B B xmlns:msxsl= . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 6:11:18 PMI just tried (this was before your response below came in: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" B B B B B xmlns:exslt="http://exslt.org/common" B B B B B xmlns:msxsl="urn:schemas-microsoft-com:xslt" B B B B B version="1.0"& . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 5:59:19 PMOn Wed, 7 Aug 2024 at 18:18, ohaya ohaya@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > David, > > The way the product works, is there is a config parameter that point to > the XLST file to be used and then the output from the XSLT gets sent to the > actual targ . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 5:18:10 PMDavid, The way the product works, is there is a config parameter that point to the XLST file to be used and then the output from the XSLT gets sent to the actual target syslogd (over network), so no browser is involved.... I read through your page and it mentions: function-available('exslt:node-se . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 5:00:46 PM> b) Also, I am wondering if anyone here has tried something like what I am describing, the "daisy-chaining" of XSLTs? If so, are there any other "gotchas"? > Yes, running a pipeline of transformations is absolutely standard practice and a highly recommended way of achie . . . Read full entry » Re: Bug in Saxon?Posted 8/7/2024 4:57:00 PMThe software is working as designed, and it's in conformance with the spec. Warnings tend to attract strong opinions, some people value them and others don't. Some people have a self-imposed rule that the code must execute without warnings, and by doing that they are making life a bit more difficu . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 4:54:32 PMIs XProc [1] possible in your solution space? It was designed for this sort of problem. bPaul [1] https://xproc.org/ > On Aug 7, 2024, at 10:36, ohaya ohaya@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > o;? > Hi, > > Currently, I am currently working wit . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 4:21:10 PMOn 07/08/2024 18:13, David Carlisle d.p.carlisle@xxxxxxxxx wrote: seems like only yesterday on this list I advertised http://dpcarlisle.blogspot.com/2007/05/exslt-node-set-function.html to make exslt:node-set work seamlessly on systems that supported it and systems that had a similar function in . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 4:13:35 PMseems like only yesterday on this list I advertised http://dpcarlisle.blogspot.com/2007/05/exslt-node-set-function.html to make exslt:node-set work seamlessly on systems that supported it and systems that had a similar function in a different namespace David (a greyer version) On Wed, 7 Aug 2 . . . Read full entry » Re: Daisy chaining XSLT and also how can I check whethPosted 8/7/2024 3:48:18 PMOn 07/08/2024 17:36, ohaya ohaya@xxxxxxxxx wrote: > > > From those threads above, it sounds like what I thinking of doing is > POSSIBLE, but one of the requirements is the availability of an extension: > > ext:node-set > > So I wanted to find out: > > a) How can I chec . . . Read full entry » Daisy chaining XSLT and also how can I check whether tPosted 8/7/2024 3:35:46 PMHi, Currently, I am currently working with a product that outputs syslog output that is formatted as XML, and the product also supports configuring an XSLT that will process the raw syslog XML from the product, before sending the transformed output to the syslog server target. The product comes wit . . . Read full entry » Re: Bug in Saxon?Posted 8/7/2024 1:09:31 PMOn 07/08/2024 15:00, Roger L Costello costello@xxxxxxxxx wrote: > > Okay, I upgraded to saxon-ee-12.5.jar and I get the same warning > message. When I run my actual program, I get dozens of these warning > messages until finally I get a message b No more warnings will be > displayedb . . . Read full entry » Re: Bug in Saxon?Posted 8/7/2024 1:06:30 PM> I believe this is a bug in the Saxon 12.4 > > Do you agree? If yes, is there a way to work around the bug? Looks like. In the example you posted, $legacy-ARINC-elmt-value is a string of six spaces. Consequently $whole-part is a string of 3 spaces. Saxon is correctly warning you that the . . . Read full entry » Re: Bug in Saxon?Posted 8/7/2024 1:00:24 PMHi Martin, Ouch! Okay, I upgraded to saxon-ee-12.5.jar and I get the same warning message. When I run my actual program, I get dozens of these warning messages until finally I get a message b No more warnings will be displayedb Turning off warning messages is not acceptable. Here is my complete . . . Read full entry » Re: Bug in Saxon?Posted 8/7/2024 12:30:02 PMOn 07/08/2024 14:16, Roger L Costello costello@xxxxxxxxx wrote: Hi Folks, I have an XSLT program with this template rule: <xsl:template match="/"> <arcRadius> <xsl:variable name="legacy-ARINC-elmt-name" select="'ARC_Radius'" as="xs:s . . . Read full entry » Bug in Saxon?Posted 8/7/2024 12:16:24 PMHi Folks, I have an XSLT program with this template rule: <xsl:template match="/"> <arcRadius> <xsl:variable name="legacy-ARINC-elmt-name" select="'ARC_Radius'" as="xs:string"/> <xsl:variable name="legacy-ARINC- . . . Read full entry » Re: xslidePosted 8/2/2024 7:29:01 PMOn 02/07/2024 02:28, Paul Tyson phtyson@xxxxxxxxxxxxx wrote: Count me as another 2-decade user of xslide, also unaware of the github site. Every few years I find myself setting up a new emacs environment, and every time I search for "xslide emacs", but this is the first time the github si . . . Read full entry » XSL-List GuidelinesPosted 8/1/2024 12:00:02 PMThis 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: How to remove a single quote?Posted 7/31/2024 10:24:51 PM> On 31/07/2024 21:51, dvint@xxxxxxxxx <mailto:dvint@xxxxxxxxx> wrote: >> I have content like this: >> >> <topic file="fs_task_with_collapse_in_tabs.dita" >> title="FORMAT: task inside a tab using collapsed sections" >> chunk=&qu . . . Read full entry » Re: How to remove a single quote?Posted 7/31/2024 8:02:01 PMOn 31/07/2024 21:51, dvint@xxxxxxxxx wrote: I have content like this: <topic file="fs_task_with_collapse_in_tabs.dita" B B B B title="FORMAT: task inside a tab using collapsed sections" B B B B chunk="child" B B B B B B B tabtitle="'Collapse Sections'"&g . . . Read full entry » Re: How to remove a single quote?Posted 7/31/2024 7:57:54 PMOn 31/07/2024 21:51, dvint@xxxxxxxxx wrote: > I have content like this: > > <topic file="fs_task_with_collapse_in_tabs.dita" > B B B B title="FORMAT: task inside a tab using collapsed sections" > B B B B chunk="child" > B B B B B B B tabtitle=&quo . . . Read full entry » Re: How to strip a single quote?Posted 7/31/2024 7:57:22 PMthanks, that was a missend, but the answer is still valid On 2024-07-31 12:46, David Carlisle d.p.carlisle@xxxxxxxxx wrote: > replace(@tabtitle, '''','') > > David > > On Wed, 31 Jul 2024 at 20:41, dvint@xxxxxxxxx > <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > . . . Read full entry » Re: How to strip a single quote?Posted 7/31/2024 7:57:00 PMthanks, that was a missend, but the answer is still valid On 2024-07-31 12:47, Martin Honnen martin.honnen@xxxxxx wrote: On 31/07/2024 21:41, dvint@xxxxxxxxx wrote: I have content like this <topic file="fs_task_with_collapse_in_tabs.dita" B B B B title="FORMAT: task inside a tab . . . Read full entry » How to remove a single quote?Posted 7/31/2024 7:51:31 PMI have content like this: <topic file="fs_task_with_collapse_in_tabs.dita" title="FORMAT: task inside a tab using collapsed sections" chunk="child" tabtitle="'Collapse Sections'"> Notice the single quotes in the tabtitle attrbiute. I would li . . . Read full entry » Re: How to strip a single quote?Posted 7/31/2024 7:47:20 PMOn 31/07/2024 21:41, dvint@xxxxxxxxx wrote: I have content like this <topic file="fs_task_with_collapse_in_tabs.dita" B B B B title="FORMAT: task inside a tab using collapsed sections" chunk="child" tabtitle="'Collapse Sections'"> translate(@tabtitle, . . . Read full entry » Re: How to strip a single quote?Posted 7/31/2024 7:46:24 PMreplace(@tabtitle, '''','') David On Wed, 31 Jul 2024 at 20:41, dvint@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > I have content like this > > <topic file="fs_task_with_collapse_in_tabs.dita" > title="FORMAT: task inside a tab u . . . Read full entry » How to strip a single quote?Posted 7/31/2024 7:41:17 PMI have content like this <topic file="fs_task_with_collapse_in_tabs.dita" title="FORMAT: task inside a tab using collapsed sections" chunk="child" tabtitle="'Collapse Sections'"> . . . Read full entry » Re: Does it make sense to collect elements with a certPosted 7/31/2024 4:06:43 PM> To my way of thinking, there is no benefit. I collected <row> elements with a matching ARPT_IDENT, then the assert tests that the collected <row> elements have a matching ARPT_IDENT. The assert seems pointless/redundant/useless/wasteful. Am I missing something? > That's surely . . . Read full entry » Re: Does it make sense to collect elements with a certPosted 7/31/2024 3:09:01 PM> Does it make sense to verify that every <row> element in $nav-records-for-this-airport > has an ARPT_IDENT that matches $airport-id? Is there a benefit to this assert: No, unless you are testing the correctness of the XPath processor itself. Such an assert could though be useful if . . . Read full entry » Re: Does it make sense to collect elements with a certPosted 7/31/2024 2:58:42 PMHi Roger, In case you process $nav-records-for-this-airport in another template or function, then it might be helpful to verify that the provided data matches the expectation. But as shown directly following the original selection seems unnecessary. Unless you consider someone tasked to change th . . . Read full entry » Re: Does it make sense to collect elements with a certPosted 7/31/2024 2:47:13 PMOn 31/07/2024 15:58, Roger L Costello costello@xxxxxxxxx wrote: > Hi Folks, > > $airport-id holds the identifier of an airport. > > I use $airport-id to collect <row> elements in $airports-nav-records with a matching ARPT_IDENT: > > <xsl:variable name="nav-records . . . Read full entry » Does it make sense to collect elements with a certainPosted 7/31/2024 1:58:01 PMHi Folks, $airport-id holds the identifier of an airport. I use $airport-id to collect <row> elements in $airports-nav-records with a matching ARPT_IDENT: <xsl:variable name="nav-records-for-this-airport" select="$airports-nav-records//row[ARPT_IDEN . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/24/2024 4:13:19 AMHi Liam, I was going to post earlier, but I'm still tied up working this, but I think I've made some progress... I was able to set a variable as follows: <xsl:template match="/syslog/audit_record/ExtraDetails"> B B B B B B B B B B B B B B B <ExtraDetails> <xsl:variabl . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/24/2024 2:56:07 AMOn Tue, 2024-07-23 at 21:47 +0000, ohaya ohaya@xxxxxxxxx wrote: > B > Hi, > > I think I spoke too soon. > > I've been trying to modify the original example below, which uses the > $input variable that gets set from the stringparam on the xsltproc > command line, to populate . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 9:47:22 PMOn Tue, 2024-07-23 at 12:27 +0000, Martin Honnen martin.honnen@xxxxxx wrote: > > But I think in the meantime you found the system you have to run your > XSLT 1.0 with uses Xalan C++ 1.2 so I don't see why looking for > xsltproc/libxslt extensions is helpful to write code. Right - i mis . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 9:47:22 PMHi, I think I spoke too soon. I've been trying to modify the original example below, which uses the $input variable that gets set from the stringparam on the xsltproc command line, to populate the before-tab and after-tab vars, to work with the incoming XML, auditrecord.xml, but I don't quite know . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 5:22:39 PMJim, nice job. It's good to see the stars aligned on this one (if that's what it is). Regards, Wendell From: ohaya ohaya@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Sent: Tuesday, July 23, 2024 12:53 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Cc: ohaya@xxxxxxxxx Subject: Re: Running x . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 4:52:29 PMLiam, I was able to get your suggested code working with xsltproc.. actually I kind of "enhanced" it a bit... <?xml version="1.0"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:param name="input&qu . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 2:10:46 PMJim, See, what he said. p XSLT 1.0 is something of an art but it is not dead, there are still practitioners and neat solutions to be had. (You might even find coaches if you approach it the right way, maybe contributors to this list who write XSLT in return for sandwiches or other valued asset . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 2:04:10 PMJim, I proposed looking at a "Fiddle" only as a way of assessing capabilities of versions (note plural) of XSLT with respect to your issue. If you know that your solution must run in a given processor supporting XSLT 1.0, then you are (a) stuck without regular expressions, while not stu . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 12:44:38 PMOn 23/07/2024 14:32, ohaya ohaya@xxxxxxxxx wrote: > > > If xsltproc won't work (because no regex extension), then I think that > maybe that XSLT Fiddle website that Wendell suggested in his message > might work? > I am not sure which XSLT fiddle Wendell had in mind, if you want to . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 12:32:16 PMHi, If xsltproc won't work (because no regex extension), then I think that maybe that XSLT Fiddle website that Wendell suggested in his message might work? Jim On Tuesday, July 23, 2024 at 07:31:45 AM EDT, ohaya <ohaya@xxxxxxxxx> wrote: Hi, This is what I get when I run xsltproc -- . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 12:27:24 PMOn 23/07/2024 13:32, ohaya ohaya@xxxxxxxxx wrote: > > > This is what I get when I run xsltproc --dumpextensions: > But I think in the meantime you found the system you have to run your XSLT 1.0 with uses Xalan C++ 1.2 so I don't see why looking for xsltproc/libxslt extensions is helpful . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 11:31:58 AMHi, This is what I get when I run xsltproc --dumpextensions: [root@nodejs ~]# xsltproc --dumpextensions Registered XSLT Extensions -------------------------- Registered Extension Functions: {http://exslt.org/common}object-type {http://exslt.org/math}max {http://exslt.org/math}power {http://exslt.o . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 11:29:16 AMHi Liam, To clarify what I posted, when I had "[Tab]" that is LITERALLY 5 characters string, "[" followed by "Tab" and then followed by "]". Thanks, Jim On Monday, July 22, 2024 at 11:58:49 PM EDT, Liam R. E. Quin <liam@xxxxxxxxxxxxxxxx> wrote: . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 4:00:51 AMOn Tue, 2024-07-23 at 03:01 +0000, ohaya ohaya@xxxxxxxxx wrote: > > So I was looking at a regex that would check for that (2 strings same > length) and found this: > I forgot to add, i donbt think xsltproc supports regular expressions. They are not in XSLT 1 (or XPath 1), although xsl . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 3:59:01 AMOn Tue, 2024-07-23 at 03:01 +0000, ohaya ohaya@xxxxxxxxx wrote: > B > I am starting to look into what needs to be done (Note this might be > a little off-topic)... > > First, reminder, the <ExtraDatails> has like: > > Command=Password$[Tab]Password$;ConnectionComponentId . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/23/2024 3:01:22 AMI am starting to look into what needs to be done (Note this might be a little off-topic)... First, reminder, the <ExtraDatails> has like: Command=Password$[Tab]Password$;ConnectionComponentId=Users;DstHost=my.soluti ons;Protocol=NC;ID=Server_W01;SessionID=0c97ce2e-c0a2-467d-952e-e1b81a9a514 . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/22/2024 9:57:39 PMJim, But your requirements are pretty well within what XSLT 1.0 will do, allowing for how ugly the string processing is likely to be - so you're not completely stuck. I would recommend playing around with the XSLT in an online test environment - there are a bunch that will run in your browser saf . . . Read full entry » [ANN] BALISAGE OPEN MIC - Invitation to ParticipatePosted 7/22/2024 7:38:04 PMANNOUNCING Open Mic: Anything Goes. Balisage participants are invited to give 2 to 10 minutes presentations on any topic (within the limits of the conference Code of Conduct). Share a markup-related achievement, ask for help with a problem, announce a new tool or updated specification, remind us . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/22/2024 7:19:52 PMHi Wendell, as I mentioned, this is being done in the context of a COTs (commercial product), so we don't have much flexility as far as the XSLT version (more precisely, it would be a LOT of other things involved, like approvals, etc.), so I think we are stuck with XSLT 1.0, unless it is not possi . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/22/2024 3:37:41 PMHello Jim, Congratulations on getting it to work so far. Others may have other advice, but I'd recommend continuing down the XSLT path here --- or at least looking. It's not that calling to Java wouldn't work (it might work fine), it's just that unless you can replace the XSLT altogether, it's ad . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/22/2024 12:23:22 PMMartin, I just noticed that my subsequent posts were causing a "message too large" response from the mailing list and also the responses were going to my spam folder. FYI, in my replies, I did catch the problem of missing the <syslog> element and was able to make xsltproc "wor . . . Read full entry » Re: Running xsltproc does not produce any outputPosted 7/21/2024 3:00:08 PMOn 21/07/2024 16:43, ohaya ohaya@xxxxxxxxx wrote: > > I am going to have to modify one of the base XSLTs so I wanted to try > xsltproc (on CENTOS) to test/debug, but when I ran a sample XML output > using one of the base XSLTs, xsltproc doesn't produce any output (and > no errors eit . . . Read full entry » Running xsltproc does not produce any outputPosted 7/21/2024 2:43:24 PMHi, I am doing some work with a product that produces XML in the syslog output, and the product configuration allows for specifying an XSLT to transform the raw XML into text format, and they provide several base example XSLT for different targets. I am going to have to modify one of the base XSLTs . . . Read full entry » [ANN] Thinking and Talking about Markup, XML, and relaPosted 7/17/2024 11:19:20 PM--~---------------------------------------------------------------- . . . Read full entry » Re: Announce: xjslt, an XSLT 2.0 compiler in TypeScripPosted 7/11/2024 3:23:46 AMMultiple result documents are now supported :) best, Erik On Mon, Jul 8, 2024 at 8:39b/AM Erik Hetzner ehetzner@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Right now it returns a single DOM tree, no reason why it can't support > multiple result trees, but it's no . . . Read full entry » Re: Announce: xjslt, an XSLT 2.0 compiler in TypeScripPosted 7/8/2024 3:39:20 PMRight now it returns a single DOM tree, no reason why it can't support multiple result trees, but it's not something I've done yet. best, Erik On Mon, Jul 8, 2024 at 8:31b/AM Martin Honnen martin.honnen@xxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > > On 08/07/2024 17: . . . Read full entry » Re: Announce: xjslt, an XSLT 2.0 compiler in TypeScripPosted 7/8/2024 3:31:26 PMOn 08/07/2024 17:21, Erik Hetzner ehetzner@xxxxxxxxx wrote: Hi all, I have written an XSLT 2.0 compiler (targeting JavaScript) in TypeScript. It was written to see if it was possible, and I don't know how useful it will prove, or how complete it will ever be, but it does work (with quirks, mistake . . . Read full entry » Announce: xjslt, an XSLT 2.0 compiler in TypeScriptPosted 7/8/2024 3:21:06 PMHi all, I have written an XSLT 2.0 compiler (targeting JavaScript) in TypeScript. It was written to see if it was possible, and I don't know how useful it will prove, or how complete it will ever be, but it does work (with quirks, mistakes and missing pieces). If you are interested, please have a . . . Read full entry » Re: Does starts-with() convert the strings to codepoinPosted 7/8/2024 2:13:12 PM> Does the starts-with() function convert the strings to codepoints and then checks that codepoint[i] in the <name> string equals codepoint[i] in the <Airport_Name> string? > No, it doesn't. Like everything else in XSLT, it operates on the XDM data model. (Surely as an experienc . . . Read full entry » Re: How to get the trailing spaces in a string?Posted 7/8/2024 1:22:10 PMHm, how about replace(Airport_Name,'^.*\S','') Enjoy, Wendell -----Original Message----- From: Roger L Costello costello@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Sent: Monday, July 8, 2024 8:42 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: How to get the trailing spaces in a . . . Read full entry » Re: How to get the trailing spaces in a string?Posted 7/8/2024 1:07:32 PMOn 08/07/2024 13:49, John Lumley john@xxxxxxxxxxxx wrote: Sorry - misread your requirement: replace(AirportName,'^(.*[^ ])?( +$)','$2') where $2 will any trailing spaces after an optional sequence ending in a non-space. I'm sure there's a shorter one.... > On 08/07/2024 13:41, Roger L Coste . . . Read full entry » Re: How to get the trailing spaces in a string?Posted 7/8/2024 12:49:13 PMOn 08/07/2024 13:41, Roger L Costello costello@xxxxxxxxx wrote: > Hi Folks, > > The value of this element contains trailing spaces: > > <Airport_Name>LOWELL FLD </Airport_Name> > > A few days ago Martin showed how to obtain the string before the t . . . Read full entry » Re: How to get the trailing spaces in a string?Posted 7/8/2024 12:48:19 PMOn 08/07/2024 14:41, Roger L Costello costello@xxxxxxxxx wrote: Hi Folks, The value of this element contains trailing spaces: <Airport_Name>LOWELL FLD </Airport_Name> A few days ago Martin showed how to obtain the string before the trailing spaces. (Thanks Martin!) . . . Read full entry » How to get the trailing spaces in a string?Posted 7/8/2024 12:41:11 PMHi Folks, The value of this element contains trailing spaces: <Airport_Name>LOWELL FLD </Airport_Name> A few days ago Martin showed how to obtain the string before the trailing spaces. (Thanks Martin!) Now I need to obtain the trailing spaces. How to do that? /Ro . . . Read full entry » Re: Does starts-with() convert the strings to codepoinPosted 7/8/2024 12:27:44 PM> <Airport_Name>B & B BOYS RANCH </Airport_Name> > <name>B & B BOYS RANCH</name> > > Notice the former uses the XML ampersand entity whereas the latter uses hex character entity for ampersand. This expression: Thatbs just two diffe . . . Read full entry » Re: Does starts-with() convert the strings to codepoinPosted 7/8/2024 12:15:08 PMOn 08/07/2024 14:08, Roger L Costello costello@xxxxxxxxx wrote: Hi Folks, I have a question about the meaning of the starts-with() function. Consider the strings in these two elements: <Airport_Name>B & B BOYS RANCH </Airport_Name> <name>B & B BOYS R . . . Read full entry » Does starts-with() convert the strings to codepoints?Posted 7/8/2024 12:08:13 PMHi Folks, I have a question about the meaning of the starts-with() function. Consider the strings in these two elements: <Airport_Name>B & B BOYS RANCH </Airport_Name> <name>B & B BOYS RANCH</name> Notice the former uses the XML ampersand ent . . . Read full entry » Re: Seek an XPath expression that removes trailing spaPosted 7/6/2024 1:09:45 PMMartin Honnen wrote: Use 'replace' e.g. Airport_Name => replace('\s*$', '') Wow! A couple minor tweaks are needed: \s is more than just the space (x20) character. So, instead of \s I will use a space. When I executed the expression, I got this error message: FORX0003 The regular expres . . . Read full entry » Re: Seek an XPath expression that removes trailing spaPosted 7/6/2024 12:51:17 PMOn 06/07/2024 14:48, Roger L Costello costello@xxxxxxxxx wrote: > Hi Folks, > > I want to convert this: > > <Airport_Name>LOWELL FLD </Airport_Name> > > to this: > > <name>LOWELL FLD</name> Use `replace` e.g. B Airport_Name . . . Read full entry » Seek an XPath expression that removes trailing spacesPosted 7/6/2024 12:47:56 PMHi Folks, I want to convert this: <Airport_Name>LOWELL FLD </Airport_Name> to this: <name>LOWELL FLD</name> The value of the <name> element must be identical to the value of the <Airport_Name> element, except without the trailing spaces. . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 9:47:14 PMMartin, your alphabetic renderer is better than mine. Apologies, Wendell From: Martin Honnen martin.honnen@xxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Sent: Tuesday, July 2, 2024 5:40 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: targeting the 'first' instance of the same elemen . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 9:40:00 PMOn 02/07/2024 23:33, Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx wrote: > Did anyone put up > > <xsl:template match="head[. Is /descendant::head[1]]"/> Is "Is" an XPath operator or an Apple product? . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 9:33:16 PMHello, Did anyone put up <xsl:template match="head[. Is /descendant::head[1]]"/> ? Apologies if I have forgotten the actual requirement -- Cheers, Wendell -----Original Message----- From: Liam R. E. Quin liam@xxxxxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Sen . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 8:51:36 PMOn Tue, 2024-07-02 at 11:42 +0000, Jean-Paul Rehr rehrjb@xxxxxxxxx wrote: > > > > > > > for $div in $mydoc//body/div > > > return > > > B B B transform:transform($div, $myxsl, ()) > > > So, you want to match the first head element in each fragment . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:50:04 AMOn 02/07/2024 13:42, Jean-Paul Rehr rehrjb@xxxxxxxxx wrote: >That sounds as ifB match="(body/div//head)[1]" should do as the XSLT processor should still see the parent (or perhaps not, what is transform:transform?, BaseX or exist-db, would need to check how their XSLT function works e . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:41:50 AM>That sounds as if match="(body/div//head)[1]" should do as the XSLT processor should still see the parent (or perhaps not, what is transform:transform?, BaseX or exist-db, would need to check how their XSLT function works exactly). It's eXist-db's XSLT transformation function, that . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:40:57 AMOn 02/07/2024 13:32, Martin Honnen martin.honnen@xxxxxx wrote: > > > On 02/07/2024 13:28, Jean-Paul Rehr rehrjb@xxxxxxxxx wrote: >> >Or can the outer div appear at any level/with any nesting and parent >> container? >> >> The fragments I pass to the transformer a . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:32:20 AMOn 02/07/2024 13:28, Jean-Paul Rehr rehrjb@xxxxxxxxx wrote: > >Or can the outer div appear at any level/with any nesting and parent > container? > > The fragments I pass to the transformer always start with <div>. > > But toB explain the larger context: > > These &l . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:28:45 AM>Or can the outer div appear at any level/with any nesting and parent container? The fragments I pass to the transformer always start with <div>. But to explain the larger context: These <div> fragments are all *direct children* of a single <body>, but for a few reasons I ca . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:24:15 AMAh! I was reading carelessly. Itbs a pattern, rather than an expression, so it matches independently on each div that has descendant heads. You should be able to fine-tune it by adding a predicate, but perhaps therebs a more elegant pattern that Ibm overlooking, and that someone else will sugges . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:22:56 AMOn 02/07/2024 13:18, David Carlisle d.p.carlisle@xxxxxxxxx wrote: Note you asked originally for an xpath not an xslt pattern (which is why I suggested select="(.//head)[1] ") It was not quite clear what was asked for but I took "I have put in red the <head> element I want to . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:18:16 AMOn Tue, 2 Jul 2024 at 12:14, Jean-Paul Rehr rehrjb@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > >How about <xsl:template match="(div/descendant::head)[1]"> ? > > same result as Martin's solution, alas. > Note you asked originally for an xpath . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:16:52 AMOn 02/07/2024 13:05, Jean-Paul Rehr rehrjb@xxxxxxxxx wrote: > At first Martin's solutionB <xsl:template match="(div//head)[1]"> > looked like it would work. But then I started to test the various > documentsB I have to work with, in particular at the most problematic. > . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:14:09 AM>How about <xsl:template match="(div/descendant::head)[1]"> ? same result as Martin's solution, alas. On Tue, Jul 2, 2024 at 1:08b/PM David Birnbaum djbpitt@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > How about <xsl:template match="(div/desce . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:08:37 AMHow about <xsl:template match="(div/descendant::head)[1]"> ? On Jul 2, 2024, at 7:04b/AM, Jean-Paul Rehr rehrjb@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: o;?At first Martin's solution <xsl:template match="(div//head)[1]"> looked like . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 11:04:54 AMAt first Martin's solution <xsl:template match="(div//head)[1]"> looked like it would work. But then I started to test the various documents I have to work with, in particular at the most problematic. Below is an actual fragment, but I've put it in this Fiddle <https://martin-ho . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 10:41:18 AMOn 02/07/2024 12:34, Jean-Paul Rehr rehrjb@xxxxxxxxx wrote: > Dear XSL list, > > I am trying to target a specific <head> which can appear nested within > a variable number of <div> and possible <list> elements. In the three > examples below I have put in red the < . . . Read full entry » Re: targeting the 'first' instance of the same elementPosted 7/2/2024 10:35:59 AMselect="(.//head)[1]" On Tue, 2 Jul 2024 at 11:34, Jean-Paul Rehr rehrjb@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Dear XSL list, > > I am trying to target a specific <head> which can appear nested within a > variable number of <div> and . . . Read full entry » targeting the 'first' instance of the same element inPosted 7/2/2024 10:33:59 AMDear XSL list, I am trying to target a specific <head> which can appear nested within a variable number of <div> and possible <list> elements. In the three examples below I have put in red the <head> element I want to target with the same XSL template. In my way of thinkin . . . Read full entry » Re: xslide [Was: Rexsel — A simpler way of writing XSPosted 7/2/2024 7:42:59 AM> The code on GitHub has included Norm's packaging of Mohamed's XSLT 3.0 > schema for about 11 years: > > https://github.com/tkg/xslide Ibm planning to update that to cover XSLT 4.0 in due course. Unless Mohamed gets there first, of course! :-) . . . Read full entry » Re: xslide [Was: Rexsel — A simpler way of writing XSPosted 7/2/2024 1:27:38 AMCount me as another 2-decade user of xslide, also unaware of the github site. Every few years I find myself setting up a new emacs environment, and every time I search for "xslide emacs", but this is the first time the github site has appeared in the top hits. Can https://sourceforge. . . . Read full entry » Re: xslide [Was: Rexsel — A simpler way of writing XSPosted 7/1/2024 8:27:05 PMOn 01/07/2024 14:16, Tony Graham tgraham@xxxxxxxxxxxxx wrote: On 01/07/2024 11:11, Peter Flynn peter@xxxxxxxxxxx wrote: On 01/07/2024 09:41, Tony Graham tgraham@xxxxxxxxxxxxx wrote: On 30/06/2024 17:26, Peter Flynn peter@xxxxxxxxxxx wrote: Good to see that someone else is still using it: 'xslide', . . . Read full entry » Re: Rexsel — A simpler way of writing XSLT — thinkingPosted 7/1/2024 7:16:40 PM> For those of us who _like_ XML, at least overall, or who work routinely > with complex documents, or both :), XSLT is a small step and a very > welcome one. But we have to remember that this is not universal, > strange as it sometimes seems! Definitely! In fact, tree-processing can . . . Read full entry » Re: Re: Rexsel - A simpler way of writing XSLTPosted 7/1/2024 4:08:00 PMHi Wendell, Not yet... there is some elegance I still hope for, one day in my current tool stack. omnimark FIND rules offer regular expressions in a declarative way very much like templates in XSLT and if your target would be SGML or XML you can get feedback from the parser for conditionals on y . . . Read full entry » XProc 3.0 alternatives, was Re: Aw: Re: Rexsel — A siPosted 7/1/2024 3:28:28 PMMartin, That is an awesome question (XProc 3.0 under Python) and I am going to track it. Unfortunately I have no answer today. Its a little off-topic here or maybe it isnt but I have a project underway, one of whose goals to make XProc 3.0 easier to run and use, starting with Achim Berndzen . . . Read full entry » XSL-List GuidelinesPosted 7/1/2024 2:45:23 PMThis 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 » Aw: Re: Rexsel — A simpler way of writing XSLTPosted 7/1/2024 2:35:48 PMGood point in general, but is there a good and easy way to use XProc 3 from/with Python ? Am 01.07.24, 16:30 schrieb "Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>: Hello, Or, today, to process HTML into an XSLT pipeline, one might op . . . Read full entry » Re: Re: Rexsel — A simpler way of writing XSLTPosted 7/1/2024 2:29:50 PMHello, Or, today, to process HTML into an XSLT pipeline, one might opt for XProc 3.0. What with plain-text, JSON and HTML inputs, and with XSLT streaming and accumulators, maybe XSLT has finally caught up with Omnimark? Regards, Wendell -----Original Message----- From: Martin Honnen martin.honn . . . Read full entry » Re: xslide [Was: Rexsel — A simpler way of writing XSPosted 7/1/2024 1:15:37 PMOn 01/07/2024 11:11, Peter Flynn peter@xxxxxxxxxxx wrote: On 01/07/2024 09:41, Tony Graham tgraham@xxxxxxxxxxxxx wrote: On 30/06/2024 17:26, Peter Flynn peter@xxxxxxxxxxx wrote: Good to see that someone else is still using it: 'xslide', Updating it for XSLT3 would be nice, though. The code on Git . . . Read full entry » Re: xslide [Was: Rexsel — A simpler way of writing XSPosted 7/1/2024 10:11:08 AMOn 01/07/2024 09:41, Tony Graham tgraham@xxxxxxxxxxxxx wrote: On 30/06/2024 17:26, Peter Flynn peter@xxxxxxxxxxx wrote: Good to see that someone else is still using it: 'xslide', Updating it for XSLT3 would be nice, though. I doubt that Peter would ever stop using Emacs. Probably not. Using a si . . . Read full entry » xslide [Was: Rexsel — A simpler way of writing XSLT]Posted 7/1/2024 8:40:45 AMOn 30/06/2024 17:26, Peter Flynn peter@xxxxxxxxxxx wrote: ... I'm speaking in ignorance of other editors here, as I've been using Emacs with xslide-mode for two decades, and it both colourises and indents XSLT pretty well, as well as the usual auto-complete. I had always assumed other editors di . . . Read full entry » Re: Rexsel — A simpler way of writing XSLT — thinkingPosted 7/1/2024 12:45:31 AMOn Sun, 2024-06-30 at 22:19 +0000, Graydon graydon@xxxxxxxxx wrote: > On Sun, Jun 30, 2024 at 10:06:01PM -0000, Liam R. E. Quin > liam@xxxxxxxxxxxxxxxxx scripsit: > > A companion question is also interesting though - an > > XSLT that is useful for, and appeals to, curly-brace-prog . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 10:19:17 PMOn Sun, Jun 30, 2024 at 10:06:01PM -0000, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx scripsit: > A companion question is also interesting though - how do you made an > XSLT that is useful for, and appeals to, curly-brace-programming > people? I think Rexsel moves in that direction, but to get t . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 10:05:54 PMOn Sun, 2024-06-30 at 19:23 +0000, Michael Kay mike@xxxxxxxxxxxx wrote: > > > My only contact with Omnimark was that (around 1997 perhaps?) it > looked like just the thing we needed for a project, so I made > inquiries, and they sent over a sales rep, and quoted me a price that > . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 9:34:23 PMOn Sun, 2024-06-30 at 20:24 +0000, Peter Flynn peter@xxxxxxxxxxx wrote: > On 30/06/2024 20:46, Liam R. E. Quin liam@xxxxxxxxxxxxxxxxx wrote: > > > And Peter gets the tee-shirt award, > > b because life is too short > > to use W3C Schemasb > > > > https://www.red . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 8:50:42 PMOn 30/06/2024 19:20, Chris Papademetrious chrispitude@xxxxxxxxx wrote: Nowadays I mostly process HTML in Python. The funny thing is, I would kill for a way to natively process HTML5 in XSLT (without resorting to XHTML) because the content processing I do would fit a template based approach very wel . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 8:24:31 PMOn 30/06/2024 20:46, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx wrote: And Peter gets the tee-shirt award, b because life is too short to use W3C Schemasb https://www.redbubble.com/shop/ap/162489585 Thank you very much, I shall wear it everywhere. It can join my TEI tee-shirt, "Yesterday's Inform . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 8:21:38 PMOn 30/06/2024 20:23, Michael Kay mike@xxxxxxxxxxxx wrote: My only contact with Omnimark was that (around 1997 perhaps?) it looked like just the thing we needed for a project, The pricing was a problem when the CELT project started: it was the same as an entire year's funding. Fortunately Brian Tr . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 7:45:59 PMOn Sun, 2024-06-30 at 18:49 +0000, Hugh Field-Richards hsfr@xxxxxxxxxx wrote: > > Most editors will be syntax aware and colourise/indent XSLT. But what > they donbt do is perform any analysis of variables andB named > templatesB used and referenced as well as duplicates. For example, & . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 7:23:13 PM> I started with OmniMark (and SGML, but that is another story) before XSLT arrived and used that for some years finally going over to XSLT. Main reason being the cost of the former after they withdrew a free version. Irritating because OmniMark could process free text, not just tagged text such . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 6:57:16 PMSlip of the memory I fear b wonbt see the right side of 75 years again :-) I started with OmniMark (and SGML, but that is another story) before XSLT arrived and used that for some years finally going over to XSLT. Main reason being the cost of the former after they withdrew a free version. Irrit . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 6:48:48 PM> On 30 Jun 2024, at 17:26, Peter Flynn peter@xxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > >> Clearly I should have done some more homework on this, sighb& >> The thing that prompted me to design Rexsel was all the >> years spent on using OmniMark . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 5:19:46 PMHi everyone, I don't do as much XSLT these days (I moved from technical writing to AI), but I empathize with how intimidating the XSLT syntax/approach/everything can be for newcomers. I appreciate that others are looking for ways to make our little corner of the universe a bit more approachable. . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 4:26:06 PMOn 30/06/2024 14:22, Hugh Field-Richards hsfr@xxxxxxxxxx wrote: Clearly I should have done some more homework on this, sighb& The thing that prompted me to design Rexsel was all the years spent on using OmniMark, then crossing over to XSLT, and then needing to b pretty-printb some XSLT to mak . . . Read full entry » Re: Need a little help with xsl:evaluatePosted 6/30/2024 3:03:04 PMn<#secure method=pgpmime mode=sign> "Roger L Costello costello@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> writes: > Martin wrote: > >>> Set the context item with e.g. >>> <xsl:evaluate xpath="." context-item="."/> & . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 1:22:08 PMClearly I should have done some more homework on this, sighb& The thing that prompted me to design Rexsel was all the years spent on using OmniMark, then crossing over to XSLT, and then needing to b pretty-printb some XSLT to make it a bit more readable. Finally a light-bulb moment to realise . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 11:30:47 AMJoin the club. There have been a number of attempts to do this over the years, most of which have disappeared without trace. The most recent contribution was by Fredrik OLhrstroLm at XML Prague 2024, see page 85 of https://archive.xmlprague.cz/2024/files/xmlprague-2024-proceedings.pdf I think . . . Read full entry » Re: Rexsel — A simpler way of writing XSLTPosted 6/30/2024 11:23:46 AMOn Sun, 30 Jun 2024 at 12:03, Hugh Field-Richards hsfr@xxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Hi > > I have been working with XSLT/XML for sometime > now (>25 years) XSL Transformations (XSLT) Version 1.0 W3C Recommendation 16 November 1999 Diffic . . . Read full entry » Rexsel — A simpler way of writing XSLTPosted 6/30/2024 11:03:24 AMHi I have been working with XSLT/XML for sometime now (>25 years) and have been minded to look at alternative ways of generating XSLT scripts. As a result I have produced a language REXSEL that provides a simpler means of writing XSLT stylesheets. More information, downloads and news can be fo . . . Read full entry » Re: Need a little help with xsl:evaluatePosted 6/30/2024 10:50:53 AM> Okay, I did that. It resulted in the following error message. Is this a bug in Saxon? > Looks like this one, fixed nearly 3 years ago: https://saxonica.plan.io/issues/4975 Michael Kay Saxonica . . . Read full entry » Aw: Re: Need a little help with xsl:evaluatePosted 6/30/2024 10:18:19 AMI can't reproduce that with Saxon 12.4 HE.On line fiddle.Which Saxon version is that? Gesendet: Sonntag, 30. Juni 2024 um 12:08 Uhr Von: "Roger L Costello costello@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> An: "xsl-list@xxxxxxxxxxxxxxxxxxxxxx" <xsl-list@xxxx . . . Read full entry » Re: Need a little help with xsl:evaluatePosted 6/30/2024 10:08:26 AMMartin wrote: >> Set the context item with e.g. >> <xsl:evaluate xpath="." context-item="."/> Okay, I did that. It resulted in the following error message. Is this a bug in Saxon? java.lang.NullPointerException at java.base/java.util.Objects.requir . . . Read full entry » Re: Need a little help with xsl:evaluatePosted 6/30/2024 9:19:05 AMOn 30/06/2024 11:15, Roger L Costello costello@xxxxxxxxx wrote: > What am I doing wrong? How to fix it? Set the context item with e.g. B B <xsl:evaluate xpath="." context-item="."/> . . . Read full entry » Need a little help with xsl:evaluatePosted 6/30/2024 9:15:23 AMHi Folks, I want to evaluate the XPath expression that is inside the <predicate> element: <mappings> <mapping> <Airport_Name>GENERAL EDWARD LAWRENCE LOGAN </Airport_Name> <name>GENERAL EDWARD LAWRENCE LOGAN</name> <predicate . . . Read full entry » Re: How to incrementally add to a result document?Posted 6/29/2024 3:06:39 PMRoger, I've posted here about this schematron validation solution a couple times, most recently in response to a question of yours! [1]. Reviewing that post, I see I actually wrote a separate stylesheet to generate schematron. That's a traditional QA black box approach. Ideally, the mind that . . . Read full entry » Re: How to incrementally add to a result document?Posted 6/29/2024 12:20:17 PMAnother solution I would mention is to use xsl:message as a side-channel. Certainly with Saxon, it's easy enough to capture the xsl:message output in a separate XML file. The order of events passed to xsl:message isn't predictable in theory, but that's rarely a problem in practice. Michael Kay Sax . . . Read full entry » Re: How to incrementally add to a result document?Posted 6/29/2024 12:17:21 PM> I would represent the log as a global map variable and place any action there as an entry like {action-key, action-info}, immediately on completing each action. > > Finally, when the processing is finished, we can produce from the log-map a single result-document that contains all ent . . . Read full entry » Re: How to incrementally add to a result document?Posted 6/29/2024 9:49:14 AMOn 29/06/2024 00:39, Dimitre Novatchev dnovatchev@xxxxxxxxx wrote: > I would represent the log as a global map variable and place any > action there as an entry likeB {action-key, action-info}, immediately > on completing each action. Is that possible to have such a map as a global vari . . . Read full entry » Re: How to incrementally add to a result document?Posted 6/29/2024 9:29:22 AMOn 28/06/2024 23:39, Roger L Costello costello@xxxxxxxxx wrote: > Is there anyway that I can achieve what I desire -- output to one > document the result of mapping the old form to the new form and output > to another document metadata that describes the mapping steps that were > taken? . . . Read full entry » Re: How to incrementally add to a result document?Posted 6/29/2024 7:15:57 AMPaul Tyson wrote: > Will your "metadata" output be further machine > processed to prove the transformation integrity? Ha! That is exactly what I am planning to do! I will do the mapping and verify the mapping. > Years ago when I was asked to verify my transform > was correc . . . Read full entry » Re: How to incrementally add to a result document?Posted 6/29/2024 12:43:44 AMThis is an interesting sort of problem. Will your "metadata" output be further machine processed to prove the transformation integrity, or just human inspected? Years ago when I was asked to verify my transform was correct, I wrote out a schematron result-document with rules stating w . . . Read full entry » Re: How to incrementally add to a result document?Posted 6/28/2024 10:55:24 PMAlternatively, one could create a separate result-document (with different name) for every log entry and write these result-documents in a specially - dedicated to the transformation "log-directory". One could probably hope that in the event of an error that causes the transformation to . . . Read full entry » Re: How to incrementally add to a result document?Posted 6/28/2024 10:39:00 PMI would represent the log as a global map variable and place any action there as an entry like {action-key, action-info}, immediately on completing each action. Finally, when the processing is finished, we can produce from the log-map a single result-document that contains all entries of the l . . . Read full entry » Re: How to incrementally add to a result document?Posted 6/28/2024 10:13:53 PMRoger, Yes, what Martin said. If you don't like separate modes because you want your tracing logic coupled closely to your transformation logic, the classic 'XSLT approach' would be to build a unified tree in one pass, then post-process that tree twice, once for main outputs (filtering out the lo . . . Read full entry »
|
PURCHASE STYLUS STUDIO ONLINE TODAY!!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Learn Stylus Studio in 6 MinutesCan 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 KnowDoes 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. |
XML EDITOR
XML PRODUCTIVITY THROUGH INNOVATION ™
