DjangoLDP-Account: Database-backed Solid-POD provider?
At the moment this package provides authentication for the Resource Server side of Solid-OIDC (#70 (closed) ) (i.e. for the server application to which the client is connecting), and it provides a federated user model (LDPUser) which is decisively not a Solid Pod
I assume that this isn't a short-term objective but worth investigating the possibility of providing a Solid Pod with DjangoLDP-Account or a new package, and what changes would need to be made to DjangoLDP
If we did go down this track, I think it'd be very challenging to efficiently model the kind of "infinite variety of fields" (the Open World Assumption) which a triplestore offers, but incredibly useful for standards compliance in DjangoLDP in general if we did provide this. I did a little investigating into Apache Jena's SQL-backed SDB, but they've discontinued this effort. It would be interesting to find out what they were doing and why they discontinued it
They provide a Triplestore-backed database system which is largely discussed as being fast, but I haven't seen any benchmark comparisons. Being able to separate the datasets into separate files is quite nice. Extending Django with a new Triplestore Database provider is possible, and it wouldn't necessarily mean that users can't use SQL-backed databases as well or instead
If we were successful in this effort it would provide a serious performance improvement over conventional filesystem-backed Pods (https://forum.solidproject.org/t/constructive-criticism-from-an-experienced-developer/3521)