Kris West

> I don't think that we can predict all the differnet ways people might want to open a new app. What about some way for the Desktop agent to provide...

Do you mean any type of context to describe the option/option chosen or do you mean any type of context to go to the app once opened (which is of...

@robmoffat at present the *only* way to implement some control for the user as to where something spawns is by adding something custom to an intent resolver - it is...

@julianna-ciq I don't think that the hostManifests pattern is something that we should emulate as it represents a failure to standardize. It does at least allow vendor specific properties to...

Hi @Roaders, prior to FDC3 2.0 there was simply a `manifest` element in appD records that was used to start an application. However, `manifest` was vendor-specific and you could only...

P.S. You are also correct that there are no generated or maintained TS types for appD records. The closest that we have is the [`AppMetadata`](https://fdc3.finos.org/docs/2.0/api/ref/Metadata#appmetadata) type which extends [`AppIdentifier`](https://fdc3.finos.org/docs/2.0/api/ref/Types#appidentifier) and...

To a certain extent there are differences in handling between agents baked into the concept of the `hostManifests` records - but we can manage that by starting to standardize the...

@Roaders there is a historical relationship between OpenAPI and JSON schema - they are partially compatible in OpenAPI 3.0 (which appD is still specified in), but I think fully compatible...

No, not sure how I did that. I think it might have been automated after I deleted the branch it targeted.

Re-opened and now pointed at main, could do with an update and `npm run build` or a rebase onto the fdc3-for-web-impl branch