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!


[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 »


Re: Select everything up to and including the first <

Posted 4/12/2017 9:30:19 PM

If only section elements can follow intro you can also do: select=b* except (section[preceding-sibling::section])b This transform: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="htt . . . Read full entry »


Re: Select everything up to and including the first <

Posted 4/12/2017 9:28:09 PM

Hi Martin, That does work. Thank you very much. I am not familiar with this construction. Does the . refer to the section[1] element? Thanks. Rick -----Original Message----- From: Martin Honnen martin.honnen@xxxxxx [mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Wednesday, April 12, 2017 . . . Read full entry »


Re: Select everything up to and including the first <

Posted 4/12/2017 9:21:30 PM

On Wed, Apr 12, 2017 at 09:06:24PM -0000, Rick Quatro rick@xxxxxxxxxxxxxx scripsit: > Hi All, > > Here is my xml: > > <?xml version="1.0" encoding="UTF-8"?> > <chapter> > <title>Title</title> > <intro> > . . . Read full entry »


Re: Select everything up to and including the first <

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

On 12.04.2017 23:06, Rick Quatro rick@xxxxxxxxxxxxxx wrote: Hi All, Here is my xml: <?xml version="1.0" encoding="UTF-8"?> <chapter> <title>Title</title> <intro> <p>Intro</p> </intro> <section>& . . . Read full entry »


Select everything up to and including the first <secti

Posted 4/12/2017 9:06:17 PM

Hi All, Here is my xml: <?xml version="1.0" encoding="UTF-8"?> <chapter> <title>Title</title> <intro> <p>Intro</p> </intro> <section></section> <section></section> <secti . . . Read full entry »


Re: Passing parameter into tag name

Posted 4/12/2017 4:18:50 PM

My preference when I see poorly-designed XML like this is to start by writing a transformation that turns it into well-designed XML, in this case converting > <Level_1_Amt>100</Level_1_Amt> to > <Amt level="1">100</Amt> The great advantage of this is that . . . Read full entry »


Re: Serializing elements in CDATA, based on an attribu

Posted 4/12/2017 4:14:02 PM

The only way of getting CDATA sections output by the serializer using standard XSLT capabilities, or using standard Saxon capabilities, is the cdata-section-elements property, and that is driven entirely by element name. For finer-grained control you'll have to do something else. One approach woul . . . Read full entry »


Serializing elements in CDATA, based on an attribute

Posted 4/12/2017 1:23:08 PM

Hello, In a document, I write many tags of metadata. Part of them, based on @code value (debug & info), MUST be serialized with a CDATA content. With this input : <metadata code="dummy">Standard serialization</metadata> <metadata code="debug">C-Data seria . . . Read full entry »


Re: Passing parameter into tag name

Posted 4/12/2017 1:18:04 PM

Thank you Martin! From: "Martin Honnen martin.honnen@xxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Sent: Wednesday, April 12, 2017 9:11 AM Subject: Re: Passing parameter into tag name On 12.04.2017 15:06, Steve Wisniewski stevewiz7 . . . Read full entry »


Re: Passing parameter into tag name

Posted 4/12/2017 1:11:23 PM

On 12.04.2017 15:06, Steve Wisniewski stevewiz76@xxxxxxxxx wrote: <foo> <Level> <Level_No>1</Level_No> </Level> <Level> <Level_No>2</Level_No> </Level> <Level> <Level_No>3</Level_No> </Level> <Cost ID='1'> <Leve . . . Read full entry »


Passing parameter into tag name

Posted 4/12/2017 1:06:01 PM

Hello all, I have a data scenario like this (edited down for clarity) where I have multiple tags that have the actual level number in the tag name: <foo> <Level> <Level_No>1</Level_No> </Level> <Level> <Level_No>2</Level_No> </Level> <Level&g . . . Read full entry »


Re: SV: questions about preceding::processing-instruct

Posted 4/10/2017 2:39:15 PM

Ah yes, then the processor can do some optimization and stop looking for 'anchor' processing instructions right after the first anchor PI has been found on the preceding axis. On 10.04.2017 16:35, Erik Zander erik.zander@xxxxxxxxxxxxxxxxxxxx wrote: Thanks Gerrit, You pointed me in the right d . . . Read full entry »


SV: questions about preceding::processing-instruction

Posted 4/10/2017 2:35:31 PM

Thanks Gerrit, You pointed me in the right direction so I could avoid the timeout :) The solution was close at hand <xsl:variable name="currentPage" select="substring-before(substring-after(./preceding::processing-instruction( 'anchor')[1], 'Page.'), '&quot;')"/> Ju . . . Read full entry »


Re: questions about preceding::processing-instruction

Posted 4/10/2017 1:30:33 PM

On 10.04.2017 15:12, Erik Zander erik.zander@xxxxxxxxxxxxxxxxxxxx wrote: Hi All! I have an optimization problem concerning preceding::processing-instruction. First some background in my xml I have processing instructions like <?anchor xml:id="orgPage.7"/?> representing the start . . . Read full entry »


questions about preceding::processing-instruction

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

Hi All! I have an optimization problem concerning preceding::processing-instruction. First some background in my xml I have processing instructions like <?anchor xml:id="orgPage.7"/?> representing the start of a page. And I have a template that matches on text(). In the template . . . Read full entry »


Fwd: Submissions open for TEI-C MM and Conference

Posted 4/7/2017 6:39:29 PM

For all you TEI users out there (with apologies for cross-posting): -------- Forwarded Message -------- Subject: Submissions open for TEI-C MM and Conference Date: Fri, 7 Apr 2017 13:48:51 -0400 From: Kathryn Tomasek <tomasek_kathryn@xxxxxxxxxxxxxxxxxx> Reply-To: Kathryn Tomasek <toma . . . Read full entry »


[ann] oXygen XML Editor, version 19

Posted 4/7/2017 8:26:30 AM

Hi all, I am happy to announce that a new version of oXygen XML Editor is available from our website: http://www.oxygenxml.com In version 19 we support Saxon 9.7.0.15, thus you can experiment with the latest XSLT, XQuery and XPath versions supported by Saxon. The default validation for XSLT sc . . . Read full entry »


Re: Moving stylesheet from Java Saxon to .NET Saxon

Posted 4/6/2017 5:09:25 PM

Thanks! Mark On 4/6/2017 10:07 AM, Michael Kay mike@xxxxxxxxxxxx wrote: Transform -it:main -xsl:xslt/content.subject.xsl . . . Read full entry »


Re: Moving stylesheet from Java Saxon to .NET Saxon

Posted 4/6/2017 5:06:34 PM

It shouldn't be necessary to do anything other than changing > java -jar saxon97\saxon9he.jar -it:main -xsl:xslt/content.subject.xsl to > Transform -it:main -xsl:xslt/content.subject.xsl The stylesheet generates a text file with x0A as the line ending, you might want to change that to x0D . . . Read full entry »


Moving stylesheet from Java Saxon to .NET Saxon

Posted 4/6/2017 4:51:34 PM

I have always used the Java version of Saxon but have been asked to supply a .Net version of a stylesheet and Windows batch file. I have never used .NET. Can anyone tell me what has to change to do this? Obviously, the call to Java must change, but how, and what else? The batch file and styleshe . . . Read full entry »


[ANN] Balisage Submissions due FRIDAY

Posted 4/4/2017 6:54:16 PM

Submissions to "Balisage: The Markup Conference" and pre-conference symposium: "Up-Translation and Up-Transformation: Tasks, Challenges, and Solutions" are due on April 7. Detailed Call for Participation: http://balisage.net/Call4Participation.html About Balisage: http://balis . . . Read full entry »


Re: [BigList Fwd] Re: XML: From flat to hierarchical w

Posted 3/30/2017 10:36:14 AM

Sorry, yes, it was harsh. I was feeling grumpy. Michael Kay Saxonica > On 30 Mar 2017, at 11:20, Pieter Lamers pieter.lamers@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Not only harsh but also incorrect. the opening post had > <xsl:stylesheet version=&q . . . Read full entry »


Re: [BigList Fwd] Re: XML: From flat to hierarchical w

Posted 3/30/2017 10:20:06 AM

Not only harsh but also incorrect. the opening post had <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" so Nicola did mention 1.0 in the first place. Other than that, it may be interesting to see if the setup Nicola uses may be altered to acc . . . Read full entry »


AW: Fwd: [BigList Fwd] Re: XML: From flat to hierarchi

Posted 3/30/2017 4:23:41 AM

Hi Nicola, Did you change the version attribute in the xsl:stylesheet to "2.0"? Maybe XSLT 2.0 is supported and you just have to enable it. However, for XSLT 1.0 I gave you already the solution: Just replace your template for rec1 with mine. At least it worked for me!? Patrik ------- . . . Read full entry »


Re: [BigList Fwd] Re: XML: From flat to hierarchical w

Posted 3/30/2017 1:49:49 AM

Hey now, that's kinda harsh... Michele ******* Michele Combs Lead Archivist, Special Collections Research Center Syracuse University 315-443-2081 mrrothen@xxxxxxx ________________________________________ From: Michael Kay mike@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Sent: Wed . . . Read full entry »


Re: [BigList Fwd] Re: XML: From flat to hierarchical w

Posted 3/30/2017 12:08:37 AM

Is it totally unreasonable to expect that if you wanted a solution using a technology that was superseded 10 years ago, you should say so in the first place rather than wasting our time? Michael Kay Saxonica > > Could you help me, please, with a solution in XSLT 1.0? > > > Thanks a . . . Read full entry »


Fwd: [BigList Fwd] Re: XML: From flat to hierarchical

Posted 3/29/2017 11:51:44 PM

Hi Patrik, Thank you very much for your help. I appreciate your solution of rec2 recursion key. It's a good idea! For XSLT 2.0, unfortunatelly it's unsupported. Perhaps is for this that <xsl:copy> <xsl:for-each-group select="*" group-starting-with="rec1"> . . . Read full entry »


Re: XML: From flat to hierarchical with grouping

Posted 3/29/2017 1:32:19 PM

You can adapt the code at http://stackoverflow.com/questions/42932880/ which gives a general approach to converting a flat sequence with level numbers into a nested hierarchy. This approach handles an arbitrary number of levels; if you only have a maximum of three then you could possibly simplif . . . Read full entry »


AW: XML: From flat to hierarchical with grouping

Posted 3/29/2017 4:41:46 AM

Hi Nicola, you need to process the rec2 elements that you got with key('k2', generate-id()) recursively instead of just copying them. And since rec1 does not contain rec2 elements the <xsl:apply-templates select="rec2" /> has no effect. So this template should work: <xsl:templa . . . Read full entry »


XML: From flat to hierarchical with grouping

Posted 3/29/2017 2:12:09 AM

I need to manipolate this XML: <root> <row> <rec1> <fld1-1/> </rec1> <rec2> <fld2-1/> </rec2> <rec3> <fld3-1/> </rec3> <rec3> <fld3-2/> </rec3> <rec2 . . . Read full entry »


Re: Case-insensitive filter match for template wanted

Posted 3/28/2017 11:42:27 AM

On 28/03/17 10:57, Michael Kay mike@xxxxxxxxxxxx wrote: > It depends a bit about whether you care what happens to characters > like "dotless i" (which probably aren't going to appear in your input > unless you are Turkish). Or Irish :-) ///Peter . . . Read full entry »


Re: Case-insensitive filter match for template wanted

Posted 3/28/2017 9:57:07 AM

> So I tried: > <x:template match="section[ parameter/@name='Rule' ][ upper-case( parameter/value/@entry ) = 'INPUT' ]" mode="processes" > > > But that gives me (using Saxon HE9.7.0.5): > bA sequence of more than one item is not allowed as the first argumen . . . Read full entry »


Re: Case-insensitive filter match for template wanted

Posted 3/28/2017 9:56:47 AM

In your first expression you were comparing two sequences: foo/bar/@att is a sequence of attributes and b= bINPUTbb is effectively b = (bINPUTb)b, that is a sequence of one item. Sequences are comparable such that if any item in the left-hand sequence matches any item in the right-hand sequ . . . Read full entry »


Re: Case-insensitive filter match for template wanted

Posted 3/28/2017 9:49:31 AM

That's brilliant. Works fine. Thanks Martin. I was tempted to say "that was easy" but it's only easy if you know the answer... Regards, Richard. Richard Kerry BNCS Engineer, SI SOL Telco & Media Vertical Practice T: +44 (0)20 3618 2669 M: +44 (0)7812 325518 Lync: +44 (0) 20 3618 . . . Read full entry »


Re: Case-insensitive filter match for template wanted

Posted 3/28/2017 9:39:26 AM

On 28.03.2017 11:35, Kerry, Richard richard.kerry@xxxxxxxx wrote: So I tried: <x:template match="section[ parameter/@name='Rule' ][ upper-case( parameter/value/@entry ) = 'INPUT' ]" mode="processes" > But that gives me (using Saxon HE9.7.0.5): bA sequence of more tha . . . Read full entry »


Case-insensitive filter match for template wanted

Posted 3/28/2017 9:35:20 AM

I have a template for which I need it to do a case-insensitive match on a value in an attribute. When my template's filter was case-sensitive it worked happily. Ie. <x:template match="section[ parameter/@name='Rule' ][ parameter/value/@entry = 'INPUT' ]" mode="processes" > . . . Read full entry »


Re: Outputting UTF-8

Posted 3/25/2017 3:33:41 PM

Hi, Martin. That is absolutely correct. I remember now that in my testing I had used 'txt' as the extension and when I loaded it into Excel set the UTF-8 flag. Problem solved. Face red. Thanks, Mark On 3/25/2017 7:50 AM, Martin Honnen martin.honnen@xxxxxx wrote: On 25.03.2017 15:39, Mark Wilson p . . . Read full entry »


Re: Outputting UTF-8

Posted 3/25/2017 2:50:08 PM

On 25.03.2017 15:39, Mark Wilson pubs@xxxxxxxxxxxx wrote: While writing and testing my XSL stylesheet, the direct output was in UTF-8. However, as soon as I switched to result-document, I got garbage characters for diacritics from my original xml. That is, for 'ZC<rich', I get ' ZCB<rich'. . . . Read full entry »


Outputting UTF-8

Posted 3/25/2017 2:39:14 PM

While writing and testing my XSL stylesheet, the direct output was in UTF-8. However, as soon as I switched to result-document, I got garbage characters for diacritics from my original xml. That is, for 'ZC<rich', I get ' ZCB<rich'. Except for the absence of UTF-8, everything else works . . . Read full entry »


Re: Generate separate elements, not just attribute val

Posted 3/24/2017 6:58:00 AM

Hi Charles, you mentionend that an XSLT 1.0 version would come handy... <?xml version="1.0"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="xs" version="1. . . . Read full entry »


Re: Generate separate elements, not just attribute val

Posted 3/23/2017 8:48:12 PM

Thanks Martin and Michael for the help and the information. Greatly appreciated! When I saw your responses, I got a bit of a laugh at how bad my original .xsl was. -Charles -----Original Message----- From: Martin Honnen martin.honnen@xxxxxx [mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx] Sent: . . . Read full entry »


Re: Generate separate elements, not just attribute val

Posted 3/23/2017 8:01:35 PM

On 23.03.2017 19:23, Charles O'Connor coconnor@xxxxxxxxxxxx wrote: Hi all, Extreme novice here, so I appreciate your help. Using XSLT 2.0 (explained later) and Saxon9 HE. I have JATS 1.1 (archiving) input: . . . <contrib-group> <contrib contrib-type="author"> <name& . . . Read full entry »


Re: Generate separate elements, not just attribute val

Posted 3/23/2017 7:59:25 PM

> On 23 Mar 2017, at 18:23, Charles O'Connor coconnor@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Hi all, > > Extreme novice here, so I appreciate your help. > > Using XSLT 2.0 (explained later) and Saxon9 HE. > > I have JATS 1.1 (archiving) in . . . Read full entry »


Generate separate elements, not just attribute values

Posted 3/23/2017 6:23:28 PM

Hi all, Extreme novice here, so I appreciate your help. Using XSLT 2.0 (explained later) and Saxon9 HE. I have JATS 1.1 (archiving) input: . . . <contrib-group> <contrib contrib-type="author"> <name> <surname>Franzke</surname> <given-names> . . . Read full entry »


Re: Streaming and grouping in XSLT 3.0

Posted 3/21/2017 12:21:27 PM

First question: in your grouping of properties using the rdf:about attribute, are the groups adjacent? The for-each-group[@group-adjacent] instruction is fully streamable according to the XSLT 3.0 rules, and the Saxon implementation is also streamable (though in some circumstances -- I would need t . . . Read full entry »


Re: Streaming and grouping in XSLT 3.0

Posted 3/21/2017 11:38:22 AM

Thanks Martin. That's a start :) As for the reason we want to use streaming, I guess the answer is both: - loading external documents such as http://dbpedia.org/resource/Copenhagen might result in large data volumes. Right now we are processing them in memory, but we are running out of it (not usi . . . Read full entry »


Re: Streaming and grouping in XSLT 3.0

Posted 3/21/2017 11:19:55 AM

On 21.03.2017 11:44, Martynas JuseviD ius martynas@xxxxxxxxxxxx wrote: Now my question is, how do I even begin analyzing the streamability of this approach in XSLT 3.0? I guess my main concern is that such grouping would not be streamable, but maybe there are other solutions? As the stylesheet uses . . . Read full entry »


Streaming and grouping in XSLT 3.0

Posted 3/21/2017 10:43:51 AM

Hi all, fistly I must admit I'm a complete novice when it comes to XSLT 3.0 and streaming (though not XSLT 2.0). My use case is as follows -- a triplestore returns streaming RDF/XML (omitting namespaces): <rdf:RDF> <rdf:Description rdf:about="http://dbpedia.org/resource/Copenhage . . . Read full entry »


XSLT docset for Dash app?

Posted 3/20/2017 7:16:47 PM

I've just been testing out Dash (https://kapeli.com/dash), a documentation browser / code snippet manager for OS X and iOS. It comes off the shelf with XSLT as a supported documentation set, but it's only XSLT 1.0 (including both XSLT elements and XPath functions). Has anyone out there generated . . . Read full entry »


[ANN] Balisage Submissions due in 3 Weeks

Posted 3/16/2017 9:19:42 PM

Submissions to "Balisage: The Markup Conference" and pre-conference symposium: "Up-Translation and Up-Transformation: Tasks, Challenges, and Solutions" are on April 7. It is time to start writing! Balisage: The Markup Conference 2017 August 1 b 4, 2017, Rockville, MD (a subu . . . Read full entry »


xspec: testing template matching document root

Posted 3/8/2017 9:15:52 AM

hi group, I have tried to post this question on the google Xspec list, but the messages didn't arrive. I hope the post is not misplaced here... I use xspec often to test bug fixes on my company's style sheets. They helped me a lot, especially when it comes to old features: some 'fixes' appear . . . Read full entry »


Re: whitespace normalization around keyword-like phras

Posted 3/8/2017 9:10:12 AM

On 07/03/17 21:20, Wendell Piez wapiez@xxxxxxxxxxxxxxx wrote: [...] > Yes indeed, why I like to say information is fractal. No matter how > fine we get, there is always a raggedy edge. I just had a call from a user thanking me for my help on [topic] and saying this would be the last time he . . . Read full entry »


Re: whitespace normalization around keyword-like phras

Posted 3/7/2017 9:19:57 PM

Peter, Gerrit and XSL-List, On Tue, Mar 7, 2017 at 4:49 AM, Flynn, Peter pflynn@xxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > On 06/03/17 21:24, Liam R. E. Quin liam@xxxxxx wrote: >> On Mon, 2017-03-06 at 14:11 +0000, Imsieke, Gerrit, le-tex >> gerrit.imsieke@xxxxx . . . Read full entry »


Re: sort on one key - duplicates

Posted 3/7/2017 10:01:14 AM

> On 7 Mar 2017, at 09:44, Dr. Patrik Stellmann patrik.stellmann@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Hi Raimund, > > You could just replace the "l_name" by "concat(l_name, ' ', f_name)" within the xsl:key, key() and xsl:sort. A b . . . Read full entry »


Re: whitespace normalization around keyword-like phras

Posted 3/7/2017 9:49:24 AM

On 06/03/17 21:24, Liam R. E. Quin liam@xxxxxx wrote: > On Mon, 2017-03-06 at 14:11 +0000, Imsieke, Gerrit, le-tex > gerrit.imsieke@xxxxxxxxx wrote: >> Over the weekend Ive been writing a whitespace normalization >> stylesheet > > Sounds like you could wrestle a Balisage pa . . . Read full entry »


AW: sort on one key - duplicates

Posted 3/7/2017 9:44:34 AM

Hi Raimund, You could just replace the "l_name" by "concat(l_name, ' ', f_name)" within the xsl:key, key() and xsl:sort. BTW: Since the 2nd and 3rd for-each loops are identical you might consider putting them into a separate template to avoid duplicated code. Regards, Patrik . . . Read full entry »


sort on one key - duplicates

Posted 3/7/2017 9:31:32 AM

Hi Folks, I have an XSL which pulls out all last names and creates a sorted list of these. Works fine, but now I noticed that for duplicated last names only the first person is created in the output! So I need to also take the first name into account! But Ibm lacking the idea to accomplish this! . . . Read full entry »


Re: whitespace normalization around keyword-like phras

Posted 3/6/2017 11:17:22 PM

Sorry, Tommie, for misspelling your nameb& And yes, Tommy, I could bring my family but Balisage is just before . . . Read full entry »


Re: whitespace normalization around keyword-like phras

Posted 3/6/2017 11:10:34 PM

On 06.03.2017 22:23, Liam R. E. Quin liam@xxxxxx wrote: Sounds like you could wrestle a Balisage paper out of this, if you're willing to travel to the USA.... Traveling to the USA is not much of an issue for me because a) Ibm unlikely to be detained and interrogated upon arrival and b) although . . . Read full entry »


Re: whitespace normalization around keyword-like phras

Posted 3/6/2017 10:54:34 PM

Consider bringing your family to Balisage. There are a lot of interesting things to do/see in the general area. See: https://www.balisage.net/2017/2017LocalActivities.html for a few of them. b Tommie > On Mar 6, 2017, at 5:34 PM, Gerrit Imsieke gerrit.imsieke@xxxxxxxxx <xsl-list-service@xx . . . Read full entry »


Re: whitespace normalization around keyword-like phras

Posted 3/6/2017 10:33:47 PM

Yes, this might fit nicely into the pre-conf symposium. Not sure though whether The Boss will let me go because itbs vacation season and Ibm supposed^H^H^H^H^H^H^H^H inclined to spend time with my family. Besides, the stylesheet does already handle punctuation in nested elements. Punctuation (br . . . Read full entry »


Re: whitespace normalization around keyword-like phras

Posted 3/6/2017 9:22:53 PM

On Mon, 2017-03-06 at 14:11 +0000, Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx wrote: > Over the weekend Ibve been writing a whitespace normalization > stylesheet Sounds like you could wrestle a Balisage paper out of this, if you're willing to travel to the USA.... A related issue is . . . Read full entry »


whitespace normalization around keyword-like phrases

Posted 3/6/2017 2:10:38 PM

Hi Folks, Over the weekend Ibve been writing a whitespace normalization stylesheet that transforms input like <emphasis>Nested<glossterm> phrases </glossterm>with whitespace </emphasis> into <emphasis>Nested <glossterm>phrases</glossterm> with whitespace . . . Read full entry »


Re: boolean(string(false())) is true - always?

Posted 3/2/2017 10:02:49 PM

Martin, David, Thank you very much for restoring sanity in my brain! - Michael > Am 02.03.2017 um 16:27 schrieb Sewell, David R. (drs2n) dsewell@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>: > > The difference in return value between fn:boolean('false') and xs:boolean('f . . . Read full entry »


Re: boolean(string(false())) is true - always?

Posted 3/2/2017 3:27:00 PM

The difference in return value between fn:boolean('false') and xs:boolean('false') must be in the top ten of XPath "gotcha's" -- I usually forget that despite having worked with XPath for more than a decade. David On Thu, 2 Mar 2017, Martin Honnen martin.honnen@xxxxxx wrote: > On . . . Read full entry »


Re: boolean(string(false())) is true - always?

Posted 3/2/2017 3:19:14 PM

On 02.03.2017 16:00, Michael MC<ller-Hillebrand mmh@xxxxxxxxx wrote: <xsl:function name="dy:isFoo" as="xs:boolean"> <xsl:param name="node" as="node()"/> <xsl:choose> <xsl:when test="$node[self::bar/@foo = 'x']" . . . Read full entry »


boolean(string(false())) is true - always?

Posted 3/2/2017 3:00:28 PM

Hi folks, I was visiting some old code: <xsl:function name="dy:isFoo" as="xs:boolean"> <xsl:param name="node" as="node()"/> <xsl:choose> <xsl:when test="$node[self::bar/@foo = 'x']"> <xsl:value- . . . Read full entry »


XSL-List Guidelines

Posted 3/1/2017 8:46:53 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: axes in XPath patterns

Posted 3/1/2017 4:42:48 PM

The pattern syntax in XSLT 1.0 and XSLT 2.0, for no good reason at all, allows the "//" pseudo-operator but does not allow *explicit* use of the descendant or descendant-or-self axes. This is fixed in 3.0, which allows all the downward axes to be used. Michael Kay Saxonica > On 1 Ma . . . Read full entry »


Re: axes in XPath patterns

Posted 3/1/2017 4:32:44 PM

On 01.03.2017 17:29, Birnbaum, David J djbpitt@xxxxxxxx wrote: Dear XSL-list, If I9ve understood correctly, the only axes supported in an XPath pattern in XSLT 2.0 are the child and the attribute axes. For that reason, a construction like: <xsl:template match="paragraph/descendant::inner& . . . Read full entry »


axes in XPath patterns

Posted 3/1/2017 4:28:51 PM

Dear XSL-list, If I9ve understood correctly, the only axes supported in an XPath pattern in XSLT 2.0 are the child and the attribute axes. For that reason, a construction like: <xsl:template match="paragraph/descendant::inner"> should raise an error, as it does in <oXygen/> . . . Read full entry »


Re: Filtering on a tokenized list

Posted 2/24/2017 6:24:23 AM

I played with your use case, and I think you need something like below: XML document <?xml version="1.0" encoding="UTF-8"?> <X colwidth="0.439in 1.845in"/> XSLT program <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xm . . . Read full entry »


Re: Filtering on a tokenized list

Posted 2/23/2017 1:01:09 PM

On 23.02.2017 13:49, Rick Quatro rick@xxxxxxxxxxxxxx wrote: I have an attribute value that I want to convert to a sequence of decimals: @colwidth="0.439in 1.845in" I am using tokenize to drop the measurement units before I convert each member to decimal: tokenize($widths,'[^\.\d]') Th . . . Read full entry »


Filtering on a tokenized list

Posted 2/23/2017 12:48:55 PM

Hi All, I have an attribute value that I want to convert to a sequence of decimals: @colwidth="0.439in 1.845in" I am using tokenize to drop the measurement units before I convert each member to decimal: tokenize($widths,'[^\.\d]') This works, except I get a empty string as the last i . . . Read full entry »


Re: XPath Expressions: Separate predicates or one pre

Posted 2/22/2017 10:13:29 AM

> On 22 Feb 2017, at 00:10, Dimitre Novatchev dnovatchev@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > >> But it occurs to me that in this case the expressions are functionally identical: the set of predicates is effectively an AND group. > >> Is there any . . . Read full entry »


Re: XPath Expressions: Separate predicates or one pre

Posted 2/22/2017 12:10:26 AM

> But it occurs to me that in this case the expressions are functionally identical: the set of predicates is effectively an AND group. > Is there any reason to prefer one form expression over the other? No, but the ordering of the sub-expressions (assuming the processor does shortcuts) can . . . Read full entry »


Re: XPath Expressions: Separate predicates or one pre

Posted 2/21/2017 11:00:25 PM

> On 21 Feb 2017, at 22:08, Eliot Kimber ekimber@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > Ibm updating code that has expressions like: > > <xsl:when test=b*[@a = b1b and @b = b2b and @c = b3b]b> > > My normal practice would be to us . . . Read full entry »


XPath Expressions: Separate predicates or one predicat

Posted 2/21/2017 10:07:55 PM

Ibm updating code that has expressions like: <xsl:when test=b*[@a = b1b and @b = b2b and @c = b3b]b> My normal practice would be to use separate predicates: <xsl:when test=b*[@a = b1b][@b = b2b][@c = b3b]b> But it occurs to me that in this case the expressions are f . . . Read full entry »


Re: Output from XSLT showing if SAXON Licence Features

Posted 2/21/2017 8:06:36 PM

Hi, As Ken says there are system functions for reflecting the processor and version. In addition, there are the XSLT functions function-available and element-available, which you can use to check dynamically whether a feature is exposed with a function or (extension) element. That's not quite th . . . Read full entry »


[ann] [webinar] Unit testing XSLT with XSpec and oXyge

Posted 2/21/2017 7:41:05 AM

Hi, I would like to invite you to attend our webinar next week, covering XSLT unit testing support in oXygen, built around XSpec: Tuesday, Feb 28 @ 8 AM PST = 11 AM EST = 5 PM CET https://www.oxygenxml.com/events/2017/webinar_unit_testing_xslt_with_xspec_and_oxygen.html Best Regards, George -- G . . . Read full entry »


Output from XSLT showing if SAXON Licence Features are

Posted 2/20/2017 2:33:33 PM

Hi, Is there a way, within an XSL style sheet, to test whether a Saxon (9.6 EE) transformation is running with licence features enabled or not? Ideally, applying the transformation would just return: <result>true</result> or <result>false</result> accordingly. This might th . . . Read full entry »


Re: Output from XSLT showing if SAXON Licence Features

Posted 2/20/2017 2:32:25 PM

Have you tried using system-property('xsl:product-version')? I hope this helps. . . . . . . Ken At 2017-02-20 14:12 +0000, Neil Hunter huntern@xxxxxxx wrote: Hi, Is there a way, within an XSL style sheet, to test whether a Saxon (9.6 EE) transformation is running with licence features enabled . . . Read full entry »


Output from XSLT showing if SAXON Licence Features are

Posted 2/20/2017 2:12:04 PM

Hi, Is there a way, within an XSL style sheet, to test whether a Saxon (9.6 EE) transformation is running with licence features enabled or not? Ideally, applying the transformation would just return: <result>true</result> or <result>false</result> accordingly. This might th . . . Read full entry »


Re: Passing NodeSet into XSLT 1.0 in Java 7 via setPa

Posted 2/17/2017 3:05:19 PM

The best information I can find on what values Xalan accepts is: The setParameter() method provides a value for a parameter that overrides any value used in the stylesheet itself. The processor is responsible for converting the Java object type passed to a reasonable XSLT equivalent. This should w . . . Read full entry »


Re: Passing NodeSet into XSLT 1.0 in Java 7 via setPa

Posted 2/17/2017 2:44:12 PM

Oops. I didn't look at the name of the author. But it doesn't matter, I've only said good things about XOM ! ;) Le 2017-02-17 15:41, Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx a C)critB : On 17.02.2017 15:35, cmarchand@xxxxxxxxxx wrote: b& If you want to manipulate the tree, have a look . . . 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