#xslt — Public Fediverse posts

I've opened a whole new can of worms: #XSLT. Specifically XSLT 2.0. It seems all #FOSS XSLT transformers are either proprietary or written in #Java :( Any tips for a Python or JS-based approach?

I've opened a whole new can of worms: #XSLT. Specifically XSLT 2.0. It seems all #FOSS XSLT transformers are either proprietary or written in #Java :( Any tips for a Python or JS-based approach?

I've opened a whole new can of worms: #XSLT. Specifically XSLT 2.0. It seems all #FOSS XSLT transformers are either proprietary or written in #Java :( Any tips for a Python or JS-based approach?

I've opened a whole new can of worms: #XSLT. Specifically XSLT 2.0. It seems all #FOSS XSLT transformers are either proprietary or written in #Java :( Any tips for a Python or JS-based approach?

I've opened a whole new can of worms: #XSLT. Specifically XSLT 2.0. It seems all #FOSS XSLT transformers are either proprietary or written in #Java :( Any tips for a Python or JS-based approach?

Martin Honnen sur Twitter "The XSLT 3 development branch of Apache Xalan has made great progress, I can now run lots of examples written for Saxon unchanged with Xalan, therefore I have created an entry page for my CheerpJ powered, Xalan XSLT 3.0 fiddle that shows some samples" #xslt https://martin-honnen.github.io/cheerpj3-xalan-xslt3/index-examples.html

Martin Honnen sur Twitter "The XSLT 3 development branch of Apache Xalan has made great progress, I can now run lots of examples written for Saxon unchanged with Xalan, therefore I have created an entry page for my CheerpJ powered, Xalan XSLT 3.0 fiddle that shows some samples" #xslt https://martin-honnen.github.io/cheerpj3-xalan-xslt3/index-examples.html

Martin Honnen sur Twitter "The XSLT 3 development branch of Apache Xalan has made great progress, I can now run lots of examples written for Saxon unchanged with Xalan, therefore I have created an entry page for my CheerpJ powered, Xalan XSLT 3.0 fiddle that shows some samples" #xslt https://martin-honnen.github.io/cheerpj3-xalan-xslt3/index-examples.html

Martin Honnen sur Twitter "The XSLT 3 development branch of Apache Xalan has made great progress, I can now run lots of examples written for Saxon unchanged with Xalan, therefore I have created an entry page for my CheerpJ powered, Xalan XSLT 3.0 fiddle that shows some samples" #xslt https://martin-honnen.github.io/cheerpj3-xalan-xslt3/index-examples.html

Martin Honnen sur Twitter "The XSLT 3 development branch of Apache Xalan has made great progress, I can now run lots of examples written for Saxon unchanged with Xalan, therefore I have created an entry page for my CheerpJ powered, Xalan XSLT 3.0 fiddle that shows some samples" #xslt https://martin-honnen.github.io/cheerpj3-xalan-xslt3/index-examples.html

Giving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox

Giving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox

Giving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox

Giving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox

Giving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox

Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.

Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.

Please say no to this #enshittification.

Yours,
@mro

P.S.: I pledge a monthly Euro to such a browser.

Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.

Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.

Please say no to this #enshittification.

Yours,
@mro

P.S.: I pledge a monthly Euro to such a browser.

Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.

Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.

Please say no to this #enshittification.

Yours,
@mro

P.S.: I pledge a monthly Euro to such a browser.

Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.

Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.

Please say no to this #enshittification.

Yours,
@mro

P.S.: I pledge a monthly Euro to such a browser.

Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.

Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.

Please say no to this #enshittification.

Yours,
@mro

P.S.: I pledge a monthly Euro to such a browser.

Hi @drscriptt @jon,
#Firefox #XSLT being on death row. Look into it's console e.g. browsing https://seppo.mro.name/aseppototry/. I mentioned that, didn't I? #Curfew May 1st AFAIK.
#Safari isn't an option here on #FreeBSD / #Linux and prbly will do likewise anyway.

Hi @drscriptt @jon,
#Firefox #XSLT being on death row. Look into it's console e.g. browsing https://seppo.mro.name/aseppototry/. I mentioned that, didn't I? #Curfew May 1st AFAIK.
#Safari isn't an option here on #FreeBSD / #Linux and prbly will do likewise anyway.

Hi @drscriptt @jon,
#Firefox #XSLT being on death row. Look into it's console e.g. browsing https://seppo.mro.name/aseppototry/. I mentioned that, didn't I? #Curfew May 1st AFAIK.
#Safari isn't an option here on #FreeBSD / #Linux and prbly will do likewise anyway.

