At this time we do not want to make changes to oto-lite or oto since e.g. IPlant's charaparser deployment depends on the running oto and oto-lite instances and a change in API may break them.
Once the time has come to update the version's installed at IPlant, and possibly elsewhere, due to a newer algorithm, we also want to make sure to treat the oto-lite/oto API changes.
Also then, remove the alternative web service implementation that was maintained only for IPlant in OTO (edu.arizona.biosemantics.rest.IPlantGlossaryService and edu.arizona.biosemantics.rest.beans.iplant.*)
...we then also want to update oto-lite and oto's APIs to return the desired formats (to be discussed), e.g. https://github.com/biosemantics/oto/issues/14
At this time we do not want to make changes to oto-lite or oto since e.g. IPlant's charaparser deployment depends on the running oto and oto-lite instances and a change in API may break them.
Once the time has come to update the version's installed at IPlant, and possibly elsewhere, due to a newer algorithm, we also want to make sure to treat the oto-lite/oto API changes.