Riko Eksteen

This whole thing concerns me a lot. I agree that identity is an important issue and should be looked at/talked about, but I don't buy the use cases so far....

This is a good catch, we need to fix this, and 2.0 will be a good place to do this, as it may require breaking changes to the `AppIntent` interface.

I personally like this suggestion @ggeorgievx - I think it is the "best" way to solve the problem, and the most flexible for the future. An AppIntent represents the relationship...

@pauldyson given that we are changing `ViewContact` to `ViewProfile`, should this also become `CreateOrUpdateProfile` which can be used in conjunction with a contact, or other context types?

Isn't this already catered for by the current API? My recollection is hazy but I thought this is why we allow retrieving multiple channel objects and calling "join" on each......

I don't have a problem with this requirement, I think you've illustrated the use case well with the accompanying picture. Some observations: - Ideally I don't want to get to...

Riko Eksteen / Adaptive

@pgn-vole can't you just broadcast `null`?

So what would this look like? `{ "type": "fdc3.nullContext" }` or `{ "type": "fdc3.empty" }` or something like that? If so, I think we should raise a PR for this...

@ggeorgievx the intention was always that full AppD data isn't made available via the FDC3 API, only the pieces required for interoperability. That is why the `AppMetadata` interface, for example,...