sueden.social ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Eine Community für alle, die sich dem Süden hingezogen fühlen. Wir können alles außer Hochdeutsch.

Serverstatistik:

1,8 Tsd.
aktive Profile

#XML

12 Beiträge10 Beteiligte1 Beitrag heute
HERMES Datenkompetenzzentrum<p>🛠️ Wir suchen Personen mit Kenntnissen in <a href="https://fedihum.org/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> -Technologien, NocoDB oder <a href="https://fedihum.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>python</span></a> die Lust und Spaß daran haben, die Inhalte unserer Lektionen für <span class="h-card" translate="no"><a href="https://hachyderm.io/@thecarpentries" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>thecarpentries</span></a></span> mit uns gemeinsam weiterzuentwickeln. </p><p>ℹ️ <a href="https://hermes-hub.de/lernen/datacarpentrieslektionen/kollaborationsmoeglichkeiten/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hermes-hub.de/lernen/datacarpe</span><span class="invisible">ntrieslektionen/kollaborationsmoeglichkeiten/</span></a></p><p>🌐 Data Visualization for Storytelling and Statistical Inference:<br><a href="https://github.com/carpentries-incubator/hermes_stat_inf_data_vis" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/carpentries-incubat</span><span class="invisible">or/hermes_stat_inf_data_vis</span></a> </p><p>🌐 Data and Metadata in the Humanities: <br><a href="https://github.com/carpentries-incubator/hermes_metadata_lesson" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/carpentries-incubat</span><span class="invisible">or/hermes_metadata_lesson</span></a> </p><p>🌐 Relational Databases with NocoDB in the humanities:<br><a href="https://github.com/carpentries-incubator/RDBMS-with-NocoDB-in-the-humanities" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/carpentries-incubat</span><span class="invisible">or/RDBMS-with-NocoDB-in-the-humanities</span></a> </p><p><a href="https://fedihum.org/tags/DigitalHumanities" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalHumanities</span></a> <a href="https://fedihum.org/tags/oer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>oer</span></a></p>
Miguel Afonso Caetano<p>This article doesn't start very well, specially because the author goes right into a conspirational mode. Maybe most Internet users don't want to deal with XML as a format and Google, being a capitalist for-profit company, wants just to appease those Internet users... </p><p>"Google is managing to achieve what Microsoft couldn't: killing the open web. The efforts of tech giants to gain control of and enclose the commons for extractive purposes have been clear to anyone who has been following the history of the Internet for at least the last decade, and the adopted strategies are varied in technique as they are in success, from Embrace, Extend, Extinguish (EEE) to monopolization and lock-in.</p><p>What I want to talk about in this article is the war Google has been waging on XML for over a decade, why it matters that they've finally encroached themselves enough to get what they want, and what we can do to fight this."</p><p><a href="https://wok.oblomov.eu/tecnologia/google-killing-open-web/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">wok.oblomov.eu/tecnologia/goog</span><span class="invisible">le-killing-open-web/</span></a></p><p><a href="https://tldr.nettime.org/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Google</span></a> <a href="https://tldr.nettime.org/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> <a href="https://tldr.nettime.org/tags/OpenWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenWeb</span></a> <a href="https://tldr.nettime.org/tags/RSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RSS</span></a></p>
Emmanuel Chateau-Dutier<p>Qui se souvient du temps où les éditeurs <a href="https://mamot.fr/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a> faisaient réellement leur travail ? <a href="https://mamot.fr/tags/xml" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xml</span></a> Yuri Rubinsky, SoftQuad, HotMetal etc.<a href="https://kristoff.it/blog/first-html-lsp/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">kristoff.it/blog/first-html-ls</span><span class="invisible">p/</span></a></p>
Norm Tovey-Walsh<p>On the subject of removing XSLT from the browser, <a href="https://blog.saxonica.com/norm/2025/08/20-removing-xslt.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.saxonica.com/norm/2025/08</span><span class="invisible">/20-removing-xslt.html</span></a> <a href="https://toot.wales/tags/xml" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xml</span></a> <a href="https://toot.wales/tags/xslt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xslt</span></a> <a href="https://toot.wales/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>web</span></a></p>
Dr. Dr. Bethan Tovey-Walsh<p>If you like <a href="https://mastodon.online/tags/markup" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>markup</span></a> languages and related technologies, we have a Discord server where you'd be extremely welcome. </p><p>We discuss development of markup technologies, teaching and learning, theoretical stuff, and general tech. We'd love to see you, whether your interest is in <a href="https://mastodon.online/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a>, <a href="https://mastodon.online/tags/DigitalHumanities" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalHumanities</span></a>, <a href="https://mastodon.online/tags/LaTeX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LaTeX</span></a>, <a href="https://mastodon.online/tags/JSON" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JSON</span></a>, <a href="https://mastodon.online/tags/Markdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Markdown</span></a>... We should use our collective experience to improve each of our technologies. </p><p>(I also just love chatting with other markup geeks!)</p><p>If you'd like a server invite, lmk.</p>
Neil Craig<p>Apropos the impending demise of XSLT[1], is anyone already selectively serving an HTML version of their RSS feed(s) rather than the raw XML based on the `accept` request header sent by the client?</p><p>i.e. if the client sends/prefs `application/xml` above/instead of `text/html` then you serve the raw XML, otherwise you serve HTML - or similar/inverted.</p><p>Maybe that's super obvious/common but I've not seen it myself.</p><p><a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</span></a> <a href="https://mastodon.social/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> <a href="https://mastodon.social/tags/RSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RSS</span></a> <a href="https://mastodon.social/tags/RSSFeed" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RSSFeed</span></a></p><p>[1] <a href="https://news.ycombinator.com/item?id=44952185" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.ycombinator.com/item?id=4</span><span class="invisible">4952185</span></a></p>
Stephen<p>If you're interested in experimenting with <a href="https://mastodon.social/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> &amp; <a href="https://mastodon.social/tags/XSLT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XSLT</span></a> to style a website I recommend Evan Widloski's project:<br><a href="https://github.com/Evidlo/xsl-website" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/Evidlo/xsl-website</span><span class="invisible"></span></a><br>(his wildcard template to ignore html tags was super useful).<br>Paco Coursey also has a cool repo:<br><a href="https://github.com/pacocoursey/xslt" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/pacocoursey/xslt</span><span class="invisible"></span></a><br>And the <a href="https://mastodon.social/tags/GrugBrained" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GrugBrained</span></a> <a href="https://mastodon.social/tags/ReadMe" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ReadMe</span></a> is worth the price of admission! Complexity very, very bad.</p>
Stephen<p>I read <span class="h-card" translate="no"><a href="https://sociale.network/@oblomov" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>oblomov</span></a></span>'s piece on the assault on the <a href="https://mastodon.social/tags/OpenWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenWeb</span></a> by <a href="https://mastodon.social/tags/BigTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BigTech</span></a> and, yes, I got riled up just as <span class="h-card" translate="no"><a href="https://aseachange.com/@elena" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>elena</span></a></span> predicted.<br>So I curated some <a href="https://mastodon.social/tags/RSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RSS</span></a> feeds in <a href="https://mastodon.social/tags/Nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Nextcloud</span></a> News to calm myself and looked into replacing my dusty website with a home-built <a href="https://mastodon.social/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> / <a href="https://mastodon.social/tags/XSLT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XSLT</span></a> <a href="https://mastodon.social/tags/indieweb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>indieweb</span></a> <a href="https://mastodon.social/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blog</span></a> now that development for <a href="https://mastodon.social/tags/PicoCMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PicoCMS</span></a> has stopped.<br><a href="https://wok.oblomov.eu/tecnologia/google-killing-open-web/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">wok.oblomov.eu/tecnologia/goog</span><span class="invisible">le-killing-open-web/</span></a></p>
Emmanuel Chateau-Dutier<p>Le prétendu living standard est une arnaque ! Honte au <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>w3c</span></a></span> d’avoir jeté l’éponge sur <a href="https://mamot.fr/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a>&nbsp;! <a href="https://mamot.fr/tags/xslt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xslt</span></a> <a href="https://mamot.fr/tags/xml" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xml</span></a> <br><a href="https://indieweb.social/@epyllia/115057637385589396" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">indieweb.social/@epyllia/11505</span><span class="invisible">7637385589396</span></a></p>
Emmanuel Chateau-Dutier<p><span class="h-card" translate="no"><a href="https://floss.social/@bart" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bart</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.social/@osnews" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>osnews</span></a></span> <a href="https://mamot.fr/tags/XSLT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XSLT</span></a> has become a niche technology (on the web) because the WHATWG has gone out of its way to undermine support for <a href="https://mamot.fr/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> technologies since the mid-2000s—for instance, by replacing XMLHttpRequest with a function that only handles JSON.</p>
Todd Knarr<p><a href="https://mstdn.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Google</span></a> <a href="https://mstdn.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chrome</span></a> <a href="https://mstdn.social/tags/WHATWG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WHATWG</span></a> <a href="https://mstdn.social/tags/XSLT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XSLT</span></a> <a href="https://mstdn.social/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> </p><p><a href="https://github.com/whatwg/html/pull/11563" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/whatwg/html/pull/11</span><span class="invisible">563</span></a></p><p>IMO this PR is a bad idea and should be closed without merging. XML is a thing in the enterprise world, and XSLT is a useful tool for manipulating it in front-end applications. It's pretty clear from reactions that Google is the *only* party that wants to remove XSLT, and that only to make RSS unusable (RSS conveniently bypasses Google's advertising).</p>
iX Magazin<p>iX-Workshop: E-Rechnungspflicht - Anpassung von Faktura- und ERP-Software</p><p>Softwareentwickler lernen Hands-on, welche Formate wie unterstützt, geprüft und umgewandelt werden können oder müssen und wie sie dabei vorgehen.</p><p><a href="https://www.heise.de/news/iX-Workshop-E-Rechnungspflicht-Anpassung-von-Faktura-und-ERP-Software-10516144.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">heise.de/news/iX-Workshop-E-Re</span><span class="invisible">chnungspflicht-Anpassung-von-Faktura-und-ERP-Software-10516144.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon</span></a></p><p><a href="https://social.heise.de/tags/ERechnung" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ERechnung</span></a> <a href="https://social.heise.de/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IT</span></a> <a href="https://social.heise.de/tags/iXWorkshops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iXWorkshops</span></a> <a href="https://social.heise.de/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> <a href="https://social.heise.de/tags/Wirtschaft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wirtschaft</span></a> <a href="https://social.heise.de/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a></p>
Marco Ivaldi<p>See also <span class="h-card" translate="no"><a href="https://bird.makeup/users/qualys" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>qualys</span></a></span> note on stack clash <a href="https://infosec.exchange/tags/exploitation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>exploitation</span></a> </p><p><a href="https://www.openwall.com/lists/oss-security/2025/03/15/1" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">openwall.com/lists/oss-securit</span><span class="invisible">y/2025/03/15/1</span></a></p><p><a href="https://infosec.exchange/tags/DoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DoS</span></a> <a href="https://infosec.exchange/tags/vulnerability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vulnerability</span></a> <a href="https://infosec.exchange/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> <a href="https://infosec.exchange/tags/Recursion" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Recursion</span></a> <a href="https://infosec.exchange/tags/Expat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Expat</span></a></p>
Marco Ivaldi<p>A fascinating story about a <a href="https://infosec.exchange/tags/DoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DoS</span></a> <a href="https://infosec.exchange/tags/vulnerability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vulnerability</span></a> in the Expat <a href="https://infosec.exchange/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> parser </p><p><a href="https://infosec.exchange/tags/Recursion" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Recursion</span></a> kills: The story behind CVE-2024-8176 / <a href="https://infosec.exchange/tags/Expat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Expat</span></a> 2.7.0 released, includes security fixes</p><p><a href="https://blog.hartwork.org/posts/expat-2-7-0-released/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.hartwork.org/posts/expat-</span><span class="invisible">2-7-0-released/</span></a></p>
Fortgeführter Thread

