Personally I don't really care about naming so renaming a service seems like a lot of unnecessary work, but there's a saying in russian which translates to something like "A ship will sail like it's called" and who am I to argue with the wisdom of proverbs.

Jokes aside I think that this renaming idea could be an opportunity for all of us to reflect on what MCS is, where is it going and what are the potential use-cases it would serve. When we have a clear view on that we'd probably come up with a good name, because I really don't want us to rename it once again in a year.

Since we have https://en.wikipedia.org/api/rest_v1/page/html/San_Francisco I wondered if this could be named https://en.wikipedia.org/api/rest_v1/page/json/San_Francisco for consistency. Is there any reason this could not be an official JSON representation of the page?

Just noting this is sort of being discussed in the main ticket as well… mostly I was tabling this topic until we finalize the requirements of the API and settle on the the format and delivery at the offsite later this month.

Feel free to discus more if you want, but just want to call out that settling on naming may be premature until then