RE: XProc 1.0 to 3.0 migration

This all makes sense. Thanks Gerrit and Martin!

Cheers, Wendell

-----Original Message-----
From: Imsieke, Gerrit, le-tex <> 
Sent: Sunday, May 24, 2020 2:29 AM
Subject: Re: XProc 1.0 to 3.0 migration

As far as I know, no one has yet taken on the task of writing such an XSLT.

One problem that I see is how to leave multiline XPath expressions intact, for example here:

In the *.xpl files of a typical transpect project, I found 101 multiline select or match attributes. Most of them are in libraries though, so they only need to be migrated once, for many projects.

I thought about patching xerces so that it optionally doesn't normalize whitespace in attributes.

But it might be useful to parse the XPath expressions anyway. For example, if the migration stylesheet tries to convert parameter ports into parameter options, it might need to change expressions that refer to /c:param-set documents, too. And if the XPath expressions are parsed (including those in inline XSLT), they can be nicely indented on output.

Anyway, I hope that if someone is able to report first useful results of their XProc migration XSLT, they will share the repo location with this list so that we can improve it collectively.


On 23.05.2020 11:36, Martin Honnen wrote:
> Am 22.05.2020 um 20:51 schrieb Piez, Wendell A. (Fed):
>> XProctors:
>> Having said the more important may I sneak in a question? When (oh 
>> happy day) I migrate to XProc 3.0, what happens to my library of 
>> XProc 1.0? Is there an XSLT I could run to update my old pipeline 
>> files, or other obvious migration pathway? I looked in the spec for 
>> hints on backward compatibility and nothing jumped out.
> Norm was asked about this in his talk at XmlPrague this year I think 
> and in

> 378&amp;
> 8d7ffabee93%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C6372589862253
> 30571&amp;sdata=FtXjyBjbZnjLR3P4pi%2Fe9FZorOODSe3aweAiuk%2Bzf%2FE%3D&a
> mp;reserved=0 indicates that they hope to have a stylesheet that 
> performs the transformation from XProc 1 to XProc 3 but probably the 
> result needs some correction.
> That's all I know about this.

Received on Tuesday, 26 May 2020 14:18:30 UTC