And it's done

wok.oblomov.eu/tecnologia/goog

If you spot any errors (e.g. in my recall of history) do let me know. If you know of additional additional (direct or by proxy) examples of the war of Google on XML, RSS and/or XSLT do let me know.
If you know of more interesting use cases for XSLT, do let me know.

Also, I'll probably add a post-scriptum in the coming hours or days, but I wanted to get this out now.

#Google #openWeb #indieWeb #XML #XSLT #selfHosting #RSS and many others

wokGoogle is killing the open webThe juggernaut is taking advantage of its dominant position to enclose and destroy the commons.

Oh, quelle surprise #whatwg a fermé la discussion sur le ticket concernant la suppression du support de #XSLT. Le roi est nu. Depuis des années, les grands éditeurs de navigateurs se sont évertués à dégrader le support de #XML sur la plateforme du #web. Il n’est plus possible de le cacher. github.com/whatwg/html/issues/

What is the issue with the HTML Standard? XSLT v1.0, which all browsers adhere to, was standardized in 1999. In the meantime, XSLT has evolved to v2.0 and v3.0, adding features, and growing apart f...
GitHubShould we remove XSLT from the web platform? · Issue #11523 · whatwg/htmlVon mfreed7

We don't need more. We need less.

Every week:
🧠 A new framework.
⚙️ A new "layer".
🤖 A new AI wrapper.
🔄 A new YAML format to abstract what used to be a shell script.

