-
Notifications
You must be signed in to change notification settings - Fork 110
Closed
Description
I suppose other rdfstore-js users are wondering about this as I am.
I'm working on a project that requires an RDF store in the browser, I chose rdfstore-js as it seemed superior to the other options I checked (and there weren't many). So, above all: Thanks @antoniogarrote for building this! It's great, and, of course, it has its problems and bugs, but the most important problem is: it's abandoned.
- @antoniogarrote - you are working on the 1.1 branch, but I don't see any documentation to help me figure out if I can use that code. Where is it going? Will it eventually replace the abandoned version in the master branch?
- To those currently working on forks and waiting on pull requests (@trueg, @JuniperChicago, @bensinober, @RubenVerborgh, @jandrieu... ) - Is any of you planning to continue working on rdfstore-js in the near future? Could we find some way of collaborating to get this code to work the way we need it? Maybe you want to share what your modifications were about? Maybe we could find a way to combine the forks into one we continue to maintain? It seems to me that the potential for continuing is there - or am I missing something?
- If we have to give up on rdfstore-js: which RDF store would you recommend for use in the browser?
Metadata
Metadata
Assignees
Labels
No labels