#markuplanguages — Public Fediverse posts

I should at some point get around to writing the specifications for the alternative web document markup language I've had in my head forever.

HTML isn't bad, but it is definitely constrained by its position as the default markup language for the whole modern web. They need to cater to everyone, from super fancy corporate websites, massive web applications, social media, video sites, encyclopedias, personal homepages, art projects, hobbyists, to professional webdev engineers ...

I really want something purpose-built for a more semantic, personal hypertext web aimed at enthusiasts.

Perhaps it wouldn't be as versatile as HTML, but it doesn't need to fit all use cases of every possible target audience or be viable for businesses.

I am thinking things like …

• Styling should be handled exclusively by the browser based on semantic elements and application-level user preferences (perhaps minimal style recommendations/hints at best).
• Differentiating types of hyperlinks; internal navigation links, important main links, optional context/rabbithole links etc.
• More granular and specific semantic elements, like the uncoupling of times and dates, splitting address/contact elements into specific fields like e-mail and name, quotations with attributions, definitions etc.
• Integration of other semantic data projects such as MusicBrainz, Wikidata or Wikipedia (holy link rot, but we'll see).
• More obligatory metadata like authorship, tags, publishing/modification date etc.
• Integration of non-search engine discoverability features like webrings, directly on a site level
• Easier cross-document reusable elements, i. e. integrating the same header or footer on each site
• Extensive entity-oriented data support with URIs, e. g. in-line fetching of things like names, pronouns or contact data from a central 'person' entity URL to automatically propagate things like name changes through the web.

… and so on.

I could even experiment with the markup tech itself; it doesn't need to be XML after all. It could even be something like a stand-off annotation document allowing the division of content writing from mark-up. Or something with a similarly simple syntax as Markdown, but with semantic instead of styling information.

And then comes the arduous task of implementing a parser. :popcorn: I'm so excited.

#web #webDev #markup #markupLanguages #html #hypertext #www #worldWideWeb #programming #tech

I should at some point get around to writing the specifications for the alternative web document markup language I've had in my head forever.

HTML isn't bad, but it is definitely constrained by its position as the default markup language for the whole modern web. They need to cater to everyone, from super fancy corporate websites, massive web applications, social media, video sites, encyclopedias, personal homepages, art projects, hobbyists, to professional webdev engineers ...

I really want something purpose-built for a more semantic, personal hypertext web aimed at enthusiasts.

Perhaps it wouldn't be as versatile as HTML, but it doesn't need to fit all use cases of every possible target audience or be viable for businesses.

I am thinking things like …

• Styling should be handled exclusively by the browser based on semantic elements and application-level user preferences (perhaps minimal style recommendations/hints at best).
• Differentiating types of hyperlinks; internal navigation links, important main links, optional context/rabbithole links etc.
• More granular and specific semantic elements, like the uncoupling of times and dates, splitting address/contact elements into specific fields like e-mail and name, quotations with attributions, definitions etc.
• Integration of other semantic data projects such as MusicBrainz, Wikidata or Wikipedia (holy link rot, but we'll see).
• More obligatory metadata like authorship, tags, publishing/modification date etc.
• Integration of non-search engine discoverability features like webrings, directly on a site level
• Easier cross-document reusable elements, i. e. integrating the same header or footer on each site
• Extensive entity-oriented data support with URIs, e. g. in-line fetching of things like names, pronouns or contact data from a central 'person' entity URL to automatically propagate things like name changes through the web.

… and so on.

I could even experiment with the markup tech itself; it doesn't need to be XML after all. It could even be something like a stand-off annotation document allowing the division of content writing from mark-up. Or something with a similarly simple syntax as Markdown, but with semantic instead of styling information.

And then comes the arduous task of implementing a parser. :popcorn: I'm so excited.

#web #webDev #markup #markupLanguages #html #hypertext #www #worldWideWeb #programming #tech

A survey of little known text markup and templating languages. It omits mainstream ones such as HTML, TeX, and Markdown.

https://brett.coulstock.id.au/markup-language-zoo.html

#MarkupLanguages #markup #text

A survey of little known text markup and templating languages. It omits mainstream ones such as HTML, TeX, and Markdown.

https://brett.coulstock.id.au/markup-language-zoo.html

#MarkupLanguages #markup #text

Other than org-mode – is there another interactivity and productivity focused plain-text markup language that allows me to magically enrich my marked-up notes with interactive elements, automation and such for the CLI/TUI?

Like, most simple markup languages for text (e. g. Markdown) concern themselves with structuring and styling, which is great. Headlines, bold, italics, lists, all that.

And then of course there are myriads of more complex markup languages (e. g. HTML) that are meant to be parsed by a program to provide functionality to the elements you marked up in the text.

The latter is pretty much what I'm looking for; but HTML specifically isn't it, because it's focused on online hypertext documents, and has surprisingly little interactive elements without scripting, much less in the command line/TUI.

I am basically looking for a markup language that is suitable for all kinds of text files I might write on my computer – to-do lists, idea collections, quick notes, structured articles, fiction stories etc. – that comes with a parser/reader/interpreter of sorts that not only adds visible style and structure, but actually makes my marked up elements as interactive, semantic and 'smart' as possible.

Like selectable datetimes, automatic time zone conversion, parsing URLs, interactive checkboxes, to-do entries that can be ticked off and/or archived, proper tables, metadata like title and author, and so on.

I want a semantic-as-fuck markup language.

I feel like org-mode is nearly alone in that niche. It would be almost perfect but I don't use emacs, I don't like how it controls, and outside of the emacs community, there is therefore little support for org-mode, interpreter application-wise.

[Not looking for advice on how to use org-mode or why I should totally give it a chance with tool neofoobar or whatnot, I'm only looking for alternatives. :P]

#MarkupLanguages #Markup #Linux #AskFedi #OrgMode #CommandLine #Tui #Cli

Other than org-mode – is there another interactivity and productivity focused plain-text markup language that allows me to magically enrich my marked-up notes with interactive elements, automation and such for the CLI/TUI?

Like, most simple markup languages for text (e. g. Markdown) concern themselves with structuring and styling, which is great. Headlines, bold, italics, lists, all that.

And then of course there are myriads of more complex markup languages (e. g. HTML) that are meant to be parsed by a program to provide functionality to the elements you marked up in the text.

The latter is pretty much what I'm looking for; but HTML specifically isn't it, because it's focused on online hypertext documents, and has surprisingly little interactive elements without scripting, much less in the command line/TUI.

I am basically looking for a markup language that is suitable for all kinds of text files I might write on my computer – to-do lists, idea collections, quick notes, structured articles, fiction stories etc. – that comes with a parser/reader/interpreter of sorts that not only adds visible style and structure, but actually makes my marked up elements as interactive, semantic and 'smart' as possible.

Like selectable datetimes, automatic time zone conversion, parsing URLs, interactive checkboxes, to-do entries that can be ticked off and/or archived, proper tables, metadata like title and author, and so on.

I want a semantic-as-fuck markup language.

I feel like org-mode is nearly alone in that niche. It would be almost perfect but I don't use emacs, I don't like how it controls, and outside of the emacs community, there is therefore little support for org-mode, interpreter application-wise.

[Not looking for advice on how to use org-mode or why I should totally give it a chance with tool neofoobar or whatnot, I'm only looking for alternatives. :P]

#MarkupLanguages #Markup #Linux #AskFedi #OrgMode #CommandLine #Tui #Cli

PSA (in case you where not yet aware of it):
#YAML is the #JavaScript of #markuplanguages .

Proof:
"There are ~~5~~ ~~6~~ NINE (or 63*, depending how you count) different ways to write multi-line strings in YAML."
Source: https://stackoverflow.com/questions/3790454/how-do-i-break-a-string-in-yaml-over-multiple-lines/21699210#21699210

I rest my case.

PSA (in case you where not yet aware of it):
#YAML is the #JavaScript of #markuplanguages .

Proof:
"There are ~~5~~ ~~6~~ NINE (or 63*, depending how you count) different ways to write multi-line strings in YAML."
Source: https://stackoverflow.com/questions/3790454/how-do-i-break-a-string-in-yaml-over-multiple-lines/21699210#21699210

I rest my case.

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

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 hashtah.

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 did not have much leisure time recently. But now I found two days to be back at the topic of #markupLanguages.

Wow, I just found a markup language implementation using the Smalltalk programming language (or Pharo language). This is really rare theses times and I did not even recognize its syntax.

https://github.com/pillar-markup/pillar

#Microdown

The space of #markupLanguages is so awkward.

There are people sitting down and write a specification for so-called #Markdown.

Then people sit down and see the obvious problem: fragmentation. Everyone writes parsers with different behavior due to underspecification.

So other people write a spec: http://vfmd.github.io/vfmd-spec/specification/#procedure-for-identifying-html-tags

They spend weeks writing a spec to fix fragmentation problems.

And in the end you cannot add id attributes to anchors. What the heck?

They just reinvent a worse wheel.

The space of #markupLanguages is so awkward.

There are people sitting down and write a specification for so-called #Markdown.

Then people sit down and see the obvious problem: fragmentation. Everyone writes parsers with different behavior due to underspecification.

So other people write a spec: http://vfmd.github.io/vfmd-spec/specification/#procedure-for-identifying-html-tags

They spend weeks writing a spec to fix fragmentation problems.

And in the end you cannot add id attributes to anchors. What the heck?

They just reinvent a worse wheel.

Well, “Episode 21: Keynote — John McCarthy” actually has a recording and he gives that quote at timestamp 1:13:15:
http://www.oopsla.org/oopsla2007/index56d8.html
http://www.oopsla.org/podcasts/Keynote_JohnMcCarthy.mp3

“When W3C decided not to use #LISP format but to imitate #SGML for that [it] showed a certain capacity to make mistakes” *laughter* “which they probably hadn't lost”

Conclusion: the first part is similar, but the second part of the original quote is unfamiliar.

Isn't the WWW a wonderful to be able to research this? #markupLanguages

After only 4 hours of sleep last night and in an attempt to not sleep at my desk, I was looking at trying out @joplinapp for my notes (till I can understand how to set up Emacs on multiple devices efficiently) because I wanted to start writing notes on my Music learning.

During a cursory investigation, I found it has an extension for ABC Notation (https://abcnotation.com/) and fell down that interesting rabbit hole.

#music #joplin #abcNotation #markupLanguages #Emacs

After only 4 hours of sleep last night and in an attempt to not sleep at my desk, I was looking at trying out @joplinapp for my notes (till I can understand how to set up Emacs on multiple devices efficiently) because I wanted to start writing notes on my Music learning.

During a cursory investigation, I found it has an extension for ABC Notation (https://abcnotation.com/) and fell down that interesting rabbit hole.

#music #joplin #abcNotation #markupLanguages #Emacs

Kotaku: Ahead Of The Game: Where Does Games Media Go From Here? https://kotaku.com/harold-goldberg-e3-new-york-video-game-awards-1850976428 #gaming #tech #kotaku #videogamecontroversies #technologyinternet #markuplanguages #htmlelement #gamesmedia #bodytext #document #sports #other #go