And then we wonder:
"Why is our software hard to debug?"
"Why do our builds break randomly?"
"Why is onboarding a 6-month journey through tribal folklore?"

I once said I write bug-free software that can be finished.
People laughed, especially product people.
Not because it's wrong.
But because they’ve forgotten it's possible.

We build complexity on top of confusion:
A + B becomes C.
C + D becomes E.
Now, E is broken, and we would create a new layer, but nobody knows how A or B worked in the first place. For example HTML/JavaScript, we leave it there and just add layers around it.

Take XML.
Everyone says it's ugly.
But you could validate it automatically, generate diagrams, enforce structure.
Now we're parsing YAML with 7 linters and still can't tell if a space is a bug.

Take Gradle.
You can define catalogues, versioning, and settings, but can't update a dependency without reading 3 blogs and sacrificing a goat.
This is called "developer experience" now?

Take Spring Boot.
I wouldn't trust a Spring Boot or any java Framework powered airplane.
Too many CVEs. Too much magic. Too little control.

We don't need "smarter" tools.
We need dumber, boring, reliable defaults.

Start boring.
Start small.
Then only change the 1% that needs to be fast, clever, or shiny.
You'll rarely even reach that point.
Like everyone says, "Y is more performant and faster than X", but no one reached the limit of X. Why should I care? Meanwhile, we use performant AI.

Real engineering is not chasing hype.
It's understanding the system so deeply that you no longer need most of it.

We've replaced curiosity with cargo cults.
We've replaced learning with LLM prompting.

And somehow, we're surprised when AI loses to a 1980s Atari in a chess game.
At least the Atari understood its own memory.

Simplicity = less maintenance = fewer bugs = happier teams.

We need less. Not more.
#devex #simplicity #softwareengineering #nocodependency#stopthehype #bugfree #springboot #gradle #xml #yamlhell #boringisgood #minimalism #AIhype #infrastructure #cleancode #pragmatism #java #NanoNative

Google started a WHATWG discussion for removing XSLT. Google has done their best to remove good tech from standards many times.

Responders raised issue with the motive for this change, as opposed to upgrading from XSLT 1.x to 3.1 which would fix all sorts of issues, etc.

Any posts that brought up Google's history and motives were marked as off-topic, and the thread was eventually locked by WHATWG.

github.com/whatwg/html/issues/

What is the issue with the HTML Standard? XSLT v1.0, which all browsers adhere to, was standardized in 1999. In the meantime, XSLT has evolved to v2.0 and v3.0, adding features, and growing apart f...
GitHubShould we remove XSLT from the web platform? · Issue #11523 · whatwg/htmlVon mfreed7
#WebStandards#OpenWeb#XML