[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xsl] linkedin discussion of "can you sell an XSLT?"
Subject: Re: [xsl] linkedin discussion of "can you sell an XSLT?" From: Dimitre Novatchev <dnovatchev@xxxxxxxxx> Date: Thu, 4 Jun 2009 15:52:15 -0700 |
Many XSLT processors can compile a (at least a main/primary) stylesheet to executable code. AFAIK Saxon can compile to Java byte-code or Java source code and .NET XslCompiledTransform compiles to .NET IL code. Many years ago Sun provided such "XSLT compilation. In this way a single application written in XSLT can be offered in executable code and this is usually a significant part of the technical protection of any software application. What is still missing is the ability to compile a set/library of stylesheets that can be used by a primary stylesheet at runtime. Though there is not any provision in the W3 Spec how to do this for XSLT (I think things are better for XQuery), a de-facto standard/implementation would be extremely useful. Not only some existing libraries such as FXSL, FunctX, ()one put here any EXSLT *implementation*, although EXSLT is just a specification, and by default the implementations are not in XSLT themselves) etc., would benefit from easier deployment (say in browsers), but this will stimulate authors to write more such libraries -- to the benefit of the whole XSLT developers community. I would welcome if EXSLT2 specifies a mechanism for run-time binding between a main stylesheets and one or more compiled libraries of functions/templates. -- Cheers, Dimitre Novatchev --------------------------------------- Truly great madness cannot be achieved without significant intelligence. --------------------------------------- To invent, you need a good imagination and a pile of junk ------------------------------------- Never fight an inanimate object ------------------------------------- You've achieved success in your field when you don't know whether what you're doing is work or play On Thu, Jun 4, 2009 at 1:21 PM, Paul Kiel <paul@xxxxxxxxxxxxxxx> wrote: > Hi Folks, > > Had an interesting discussion that I started on a Linkedin group, but should > probably have started here.B I had originally asked the question "can you > sell an XSLT?".B And by that I don't mean is it possible, but would anyone > buy one.B What is the market for XSLTs as products? > > The comments clearly indicated that people are willing to (and actually do) > buy XSLTs.B They tend to come in two forms.B First, a specific solution to a > specific task.B A key niche need.B Second, there is the idea of XSLT as a > software platform.B XSLT as programming in Xml.B I've certainly thought this > because I've been working with xml for so long that I *think* in terms of > Xml (perhaps there is a 12 step program for this).B So XSLT to me is the > java of Xml.B Of course no offense to java users, myself being one too. > > The reason I brought this up is that while I've been involved in open source > XSLT work as well as created innumerable ones for clients individually, I > have lots of ideas about XSLTs as general products. > > B Ken Holman of course highlighted a key component to this topic, which is > obfuscation in order to protect intellectual property.B B That would be the > difference between open source and product solutions. > > So I post these comments here wondering if you have thoughts on this topic > as well.B Would love to hear them. > > Cheers, > > Paul Kiel > > =================================== > W. Paul Kiel > xmlHelpline.com Consulting > bCelebrating 10 years of Xml developmentb > paul@xxxxxxxxxxxxxxx > work: 919-846-0224 > cell: 919-449-8801 > website: http://www.xmlhelpline.com > ===================================
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] linkedin discussion of "c, Michael Kay | Thread | Re: [xsl] linkedin discussion of "c, Robert Koberg |
RE: [xsl] linkedin discussion of "c, Michael Kay | Date | Re: [xsl] linkedin discussion of "c, Robert Koberg |
Month |