Re:Storing knowledge in a single long plain text file
by the_duke on Wednesday May 22, 2024 @09:06AM
(#40440466)
From a quick scan, it sounds like you re-invented a lot of the concepts of semantic data, just with different terminology and a different text format. (RDF, triples, ...)
Re:Storing knowledge in a single long plain text file
by 0x445442 on Wednesday May 22, 2024 @09:41AM
(#40440870)
I wish there was a defacto/canonical site that housed free papers that people could go search before embarking on these types of efforts. Perhaps there is but when I attempt these types of searches I get directed to pay walled ACM type links or Github "Papers We Love" type links.
Re:Storing knowledge in a single long plain text file
by breck on Wednesday May 22, 2024 @09:43AM
(#40440913)
You might enjoy https://pldb.io/, which is a paywall free, open source, public domain, database you can browse completely locally, with information on all of these kinds of prior languages.
:)
Re:Storing knowledge in a single long plain text file
by mynotaccount on Thursday May 23, 2024 @12:31PM
(#40456759)
sci-hub
Re:Storing knowledge in a single long plain text file
by sleno on Thursday May 23, 2024 @02:43PM
(#40458308)
Funny, someone linked me here. I just posted a project that got a bit of traction related to this: papertalk.xyz
Re:Storing knowledge in a single long plain text file
by breck on Wednesday May 22, 2024 @09:41AM
(#40440883)
It would certainly be fair to add RDF/triples/semantic web, to prior work. I spent many years exploring that stuff.
We are aiming at roughly the same problem. Our implementation has solved some important details.
I agree with you. More details will come out over time but I wanted to keep yesterday's paper a single page.
> You mention in the citations that "Hierarchies are painless in our system through nested parsers, parser inheritance, parser mixins, and nested measurements." Nothing else in the article gives any hint as to what those things are or how your system implements them except nested measurements. It's unclear at all what a parser is in your system.
Below is a link to a web IDE we built. You can see parsers (on the left), and concepts (on the right). Nested parsers and parser inheritance are demonstrated. Mixins is not currently in that branch yet. Ignore the "cells" stuff at top (that turned out to be an unneeded division between lines parsers and word parsers).
https://jtree.treenotation.org/designer#url%20https%3A%2F%2F...
> Overall it seems like your ideas would make more sense if you used more widely adopted language to describe it. "Concepts" are records, "measurements" are fields.
Yes, concepts often map to records or rows. Measures to fields or columns. Measurements to the cells in a spreadsheet.
There are reasons for my terminology, that should become clearer over time.