-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
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
Would HDT be considered for a binary format? #3
Comments
Looks great indeed. Thanks. I will definitely have a look. Given the format's properties we should implement it or a similar one. |
I think Joseki took a stab at this: https://github.com/Callidon/joseki/blob/master/graph/treeGraph.go |
Side note: Unfortunately I cannot give a deadline on when it will be done. I might do the JSON-LD implementation before and the support of blank nodes / languague tag on the custom binary format (for full compatibility) |
Not sure if the right place to ask, but was wondering if something similar is already possible with wallix/triplestore: Query big datasets on disk, based on a disk based index? (Having a 12GB .hdt file with a 8GB index that I'd like to work with in Golang if possible :) ). In any case, HDT seems like a great path, as a standardized format for this. |
@samuell HDT is a great path indeed and this should be an option for this triplestore. Unfortunately, I cannot devote time at the moment to work on it. To ease the task, we might cut the work in different pieces. For instance, we could start by only implementing a reader/decoder for this format. I hope to do so in the next coming 3 months. |
@simcap IC, thanks for the status update! |
http://www.rdfhdt.org/
I honestly don't know if HDT would be a benefit or a hindrance. I'm really just passing this along as an FYI to the developers.
The text was updated successfully, but these errors were encountered: