@rq @crafti #SXML

@Li @astrid Yes.

It should have remained an #XML / #SXML schema.

@astrid If four angle brackets were too hard, why not use #SXML? Then you can just use two parens.

@enigmatico #JSON.

I think the problem isn't quite that simple, because most of the issues with #XML are representational.

Consider #SXML-like equivalents for #MathML https://en.wikipedia.org/wiki/MathML#Content_MathML

A Plist is even shorter and simpler a representation than JSON objects.

#SExp #SExpressions

A lot of time and energy for learning to use #sxml and #SXPath! I used the Racket docs to get examples from #OlegKiselyov's talks and from a w3schools tutorial to work. If I knew of a good way to share them I'd try. Seeing more sxpath examples might have saved me some time. I still can't get the low-level node-** stuff back into short-cut sxpath as I imagine I should. Shared the right way...
#Racket #Xpath
- https://docs.racket-lang.org/sxml/sxpath.html
- https://okmij.org/ftp/Scheme/SXML-short-paper.html
- https://www.w3schools.com/xml/xpath_examples.asp

Now is just the matter of converting all my #Skribe documents to #SXML

...

Past me did not make this easy.

When you have your own website, you don't have to worry about being banned for crappy, useless content.

On a /completely unrelated/ note, I wrote about #SXML (using #Guile #Scheme )

http://muto.ca/messing-around-with-sxml.html

For my #Guile #SXML projects I modified the original module for prettier printing (no indentation, but newlines between tags at least).
I also added support for comments in sxml->xml so that ends that.

I can't for the love of god figure out what the #Guile #SXML / #SSAX equivalent is to XML's <!-- comment --> tags, or how to properly define my own, since sxml->xml transforms all "< >" characters to "&lt; &rt;".

I'm going to take a break from that now, though.