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!


Re: ceiling(), floor(), and data types

Posted 9/14/2017 2:37:10 PM

Fully supporting xs:integer or xs:decimal would need for implementers to support arithmetics with infinite precision while, usually, programming language just allow int, long,..., float, double (even just double for Javascript, actually, while COBOL is smarter!). Then, specifically for ceiling() o . . . Read full entry »


Re: ceiling(), floor(), and data types

Posted 9/14/2017 2:23:57 PM

Answering "why" questions about specs is notoriously difficult. Do you want a historical exposition of how and when the decisions were made, or do you simply want an opinion as to why a reasonable designer might have chosen to do it that way? Looking at the history, the WG discussed the . . . Read full entry »


Re: ceiling(), floor(), and data types

Posted 9/14/2017 12:57:56 PM

It is preferable to have a result that is of the same type as the argument. This avoids the (possibly costly) conversion to xs:integer which may have implementation dependent limitations and loss of precision. Should a certain quality of a number automatically imply a certain datatype? Not all &qu . . . Read full entry »


ceiling(), floor(), and data types

Posted 9/14/2017 10:30:02 AM

Dear XSL List, I was surprised to learn today that ceiling() and floor() do not obligatorily return a value of type xs:integer. If I've understood correctly that they necessarily return a value that a human would consider an integer, is there a reason that other return types are permitted? Thanks . . . Read full entry »


