[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] XML Preprocessing and XSLT Processing Models

Subject: Re: [xsl] XML Preprocessing and XSLT Processing Models
From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx>
Date: Sun, 16 Feb 2014 11:49:07 -0800

At 2014-02-15 15:08 +0000, Adam wrote:
XSL Working Group,
Argumentation Community Group,

Greetings. There has been interest in dynamic or parameterizable XSLT imports and includes.
advanced functionalities are possible from parallel processing

This surprises me.

Is not the inherent structure of XML (e.g. sibling elements) and template matching model of XSLT (e.g. sibling rules) sufficient for parallelism?

XML preprocessing, XML macros (https://www.w3.org/community/argumentation/wiki/XML_Macros) and XSLT-enhanced XML includes (https://www.w3.org/community/argumentation/wiki/XSLT-Enhanced_XML_Include), facilitates such expressiveness.

None of the example instances in either of those linked documents are well-formed XML. The use of brace brackets in element names is forbidden.

How does it help the general markup community introducing yet another non-XML syntax that might confuse new users of XML? If it isn't XML, I think it should not look like XML.

At 2014-02-15 16:42 +0000, Adam wrote:
XSL Working Group, http://www.w3.org/community/argumentation/2014/02/15/xml-preprocessing-and-xslt-processing-models/ Kind regards, Adam Sobieski

While the examples on this page do not reveal the invalid syntax used in the other documents, the use of the three letters "xml" at the beginning of element names or attribute names is reserved by the W3C and should not be used by others.

I understand this is a community effort and does "not necessarily represent the views of the W3C Membership or staff", but I worry readers may get the impression that the concepts presented therein are somehow supported.

I'm in no position to say a group of like-minded enthusiasts cannot go off and do their own thing, but by using the W3C site and by posting on the list here I'm assuming you are inviting comment and my comment is that introducing your macro concept and utilizing non-XML syntax is distracting.

Since XSLT itself is composable using XSLT, then supporting "dynamic or parameterizable XSLT imports and includes" is easily supported by preprocessing the imports and includes before running the process that imports and includes them. Since XSLT is XML, do the parameterization using well-formed XML. Do annotation through the use of XML namespaces (I've done that a lot ... no need for custom syntax). Use the syntax already provided so that existing tools can be used to get the functionality you've identified as being needed.

I hope you find this feedback useful. As, I hope, do readers of the archive.

. . . . . . . . Ken

Public XSLT, XSL-FO, UBL & code list classes: Melbourne, AU May 2014 |
Contact us for world-wide XML consulting and instructor-led training |
Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm |
Crane Softwrights Ltd.            http://www.CraneSoftwrights.com/s/ |
G. Ken Holman                   mailto:gkholman@xxxxxxxxxxxxxxxxxxxx |
Google+ profile:      http://plus.google.com/+GKenHolman-Crane/about |
Legal business disclaimers:    http://www.CraneSoftwrights.com/legal |

Current Thread