💾 Archived View for rawtext.club › ~sloum › geminilist › 006861.gmi captured on 2023-11-14 at 09:02:26. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Why XML/Atom for feeds

Jonathan McHugh indieterminacy at libre.brussels

Wed Jul 7 14:23:20 BST 2021

- - - - - - - - - - - - - - - - - - -

Dear ~m,

Having spent time transposing the Discogs data archive from XML (with 50GB+ files), I canappreciate both the stengths and weaknesses of it as a format.

I can also understand why it got pushed out by the JSON format in the HTTP space (though I toolament that the Ini file format wasnt used more for config style problems). However, I also get why XML canbe useful for the Gemini space. For example, I speculated re the utility of XML Bookmark ExchangeLanguage (XBEL) on this ML for bookmarking (this is available for Amfora and eLinks browsers for example):=

https://lists.orbitalfox.eu/archives/gemini/2021/006818.html

FWIF, I intend to get around to transposing the discogs dataset into Gemini. Id be fascinated re how it could make use of stream links provided within the catalogues (such an undertaking would skew some of the statistical analyses of Gemini content).

====================Jonathan McHughindieterminacy at libre.brussels

July 7, 2021 3:01 PM, gemproj at suckless.anonaddy.com wrote:

Hello geminauts

Yesterday I decided to add a feed to my gemlog and when I checked other logs, most seem to feed XML

or Atom. While I get that it's popular and useful in existing clients, I am wondering why it's the

de facto standard in a protocol that favors a reduced markdown. XML always felt worse than HTML to

me, yet to do anything feed related in geminispace, I still need to XML. Is it just me?

Best

~m