FW: Job opening - Software Engineer (XML-based Techno

Posted 9/5/2017 1:53:34 PM

Forwarded from another list. Not my posting, don't ask me questions! Michele ---------------------------------------------------- Please see below for an opportunity at the Bodleian Libraries, University of Oxford. The closing date has been extended to 8 September 2017. ------------ . . . Read full entry »


XSL-List Guidelines

Posted 9/4/2017 5:34:39 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 »


XSL-List Guidelines

Posted 9/1/2017 9:50:40 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: Structuring templates

Posted 9/1/2017 4:57:16 PM

-----Original Message----- From: Martin Honnen martin.honnen@xxxxxx [mailto:xsl-list- service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Friday, September 1, 2017 10:47 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Structuring templates > Are you aware that XslCompiledTransform supports extension obj . . . Read full entry »


Re: Structuring templates

Posted 9/1/2017 4:46:23 PM

On 01.09.2017 18:16, Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx wrote: I am trying to split up a few large xsl templates where one contains a large block of msxsl:script based C# functions. Almost all of the templates use some quantity of the functions made available through this facility as well a . . . Read full entry »


Structuring templates

Posted 9/1/2017 4:16:17 PM

I am trying to split up a few large xsl templates where one contains a large block of msxsl:script based C# functions. Almost all of the templates use some quantity of the functions made available through this facility as well as some quantity of shared variables for data like apostrophes, quotes a . . . Read full entry »


Re: [XSL-List: The Open Forum on XSL] Digest for 2017

Posted 8/31/2017 12:31:24 PM

Hi Rahul, I might have an idea what you are trying to achieve, but I still donbt know exactly because something is still missing (see below). When you write <xsl:when test="exists($XMLMerge2/ClientInfo/clientdata[name = $Email_from_merge1])"> <xsl:copy> <xsl:cop . . . Read full entry »


Re: XSL matching and duplication!

Posted 8/31/2017 6:01:30 AM

Hi Rahul, A couple of observations/questions: b Assuming that you invoke the transformation with Input1.xml as the source, how does the stylesheet ever get to know Input2.xml in order to do any comparisons with clientdata/name? If Input1.xml is the input, I would have expected something like . . . Read full entry »


XSL matching and duplication!

Posted 8/31/2017 3:27:45 AM

Hi, i need data from input1.xml check first if clientname/id is matching with clientdata/name from input2.xml otherwise delete duplication based on clientname/Email from input1.xml, My duplication is working but i am not geetitng first condition data: <xsl:stylesheet version="2.0" xm . . . Read full entry »


Re: Can I use xsl:key to select elements up to certain

Posted 8/30/2017 10:20:00 PM

> And then I was doing the following to find all ancestors that share the same "topic ancestor": > > <xsl:variable name="ancestors-in-topic" > select="ancestor-or-self::*[ancestor-or-self::* = $topic]" as="element()*"/> > > This did n . . . Read full entry »


Re: Can I use xsl:key to select elements up to certain

Posted 8/30/2017 7:24:14 PM

Wouldn't assigning any element with an @id to a temporaty document and running rules against this reduce the overhead? -W On 30 August 2017 at 21:08, David Carlisle d.p.carlisle@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > You seem to be listing ancestor-or-self rather t . . . Read full entry »


Re: Can I use xsl:key to select elements up to certain

Posted 8/30/2017 7:19:16 PM

I think there may be a more efficient way to do this overall, but certainly if you declare those @id attributes as ID, then you could use the id() function. E.g.: --------- <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XS . . . Read full entry »


Re: Can I use xsl:key to select elements up to certain

Posted 8/30/2017 7:08:17 PM

You seem to be listing ancestor-or-self rather than ancestor, I think you only need to go up the ancestor axis once in each case, something like <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="/" . . . Read full entry »


Can I use xsl:key to select elements up to certain an

Posted 8/30/2017 6:49:12 PM

Hi all, I had an embarrassing moment today, when I found that the source of a severe performance problem was sitting in front of the screen. Using XSLT 2.0 I am transforming elements and at many points I have to look up the ancestor axis, but only up to an element with an attribute "id" . . . Read full entry »


Re: XPath string comparison of two strings representin

Posted 8/16/2017 7:14:08 PM

Yes, comparison as a string will work from 1000-01-01 to 9999-12-31, or the strings could be converted to dates as others have mentioned. But be sure this field is a DATE, not a DATE or DATE-TIME, as the latter in RFC 5545 permits time zones in any of 3 formats. At least one of those formats will . . . Read full entry »


Re: no XSLT Jobs USA

Posted 8/16/2017 7:10:20 PM

> StackOverflow currently has 9 job openings tagged XSLT, of which 5 are in Germany (Germany is also probably Saxonica's strongest market, if you exclude sales to software companies). These ads all list XSLT as one of a long list of technologies they are interested in, which reflects the fact th . . . Read full entry »


Re: XPath string comparison of two strings representin

Posted 8/16/2017 4:51:13 PM

> Note that I am doing mere string comparison. I am comparing the string '20170817' against the string '20170816'. > > Will the XPath always work? > It will always work if the dates are valid dates in the Gregorian calendar between years 0 and 9999, always represented by 4 digits, and . . . Read full entry »


Re: XPath string comparison of two strings representin

Posted 8/16/2017 4:43:48 PM

On Wed, Aug 16, 2017 at 04:09:15PM -0000, Costello, Roger L. costello@xxxxxxxxx scripsit: > Note that I am doing mere string comparison. I am comparing the string '20170817' against the string '20170816'. > > Will the XPath always work? If and only if you've got a guarantee that the dat . . . Read full entry »


Re: XPath string comparison of two strings representin

Posted 8/16/2017 4:36:02 PM

The values are not directly parseable as xs:date or xs:dateTime values, so I think youbll have to preprocess them to make proper date strings out of them and compare them as dates(), e.g.: local:makeDate(/Test/Date2) gt local:makeDate(/Test/Date1) Where I leave local:makeDate() as an exercise to . . . Read full entry »


Re: XPath string comparison of two strings representin

Posted 8/16/2017 4:26:38 PM

On 16 August 2017 at 18:09, Costello, Roger L. costello@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > I wish to test to see if the calendar date represented in <Date2> is > greater than (occurs later in chronological time) the calendar date > represented i . . . Read full entry »


XPath string comparison of two strings representing c

Posted 8/16/2017 4:09:07 PM

Hi Folks, I have an XML document that contains two elements with values representing calendar dates, in YYYYMMDD format, e.g., <Test> <Date1>20170816</Date1> <Date2>20170817</Date2> </Test> This is the format that iCalendar (RFC 5545) uses to represent . . . Read full entry »


Re: no XSLT Jobs USA

Posted 8/16/2017 11:40:43 AM

XSLT as a :one-of-the-skillset" is specifically true in the USA market. I was once Called in for an interview for XML architect and I was being asked Java questions, which followed questions in Python etc... They finally asked me what processors did I use for XML .. and difference between for- . . . Read full entry »


Re: no XSLT Jobs USA

Posted 8/16/2017 11:25:41 AM

XSLT as a :one-of-the-skillset" is specifically true in the USA market. I was once Called in for an interview for XML architect and I was being asked Java questions, which followed questions in Python etc... They finally asked me what processors did I use for XML .. and difference between for- . . . Read full entry »


Re: no XSLT Jobs USA

Posted 8/16/2017 8:20:18 AM

> On 16 Aug 2017, at 01:48, Mailing Lists Mail daktapaal@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Dear All, > Is USA bad for XSLT developers? > There is not one job for people from this elite club? StackOverflow currently has 9 job openings tagged XSLT, o . . . Read full entry »


Re: no XSLT Jobs USA

Posted 8/16/2017 2:07:33 AM

On Wed, 2017-08-16 at 01:02 +0000, Mailing Lists Mail daktapaal@xxxxxxxxx wrote: > I think junior level guys are still probably ok, but spending all > life doing XSLT, i think it makes you feel , why??? may be time to > jump off to a different technology? Or change country? I don't see wh . . . Read full entry »


Re: no XSLT Jobs USA

Posted 8/16/2017 2:05:33 AM

A few thoughts: The library field -- linked data, digital libraries, digital humanities, etc. MARC (still the main data format for library catalogs) has an xml format (unsurprisingly, its called MARC-XML) used for data exchange and data reuse. Many digital library platforms have a METS or MODS . . . Read full entry »


Re: no XSLT Jobs USA

Posted 8/16/2017 1:05:18 AM

To be sure, those who learn XSLT typically learn the XML stack and lots more related to it, and they know how to learn. But hey, I'm not an industry expert--I came into this as an English professor (what am I doing here? I'm one of those interlopers from the Digital Humanities). The tech world is n . . . Read full entry »


Re: no XSLT Jobs USA

Posted 8/16/2017 1:01:29 AM

I think junior level guys are still probably ok, but spending all life doing XSLT, i think it makes you feel , why??? may be time to jump off to a different technology? Or change country? On Tue, Aug 15, 2017 at 8:56 PM, Elisa Beshero-Bondar ebbondar@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxx . . . Read full entry »


Re: no XSLT Jobs USA

Posted 8/16/2017 12:56:49 AM

I really hope that isn't the case, but I'm worried. We have three coding courses in the U. of Pitt system running over the past several years, students are learning how to write XSLT in particular, as well as XQuery. Some of them are, I know, looking for jobs and would love to put their skills to w . . . Read full entry »


no XSLT Jobs USA

Posted 8/16/2017 12:48:36 AM

Dear All, Is USA bad for XSLT developers? There is not one job for people from this elite club? Vasu<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table style="border-top: 1px solid #D3D4DE;"> <tr> <td style="width: 55px; padding- . . . Read full entry »


Re: alternate attribute types in xsd

Posted 8/11/2017 10:35:21 PM

Hi Patrik, Well at least you managed to transfer some of that knowledge to me. It is all working fine now. Even better than I hoped. I also managed to somewhat improve my understanding of XSD. Thank you very much for your time and patience. Regards, ac 2017-08-11 0:43 GMT-05:00 Dr. Patrik Stel . . . Read full entry »


AW: alternate attribute types in xsd

Posted 8/11/2017 5:43:11 AM

Hi Andre, Just as the derived types added the @type attribute they can add any number of attributes - e.g. @phase: [...] <xs:complexType name="res-thing"> <xs:complexContent> <xs:extension base="res-base"> <xs:attribute name="type& . . . Read full entry »


Re: alternate attribute types in xsd

Posted 8/11/2017 2:21:54 AM

Dear Dr Stellmann, While it seems unfortunate that XSD (e.g. 1.1) does not support conditional attribute types, some subscribers to this list have suggested interesting workarounds. The RELAX NG approach suggested by Syd Bauman, seems especially elegant, expressive, and powerful. Unfortunately, th . . . Read full entry »


AW: alternate attribute types in xsd

Posted 8/7/2017 4:29:00 AM

You can get the desired behavior already with the current capabilities - just by providing alternative types for the res element: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:e . . . Read full entry »


Re: alternate attribute types in xsd

Posted 8/4/2017 8:03:22 PM

Hi Wolfgang, Thank you for your reply. It seems as if an element can have a type determined from a value of its attributes, attributes in that element should also be able to have their types determined by other attributes of the element. Here is a simple example. The key, and currently unsupport . . . Read full entry »


Re: alternate attribute types in xsd

Posted 8/4/2017 7:58:43 PM

Hi Wolfgang, Thank you for your reply. It seems as if an element can have a type determined from a value of its attributes, attributes in that element should also be able to have their types determined by other attributes of the element. Here is a simple example. The key, and currently unsupport . . . Read full entry »


Re: alternate attribute types in xsd

Posted 8/4/2017 3:43:54 AM

The definition of a simple type can make use of features such as union and facets. It would help if you would provide an example of what you are missing. -W On 4 August 2017 at 05:02, Andre Cusson akhu01@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi, > > I am re . . . Read full entry »


alternate attribute types in xsd

Posted 8/4/2017 3:02:12 AM

Hi, I am reaching out to this list, as I did not succeed in finding the answer in the archives, the web or even in the specs, hoping that someone here, possibly having contributed to the specs, may know better. Please forgive me if either I have not found what I should have or if this question wo . . . Read full entry »


XSL-List Guidelines

Posted 8/2/2017 1:04:42 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: Is the context node accessible from within a calle

Posted 8/1/2017 4:00:10 PM

>An xsl:call-template does not change the context node, of course using >an xsl:for-each for instance inside the called template then would. Thank you. Ok, that confirms what I should expect. I'm not using for-each in this area so that shouldn't be an issue. >You >haven't provided a m . . . Read full entry »


Re: Is the context node accessible from within a calle

Posted 8/1/2017 3:43:03 PM

On 01.08.2017 17:31, Kerry, Richard richard.kerry@xxxxxxxx wrote: I have a pattern-matching template which calls (ie with call-template) a named template. Although there is of course a context node that is valid throughout the pattern-matched template it isn't clear whether it remains accessibl . . . Read full entry »


Is the context node accessible from within a called t

Posted 8/1/2017 3:30:49 PM

I have a pattern-matching template which calls (ie with call-template) a named template. Although there is of course a context node that is valid throughout the pattern-matched template it isn't clear whether it remains accessible from within the called template. Can someone please tell me whethe . . . Read full entry »


Re: Context in nested loop

Posted 7/28/2017 3:49:26 PM

-----Original Message----- From: Martin Honnen martin.honnen@xxxxxx [mailto:xsl-list- service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Friday, July 28, 2017 8:49 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Context in nested loop > <xsl:for-each select="/root/nodeA/nodeB"> > . . . Read full entry »


Re: Context in nested loop

Posted 7/28/2017 2:48:23 PM

On 28.07.2017 16:30, Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx wrote: Its schema is exactly the same as the sample XML, itbs a similar document with different values. To be honest, I whipped this repro up in vim so in reality the xpath selection within the message should correspond to the same . . . Read full entry »


Re: Context in nested loop

Posted 7/28/2017 2:30:02 PM

-----Original Message----- From: Martin Honnen martin.honnen@xxxxxx [mailto:xsl-list- service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Friday, July 28, 2017 8:19 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Context in nested loop > > <xsl:variable name="document" select="do . . . Read full entry »


Re: Context in nested loop

Posted 7/28/2017 2:18:39 PM

On 28.07.2017 16:11, Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx wrote: I am unclear with the correct syntax for the corresponding context of the $name and $attr variables in the following repro. For $name, mailto:../@name is what I want, but I know that is incorrect and for $attr, "." get . . . Read full entry »


Context in nested loop

Posted 7/28/2017 2:11:16 PM

I am unclear with the correct syntax for the corresponding context of the $name and $attr variables in the following repro. For $name, mailto:../@name is what I want, but I know that is incorrect and for $attr, "." gets the value and not the name. This is similar to a question I had a few . . . Read full entry »


Re: Mode in XSLT 3.0

Posted 7/27/2017 2:32:09 AM

> I think you're starting from the position that if the XML vocabulary that you're dealing with is partitioned into modules, then it ought to be possible to mirror the independent > modules in the XML vocabulary with independent packages in the stylesheet. I would suggest that if these pa . . . Read full entry »


Re: Mode in XSLT 3.0

Posted 7/25/2017 11:44:52 PM

On Tue, Jul 25, 2017 at 11:01:46PM -0000, Michael Kay mike@xxxxxxxxxxxx scripsit: > It's not clear to me what you are trying to achieve by using packages. > The design intent of packages is that a package can be developed > without any knowledge of, or dependency on, packages other than th . . . Read full entry »


Re: Mode in XSLT 3.0

Posted 7/25/2017 11:01:39 PM

It's not clear to me what you are trying to achieve by using packages. The design intent of packages is that a package can be developed without any knowledge of, or dependency on, packages other than those it explicitly uses. If template rules for the same mode are distributed across two packages, . . . Read full entry »


Re: Mode in XSLT 3.0

Posted 7/25/2017 3:45:25 PM

So I went and pulled the package example out of the spec and got that to run from the command line. I can construct (and have attached) a trivial example where there are block, table, list, and figure elements and equally trivial packages with block, table, list, and figure modes and template matc . . . Read full entry »


Re: Mode in XSLT 3.0

Posted 7/25/2017 2:30:13 PM

Thank you for sorting out the DITA stylesheet requirement features. >>From Makita-sanbs analysis it sounds like the XSLT 3 module mechanism may not match well to the natural DITA way of thinking about implementation modularity, > especially if itbs not possible (or at least not easy) . . . Read full entry »


Re: Mode in XSLT 3.0

Posted 7/24/2017 3:09:40 PM

On Mon, Jul 24, 2017 at 02:14:28PM -0000, Eliot Kimber ekimber@xxxxxxxxxxxx scripsit: > Ibm not sure I understand the DITA-to-module issue here: Ibm not yet > up to speed on XSLT 3 modulesb& [snip] > In DITA, sets of element types (grammars) are formally defined in > bmodulesb, . . . Read full entry »


Re: Mode in XSLT 3.0

Posted 7/24/2017 2:14:21 PM

Ibm not sure I understand the DITA-to-module issue here: Ibm not yet up to speed on XSLT 3 modulesb& But the implicit requirement with DITA is that you can have processing that will handle elements based on their base types (as defined in their @class attributes) and then, for more-specializ . . . Read full entry »


Re: Mode in XSLT 3.0

Posted 7/23/2017 11:56:25 PM

On Sun, Jul 23, 2017 at 11:08:53PM -0000, Toshihiko Makita tmakita@xxxxxxxxxxxxx scripsit: > > If that's what you're trying to achieve, then it isn't going to work: > >you're trying to create packages that aren't sufficiently independent of > > each other. > > The insuffici . . . Read full entry »


Re: Mode in XSLT 3.0

Posted 7/23/2017 11:08:44 PM

> If that's what you're trying to achieve, then it isn't going to work: you're trying to create packages that aren't sufficiently independent of each other. The insufficiency comes form XML document (DITA) content model itself. For instance: - concept/body can contain dl, ol, ul, p, table, . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 1:58:45 PM

Thanks for the explanation. Agree re 'moving on', but the work in docbook is 'significant'. regards On 23 July 2017 at 14:50, Michael Kay mike@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > >> On 23 Jul 2017, at 14:43, Dave Pawson dave.pawson@xxxxxxxxx <xsl-list . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 1:50:17 PM

> On 23 Jul 2017, at 14:43, Dave Pawson dave.pawson@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Mike - that really messes with docbook which are all 1.0 stylesheets. > Is that the rec or your decision? Or a compat issue? > It's our decision. It's time peopl . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 1:45:53 PM

We dropped the warning in 9.8.0.2, see https://saxonica.plan.io/issues/3278 But yes, Saxon-HE no longer supports 1.0 compatibility mode, and therefore gives you an error if your stylesheet says version="1.0". We're trying to encourage users to eliminate any dependencies on 1.0-mode - it' . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 1:43:31 PM

Mike - that really messes with docbook which are all 1.0 stylesheets. Is that the rec or your decision? Or a compat issue? regards On 23 July 2017 at 14:36, Martin Honnen martin.honnen@xxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > On 23.07.2017 15:26, Dave Pawson dave.pawson . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 1:42:26 PM

> First plus I've come across for 3.0 Mike... > I've not seen a reason to move yet. > Question. Same way as 2.0 using 1.0 stylesheet, does it just warn me and work? > It doesn't even warn you any more (there's no need for the warning in 3.0 because the level of compatibility is very h . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 1:36:57 PM

On 23.07.2017 15:26, Dave Pawson dave.pawson@xxxxxxxxx wrote: That's running 1.0 stylesheets with 2.0 processor? Saxon 9.8 HE is an XSLT 3.0 processor and does what I said, it refuses to run version="1.0" code but only emits a warning when running version="2.0" code. >> . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 1:26:11 PM

That's running 1.0 stylesheets with 2.0 processor? What of running 2.0 stylesheet with 3.0 processor Martin? regards On 23 July 2017 at 14:20, Martin Honnen martin.honnen@xxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > On 23.07.2017 14:58, Dave Pawson dave.pawson@xxxxxxxxx wrot . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 1:20:45 PM

On 23.07.2017 14:58, Dave Pawson dave.pawson@xxxxxxxxx wrote: First plus I've come across for 3.0 Mike... I've not seen a reason to move yet. Question. Same way as 2.0 using 1.0 stylesheet, does it just warn me and work? Saxon 9.8 HE does tell you with version="1.0" stylesheets that it . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 12:58:13 PM

First plus I've come across for 3.0 Mike... I've not seen a reason to move yet. Question. Same way as 2.0 using 1.0 stylesheet, does it just warn me and work? Regards On 23 July 2017 at 13:50, Michael Kay mike@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > In XSLT 3.0 . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 12:50:13 PM

In XSLT 3.0 you can do this with static variables/parameters: <xsl:param name="disk" static="yes" required="yes"> <xsl:import _href="{$disk}/path"/> Note the underscore. This is referred to as a "shadow attribute" - it is evaluated at . . . Read full entry »


Re: xsl:import

Posted 7/23/2017 12:48:21 PM

On 23.07.2017 14:03, Dave Pawson dave.pawson@xxxxxxxxx wrote: AFAICT I can't use a variable inside an import? <xsl:import href="{$disk}/path"/> I'm running with all xsl files on a HDD (currently XXX) and know I'll change it to YYY in a year or so. Is there any way to use the above . . . Read full entry »


xsl:import

Posted 7/23/2017 12:03:17 PM

AFAICT I can't use a variable inside an import? <xsl:import href="{$disk}/path"/> I'm running with all xsl files on a HDD (currently XXX) and know I'll change it to YYY in a year or so. Is there any way to use the above syntax? I.e. prefix the 'disk' to a given path? Relative pa . . . Read full entry »


Re: Mode in XSLT 3.0

Posted 7/22/2017 4:11:07 PM

The design doesn't allow you to construct a mode by combining template rules from two different packages, except for the specific case where a using package adds overriding template rules to a mode that is defined in a used package. If that's what you're trying to achieve, then it isn't going to wo . . . Read full entry »


Mode in XSLT 3.0

Posted 7/22/2017 2:58:00 PM

Hi list, I'm testing to convert XSLT 2.0 stylesheet modules that have xsl:template with @match attributes to XSLT 3.0 packages. They belong DITA-OT plug-in and generates XSL-FO from DITA maps and topics. Most of templates are defined with no @mode attributes which means that they are defined as . . . Read full entry »


Re: XSLT program that generates XSD, the XSD has a pa

Posted 7/19/2017 1:58:55 PM

>> Note that replacing the curly braces with their character references also failed: >> >> <xs:pattern value="[a-z\&#x7B;\ &#x7D;]*" /> > > Because XSD doesn't care what syntax is used in the stylesheet for the characters to be used in the logic. > . . . Read full entry »


Re: Using variables in xpath expression

Posted 7/19/2017 1:49:19 PM

On 19.07.2017 15:17, Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx wrote: I have several templates with similar code to the following: <xsl:template match="wix:Component[wix:File[substring(@Source, string-length(@Source) - 7) = 'MyString']]"> I want to substitute 'MyString' with a . . . Read full entry »


Using variables in xpath expression

Posted 7/19/2017 1:17:20 PM

I have several templates with similar code to the following: <xsl:template match="wix:Component[wix:File[substring(@Source, string-length(@Source) - 7) = 'MyString']]"> I want to substitute 'MyString' with a variable and the 7 with a "string-length($var) -1" however th . . . Read full entry »


Re: XSLT program that generates XSD, the XSD has a pa

Posted 7/19/2017 1:11:17 PM

At 2017-07-19 12:45 +0000, Costello, Roger L. costello@xxxxxxxxx wrote: I am writing an XSLT program that outputs an XML Schema. The generated XML Schema is to contain a simpleType, with a pattern facet. Its regex is to express: zero or more lowercase letters of the English alphabet, the left cu . . . Read full entry »


Re: XSLT program that generates XSD, the XSD has a pa

Posted 7/19/2017 1:07:13 PM

you can avoid putting the string in an attribute value template, as Syd Bauman just said, or within an AVT use {{ to denote a { David On 19 July 2017 at 14:01, Syd Bauman s.bauman@xxxxxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > How about using XSLT constructors, so t . . . Read full entry »


Re: XSLT program that generates XSD, the XSD has a pa

Posted 7/19/2017 1:01:43 PM

How about using XSLT constructors, so the part of interest is just a string? <xsl:element name="pattern" namespace="http://www.w3.org/2001/XMLSchema"> <xsl:attribute name="value"> <xsl:text>[a-z\{\}]*</xsl:text> </xsl . . . Read full entry »


XSLT program that generates XSD, the XSD has a pattern

Posted 7/19/2017 12:44:15 PM

Hi Folks, I am writing an XSLT program that outputs an XML Schema. The generated XML Schema is to contain a simpleType, with a pattern facet. Its regex is to express: zero or more lowercase letters of the English alphabet, the left curly brace, and the right curly brace: <xs:simpleType name=& . . . Read full entry »


Re: Fetching the value of a dynamically assigned attr

Posted 7/19/2017 11:01:35 AM

-----Original Message----- From: Michael Kay mike@xxxxxxxxxxxx [mailto:xsl-list- service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Wednesday, July 19, 2017 3:29 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Fetching the value of a dynamically assigned attribute > Better is <xsl:value-of select=&q . . . Read full entry »


Re: Fetching the value of a dynamically assigned attr

Posted 7/19/2017 9:29:11 AM

> On 19 Jul 2017, at 00:52, Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > While mocking up some examples related to a previous question, > I have an example where I add a namespace to my stylesheet and > add some data to it: > . . . Read full entry »


AW: Fetching the value of a dynamically assigned attr

Posted 7/19/2017 4:13:03 AM

You can use the current() function to get the XSLT context node from within an XPath: <xsl:value-of select="$documentAppConfig/configuration/myNode/@*[local-name()=current()/tex t()]" /> Patrik > ------------------------------------------------------------------ Systemarchitekt . . . Read full entry »


Fetching the value of a dynamically assigned attribute

Posted 7/18/2017 11:52:10 PM

While mocking up some examples related to a previous question, I have an example where I add a namespace to my stylesheet and add some data to it: <myns:data> <foo> <bar>one</bar> <bar>two</bar> <bar>three</bar> </foo&g . . . Read full entry »


[ANN] Balisage Registration closes on Friday

Posted 7/18/2017 3:59:20 PM

Balisage 2017, and the pre-conference symposium on up-translation are are nearly here. Registration closes THIS FRIDAY, July 21st! If you want to participate in the years best Markup Geekfest, come to Balisage! Symposium Program at: https://www.balisage.net/UpTransform/symposiumProgram.html Con . . . Read full entry »


Re: JWT by XSL

Posted 7/18/2017 2:40:16 PM

yes On 18 July 2017 at 06:36, Rahul Singh rahulsinghindia15@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi, > > > Is JWT signature is possible to henerate JWT assertion or JWT signature > based on RSA-SHA256 as per jwt.io. > > > For that JWT assertion . . . Read full entry »


Re: Processing approach

Posted 7/18/2017 2:07:01 PM

> I have a template that matches nodeC based on its ID, copies it contents and appends child nodes. > Its at this time that much info gets derived which is useful elsewhere. In XSLT 1.0 there are a couple of approaches to this: (a) put both the primary and secondary results into a variable . . . Read full entry »


JWT by XSL

Posted 7/18/2017 1:35:47 PM

Hi, Is JWT signature is possible to henerate JWT assertion or JWT signature based on RSA-SHA256 as per jwt.io. For that JWT assertion we need 3 parts: <header>.<claims>.<signature>. . . . Read full entry »


Re: Processing approach

Posted 7/18/2017 1:15:59 PM

From: Michael Kay mike@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Sent: Monday, July 17, 2017 9:48 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Processing approach > Please show us some input and desired output that capture the essence of the > problem, and give en . . . Read full entry »


Re: Processing approach

Posted 7/18/2017 8:55:44 AM

There's a lot of temporal language in this description ("while", "then", "same time", "ends up", "as I process"). That's usually a sign that you are thinking procedurally. Try to describe the output as a function of the input, and forget about what . . . Read full entry »


Re: Processing approach

Posted 7/18/2017 3:47:55 AM

Please show us some input and desired output that capture the essence of the problem, and give enough information so we can see how one derives from the other. Then show us your best attempt at solving the problem. Your current logic sounds really contorted and you may find that people suggest tack . . . Read full entry »


Re: Processing approach

Posted 7/18/2017 1:12:16 AM

hard to say without the details.. but kind of sounds like something that would be best fit (in 1.0) to multiple stylesheets... the first being an identity-based transform distributing your aggregate data to the various appropriate nodes in some sort of metadata format, and the second performing you . . . Read full entry »


Re: Processing approach

Posted 7/18/2017 12:50:50 AM

-----Original Message----- From: Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx [mailto:xsl-list- service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Monday, July 17, 2017 6:15 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Processing approach > Ibm not sure whether I have completely understood the . . . Read full entry »


Re: Processing approach

Posted 7/18/2017 12:15:21 AM

Ibm not sure whether I have completely understood the scenario, but did you consider using tunnel parameters? https://www.w3.org/TR/xslt-30/#tunnel-params https://www.w3.org/TR/xslt20/#tunnel-params Calculate the variable once, in the context of a node that is ancestor-or-self to all affected n . . . Read full entry »


Processing approach

Posted 7/17/2017 11:39:32 PM

I am processing an xml doc where a template adds some elements at one point in the tree. While doing this, it generates a variable that I also use at another location in the tree. Rather than regenerate the variable and introduce a chance for breakage in the future, is there a more efficient approa . . . Read full entry »


Re: HTML tables to CALS tables conversion help

Posted 7/17/2017 11:58:05 AM

This is a fragment of an XPath expression > preceding::xhtml:td[count(preceding-sibling::xhtml:td)=count(current()/preced ing-sibling::xhtml:td)+1 and current()/@rowspan] which, starting from a context node C, selects all xhtml::td elements T satisfying the conditions (a) T is before C in doc . . . Read full entry »


Re: HTML tables to CALS tables conversion help

Posted 7/17/2017 7:04:08 AM

Hi Michele Need help to understand this '<!ENTITY preceding_rowspan_td "preceding::xhtml:td[count(preceding-sibling::xhtml:td)=count(current()/prece ding-sibling::xhtml:td)+1 and current()/@rowspan]">' what values are in this. Thanks Love Kumar Sharma _____________________ . . . Read full entry »


Introducing XCST

Posted 7/15/2017 2:47:08 AM

Fellow XSLT lovers, I'm happy to introduce to you XCST, a language heavily inspired in XSLT, but for non-xml data. XCST uses C# as expression language, and compiles to plain C#. It includes XSLT 3.0 features like packages and text value templates, as well as other cool features XSLT does not have. . . . Read full entry »


Re: HTML tables to CALS tables conversion help

Posted 7/14/2017 8:59:12 PM

...This looks like a spear phishing attempt... From: Michele R Combs mrrothen@xxxxxxx [mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Friday, July 14, 2017 11:59 AM To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx' <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Subject: Re: HTML tables to CALS tables conve . . . Read full entry »


Re: HTML tables to CALS tables conversion help

Posted 7/14/2017 3:59:18 PM

What is it you don't understand? Michele From: Love Kumar Sharma luvks@xxxxxxx [mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Friday, July 14, 2017 5:37 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: HTML tables to CALS tables conversion help Hi Team Hope Everyone are doing well! . . . Read full entry »


Re: Question on streaming and grouping with nested key

Posted 7/14/2017 2:13:23 PM

On 14.07.2017 15:02, Felix Sasaki felix@xxxxxxxxxxxxxx wrote: 2017-07-14 14:41 GMT+02:00 Martin Honnen martin.honnen@xxxxxx <mailto:martin.honnen@xxxxxx> <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx <mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>>: On 14.07.2017 14:05, Felix . . . Read full entry »


Re: Question on streaming and grouping with nested key

Posted 7/14/2017 1:02:18 PM

2017-07-14 14:41 GMT+02:00 Martin Honnen martin.honnen@xxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>: > On 14.07.2017 14:05, Felix Sasaki felix@xxxxxxxxxxxxxx wrote: > > I tried the example from Martin with >> >> <xsl:template match="TRANSACTION-LIST"> . . . Read full entry »


Re: Question on streaming and grouping with nested key

Posted 7/14/2017 12:44:17 PM

> As you mention Saxon EE, let's hope Michael Kay comes across this thread and can certainly tell you more on how to tackle that problem with his product. I'm aware of the thread but may not have time to study it today. Michael Kay . . . Read full entry »


Re: Question on streaming and grouping with nested key

Posted 7/14/2017 12:41:55 PM

On 14.07.2017 14:05, Felix Sasaki felix@xxxxxxxxxxxxxx wrote: I tried the example from Martin with <xsl:template match="TRANSACTION-LIST"> <xsl:copy> <xsl:for-each-group select="copy-of(TRANSACTION)" group-by="ITEM2/SUBITEM2/GROUPING-KEY&quo . . . Read full entry »


Re: Question on streaming and grouping with nested key

Posted 7/14/2017 12:04:54 PM

Thank you for your feedback, Martin and David. I tried the example from Martin with <xsl:template match="TRANSACTION-LIST"> <xsl:copy> <xsl:for-each-group select="copy-of(TRANSACTION)" group-by="ITEM2/SUBITEM2/GROUPING-KEY"> . . . Read full entry »


HTML tables to CALS tables conversion help

Posted 7/14/2017 9:36:33 AM

Hi Team Hope Everyone are doing well! I need your help to understand one of famous XSLT code. Note: I have visited here for code. https://trac.cnx.org/wiki/HtmlTables2CalsTables Thanks Love Kumar Sharma +91 9716036188 . . . Read full entry »


Re: Question on streaming and grouping with nested key

Posted 7/14/2017 8:17:46 AM

Am 14.07.2017 um 09:09 schrieb Felix Sasaki felix@xxxxxxxxxxxxxx: > > I want to analyse a list of transactions in XSLT 3.0 streaming mode. > Transactions should be grouped by a key which is nested inside each > transaction (see SUBITEM2.2/GROUPING-KEY below). For the grouped > tra . . . Read full entry »


Re: Question on streaming and grouping with nested key

Posted 7/14/2017 8:06:07 AM

I'm sure someone with more savvy can tell you how to do this with accumulators, but it seems that there is a straightforward way to do this with streaming iterate. Use burst-mode streaming to iterate through each <TRANSACTION> element. This <xsl:iterate> instruction should have two pa . . . Read full entry »


Re: Question on streaming and grouping with nested key

Posted 7/14/2017 8:05:46 AM

Am 14.07.2017 um 09:09 schrieb Felix Sasaki felix@xxxxxxxxxxxxxx: > > I want to analyse a list of transactions in XSLT 3.0 streaming mode. > Transactions should be grouped by a key which is nested inside each > transaction (see SUBITEM2.2/GROUPING-KEY below). For the grouped > tra . . . Read full entry »


Question on streaming and grouping with nested keys

Posted 7/14/2017 7:09:06 AM

I want to analyse a list of transactions in XSLT 3.0 streaming mode. Transactions should be grouped by a key which is nested inside each transaction (see SUBITEM2.2/GROUPING-KEY below). For the grouped transactions, there are items to count or items with numeric values to some up, see ITEM1 and ITE . . . Read full entry »


Re: is there any XSL Splitter to split XML in 200 chun

Posted 7/12/2017 7:19:41 PM

On 07/12/2017 10:52 AM, Martin Honnen martin.honnen@xxxxxx wrote: > Do you want to create several result files, each containing a certain > number of records? Or simply one file where you wrap a certain number of > records? I think he means the latter, grouping 200 <name> elements a . . . Read full entry »


Re: is there any XSL Splitter to split XML in 200 chun

Posted 7/12/2017 9:51:49 AM

Do you want to create several result files, each containing a certain number of records? Or simply one file where you wrap a certain number of records? In any way, assuming XSLT 2.0, you can use positional grouping e.g. <xsl:for-each-group select="/optical/name" group-by="(p . . . Read full entry »


is there any XSL Splitter to split XML in 200 chunk of

Posted 7/12/2017 9:11:03 AM

Hi, Is there any posiblites in XSL to split XML in 200 200 chunk of record in same xml by xsl, *below is inputm expected putput, xsl:* <?xml version="1.0" encoding="UTF-8"?> <optical> <name> <Doc>log00.txt</Doc> </name> <name&g . . . Read full entry »


Re: XML schema: require a descendant?

Posted 7/8/2017 5:40:14 PM

Hey Chuck, Another route to XPath-based validation -- wherein you could implement a rule for your entry that at least one 'sense' child has some-child-or-other -- would be embedding Schematron in your schema -- or maintaining an extra-schema constraint layer (in the form of a Schematron) -- and th . . . Read full entry »


Re: Document processing order

Posted 7/7/2017 6:44:07 PM

I like this :) Michele -----Original Message----- From: Michael Kay mike@xxxxxxxxxxxx [mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Friday, July 07, 2017 12:42 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Document processing order ... You don't ever delete anything from the sour . . . Read full entry »


Re: Document processing order

Posted 7/7/2017 6:34:31 PM

-----Original Message----- From: Michael Kay mike@xxxxxxxxxxxx [mailto:xsl-list- service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Friday, July 7, 2017 10:41 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Document processing order > You're thinking of old-fashioned procedural programming languages th . . . Read full entry »


Re: Document processing order

Posted 7/7/2017 4:41:41 PM

-----Original Message----- From: Peter Flynn peter@xxxxxxxxxxx [mailto:xsl-list- service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Friday, July 7, 2017 10:29 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Document processing order > Am I right in deducing that your concern is that once the first set . . . Read full entry »


Re: Document processing order

Posted 7/7/2017 4:41:14 PM

You're thinking of old-fashioned procedural programming languages that modify data as they go along and where you have to worry about order of execution. In XSLT, data is immutable, and operations happen conceptually in parallel. You don't ever delete anything from the source document, you only ref . . . Read full entry »


Re: Document processing order

Posted 7/7/2017 4:35:20 PM

From: Michael Kay mike@xxxxxxxxxxxx [mailto:xsl-list- service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Friday, July 7, 2017 9:52 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Document processing order > I don't really see the problem, but that probably means I haven't understood > your explanati . . . Read full entry »


Re: Document processing order

Posted 7/7/2017 4:29:20 PM

On 07/07/17 16:03, Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx wrote: > I have a situation where I need to remove child elements from two distinct paths > relative to the root, however the second path from document order is inferred by > an xpath query that depends on the existence of the e . . . Read full entry »


Re: Document processing order

Posted 7/7/2017 3:51:46 PM

I don't really see the problem, but that probably means I haven't understood your explanation. Perhaps you could illustrate it with an example. Michael Kay Saxonica > On 7 Jul 2017, at 16:03, Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > . . . Read full entry »


Document processing order

Posted 7/7/2017 3:02:51 PM

I have a situation where I need to remove child elements from two distinct paths relative to the root, however the second path from document order is inferred by an xpath query that depends on the existence of the earlier child elements. How does one accomplish such a task in xsl? Thanks, jlc . . . Read full entry »


Re: Xpath conditional

Posted 7/6/2017 5:40:38 PM

-----Original Message----- From: Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx [mailto:xsl-list- service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Thursday, July 6, 2017 11:26 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Xpath conditional > How can I generate a match expression for a template that selects . . . Read full entry »


Xpath conditional

Posted 7/6/2017 5:26:10 PM

Hi have some XML resembling the following: <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Fragment> <DirectoryRef Id="WEBSITEDIR"> <Component Id="cmpCA929 . . . Read full entry »


Re: XSLT site (code quality tool)

Posted 7/6/2017 4:58:40 AM

One point, which I forgot to mention. This tool has a provision to set desired priority to the rules. On the site, I've mentioned "I suggest the rule priorities from 1 to 5, where 1 is a most severe violation and 5 is the least severe". This could be useful to customize the rules provid . . . Read full entry »


Re: XSLT site (code quality tool)

Posted 7/4/2017 3:56:39 AM

Hi Mike, Thanks for a nice analysis, of this tool. If time permits me, I'll modify this tool as per your suggestions. On 3 July 2017 at 20:23, Michael Kay mike@xxxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Some comments on Mukul's rules (looking both at the prose de . . . Read full entry »


Re: XSLT site (code quality tool)

Posted 7/3/2017 2:53:09 PM

Some comments on Mukul's rules (looking both at the prose description and the XPath implementation): The following rules are supported out of the box, with this tool: 1. DontUseDoubleSlashOperatorNearRoot: Avoid using the operator // near the root of a large tree. The implementation checks for & . . . Read full entry »


Re: XSLT site

Posted 7/3/2017 5:19:26 AM

Thank you for your response. On 2 July 2017 at 17:38, Michael MC<ller-Hillebrand mmh@xxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > > I always kept a link to your page regarding static XSLT quality tool, and > moved some of the rules into my own Schematron rul . . . Read full entry »


Re: XSLT site

Posted 7/2/2017 1:03:07 PM

. . . Read full entry »


Re: XSLT site

Posted 7/2/2017 12:08:20 PM

Hello Mukul, I always kept a link to your page regarding static XSLT quality tool, and moved some of the rules into my own Schematron ruleset. As OxygenXML now also has some quality rules implemented I think it is worth exploring this path. E.g. with XSLT packages it becomes even more important to . . . Read full entry »


Re: XML schema: require a descendant?

Posted 7/2/2017 9:04:54 AM

XML Schema 1.1 has XPath evaluation and validation. Your constraint can be easily expressed as the existence of at least one <sense> with at least one child element for an <entry>. -W On 2 July 2017 at 10:01, Charles Muller acmuller@xxxxxxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxx . . . Read full entry »


XML schema: require a descendant?

Posted 7/2/2017 8:01:05 AM

I guess this might be a bit off-topic for an XSLT list, but in any case it's related to XPath. In my data (simplified here): <entry> <sense> <sense> <sense> </entry> I want at least *one* of the <sense> nodes to contain <term>, <persName>, o . . . Read full entry »


XSLT site

Posted 7/2/2017 7:41:44 AM

Hello, There was a time, when I was heavily involved with XSLT. I had created this web site related to XSLT, http://gandhimukul.tripod.com/xslt/index.html This hasn't been updated in a while. Looking at this site, can anyone suggest if this site is still valuable? I can start adding informati . . . Read full entry »


XSL-List Guidelines

Posted 7/1/2017 6:46:35 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 »


Posting to XSL-List - Good Subject Lines

Posted 6/29/2017 3:47:15 AM

When replying the list digest please replace the automagically create subject line, which is the digest, with the name of the thread to which you are responding. Good subject lines make the discussion available in the archives. It is interesting that in 2017 we see significantly more traffic to th . . . Read full entry »


Re: Re: [XSL-List: The Open Forum on XSL] Digest for

Posted 6/29/2017 3:26:08 AM

Think this is a key problem so try something like this. <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheetxmlns:xsl="http://www.w3.org/1999/XSL/Transform"xmlns:xs="http ://www.w3.org/2001/XMLSchema"exclude-result-prefixes="xs"version=&q . . . Read full entry »


Re: [XSL-List: The Open Forum on XSL] Digest for 2017

Posted 6/28/2017 9:07:02 AM

Thanks On Wed, Jun 21, 2017 at 2:50 PM, XSL-List: The Open Forum on XSL < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > This message contains the recent posts to the XSL-List: The Open Forum on > XSL > mailing list managed by Mulberry Technologies, Inc. ( > http://lists.mulb . . . Read full entry »


Re: Transform help

Posted 6/27/2017 9:05:07 PM

On 06/27/2017 05:52 PM, Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx wrote: > I have an XML file with the following format: [snip] > I need to apply a transform to re-order the DirectoryRef child elements such > that Component/File[@Source="$(var.SomeVar)\Foo.exe"] appears first. . . . Read full entry »


Re: Transform help

Posted 6/27/2017 6:25:29 PM

This should do it. You need the 2 copyall templates from Ken Holman then your template that does special processing of the parent of the elements you want to change their order within the parent. I was a bit lazy and added this to the root of the style sheet xpath-default-namespace="http://sc . . . Read full entry »


Re: Transform help

Posted 6/27/2017 5:46:41 PM

-----Original Message----- From: Martin Honnen martin.honnen@xxxxxx [mailto:xsl-list- service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Tuesday, June 27, 2017 10:56 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Transform help > Change > > > <xsl:template match="//wix:DirectoryRef . . . Read full entry »


Re: Transform help

Posted 6/27/2017 4:55:47 PM

On 27.06.2017 18:51, Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx wrote: Change <xsl:template match="//wix:DirectoryRef[@Id = 'WIXUI_INSTALLDIR']"> <xsl:copy> <xsl:apply-templates select="@*" /> <xsl:apply-templates select=" . . . Read full entry »


Transform help

Posted 6/27/2017 4:51:35 PM

I have an XML file with the following format: <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Fragment> <DirectoryRef Id="WIXUI_INSTALLDIR"> <Component Id=" . . . Read full entry »


Re: XSL Condition is not working

Posted 6/20/2017 6:03:41 PM

I donbt understand it fully. The output comprises all of merge1.xmlbs Alter__c items because all meet your conditions. Why do you expect that the output objects element contains only Alert__c[Document_Name__c = 'abcTest.txt']]? For example, take <Alert__c> <Alert_Type__c>Docume . . . Read full entry »


XSLT at the XML Summer School 2017

Posted 6/20/2017 5:23:03 PM

Hello, We have announced the program for the XML Summer School, which takes place September 17-22 in Oxford, UK. The XSLT and XQuery course may be of particular interest. It is an intermediate to advanced course with the goal of helping developers who are currently using XSLT to be more effectiv . . . Read full entry »


XSL Condition is not working

Posted 6/20/2017 1:29:51 PM

My xsl code is not working as per given expected output. I need data from merge1.xml if Alert_Type__c='Document Downloaded' and Document_Name__c='abcTest.txt' is match with merge2.xml with Document_Name__c='abcTest.txt' and Alert_Type__c!='Document Downloaded' Input Merge1.xml: <?xml vers . . . Read full entry »


Compare 2 xml in XSL based on some condition is not w

Posted 6/16/2017 11:27:57 AM

Hi, I have written code to check if <CreatedDate> from merge1.xml is grater-then of <Last_Alert_Import__c> from merge2.xml then i need all the data in the case of grater-then from merge1.xml and if <CreatedDate> from merge1.xml is less-then of <Last_Alert_Import__c> from me . . . Read full entry »


How to compare 2 xml based on some condition in XSL

Posted 6/16/2017 8:06:40 AM

Hi, I have written code to check if CreatedDate from merge1 is grater then of Last_Alert_Import__c from merge2 then i need all data in grater case from merge1 and if CreatedDate from merge1 is less then of Last_Alert_Import__c from merge2 then i need less-then case data only from merge1. XSL: . . . Read full entry »


AW: Function to resolve URNs?

Posted 6/13/2017 11:48:10 AM

Thanks, for the explanation, Michael. So I will stick to my base-uri(doc(b&)) for now. And if it should turn out to be necessary I will call a static Java method to use the URI resolver from the Saxon configuration. Regards, Patrik ----------------------------------------------------------- . . . Read full entry »


Re: Function to resolve URNs?

Posted 6/13/2017 9:10:23 AM

Unfortunately terminology in this area is very confused and it's best to try and distinguish: - expanding a relative reference - this means taking what is popularly called a relative URI and turning it into an absolute URI, for example index.html becomes http://www.ibm.com/index.html. This is what . . . Read full entry »


Function to resolve URNs?

Posted 6/13/2017 8:02:00 AM

Hi, I have files that reference other files and I need to get the URLs of the files being referenced (e.g. an xsd file including or importing other xsd files). I tried to use resolve-uri(@schemaLocation) which works fine for relative URLs but this does not resolve URNs (which are used in most of . . . Read full entry »


[ANN] Balisage 2017 Program updated with Late-breaking

Posted 6/12/2017 6:17:33 PM

The Balisage 2017 program has been enhanced with 7 late-breaking presentations. Take a look at the program: https://www.balisage.net/2017/Program.html This year we will be talking about: XML documents, vocabularies, and applications. There will be case studies about historical documents, internat . . . Read full entry »


catalog with saxon 9.7

Posted 6/12/2017 6:29:04 AM

Hi, I use the catalog with the Apache XMLResolver. I use saxon 9.7 EE I don't understand what happens with the DTD catalog resolution. I try to do an example and verify if the files are correct with the resolver included parser. The solution is perhapsan evidence, and I used the catalog Apache r . . . Read full entry »


Streamability of rounding effects

Posted 6/11/2017 9:40:49 PM

Idle relaxation after XML London. Here is some random text generated using the vocabulary of the XSLT 3.0 spec: <quote> This means cases where a parameter to match certain function are copied node matches replace all the pattern is no such a valid relative to declarations in which is used t . . . Read full entry »


Re: Merging is not working by xsl for 2 xml

Posted 6/11/2017 12:53:03 PM

On 11.06.2017 13:46, Rahul Singh rahulsinghindia15@xxxxxxxxx wrote: I tried to merge 2 xml based if /objects/phone/ContactId from merge1.xml equal to /objects/Contact/Id from merge2.xml Is there any match at all in the two samples you posted? For your first file I get distinct-values(//phone/Con . . . Read full entry »


Re: Merging is not working by xsl for 2 xml

Posted 6/11/2017 11:52:23 AM

On 11.06.2017 13:46, Rahul Singh rahulsinghindia15@xxxxxxxxx wrote: I tried to merge 2 xml based if /objects/phone/ContactId from merge1.xml equal to /objects/Contact/Id from merge2.xml with below xsl, both xml are attached: <?xml version="1.0" encoding="UTF-8"?> <x . . . Read full entry »


Merging is not working by xsl for 2 xml

Posted 6/11/2017 11:46:35 AM

Hi, I tried to merge 2 xml based if /objects/phone/ContactId from merge1.xml equal to /objects/Contact/Id from merge2.xml with below xsl, both xml are attached: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform . . . Read full entry »


Re: [ANN] XSLT 3.0 and Saxon 9.8

Posted 6/9/2017 3:25:35 AM

Congratulations! I hope to use the XSLT 3.0 language on a regular basis. On 8 June 2017 at 22:56, Michael Kay mike@xxxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > XSLT 3.0 becomes a Recommendation today! > > We kept you waiting for ten years, but it has finally hap . . . Read full entry »


Re: [saxon] XSLT 3.0 and Saxon 9.8

Posted 6/8/2017 8:37:51 PM

Congrats for getting things done! Tremendous achievement and will need at least 3 - 5 years to be understood and to start to be used on a regular basis by a substantial developers base. Hope soon to see tuple types, union types, and type aliases in XSLT 4 . I was lucky and honored to have worked . . . Read full entry »


Re: [ANN] XSLT 3.0 and Saxon 9.8

Posted 6/8/2017 7:40:51 PM

Congratulations! David . . . Read full entry »


Re: [ANN] XSLT 3.0 and Saxon 9.8

Posted 6/8/2017 6:39:19 PM

Wau, well done, congratulations ! Always in awe Leo > On 8 Jun 2017, at 19:27, Michael Kay mike@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > XSLT 3.0 becomes a Recommendation today! . . . Read full entry »


[ANN] XSLT 3.0 and Saxon 9.8

Posted 6/8/2017 5:26:44 PM

XSLT 3.0 becomes a Recommendation today! We kept you waiting for ten years, but it has finally happened. A reminder of some of the key features: * Streaming * Separately compiled packages * Higher-order functions * JSON, maps, and arrays and of course lots of goodies like trigonometric funct . . . Read full entry »


XSL-List Guidelines

Posted 6/1/2017 6:13:10 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] Balisage Late-breaking Proposals Due FRIDAY

Posted 5/30/2017 7:48:49 PM

Hi Adam b Finished Balisage papers are due July 7, 2017. b Tommie > On May 30, 2017, at 3:40 PM, Adam Retter adam.retter@xxxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Out of interest, if one was to submit an unpublished yet lengthly > article which stil . . . Read full entry »


Re: [ANN] Balisage Late-breaking Proposals Due FRIDAY

Posted 5/30/2017 7:40:15 PM

Out of interest, if one was to submit an unpublished yet lengthly article which still needed reformatting into a more academic paper like style and a couple parts strengthened, what would be the deadline for getting you the finished paper? On 30 May 2017 at 15:32, Tommie Usdin btusdin@xxxxxxxxxxxx . . . Read full entry »


[ANN] Balisage Late-breaking Proposals Due FRIDAY

Posted 5/30/2017 7:32:29 PM

The Balisage program looks pretty good: https://www.balisage.net/2017/Program.html but there are spaces saved for late-breaking talks. See details at: https://www.balisage.net/latebreaking-call.html Balisage: where serious markup practitioners and theoreticians meet every August. ============== . . . Read full entry »


Re: Muenchain method

Posted 5/27/2017 8:55:17 AM

Thank you so much Martin. You save my week end :-) Regards _____ De : Martin Honnen martin.honnen@xxxxxx [mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx] Envoyi : samedi 27 mai 2017 10:34 @ : xsl-list@xxxxxxxxxxxxxxxxxxxxxx Objet : Re: Muenchain method You might want to move to XSLT 2.0 wit . . . Read full entry »


Re: Muenchain method

Posted 5/27/2017 8:33:32 AM

You might want to move to XSLT 2.0 with nested for-each-group where these kind of problems don't occur, in your case you have defined the key for any elements but only want to apply it with Muenchian grouping for a subtree, therefore you have to use a key concatenating the id of the parent node . . . Read full entry »


Muenchain method

Posted 5/26/2017 8:57:51 PM

Hi all, Could someone help me, it drives me completly mad. For a bibliographic list, I'm trying to display author/title index entries. I'm using the Muenchain method to group books by author/titles. There's an index for author and titles. Titles are generated from the indexsort XML node. Coul . . . Read full entry »


[ANN] Call for Late-Breaking News - Balisage 2017

Posted 5/22/2017 8:17:46 PM

It is not too late for you to speak at Balisage! The peer-reviewed part of the Balisage 2017 program has been scheduled (https://www.balisage.net/2017/Program.html). The Markup world moves quickly, so every year some speaking slots are set aside for late-breaking news, updates, and fast-breaking s . . . Read full entry »


[ANN] Balisage 2017 Program Announced

Posted 5/17/2017 6:27:15 PM

Balisage: The Markup Conference 2017 Program Now Available http://www.balisage.net/2017/Program.html Balisage: where serious markup practitioners and theoreticians meet every August. The 2017 program includes papers discussing XML vocabularies, cutting-edge digital humanities, lossless JSON/XML r . . . Read full entry »


Re: Remove internal parsing and exclude one child

Posted 5/16/2017 6:18:53 PM

Thank you Graydon and Martin! These both work perfectly, and it's kind of neat to see the rather different approaches to the same issue. I groped along each path before asking for help. Martin, regarding XSLT 1.0 and Saxon 9, I was mixing concerns. I'm using Saxon on my own machine, but the enviro . . . Read full entry »


Re: Remove internal parsing and exclude one child

Posted 5/16/2017 6:01:43 PM

On Tue, May 16, 2017 at 05:29:27PM -0000, Charles O'Connor coconnor@xxxxxxxxxxxx scripsit: > Using XSLT 1.0/Saxon9he > > I have this input > > <aff id="aff1"><label>1</label>Jet Propulsion Laboratory (JPL), 4800 Oak Grove Dr Pasadena, CA <addr-line> . . . Read full entry »


Re: Remove internal parsing and exclude one child

Posted 5/16/2017 5:38:48 PM

On 16.05.2017 19:29, Charles O'Connor coconnor@xxxxxxxxxxxx wrote: Using XSLT 1.0/Saxon9he I have this input <aff id="aff1"><label>1</label>Jet Propulsion Laboratory (JPL), 4800 Oak Grove Dr Pasadena, CA <addr-line><postal-code>91109</postal-code>, & . . . Read full entry »


Remove internal parsing and exclude one child

Posted 5/16/2017 5:29:19 PM

Hi, Using XSLT 1.0/Saxon9he I have this input <aff id="aff1"><label>1</label>Jet Propulsion Laboratory (JPL), 4800 Oak Grove Dr Pasadena, CA <addr-line><postal-code>91109</postal-code>, <country>USA</country></addr-line></aff> . . . Read full entry »


Re: How To Use Streaming To Group Elements in a Flat

Posted 5/2/2017 10:25:28 PM

Running your code on Saxon 9.7, I get XTSE3430: Template rule is declared streamable but it does not satisfy the streamability rules. * The xsl:for-each-group/@group-starting-with pattern is not motionless That's because *[position()] involves counting preceding siblings. Or to look at it ano . . . Read full entry »


How To Use Streaming To Group Elements in a Flat List?

Posted 5/2/2017 8:55:04 PM

I have some very large (100s of MBs) XML database dump docs that I want to break into smaller docs. This is an easy application of for-each-group or of a simple tail recursion approach but I wanted to use this as an opportunity to learn more about XSLT 3 streaming. Ibve read through the XSLT 3 sp . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 9:38:32 PM

I still have my copy of "APL An Interactive Approach" by Gilman/Rose 1974. I did APL on a Vector Graphics terminal with that great keyboard of all the special symbols. Curiously, met some APL developers at XML Summer School when I went a few years back. On May 1, 2017 11:21 PM, " . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 9:21:15 PM

It looks like, if Ibm reading the Wikipidea entry for APL correctly: https://en.wikipedia.org/wiki/APL_syntax_and_symbols During my IBM new-hire orientation they asked how many of us had written one-line APL chess programs. About 4 people out of the 100 or so in the room raised their hands. Chee . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 9:15:22 PM

An APL-> XSLT compiler..... Now there's a challenge ! Did the APL character set ever get defined in Unicode? J Sent from my iPad > On 1 May 2017, at 21:49, Liam R. E. Quin liam@xxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > On the other hand even experienced APL pr . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 8:49:35 PM

On Mon, 2017-05-01 at 20:01 +0000, Dimitre Novatchev dnovatchev@xxxxxxxxx wrote: > > And here is an XPath 2.0 expression: > > [...[ > B B B B B B B empty(/*/*[not(self::A)][. >> /*/A[1] and /*/A[last()] >> .]) > > This XPath expression happens to be slightly short . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 8:00:30 PM

> And here is an XPath 2.0 expression: > > empty(/*/B[. >> /*/A[1] and /*/A[last()] >> .]) Making this more general: empty(/*/*[not(self::A)][. >> /*/A[1] and /*/A[last()] >> .]) This XPath expression happens to be slightly shorter (by 3 characters) than . . . Read full entry »


XSL-List Guidelines

Posted 5/1/2017 6:44:15 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: XPath for expressing contiguous elements?

Posted 5/1/2017 6:43:00 PM

And here is an XPath 2.0 expression: empty(/*/B[. >> /*/A[1] and /*/A[last()] >> .]) On Mon, May 1, 2017 at 5:59 AM, Costello, Roger L. costello@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi Folks, > > I want an XPath expression that implements this . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 4:34:03 PM

If it's possible to use some XSLT2.0 to set up a variable before then checking it via XPATH, could use the group-adjacent feature of for-each-group to set up a variable $adjacentAs <xsl:variable name="adjacentAs" as="element(adjacentAs)*> <xsl:for-each-group select=&quo . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 4:03:48 PM

not(/*/A[following-sibling::*[not(self::A)][following-sibling::A]]) returns true() if and only if there is a non-A element with following-sibling an A element, and this non-A element also has a following A sibling. -- Cheers, Dimitre Novatchev --------------------------------------- Truly grea . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 3:27:19 PM

Sorry, this works only on Roger's examples ... > Here is one without any negation: > > /*/A[preceding-sibling::A][following-sibling::A] > [preceding-sibling::*[1][self::A]] > [following-sibling::*[1][self::A]] > and true() On Mon, May 1, 2017 at 8:06 AM, . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 3:07:13 PM

Here is one without any negation: /*/A[preceding-sibling::A][following-sibling::A] [preceding-sibling::*[1][self::A]] [following-sibling::*[1][self::A]] and true() On Mon, May 1, 2017 at 7:21 AM, Michael Kay mike@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 2:21:28 PM

not(*[not(self::A)][following-sibling::A][preceding-sibling::A]) returns true if and only if there is no non-A element that is both preceded and followed by an A element, which I think is equivalent to your expression and rather simpler. Michael Kay Saxonica > On 1 May 2017, at 14:00, Costel . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 2:09:26 PM

On Mon, May 01, 2017 at 12:59:57PM -0000, Costello, Roger L. costello@xxxxxxxxx scripsit: > Hi Folks, > > I want an XPath expression that implements this rule: > > All <A> elements shall be contiguous within <Test>. I think it's easier to think of this as "is the . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 1:19:44 PM

On 01.05.17 15:13, Syd Bauman s.bauman@xxxxxxxxxxxxxxxx wrote: But if what you really want is a simple Schematron test, then | <sch:rule context="A"> | <sch:report test="following-sibling::B[following-sibling::A]">oops</sch:report> | </sch:rule> has th . . . Read full entry »


Re: XPath for expressing contiguous elements?

Posted 5/1/2017 1:13:41 PM

Roger -- I'm just wondering if this isn't the wrong tool for the job. element Test { B*, A*, B* } While non-deterministic, does ensure that all As are contiguous. (And, if at least one A is required, i.e. "A+" instead of "A*", then it is deterministic.) But if what you rea . . . Read full entry »


XPath for expressing contiguous elements?

Posted 5/1/2017 12:59:49 PM

Hi Folks, I want an XPath expression that implements this rule: All <A> elements shall be contiguous within <Test>. In this example all A's are contiguous, so the rule is satisfied: <Test> <B/> <A/> <A/> <A/> <B/> </Test> . . . Read full entry »


Re: Select everything up to and including the first <

Posted 4/19/2017 9:47:02 PM

> My context node is the <chapter> element. I want to select everything up to > and including the first <section>. In case this will be needed more than once, then using XSLT 1.0 one can do this: key('kPreceding', generate-id(/*/section[1])) | /*/section[1] where the . . . Read full entry »


Re: Select everything up to and including the first <

Posted 4/19/2017 9:19:35 PM

Hi, Or there is the XSLT Way, namely modes <xsl:template match="section"/> <xsl:template match="body"> <intro> <xsl:apply-templates/> </intro> <xsl:apply-templates select="section" mode="now-sections"/> </xs . . . Read full entry »


Re: Serializing elements in CDATA, based on an attribu

Posted 4/13/2017 9:11:23 AM

Ok, thanks a lot. I'm gonna look at both solutions. Best regards, Christophe Le 2017-04-12 18:14, Michael Kay mike@xxxxxxxxxxxx a C)critB : The only way of getting CDATA sections output by the serializer using standard XSLT capabilities, or using standard Saxon capabilities, is the cdata-section-el . . . Read full entry »


Re: Select everything up to and including the first <

Posted 4/13/2017 7:24:29 AM

Hi Rick, In Michael Kay's book, check under xsl:for-each-group, "Using group-starting-with", there is an example "Handling flat XHTML documents" which describes the situation. I think it is easier to understand group-starting-with="section" instead of group-ending-wi . . . Read full entry »


Re: Select everything up to and including the first <

Posted 4/13/2017 4:27:21 AM

May be something like this *[not(self::section)] | section[1] (not tested) On 13 April 2017 at 02:36, Rick Quatro rick@xxxxxxxxxxxxxx < xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi All, > > Here is my xml: > > <?xml version="1.0" encoding="UTF-8&qu . . . Read full entry »


Re: Select everything up to and including the first <

Posted 4/12/2017 10:12:49 PM

How about for-each-groups? <?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"> B <xs . . . Read full entry »


Re: Select everything up to and including the first <

Posted 4/12/2017 9:58:15 PM

I've always regretted that we don't have operators "until" "until-and-including". But with 3.0 you can implement them as higher-order-functions: declare function until-and-including ($seq, $condition) { head($seq), until-and-including(tail($seq)[$condition(head($seq))], $cond . . . 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

Attend a Live Webinar This Week!

Learn about Stylus Studio's unique features and benefits in just under an hour. Register for the Stylus Studio QuickStart Training WebCast!

Why Pay More for XML Tools?

With Stylus Studio® X14 XML Enterprise Suite, you get the most comprehensive XML tool suite at one incredibly low price. Value: it's just one of many reasons why smart XML developers are choosing Stylus Studio!

 
Free Stylus Studio XML Training:
W3C Member