[PaulHoule]

I'd add also that the SPARQL database paradigm runs into trouble because it doesn't have a completely clear model of where a "document" or a "record" begins and ends. If I want to build an everyday boring bizapp I need to be able to delete a "customerrecord" and that's not simple as nuking

   :ThatCustomer ?p ?o .

but there could be RDF lists and other hierarchical stuff that I think is part of a customer record, but other related things (say an order record) that I don't think are part of the customer record.

Document databases like arangodb give a more clear model for updating and transactions as do SQL databases with rows. I guess I could write some framework to help but it just seems very dangerous to build an OLTP application on top of a SPARQL database without one... And some specification of what exactly a "record" is would be necessary for such a framework, does LinkML answer that?

[saxomoose]

Interesting point. terminusdb works as a graph of documents and I believe it addresses the issue you are discussing.

LinkML on the other hand is a modelling language and it does not concern itself by how things are queried when the models are implemented.