It's worth noting the MCS is a collection of services used by the mobile
team . It includes endpoints such as `feed` (
). Why not put `summaries` in
there too?
On Thu, Jun 22, 2017 at 6:52 AM Sam Smith <samsmith(a)wikimedia.org> wrote:
It's only just occurred to me that I've been
making a serious mistake in
conflating RESTBase and RESTful services, like MCS, in my recent
communications up to and including my initial email.
On Thu, Jun 22, 2017 at 2:43 PM, Marko Obrovac <mobrovac(a)wikimedia.org>
wrote:
While it could be done in REDTBase as well, I
think that this is not a
good long-term solution as it introduces a dependency on the Services team
for something that you ultimately own the output of.
This is an excellent point.
With the above in mind, I think that the ideal solution is creating a new
service for generating page summaries that can be consumed by multiple
platforms. Just as with TextExtracts, page summaries are distinct from MCS.
It's up to the Reading Web team to decide whether they want to implement it
in Node or as a new MediaWiki API module that lives in the Popups extension.
-Sam
--
IRC (Freenode): phuedx
Timezone: BST (UTC+1)