Hi @drscriptt @jon,
#Firefox #XSLT being on death row. Look into it's console e.g. browsing https://seppo.mro.name/aseppototry/. I mentioned that, didn't I? #Curfew May 1st AFAIK.
#Safari isn't an option here on #FreeBSD / #Linux and prbly will do likewise anyway.

Hi @drscriptt @jon,
#Firefox #XSLT being on death row. Look into it's console e.g. browsing https://seppo.mro.name/aseppototry/. I mentioned that, didn't I? #Curfew May 1st AFAIK.
#Safari isn't an option here on #FreeBSD / #Linux and prbly will do likewise anyway.

Hi @jon,
#JS being more powerful is the case against it.

The other is the irresponsibility to just drop features at will. #XSLT was a #w3c standard. If that's not a thing to rely on and publish documents for long-term availability, then there isn't such a thing. Fits with TLS and short lived certs.

That's all toward card houses. And I hate any of it.

It's not about XSLT, it's about #reliability.

Hi @jon,
#JS being more powerful is the case against it.

The other is the irresponsibility to just drop features at will. #XSLT was a #w3c standard. If that's not a thing to rely on and publish documents for long-term availability, then there isn't such a thing. Fits with TLS and short lived certs.

That's all toward card houses. And I hate any of it.

It's not about XSLT, it's about #reliability.

Hi @jon,
#JS being more powerful is the case against it.

The other is the irresponsibility to just drop features at will. #XSLT was a #w3c standard. If that's not a thing to rely on and publish documents for long-term availability, then there isn't such a thing. Fits with TLS and short lived certs.

That's all toward card houses. And I hate any of it.

It's not about XSLT, it's about #reliability.

Hi @jon,
#JS being more powerful is the case against it.

The other is the irresponsibility to just drop features at will. #XSLT was a #w3c standard. If that's not a thing to rely on and publish documents for long-term availability, then there isn't such a thing. Fits with TLS and short lived certs.

That's all toward card houses. And I hate any of it.

It's not about XSLT, it's about #reliability.

Hi @jon,
#JS being more powerful is the case against it.

The other is the irresponsibility to just drop features at will. #XSLT was a #w3c standard. If that's not a thing to rely on and publish documents for long-term availability, then there isn't such a thing. Fits with TLS and short lived certs.

That's all toward card houses. And I hate any of it.

It's not about XSLT, it's about #reliability.

I don’t know who knows this apart from the experts, but #XSLT is a beautiful #functional language. I like it because it is purely so.

I don’t know who knows this apart from the experts, but #XSLT is a beautiful #functional language. I like it because it is purely so.

I don’t know who knows this apart from the experts, but #XSLT is a beautiful #functional language. I like it because it is purely so.

I don’t know who knows this apart from the experts, but #XSLT is a beautiful #functional language. I like it because it is purely so.

I don’t know who knows this apart from the experts, but #XSLT is a beautiful #functional language. I like it because it is purely so.

Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.

#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primär für lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur Verfügung.

Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.

Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.

#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primär für lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur Verfügung.

Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.

Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.

#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primär für lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur Verfügung.

Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.

Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.

#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primär für lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur Verfügung.

Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.

Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.

#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primär für lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur Verfügung.

Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.

#Browser #Enshittification: no more #XSLT (= human-friendly #XML).
https://github.com/mozilla/standards-positions/issues/1287
#Google continues their strangling of the #open #web - most influential was maybe killing the #Blogosphere and giving rise to the #corporate #platform #web by sunsetting their #Reader.

Now another #monopoly is used to get rid of human-friendly xml documents. A thing many of people involved in the decision likely can't imagine and many people familiar with the corporate platform web won't miss. They're fine with a browser that can render animated #advertising and are not interested in documents which their attention span doesn't allow to read them anyway.

Exceptionally sad, yet not surprising, is that Google is aided by #Mozilla and #Firefox in doing so.

The demolition timeline: https://mastodon.social/@Edent/115048990801167629
¹ https://mro.name/b94393r

#Browser #Enshittification: no more #XSLT (= human-friendly #XML).
https://github.com/mozilla/standards-positions/issues/1287
#Google continues their strangling of the #open #web - most influential was maybe killing the #Blogosphere and giving rise to the #corporate #platform #web by sunsetting their #Reader.

