Re: Are folks still actively using Xalan-J?

--000000000000a2e15e05d73244bf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Say what you will about XML, JSON is just reinventing the wheel. How do you
transform a JSON document into another JSON document or into a PDF? With
Jolt? Good luck. XML and XSLT, XML Schema, and on.

2c,
Gary

On Fri, Feb 4, 2022 at 9:07 AM Klaus Malorny <[email protected]> wrote=
:

> On 02.02.22 18:07, Joseph Kesselman wrote:
> > Or has everyone moved to other tools?
> >
> > As [email protected], I was involved in Xalan's development. (And
> > Xerxes, to a _much_ lesser extent; I wrote their first DOM
> implementation.)
> >
> > [...]
> >
>
> Hi,
>
> just my personal view: Several years ago, we moved away from XSL/T 1.0
> to XSL/T 2.0, as it provided so much more functionality and allowed us
> to simplify our tasks. We are currently using the open source Saxon
> "Home Edition" as the processor. It is limited in its functionality,
> however, while the limitations do exist, they do not prevent anyone from
> taking advantage of the important features of XSLT/2+. So this is more
> than fair and the said shall not be regarded as any kind of negative
> critics on Michael Kay's business model. Nevertheless, to my knowledge,
> there is no open source Java implementation available that fully
> implements XSL/T 2.0 and later versions.
>
> On the other hand, one has to admit that XML and the related
> technologies are no longer everyone's darling. XML and the related
> technologies are nowadays regarded as verbose, cumbersome and no longer
> as modern or state-of-the-art. The next generation of developers
> probably might see these as dinosaurs like my generation saw the
> mainframes and COBOL. They are more and more replaced by other
> technologies (which are IMHO in no way better). For example, in a
> recently project, I could not convince my younger colleagues to use
> XSL/T for a specific task as we did in previous projects =E2=80=93 a much
> simpler, but also much less powerful approach was chosen.
>
> That said, I believe there is surely a community that would appreciate
> your work, but that community will likely shrink over time (cannot say
> how fast, though).
>
> Hope that helps,
>
> Klaus
>
>
>

--000000000000a2e15e05d73244bf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Say what you will about XML, JSON is just reinventing the =
wheel. How do you transform a JSON document into another JSON document or i=
nto a PDF? With Jolt? Good luck. XML and XSLT, XML Schema, and on.=C2=A0<di=
v><br></div><div>2c,</div><div>Gary</div></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 4, 2022 at 9:07 AM Kla=
us Malorny &lt;<a href=3D"mailto:[email protected]">Klaus.Malorny@knip=
p.de</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">On 02.02.22 18:07, Joseph Kesselman wrote:<br>
&gt; Or has everyone moved to other tools?<br>
&gt; <br>
&gt; As <a href=3D"mailto:[email protected]" target=3D"_blank">keshlam=
@watson.ibm.com</a>, I was involved in Xalan&#39;s development. (And <br>
&gt; Xerxes, to a _much_ lesser extent; I wrote their first DOM implementat=
ion.)<br>
&gt; <br>
&gt; [...]<br>
&gt; <br>
<br>
Hi,<br>
<br>
just my personal view: Several years ago, we moved away from XSL/T 1.0 <br>
to XSL/T 2.0, as it provided so much more functionality and allowed us <br>
to simplify our tasks. We are currently using the open source Saxon <br>
&quot;Home Edition&quot; as the processor. It is limited in its functionali=
ty, <br>
however, while the limitations do exist, they do not prevent anyone from <b=
r>
taking advantage of the important features of XSLT/2+. So this is more <br>
than fair and the said shall not be regarded as any kind of negative <br>
critics on Michael Kay&#39;s business model. Nevertheless, to my knowledge,=
 <br>
there is no open source Java implementation available that fully <br>
implements XSL/T 2.0 and later versions.<br>
<br>
On the other hand, one has to admit that XML and the related <br>
technologies are no longer everyone&#39;s darling. XML and the related <br>
technologies are nowadays regarded as verbose, cumbersome and no longer <br=
>
as modern or state-of-the-art. The next generation of developers <br>
probably might see these as dinosaurs like my generation saw the <br>
mainframes and COBOL. They are more and more replaced by other <br>
technologies (which are IMHO in no way better). For example, in a <br>
recently project, I could not convince my younger colleagues to use <br>
XSL/T for a specific task as we did in previous projects =E2=80=93 a much <=
br>
simpler, but also much less powerful approach was chosen.<br>
<br>
That said, I believe there is surely a community that would appreciate <br>
your work, but that community will likely shrink over time (cannot say <br>
how fast, though).<br>
<br>
Hope that helps,<br>
<br>
Klaus<br>
<br>
<br>
</blockquote></div>

--000000000000a2e15e05d73244bf--