Skip to content
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

Create a single .ttl file for saving experiment plans #40

Open
smpadhy opened this issue Aug 10, 2017 · 1 comment
Open

Create a single .ttl file for saving experiment plans #40

smpadhy opened this issue Aug 10, 2017 · 1 comment

Comments

@smpadhy
Copy link
Collaborator

smpadhy commented Aug 10, 2017

Currently, for each new experiment plan submitted, a new turtle file is created. Each plan is represented as a RDF graph. We decided to serialize all plans to a single file and loads/query the qraph as required.

@smpadhy smpadhy self-assigned this Aug 10, 2017
@smpadhy
Copy link
Collaborator Author

smpadhy commented Aug 31, 2017

Different experiment plans are represented as different named graphs. The way to serialize all named graphs to a single file is to use TRIG format. In Brainverse, we are using rdfstore-js . This does not support TRIG format to load a serialized file to the rdf store. There are also discussion around this in the rdfstore-js repo in the issue: antoniogarrote/rdfstore-js#86. The way around this is to save experiment plans in different turtle filse and load as different named graphs to the store.
Though from the README, it appears to support query against multiple named graphs, but I am getting errors or no results. This also seems to be a known issue reported and resolved (antoniogarrote/rdfstore-js#119) still there is error.
To query against named graphs, is to get a list of registered graph names and query for a specific graph.

@smpadhy smpadhy changed the title [EP] Create a single .ttl file for saving experiment plans Create a single .ttl file for saving experiment plans Jan 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant