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.

Sign up for GitHub

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

Jump to bottom

Meta: do we use "complicated" federated SPARQL queries or do we use simple queries behind an API that are then combined in something else (e.g. Python) #6

Open
Chris-Evelo opened this issue Aug 19, 2019 · 1 comment
Open

Meta: do we use "complicated" federated SPARQL queries or do we use simple queries behind an API that are then combined in something else (e.g. Python) #6

Chris-Evelo opened this issue Aug 19, 2019 · 1 comment

Comments

@Chris-Evelo
Copy link
Collaborator

No description provided.

@Chris-Evelo Chris-Evelo changed the title Meta: do we use c Meta: do we use "complicated" federated SPARQL queries or do we use simple queries behind an API that are then combined in something else (e.g. Python) Aug 19, 2019
@Chris-Evelo
Copy link
Collaborator Author

We are for now trying both. The problem with real federated queries is not only that they are hard to write (and read) but also that they often time out. Still worthwhile to try whether we can actually perform things like ID mappings between parts of the queries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Chris-Evelo