Just realized that #HTML is extensible and #Markdown isn't.

HTML's #XML-like syntax allows for arbitrary non-standard tags that can be made sense of later, in the parser / scraper / renderer. Or animated with #JavaScript custom elements API. Note that I only mention XML syntax, not its semantics, with all the domains, schemes, namespaces, and imports of ontologies or whatever. I just talk random user-specific tags. That's more than enough for reliable ad-hoc extensibility if the syntax is uniform. And HTML syntax is uniform.

While Markdown syntax is not. It's arbitrary (and it doesn't consider the conventions that came before it: https://aartaka.me/email-formatting.html, but I digress) and thus extensions have to come up with random syntaxes for their custom entities. Which wont look good across Markdown renderers supporting the new syntax and the ones that don't. Especially given that new syntaxes (for whatever reason) always are quite ugly.

HTML will just treat new tags' contents as new blocks (legacy) or phrases (more modern), which is much more reliable than seeing a symbol soup in the rendered Markdown.

Just realized that #HTML is extensible and #Markdown isn't.

HTML's #XML-like syntax allows for arbitrary non-standard tags that can be made sense of later, in the parser / scraper / renderer. Or animated with #JavaScript custom elements API. Note that I only mention XML syntax, not its semantics, with all the domains, schemes, namespaces, and imports of ontologies or whatever. I just talk random user-specific tags. That's more than enough for reliable ad-hoc extensibility if the syntax is uniform. And HTML syntax is uniform.

While Markdown syntax is not. It's arbitrary (and it doesn't consider the conventions that came before it: https://aartaka.me/email-formatting.html, but I digress) and thus extensions have to come up with random syntaxes for their custom entities. Which wont look good across Markdown renderers supporting the new syntax and the ones that don't. Especially given that new syntaxes (for whatever reason) always are quite ugly.

HTML will just treat new tags' contents as new blocks (legacy) or phrases (more modern), which is much more reliable than seeing a symbol soup in the rendered Markdown.

Announcing Jabboratory, a partner collective of @joinjabber
Jabboratory aims to be for the people who already have an XMPP account and want to help improve XMPP and the Jabber network.

We use the same CoC as JoinJabber and all the same governance documents. All of them being by Vojkruco https://codeberg.org/Vojkruco/Cooperative_Development_Guidelines and we are hosted under the Vojkruco umbrella.

Some of the things we do are:
- specifications (called XCSPs in Jabboratory),
- developer help/documentation and implementation collaboration
- improve XMPP/Jabber network socially (safer spaces, blocklists, outreach, organizing events, pushing for a better non-tech culture, etc.)
or anything else that includes improving XMPP and Jabber network as a whole.

We aim for diversity of ideas, include people directly in all aspects of decision making (protocol, implementations, social, etc.) and build a space where people feel safe to talk, ask for help, bring up any kind of ideas and work with others to implement said ideas. By the community for the community with inclusive decision making to serve the people affected.

you are welcome to join our lounge room here -> https://invite.joinjabber.org/#lounge@chat.jabboratory.org%3Fjoin
It is strictly non-tech because we aim for inclusivity, but we do of course have other channels some of them being tech related🙂

We already have some implementations, servers, and XMPP collectives involved (including JoinJabber) and we are all building a better XMPP and Jabber network together 🙂

#xmpp #jabber #xml #SecureMessaging #decentralization #privacy #security #federated #jabboratory

Announcing Jabboratory, a partner collective of @joinjabber
Jabboratory aims to be for the people who already have an XMPP account and want to help improve XMPP and the Jabber network.

We use the same CoC as JoinJabber and all the same governance documents. All of them being by Vojkruco https://codeberg.org/Vojkruco/Cooperative_Development_Guidelines and we are hosted under the Vojkruco umbrella.

Some of the things we do are:
- specifications (called XCSPs in Jabboratory),
- developer help/documentation and implementation collaboration
- improve XMPP/Jabber network socially (safer spaces, blocklists, outreach, organizing events, pushing for a better non-tech culture, etc.)
or anything else that includes improving XMPP and Jabber network as a whole.

We aim for diversity of ideas, include people directly in all aspects of decision making (protocol, implementations, social, etc.) and build a space where people feel safe to talk, ask for help, bring up any kind of ideas and work with others to implement said ideas. By the community for the community with inclusive decision making to serve the people affected.

you are welcome to join our lounge room here -> https://invite.joinjabber.org/#lounge@chat.jabboratory.org%3Fjoin
It is strictly non-tech because we aim for inclusivity, but we do of course have other channels some of them being tech related🙂

We already have some implementations, servers, and XMPP collectives involved (including JoinJabber) and we are all building a better XMPP and Jabber network together 🙂

#xmpp #jabber #xml #SecureMessaging #decentralization #privacy #security #federated #jabboratory

ActivityPub would have been better if it used XML instead of JSON.

/duck

#lang_en #ActivityPub #thoughts #XML

ActivityPub would have been better if it used XML instead of JSON.

/duck

#lang_en #ActivityPub #thoughts #XML

What You Hack Is What You Mean: My #TEI talk at #39C3 will elaborate on how to turn literature, research, and even hacker lore into machine-readable, remixable, and sustainable data by using the guidelines of the Text Encoding Initiative. https://events.ccc.de/congress/2025/hub/de/event/detail/what-you-hack-is-what-you-mean-35-years-of-wiring-sense-into-text #DigitalHumanities #XML

#XML people!

How do we communicate the idea that declarative markup is a good idea? Declarative markup is where you identify what is there, not what it does.

For an internal memo, for an insurance letter to a client, how much matters? Well, the insurance company has to be able to search the letters for specific information for 10, 20, 40, 100 years. What word processor did you use 40 years ago? Wordstar? Magic Wand? Ventura?

#markupMonday #declarativeMarkup

What You Hack Is What You Mean: My #TEI talk at #39C3 will elaborate on how to turn literature, research, and even hacker lore into machine-readable, remixable, and sustainable data by using the guidelines of the Text Encoding Initiative. https://events.ccc.de/congress/2025/hub/de/event/detail/what-you-hack-is-what-you-mean-35-years-of-wiring-sense-into-text #DigitalHumanities #XML

Playing with XML+XSLT=SVG because I just hate circos.

#bioinformatics #svg #xml #xslt

Playing with XML+XSLT=SVG because I just hate circos.

#bioinformatics #svg #xml #xslt

Slow Horses screen grab, gotta love it.

#XML #SlowHorses

But as I've already mentioned in other threads, the #GeminiProtocol approach IMO throws away the baby with the bathwater. Many of the web formats and technologies are actually extremely useful even for the “web of documents”: the problem isn't with #HTML, #CSS, #XML, #XSLT, #SVG or even #JavaScript, the problem is that browsers have been catering exclusively to the “web of apps” instead of the “web of documents”. We *can* keep that tech *and* the “web of documents”.

18/

Slow Horses screen grab, gotta love it.

#XML #SlowHorses

When I think about the amount of resources #Mozilla is throwing behind the integration of #genAI #LLM integration nobody wants to then complain they don't have the resources to maintain and improve #XML & #XSLT or bring back #RSS support makes me seriously angry.

Despite rumours, #XML, #invisibleXML ( #iXML) #XSLT, #XQuery all very much alive. They solve real problems and meet people’s needs.

native XSLT in the browser might go away. So applications like https://wendellpiez.github.io/PellucidLiterature/Amsel/amsel.scholia.xmll might stop working (made by Wendell Piez) which is sad but won’t affect large corporations and their revenue.

There is still no standard way to mark up a poem in HTML. No business case for it. But you can do it in XML with the #TEI.

#markupMonday

Despite rumours, #XML, #invisibleXML ( #iXML) #XSLT, #XQuery all very much alive. They solve real problems and meet people’s needs.

native XSLT in the browser might go away. So applications like https://wendellpiez.github.io/PellucidLiterature/Amsel/amsel.scholia.xmll might stop working (made by Wendell Piez) which is sad but won’t affect large corporations and their revenue.

There is still no standard way to mark up a poem in HTML. No business case for it. But you can do it in XML with the #TEI.

#markupMonday

i thought i would scare away any browser people 😄 😄 :-)

#halloween #xml #Halloween2025 #pumpkin #JackOLantern