Skip to content

Product management

Jump to bottom Edit New page
taylorbr edited this page Aug 4, 2013 · 6 revisions

Tatoeba API Roadmap 2013

Date Objective Comments 
Aug, 9th    |  Finalize the API spec       |   
Aug, 26th    |  API on the server          |   The initial server-side implementation of the API.
Sep, 8th     |  Basic search               |   Normal, character-wise search.
Oct, 6th     |  The first release          |   The API should be fully functional according to the specification
Oct, 27th    |  Fuzzy  search              |   Helps to find the conjugated forms of verbs (maybe not only verbs? There are nouns and adjectives, changing their forms in languages like Russian, Finnish and Estonian)
Nov, 17th    |  Regex search               |

Tatoeba API Product Backlog

  • Caching mechanism
  • Pre-fetching/pre-caching mechanism
  • Support for search type ("search type" field in the protocol, corresponding UI elements on the client)
  • Segregate user information from comment information and sentence information. So the API, for example, will allow calls for sentence information excluding user information, or comment information excluding sentence information. This will result in more overall API calls but with fewer packet sizes.
Add a custom footer
Add a custom sidebar
Clone this wiki locally