#LegalXML is a #nonprofitOrganization developing in the frame of the #OASIS consortium open standards for legal documents, such as electronic court filing, court documents, legal citations, and transcripts, and related applications. The building block for Legal XML standards is eXtensible #MarkupLanguage ("XML"). LegalDocML and LegalRuleML are affiliated committees and standard proposals of the LegalXML committee.

Oh joy, yet another markup language that promises to revolutionize the world but will probably just elevate your blood pressure instead. 🤦‍♂️ It's like they threw a bunch of tech buzzwords in a blender and hit "puree." 🍹
https://github.com/Mcmartelle/deml #markuplanguage #techbuzzwords #innovation #frustration #humor #HackerNews #ngated

A #Fediverse tech idea I've been considering for a while.

Hashtags can sometimes be annoying, right? Their primary application is finding posts related to a certain topic, including following one. Therefore, if I look for "horses", I want to find everything horse-related.

The following hashtags should therefore lead to the same set of posts:
- #horse
- #horses
- #equines
- #equine
- #horsetodon

Right? But that's not a reality. Some people tag with one of them, with multiple, or with none at all.

Similarly, #Döner, #Doener and perhaps even #Doner should lead to the same set of posts, right? And what about British-American-splits like how #Localization is #Localisation, and perhaps even #l10n as well? And #LGBT, #LGBTQ, #LBGTQ+, #LGBT+, #LGBTQIA and so on and so on also really should be one hashtag.

So what to do?

I propose:
We should introduce a second symbol for something like "fuzzy hashtags". Not the '#' symbol, but another; perhaps '&' or '~'.

That way I could tag my post '~horse', and it could appear on all hashtag feeds concerning the different spellings of horses! Or I could search for such a fuzzy hashtag.

The different variants could be crowdsourced, or overridden by instance mods. You could also opt-out of that system - your posts showing up in fuzzy searches, most likely.

This would also fix languages like German, where you have many inflected forms: #Männer #Mann #Mannes #Manns #Männern #Männers and so on should all lead to the same result.

Behold what I have to do to sign off on this post:
#MarkupLanguages #MarkupLanguage #Markup

I'm interested in experimenting with Typst. There's a sample document that I would like to convert to Typst: title, author's name, table of contents, numbered sections, paragraphs and lists are most of the elements.

Is there a template that I should use, similar to the LaTeX article class? I've reviewd Typst templates on GitHub, but I haven't found one suitable for such a basic document.

My plan is to use someone else's typographic design so that I can concentrate on the content, leaving formatting decisions to the designers. As an author who happens to be blind, I find it convenient when someone else takes care of presentational details.

Support for HTML output is available as a "preview" currently, but it is likely to improve in later releases. My intention is to produce both HTML and PDF from the same source. If Typst continues to mature rapidly, I'll probably write research papers in it also.
#Typst #MarkupLanguage