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

Document usage and supported queries #5

Open
mchaloupka opened this issue Nov 21, 2014 · 2 comments
Open

Document usage and supported queries #5

mchaloupka opened this issue Nov 21, 2014 · 2 comments
Assignees
Projects
Milestone

Comments

@mchaloupka
Copy link
Owner

No description provided.

@mchaloupka mchaloupka self-assigned this Nov 21, 2014
@mchaloupka mchaloupka added this to the Version 0.1 milestone Nov 21, 2014
@mchaloupka mchaloupka removed this from the Version 0.0.1-beta milestone Feb 6, 2015
@mchaloupka mchaloupka added this to the Version 1.0 milestone Jan 27, 2016
@arenas-guerrero-julian
Copy link

Hi @mchaloupka!

I want to use EVI for materialization, is this option available? is there any documentation on this?

Best,
Julián

@mchaloupka
Copy link
Owner Author

Hi,
EVI is a solution for query translation. A sample server is shown in the repository: https://github.com/mchaloupka/EVI-SampleServer When you have a running server, you can materialize the whole database using a construct query

CONSTRUCT { ?s ?p ?o }
WHERE  { ?s ?p ?o }

You can change the WHERE bit in case you want to materialize just subset of your database.

However, if you are interested just in materialization of the whole database you can take a look on the library that is used for r2rml under the hood: https://github.com/r2rml4net/r2rml4net I wonder whether that library will be a better fit for your use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
EVI
  
Future
Development

No branches or pull requests

2 participants