We want to generalize TranslateRanker in order to be able to reuse code for other assist features such as Contextual search. Moving the code to its own component will allow other features to call Ranker
After deliberation, we decided to go with a component name more general than just 'ranker', since parts of the ranker (model loader, model inference) may be of general use for other machine_intelligence applications. I belive 'machine_intelligence' would be a suitable name.
Relevant documentation:
go/chromerankergo/translateranker
Comment 1 by hamelphi@chromium.org
, Jun 9 2017