For revision visibility updates and other revision info retrieval it would be great to provide a `/page/revision/{revision}` entry point. A `GET` with a `no-cache` header set can be used to refresh revision information from the MW API (normally done through the RESTBaseUpdateJobs extension).
Additionally, for consistency, `/page/revision/` should list revisions.
Later, we could consider exposing individual revision properties at `/page/revision/{revision}/someprop`.
**Note**: we discussed the API structure in a meeting and concluded that we need to restructure it in order to allow for easier branching and future functionality additions. Henceforth, the API structure will be:
- `/page/` - lists the props
- `/page/title/` - lists all of the titles
- `/page/title/{title}` - get metadata about a specific page
- `/page/html/{title}{/revision}` - get HTML for title (and/or revision)
- `/page/data-parsoid/{title}{/revision}` - get data-parsoid for title (and/or revision)
- `/page/revision/` - list all of the revisions
- `/page/revision/{revision}` - get attributes for a revision