💾 Archived View for rawtext.club › ~sloum › geminilist › 006421.gmi captured on 2024-02-05 at 11:00:02. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Luke Emmet luke at marmaladefoo.com
Fri Apr 23 09:22:47 BST 2021
- - - - - - - - - - - - - - - - - - -
On 23-Apr-2021 01:00, Chris McGee wrote:
I've written up a first draft of an RFC for using RDF within gemini
resources to add parsable metadata and semantics.
gemini://lonelysilo.ca/rfc/gemini-semantics.gmi
<http://lonelysilo.ca/rfc/gemini-semantics.gmi>
I think it would be really cool if the feedback came in the form of a
semantic comment resource from your own gemini capsule using an existing
RDF schema (eg. https://schema.org/Comment <https://schema.org/Comment>
). Feedback is welcome in any form.
Hello Chris
It was interesting to see your RFC for embedded RDF semantics in gemtext. I like to see new proposals of how people are adapting to Gemini to see what is possible and what can become naturalised within its orbit.
Personally I don't have much of a horse in the semantic web race so take these comments with that in mind. However my impression is that it is not the success its originators hoped for, perhaps due to various reasons, including the effort and inherent ambiguities of classification, issues of trust and assurance of data encoding, lack of tool support for normal people to use etc. But maybe there is an active body of users who find there is a definite benefit?
I don't object to finding additional interpretations of content on top of gemtext (after all that is what the gemini subscription adjacent spec captures, very successfully). However my main concern is that the semantics of the links are not what they normally are in gemini. For example the URL links are schema references, rather than browsable content for users. So the normal processes of reading a hypertext gemini document and following a link to another gemini document don't apply and so you have to approach such an encoded document with the expectation that many of the links may not be normal links. This is somewhat of a cognitive overhead.
Gemtext at the moment is primarily technology for human clients, so I think any conventional usage has to work firstly for humans in mind, then perhaps also for other clients.
My feeling would be perhaps a separate media type would be better to serve over the gemini protocol. Or even use one that already exists such as RDF/XML for those that want to experiment in this area. You could have such a file with the metadata easily linked from a gemini page as a "metadata" link.
Also there were some discussions on the list a few months ago about metadata embedding in gemtext - I can't find the link right now but you should be able to find it in the email archives.
regards
- Luke