Now another #monopoly is used to get rid of human-friendly xml documents. A thing many of people involved in the decision likely can't imagine and many people familiar with the corporate platform web won't miss. They're fine with a browser that can render animated #advertising and are not interested in documents which their attention span doesn't allow to read them anyway.

Exceptionally sad, yet not surprising, is that Google is aided by #Mozilla and #Firefox in doing so.

The demolition timeline: https://mastodon.social/@Edent/115048990801167629
¹ https://mro.name/b94393r

#Browser #Enshittification: no more #XSLT (= human-friendly #XML).
https://github.com/mozilla/standards-positions/issues/1287
#Google continues their strangling of the #open #web - most influential was maybe killing the #Blogosphere and giving rise to the #corporate #platform #web by sunsetting their #Reader.

Now another #monopoly is used to get rid of human-friendly xml documents. A thing many of people involved in the decision likely can't imagine and many people familiar with the corporate platform web won't miss. They're fine with a browser that can render animated #advertising and are not interested in documents which their attention span doesn't allow to read them anyway.

Exceptionally sad, yet not surprising, is that Google is aided by #Mozilla and #Firefox in doing so.

The demolition timeline: https://mastodon.social/@Edent/115048990801167629
¹ https://mro.name/b94393r

#Browser #Enshittification: no more #XSLT (= human-friendly #XML).
https://github.com/mozilla/standards-positions/issues/1287
#Google continues their strangling of the #open #web - most influential was maybe killing the #Blogosphere and giving rise to the #corporate #platform #web by sunsetting their #Reader.

Now another #monopoly is used to get rid of human-friendly xml documents. A thing many of people involved in the decision likely can't imagine and many people familiar with the corporate platform web won't miss. They're fine with a browser that can render animated #advertising and are not interested in documents which their attention span doesn't allow to read them anyway.

Exceptionally sad, yet not surprising, is that Google is aided by #Mozilla and #Firefox in doing so.

The demolition timeline: https://mastodon.social/@Edent/115048990801167629
¹ https://mro.name/b94393r

#Browser #Enshittification: no more #XSLT (= human-friendly #XML).
https://github.com/mozilla/standards-positions/issues/1287
#Google continues their strangling of the #open #web - most influential was maybe killing the #Blogosphere and giving rise to the #corporate #platform #web by sunsetting their #Reader.

Now another #monopoly is used to get rid of human-friendly xml documents. A thing many of people involved in the decision likely can't imagine and many people familiar with the corporate platform web won't miss. They're fine with a browser that can render animated #advertising and are not interested in documents which their attention span doesn't allow to read them anyway.

Exceptionally sad, yet not surprising, is that Google is aided by #Mozilla and #Firefox in doing so.

The demolition timeline: https://mastodon.social/@Edent/115048990801167629
¹ https://mro.name/b94393r

@mro

A sad day indeed. I have had a lotta fun with #XSLT in the past, long ago when working for the larges Print company in the #EU (today due to internet et al, it went bankrupt, broken up).

Most fun was a single (complex, yes) stylesheet that created the #HTML UI form for creation and editing of any #XML + #XMLSchema thrown at it, to allow subsequent update of itself.

@mro

A sad day indeed. I have had a lotta fun with #XSLT in the past, long ago when working for the larges Print company in the #EU (today due to internet et al, it went bankrupt, broken up).

Most fun was a single (complex, yes) stylesheet that created the #HTML UI form for creation and editing of any #XML + #XMLSchema thrown at it, to allow subsequent update of itself.

@mro

A sad day indeed. I have had a lotta fun with #XSLT in the past, long ago when working for the larges Print company in the #EU (today due to internet et al, it went bankrupt, broken up).

Most fun was a single (complex, yes) stylesheet that created the #HTML UI form for creation and editing of any #XML + #XMLSchema thrown at it, to allow subsequent update of itself.

@mro

A sad day indeed. I have had a lotta fun with #XSLT in the past, long ago when working for the larges Print company in the #EU (today due to internet et al, it went bankrupt, broken up).

Most fun was a single (complex, yes) stylesheet that created the #HTML UI form for creation and editing of any #XML + #XMLSchema thrown at it, to allow subsequent update of itself.

@mro

A sad day indeed. I have had a lotta fun with #XSLT in the past, long ago when working for the larges Print company in the #EU (today due to internet et al, it went bankrupt, broken up).

Most fun was a single (complex, yes) stylesheet that created the #HTML UI form for creation and editing of any #XML + #XMLSchema thrown at it, to allow subsequent update of itself.