jdev - 2025-11-11

👍

> No presence at all, no need ❤️ ↺

edhelas. What is your opinion of this? It seems, to me, that both, Mastodon and GoToSocial are disinterested in standards neither RSS, either by not allowing titles, or setting misfit "type" directives, or inventing new tags (i.e. <Rss> instead of <rss>). https://social.firesidefedi.live/@firesidefedi/feed.rss

I advocate for Libervia, Movim, Friendica, or Pleroma. Just utilize platforms that respect standards, so that people would develop correctly, faster, and without confusions.

Schimon, how would you even implement Atom Syndication incorrectly

It's a very simple format (for XML-based one), you could write Atom feeds by hand

alexkurisu. Apparently, some fail at it, and I suppose that it is deliberately so. WordPress includes the directive "CDATA" of element "content:encoded" of namespace "http://purl.org/rss/1.0/modules/content/", even though it does not belong to The Atom Syndication Format (RFC 4287); and According to the specification, content of type="html" has to be with "escaped" characters. ```xml <title type="html"><![CDATA[Priority Continuum Onyx Unboxing and Assembly (Photos)]]></title> ``` Source: https://singpolyma.net/feed/atom/ Interestingly, the specification allows to enclose XHTML, as done with Movim. Yet, that is how (X)HTML is represented in an Atom document of WordPress. ✏

> alexkurisu. Apparently, some fail at it, and I suppose that it is deliberately so. > WordPress includes the directive "CDATA" of element "content:encoded" of namespace "http://purl.org/rss/1.0/modules/content/", even though it does not belong to The Atom Syndication Format (RFC 4287); and > According to the specification, content of type="html" has to be with "escaped" characters. > ```xml > <title type="html"><![CDATA[Priority Continuum Onyx Unboxing and Assembly (Photos)]]></title> > ``` > Source: https://singpolyma.net/feed/atom/ > Interestingly, the specification allows to enclose XHTML, as done with Movim. > Yet, that is how (X)HTML is represented in an Atom document of WordPress. Additionally, "atom:category" is improperly implemented. ``` <category scheme="https://singpolyma.net" term="Bicycles" /> ``` Attribute "term" should be lower-case, for URL (URI, IRI), and atribute "label" should be "human readable", and "scheme" should be https://singpolyma.net/category/ so that it be possible to conclude this URL https://singpolyma.net/category/bicycles/ ↺

I deem that these are designed malfunctions, because they do not want people to realize that it is possible to have an internet which is purely based on XML (or JSON), and they want to keep HTML and its malformities afloat.

If JMAP is anything to go by, HTTP and JSON is unfortunately a major pair in the future.

agh. The principle is a structured internet, be it with JSON or XML, not a conglomeration of designed inefficiencies (CSS3) and insecurities (ECMAScript) that were introduced with HTML5. Of course, I advocate more for XML. ✏

We need simpler XML )

wendellpiez (w3ctag/obsoletion#10) > > A much better solution than abandoning XSLT would be to invest in XML's rejuvenation, maybe starting with something like https://dvcs.w3.org/hg/microxml/raw-file/tip/spec/microxml.html (or its premise) - XML, the good parts. > > A clean and testable subset of XML, stripped of the SGML features that have caused such headaches and lingering distrust. > > This could simultaneously open a new development platform on the web while leveraging -- and giving new life to -- the many important and successful XML backends that provide content and metadata for today's web, largely unnoticed. > https://github.com/w3ctag/obsoletion/issues/10#issuecomment-3480189944

SXML maybe?

What is SXML?

S-expressions syntax for XML

S-exps are known to be a lot easier to parse

alexkurisu. Is SXML compatible with XPath Query?

> We need simpler XML ) Or just better XML libraries, and documentation.

> agh. > The principle is a structured internet, be it with JSON or XML, not a conglomeration of designed inefficiencies (CSS3) and insecurities (ECMAScript) that were introduced with HTML5. Agreed, tho, JMAP does come off as NIN. > Of course, I advocate more for XML. Same.

> > We need simpler XML ) > > Or just better XML libraries, and documentation. agh. I agree. Better software to handle XML is what we need. It was even predicted, that XSLT would not be handled manually, but by software which would automate their creation. This prediction is not realized yet, as there are continuous attempts to try to suppress XSLT and XML. ↺

I have recently published a couple of ECMAScript modules to easily handle XML files with JS. https://openuserjs.org/discuss/XPath_equivalents_to_querySelector ✏

There a number of Ada libraries, some are updated. I have never tried them tho.