Identify open issues
Resolve open issues
Unify and update API documentation
http://opentox.org/dev/apis/api-1.2
Focus on predictive toxicology
REST interfaces for: Compound, Feature, Dataset, Algorithm, Model, Validation, Report, Ontology, Task, Authentication and Authorisation
RDF representation
Extensions for capturing bioassay data
Additional objects: Alert, Data, Index, Investigation, Organisation, Project, Protocol, Search, Session, Template, User.
RDF representation, ISA-Tab (http://isatab.sourceforge.net/format.html)
IDEA: http://enanomapper.github.io/API
NTUA: http://app.jaqpot.org:8080/jaqpot/swagger
IST: https://enm.in-silico.ch/api/dist
Extensions for capturing nanomaterial data
Additional objects: Bundle, Myaccount, Property, Query, Substance, Substanceowner, Pmml, Bibtex
JSON representation
- system/infrastructure limitations (time, memory, database/webserver size limits, ...)
- impossible for RDF (performance of RDF parsers/serializers, markup size)
- even JSON markup can cause problems
- we propose CSV/TSV as data exchange format for datasets
- code separation, maintenance
- performance penalties caused by suboptimal data structures
- performance penalties of webservices (data (de)serialisation)
- complicated server infrastructure
- ad hoc requests for features that deviate from official API
- reliablity/availability of external services
- undocumented API details
- undocumented/silent API/data format changes
- no common strategy for conflict resolution, API or data representation updates
- installation far from straightforward
- management of additional server instances
- duplication of functionality, bloat
- update strategy
- scattered/outdated documentation
- maintenance - too many places to consider (error prone) - ideally autogenerated from code
- ideally combined with tests (availability, API coverage, API compliance)
...
http://opentox.org/dev/apis/api-1.2
http://enanomapper.github.io/API