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

[xsl] [ANN] Saxon-CE 1.0 (XSLT 2.0 on the browser)


Subject: [xsl] [ANN] Saxon-CE 1.0 (XSLT 2.0 on the browser)
From: Mark Anderson <mark@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 15 Jun 2012 21:26:15 +0000

Hi Michael

Just read this about Saxon-CE " the ability to launch Saxon from the
xml-stylesheet processing instruction via an XSLT 1.0 bootstrap stylesheet
came from a chance remark during the XML Prague conference, but it will make a
big difference to anyone trying to migrate an existing XSLT 1.0 application."
Does this mean any app that uses XSLT1.0 (i.e. non browser) could use it?

Regards

Mark




-----Original Message-----
From: xsl-list-digest-help@xxxxxxxxxxxxxxxxxxxxxx
[mailto:xsl-list-digest-help@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Friday, June 15, 2012 12:10 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: xsl-list Digest 15 Jun 2012 05:10:02 -0000 Issue 2855

xsl-list Digest 15 Jun 2012 05:10:02 -0000 Issue 2855

Topics (messages 62365 through 62368):

[ANN] Saxon-CE 1.0 (XSLT 2.0 on the browser)
	62365 by: Michael Kay
	62366 by: Dimitre Novatchev
	62367 by: Michael Kay
	62368 by: Philip Fearon

Administrivia:

To subscribe to the digest, e-mail:
	<xsl-list-digest-subscribe@xxxxxxxxxxxxxxxxxxxxxx>

To unsubscribe from the digest, e-mail:
	<xsl-list-digest-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx>

To post to the list, e-mail:
	<xsl-list@xxxxxxxxxxxxxxxxxxxxxx>


----------------------------------------------------------------------
Date: Thu, 14 Jun 2012 18:19:04 +0100
To: Xsl-List <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
From: Michael Kay <mike@xxxxxxxxxxxx>
Subject: [ANN] Saxon-CE 1.0 (XSLT 2.0 on the browser)
Message-ID: <4FDA1D08.8080306@xxxxxxxxxxxx>

After a long gestation period, we are pleased to announce that Saxon Client
Edition is now a product.

This means that finally, XSLT 2.0 is available on the browser. For practical
purposes, that means every browser.

I feel this is a pretty significant event; it's doing what XSLT was intended
to do all those years ago, of serving XML content and leaving all the
presentation and interaction logic to happen client side. In fact it goes a
lot further than the original concept, because it allows XSLT to be used not
only for generation of (HTML + Javascript), but it also cuts out the need to
write Javascript since all the user interaction can now be handled in XSLT as
well.

It's not open source, but there's a free license for small organizations, and
it's our hope that the pricing is sufficiently attractive to give good value
to everyone. Licensing is on a per-web-domain basis.

If you've been following progress through the alpha and beta releases, the
changes in the final product are mainly about creating interfaces to allow
much closer integration with the browser environment (via Javascript APIs), as
well as a lot of detailed engineering work on logging, diagnostics, debugging
features and the like, and of course performance. We've had excellent feedback
during the beta release and most of the suggestions that came back from users
have been incorporated. As well as the demos we have created ourselves, the
web site links to some fascinating applications built by users.

Special congratulations to Phil Fearon who joined Saxonica with the task of
turning Saxon-CE from a prototype to a product and has completed that task
admirably.

Product information can be found at http://www.saxonica.com/ce/download.xml

I've written a blog entry with more thoughts on the significance of this
development at http://dev.saxonica.com/blog/mike/2012/06/index.html

Michael Kay
Saxonica

------------------------------

Date: Thu, 14 Jun 2012 13:20:13 -0700
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
From: Dimitre Novatchev <dnovatchev@xxxxxxxxx>
Subject: Re: [xsl] [ANN] Saxon-CE 1.0 (XSLT 2.0 on the browser)
Message-ID:
<CAK4KnZfcFyaLwCF88d7+Jn2vdYen2GB8mL=rPV+3z9Hz57upHw@xxxxxxxxxxxxxx>

Congratulations!

I really hope this will be a game changer.

I am interested to tweak the XPath Visualizer for XPath 2.0 (which is now a
.NET WinForms application) into one that uses Saxon CE and can be run in any
of today's major five browsers.

Is there an option to package Saxon CE (local machine) only with a particular
app, so that the app users will not be required to obtain and re-register a
license? There may be a class of users that aren't XSLT developers but need to
learn XPath 2.0 using an in-browser tool.
Such people are better spared the need to obtain a license that they aren't
going to use but inside the App.

Needless to say, the App + SaxonCE integration should not allow use of SaxonCE
separately from the App (something that I believe is the case of how oXygen
and Saxon are bundled together at present).

Cheers,
Dimitre.

On Thu, Jun 14, 2012 at 10:19 AM, Michael Kay <mike@xxxxxxxxxxxx> wrote:
>
> After a long gestation period, we are pleased to announce that Saxon
> Client Edition is now a product.
>
> This means that finally, XSLT 2.0 is available on the browser. For
> practical purposes, that means every browser.
>
> I feel this is a pretty significant event; it's doing what XSLT was
> intended to do all those years ago, of serving XML content and leaving
> al=
l
> the presentation and interaction logic to happen client side. In fact
> it goes a lot further than the original concept, because it allows
> XSLT to b=
e
> used not only for generation of (HTML + Javascript), but it also cuts
> out the need to write Javascript since all the user interaction can
> now be handled in XSLT as well.
>
> It's not open source, but there's a free license for small
> organizations, and it's our hope that the pricing is sufficiently
> attractive to give goo=
d
> value to everyone. Licensing is on a per-web-domain basis.
>
> If you've been following progress through the alpha and beta releases,
> th=
e
> changes in the final product are mainly about creating interfaces to
> allo=
w
> much closer integration with the browser environment (via Javascript
> APIs=
),
> as well as a lot of detailed engineering work on logging, diagnostics,
> debugging features and the like, and of course performance. We've had
> excellent feedback during the beta release and most of the suggestions
> th=
at
> came back from users have been incorporated. As well as the demos we
> have created ourselves, the web site links to some fascinating
> applications bu=
ilt
> by users.
>
> Special congratulations to Phil Fearon who joined Saxonica with the
> task of turning Saxon-CE from a prototype to a product and has
> completed that task admirably.
>
> Product information can be found at
> http://www.saxonica.com/ce/download.xml
>
> I've written a blog entry with more thoughts on the significance of
> this development at
> http://dev.saxonica.com/blog/mike/2012/06/index.html
>
> Michael Kay
> Saxonica
>

--
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
-------------------------------------
To avoid situations in which you might make mistakes may be the biggest
mistake of all
------------------------------------
Quality means doing it right when no one is looking.
-------------------------------------
You've achieved success in your field when you don't know whether what you're
doing is work or play
-------------------------------------
Facts do not cease to exist because they are ignored.
-------------------------------------
I finally figured out the only reason to be alive is to enjoy it.

------------------------------

Date: Thu, 14 Jun 2012 22:02:12 +0100
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
From: Michael Kay <mike@xxxxxxxxxxxx>
Subject: Re: [xsl] [ANN] Saxon-CE 1.0 (XSLT 2.0 on the browser)
Message-ID: <4FDA5154.2050704@xxxxxxxxxxxx>

 >Is there an option to package Saxon CE (local machine) only with a
particular app, so that the app users will not be required to obtain and
re-register a license?

Not at the moment. We've always known such requirements would come up, but we
put them to one side to worry about once we had the basic end-user product
out. There's a whole load of ways people are going to want to configure this
technology - Phil has been looking at the way Windows 8 uses HTML5 and
Javascript for non-web applications, for example - and it will take us time to
work out what hooks and interfaces we need to exploit all the opportunities,
as well as the commercial offerings we need to put in place.

Michael Kay
Saxonica

------------------------------

Date: Thu, 14 Jun 2012 22:30:34 +0100
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
From: Philip Fearon <pgfearo@xxxxxxxxxxxxxx>
Subject: Re: [xsl] [ANN] Saxon-CE 1.0 (XSLT 2.0 on the browser)
Message-ID:
<CADV2FzR9oWS=2MwwC=oMWV2T_kHsNHnQfNo-ksq3ehQAG5yUMA@xxxxxxxxxxxxxx>

Just to expand on Michael's comment on hooks and interfaces: Saxon-CE
currently has a capability to make function calls to an app hosting a web
browser via the window.external object. There's just one function supported,
saxonErrorHandler - for sending error and diagnostics messages (like
xsl:message or fn:trace() output) to the host
applciation[1]:

To initiate the 'bridge' connection (to check the function exists within the
external object), Saxon-CE's first call uses a special INIT logLevel - so one
simple solution would be for the host app to send a license key in response to
this first call. I'm getting into solution space too early here, but the main
thing is that this is certainly feasible from a technical standpoint.

Phil Fearon
Saxonica

[1]http://www.saxonica.com/ce/doc/system-interfaces/external.xml

On Thu, Jun 14, 2012 at 10:02 PM, Michael Kay <mike@xxxxxxxxxxxx> wrote:
>>Is there an option to package Saxon CE (local machine) only with a
>>particular app, so that the app users will not be required to obtain
>>and  re-register a license?
>
> Not at the moment. We've always known such requirements would come up,
> bu=
t
> we put them to one side to worry about once we had the basic end-user
> product out. There's a whole load of ways people are going to want to
> configure this technology - Phil has been looking at the way Windows 8
> us=
es
> HTML5 and Javascript for non-web applications, for example - and it
> will take us time to work out what hooks and interfaces we need to
> exploit all the opportunities, as well as the commercial offerings we
> need to put in place.
>
>
> Michael Kay
> Saxonica
>

------------------------------

End of xsl-list Digest
***********************************


Current Thread
Keywords