For what we know right now, we have come up with the namespace for Liftwing's REST APIs that plan to publish under "inferences".

The reasoning behind this is that not all models provided through the API portal are guaranteed to be ML-based, so we've removed that. Discussing the namespace "model" came up and is also not accurate as there might me non-model things that make predictions such as algorithms. But both models and algorithms align under inferences. One anecdote to reference is Google's Cloud Inference API.

The one example that we have and could restructure is /link-recommendations to put under the inference namespace as follows:
/inferences/suggestions/links or /inferences/suggestions/hyperlinks. This would be suitable for the upcoming image suggestions and content translation suggestions that would fit within this resource.

Addressing the upcoming Wikibase REST API addition to the API Platform, API resources will live under the "entities" namespace.

A distinct ontology has not been standardized or addressed at this time, but there is still value in iteratively releasing more clear interfaces than what is currently being provided through the action API. As an "entity" current exists as a first class object and we want to provide consistency with what is currently understood as the Wikidata data model, designating its' own namespace will be the approach.

Next steps are soliciting feedback from the Wikidata team to see if any use cases or scenarios break this paradigm.

Next steps are soliciting feedback from the Wikidata team to see if any use cases or scenarios break this paradigm.

Confirmed, no immediate objections from Wikidata via @WMDE-leszek

A first draft of potential namespaces with some example resources:

api.wikimedia.org/
user

• /{id}
  • /preferences
  • /notifications

media

• /articles
  • /{title}
    • /history
    • /summary
• /images
  • /{title}

stats

• /metrics
  • /page-views
  • /unique-devices
• /trends
  • /most-viewed

inferences

• /models

entities

• /{id}

MediaWiki Core REST API endpoints under /core

If API gateway is intended to be useful for things that are not mediawiki, than not having 'mediawiki' (or wiki, or something?) itself in the namespace is going to be confusing.

E.g. having api.wm.org/core (as a namespace) at the same level as something like api.wm.org/service/thing (that has nothing to do with mediawiki) is confusing. api.wm.org/mediawiki_core? api.wm.org/mediawiki/core ?