Allow apps to update their metadata that is returned in instanceMetadata

Enhancement Request

Use Case

FDC3 allows a user to open multiple instances of the same application. If you have an application that displays a stock price chart then you could have an instance that displays prices for Apple, Google and Meta. If you raise an intent and want to handle that intent in one of those applications there is currently no way of telling these 3 instances apart and they will all appear the same in the app resolver UI.

The closest that we currently have is the name and title field in the AppMetadata object. This object can be returned by the getAppMetadata function where it should obviously return data for the queried app but when returned from the findIntents or findIntentsByContext functions it would be possible to modify this object on a per instance basis. It would also be possible to modify the result from getAppMetadata to return instance specific details if an instanceId was included in the AppIdentifier - but I do no think that this would be a good idea.

There is also no defined way that an application is able to update it's title so that if a user navigates from Apple to Google within the app the Desktop Agent is able to correctly display the updated title the next time that the app resolver ui is displayed.

Questions:

• should we add a getInstanceMetadata function that would return an InstanceMetadata object? (this object may not be required, we could probably just use the AppMetadata object).
• should we define a way that applications are able to inform the desktop agent what their title is? It would currently be possible to generate a title for new instance when it is opened based on the context that is sent. For example the name of a contact or the id of a stock ticker but there is no standardized way of updating this title. It is obviously possible to do this but with no standardised way of doing it apps from different sources will not be able to do it in Desktop Agents that they do not know about.

I thought it was worth discussing this before I implement a home brew way of handling this in our own agent.