Roaders

Some thoughts after our discussion during #1591 There was some concern raised that this would increase the complexity of the standard and require more efforts by the desktop agent implementors....

After reading back through this and after discussions on this topic during OSFF London yesterday I think that I can propose 2 different solutions to this problem (I've tried to...

as an enhancement to the above we could also pass the appId that we're opening into the `getPositions` function so that the `DA` coould return only positions that work for...

Thanks Kris It seems like a good idea to provide more guidance on how a desktop agent should handle the app directory record. Ideally we would not have different behavior...

Thanks for the as always detailed reply @kriswest . Yes, the `hostManifests` records allow differnet vendor implementations to behave differently but some guidance on what to do if multiple or...

The reason for `RequestMessage` is to support Discriminated unions: ```ts public onMessage(message: RequestMessage): void{ switch(message.type){ case: "raiseIntentRequest": return this.handleRaiseIntentRequest(message); // here message is typed as RaiseIntentRequestMessage rather than RequestMessage case...

Notes from FDC3 for Web Browsers Discussion group 17th October 2024 #1391 It would be better if didn't rely on the interface name to build the union types. If we...

I realise that this is probably going to be an issue as anyone relying on this type being defined will now get a breaking change as it might not be...

Great! pr raised.

I don't like 2 or 3. I think it would be normal to have many places in an app that will call `getAgent()` - that's certainly how we intend to...