💾 Archived View for gemi.dev › gemini-mailing-list › 000951.gmi captured on 2024-03-21 at 18:13:33. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-12-28)
-=-=-=-=-=-=-
Hello all, Im considering gemini interoperability with regards to the felinks browser (given is should hopefully be added to it this year): => https://github.com/rkd77/elinks/issues/121 (https://github.com/rkd77/elinks/issues/121) Im hoping to prioritise using its (rough around the edges) bookmarking facility to access XBEL - the XML Exchange Language. => http://pyxml.sourceforge.net/topics/xbel/docs/html/xbel.html (http://pyxml.sourceforge.net/topics/xbel/docs/html/xbel.html) The justification for this is that I hope to connect it with other information assets :
Hi Jonathan, On 29 Jun 2021, Jonathan McHugh wrote: > However, are there any people in the Gemini community currently: > * Absorbing a lot of XML data in order to generate .gmi content? > * Grapping .gmi content and extracting it into XML. Amfora [1] uses XBEL to store bookmarks but that's where its usage of XML ends as far as I know. Not sure whether this is what you're looking for though. [1] https://github.com/makeworld-the-better-one/amfora > I would assert that migrating data from HTML centric bookmarking to Gemini centric bookmarking would be a win. Using gemtext to store bookmarks in amfora was one of the proposals but XBEL seemed like a better fit for structured data [2]. [2] https://github.com/makeworld-the-better-one/amfora/issues/68 Best regards, Sotiris
Hi Sotiris, # Evaluating usability for XML Im at the exploratory stage, so your citation provided good validation. A Guix user, I havent (yet) had direct access to Amfora. Packaging in Go is now easier, so I can use it. Once this thread goes cold I will contact the XBEL mailing list to update them re Gemini usecases via xml-sig@python.org => https://mail.python.org/mailman/listinfo/xml-sig xml-sig -- Python XML Special Interest Group FWIW, I do agree with those emphasising an inhouse Gemini solution (especially as I enjoy parsing). I similarly could rely on eLinks own approach to bookmarking => https://github.com/rkd77/elinks/blob/master/doc/bookmarks.txt [eLinks] The Ultimate Bookmarks Guide However, I wanted to approach it in a way to fit a broader body of users and usecases. Besides, I feel that XML's design style provides an interesting counterpoint to that of .gmi files. # In body references FYI, I recently made some enquiries on the ML regarding in body URI references => https://lists.orbitalfox.eu/archives/gemini/2021/thread.html#6684 In Body URI references I may explore citation areas for .gmi content - solving the aforementioned problem through providing the classic Gemini links and also references, with a footer citation block containing further meta data. Kind regards, Jonathan June 29, 2021 7:12 PM, "Sotiris Papatheodorou" <sotiris@papatheodorou.xyz> wrote: > Hi Jonathan, > > On 29 Jun 2021, Jonathan McHugh wrote: > >> However, are there any people in the Gemini community currently: >> * Absorbing a lot of XML data in order to generate .gmi content? >> * Grapping .gmi content and extracting it into XML. > > Amfora [1] uses XBEL to store bookmarks but that's where its usage of XML ends as far as I know. > Not sure whether this is what you're looking for though. > > [1] https://github.com/makeworld-the-better-one/amfora > >> I would assert that migrating data from HTML centric bookmarking to > Gemini centric bookmarking >> would be a win. > > Using gemtext to store bookmarks in amfora was one of the proposals but XBEL seemed like a better > fit for structured data [2]. > > [2] https://github.com/makeworld-the-better-one/amfora/issues/68 > > Best regards, > Sotiris
---