Open keighrim opened 2 years ago
I added https://github.com/clamsproject/consumer-evaluation repository, based on assumption that evaluation code will be consumers of MMIF. However, often ML evaluation pipeline takes a collection of documents instead of a single document, but the way other consumers we have currently were developed has been to handle a single MMIF input.
That said, my questions:
We could start with limiting consumers to one MMIF file at the time, like the producers. It is possible that there are use cases for collection-level consumers (and maybe collection-level producers as well), the question there is whether it is better to add collection consumers to the code here or run a batch like GBH does.
Regarding "interface" of the consumers;
The first consumer (prototype) was mmif-visualizer
and it was developed not only as a standalone web app, but also as a "display application" integrated to the galaxy workflow engine.
The /display
route in the mmif-viz
was originally designed for such integration to galaxy
(but during recent updates, the route has been re-purposed, and no longer support galaxy integration)
However, given
I'd like to go back to the idea of using HTTP as the common interface, and want bring a common route (that any HTTP clients can call, including galaxy engine) defined in the interface.
(related: cataloguing consumer apps https://github.com/clamsproject/clams-apps/issues/22)