Coder, Artist, Blogger (https://fungiverse.wordpress.com/, https://philpapers.org/archive/BINAKR.pdf, https://pinocchioverse.org/), former admin of https://diagonlemmy.social/, Programmer of MyceliumWebServer
- 2 Posts
- 3 Comments
blue_berry@lemmy.worldOPto Technology@lemmy.world•SemanticWebBrowser - A browser for the semantic web with a controlled natural language as the primary interfaceEnglish2·2 days agoI don’t know. Basically, if you already know what you want, maybe you only want to type down a couple of statements (maybe even from a template or a tutorial that you found online), modify some stuff and then hit enter. And maybe this modifying of language could be the “browsing” part of the browser.
If you look at it like this it would also be immediate and precise. You would only need to add very good code completion tools, e.g. when you click on a noun, you see all the attributes it has in your ontology. Much like in a IDE. There you also “browse” the space of all potential programs with the interface of language with code completion for keywords and defined concepts, which act like links in traditional browsers.
In contrast, the semantic web is like a open, global code base, where everybody can contribute to. And traditional browser could not successfully implement a language interface because the code base had no defined semantic, this would be possible for the semantic web. And using LLMs, it could be propagated into other web paradigms.
blue_berry@lemmy.worldOPto Technology@lemmy.world•SemanticWebBrowser - A browser for the semantic web with a controlled natural language as the primary interfaceEnglish3·3 days agothere are already text-based browsers like qutebrowser
hypercard
Awesome! Thanks for the references, didn’t know there were already some applications in this direction
I’s blurring the line in-between. It’s trying to set the interaction with the web on a lower level that is closer to the data. It’s like you are live-coding the website you want to use for a specific use-case. But then just call the high-level API-endpoints right away. Basically making the dev-tools and the dev-console of browsers the main way to interact with the web (which assumes a web that is build in a similar fashion).
Yeah, that’s true :(