-
Notifications
You must be signed in to change notification settings - Fork 30
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
RFC: Creating a set of standard libraries #408
Comments
Merged
Current work: |
NIDM-Results json API (WIP): https://github.com/cmaumet/nidmresults/blob/json_export_import/json_ex.json |
NIDM Swagger specs : https://github.com/smpadhy/nidm-swagger-specs |
you can use this link directly: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create a set of libraries for developers to use. Abstract away details of the model through a clean API.
Develop a common library for common languages:
We would want the api of these tools to support both generic prov objects (entities, activities, agents) and specific objects (e.g., Projects, Datasets, Results, Workflows). The focus in early development should be on the specific objects to make it more useful to the developer.
Also develop a set of RESTful services for NIDM. The backend would be via python or node. Use swagger to design the API around the neuroimaging models.
Example top-level API:
These top level APIs should support use-cases.
Concurrent with the development of the libraries we would like to use them in user facing applications. These could be viewers, search engines, and workflow tools.
The text was updated successfully, but these errors were encountered: