We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
instead of mongodb, i reckon it'd be better for us to use a database more suited for linked data graphs.
my recommendation is levelgraph-jsonld, as it's built on the levelup and levelgraph ecosystems, where the philosophy is "build your own database" based on your needs instead of "batteries included".
there's also more options for linked data graph databases:
The text was updated successfully, but these errors were encountered:
@Bortseb I recommend checking out this presentation that Mikey linked to above https://mcollina.github.io/levelup-talk-cloudconf/
Sorry, something went wrong.
thanks Mikey, that's very interesting! it would certainly appear to make a lot more sense than mongo
We have moved the ValueFlows organization from GitHub to https://lab.allmende.io/valueflows.
This issue has been closed here, and all further discussion on this issue can be done at
https://lab.allmende.io/valueflows/linked-data-creator-api/-/issues/2.
If you have not done so, you are very welcome to register at https://lab.allmende.io and join the ValueFlows organization there.
No branches or pull requests
instead of mongodb, i reckon it'd be better for us to use a database more suited for linked data graphs.
my recommendation is levelgraph-jsonld, as it's built on the levelup and levelgraph ecosystems, where the philosophy is "build your own database" based on your needs instead of "batteries included".
there's also more options for linked data graph databases:
The text was updated successfully, but these errors were encountered: