Potentially change the value for the "query" key into a string rather than a list

[nicholsn]

Maybe there is a good reason for storing the query as a list rather than a string. If not, I propose it be stored as a string so it can be executed directly w/o preprocessing.

[vsoch]

I don't understand - with the current standard it is stored as a list... see here!

https://github.com/incf-nidash/nidm-query/blob/master/results/b73b423e-0660-42a1-a7d3-48e300f44872.json#L7

You mean there is good reason to store as a string rather than a list?

[vsoch]

The benefit of a list is that it ensures readability when you look at the structure from within python, or just as a file. If we were to scrunch it into a string with newline characters, that would not be possible. I think there is always going to be some pre-processing given that the query is in a json file period, and the vision of nidm-api is that we can serve it somewhere and the query is executed from a URL anyway.

[vsoch]

@nicholsn don't forget about the nidmviewer sparql query! I am hoping to finalize the integration of the viewer into NeuroVault, and that is the last missing component. Then we can pretty much take over the world:

[nicholsn]

Do you have a way of formatting queries? I was hoping to preserve the formatting for readability, but can see where that could be a mess with new line chars. It would be nice if there was a way to pretty print sparql.. might be possible though rdflib