API endpoint registration in MPASS discovery API

[jussih]

There's a possibility that services integrated to MPASS could have interaction between them, for example a schedule planning service could provide the current user's next classroom time and location to a card on the Velmu desktop.

• Could, or even should MPASS provide a discovery API where the services could register their endpoints that can be used by other MPASS ecosystem services? Or is this something the services must privately do between them?
• If API discovery would be implemented, should MPASS define a set of interfaces the registered API's must implement, in essence providing an API contract? Using the classroom schedule example, MPASS could define an API interface where a service provides some human-readable data in list form. In this example Velmu would autodiscover the API and automatically create a card on the user's desktop which dynamically displays the list of classes for that user. Velmu would have a generic layout for a card which displays data in list mode, and could use any available data sources based on the API contract.