4 ms·
I’d love to understand your thinking behind the idea that a document standard should rely on a query language and not a file format… Document standards are fil
by orf 3y ago
I’d love to understand your thinking behind the idea that a document standard should rely on a query language and not a file format…
Document standards are file formats…
Or are you saying a document format should just be some DDL statements? What? How is that interoperable? It’s coupled to the database that is storing the data as an implementation detail, which is exactly the problem with using SQLite.
> That alone would be a difficult project
I’m not suggesting using the SQLite file format, I’m suggesting the pretty basic idea that the storage for a general purpose widely used and interoperable document format should be logically decoupled from anything else, and definitely not be tied to the implantation details of a single library or even a single version of that library.
The file format is the most important part. It’s the only part. Nothing else matters because there is nothing else.
It’s not rocket science.
- hot_gril 3y ago> Or are you saying a document format should just be some DDL statements? What? How is that interoperable? Yes. How is it interoperable, because it's quite easy to make DDL for SQLite that also works for many other DBMSes, given that SQLite is kinda the lowest common denominator of those. Maybe not as interoperable as ODF since it's easier to implement an ODF parser/writer than a SQLite clone, but probably more interoperable than some kind of advanced ODF designed for efficient updates. Just because you define a standard doesn't mean there are good portable implementations out there.
- orf 3y ago> Maybe not as interoperable as ODF since it's easier to implement an ODF parser/writer than a SQLite clone Ladies and gentlemen: he’s so close, he’s nearly there, but he just can’t make the final connection!