Updated for 2.2 Conformance

[robmoffat]

No description provided.

[robmoffat]

@kriswest anything else to add to this? Perhaps something around the channel change listener?

[kriswest]

@kriswest anything else to add to this? Perhaps something around the channel change listener?

I can confidently say yes theres more to add - but I'm not focused on it right now. This is secondary to getting the scope for 2.2 agreed. The maintainers can deal with confirmance after whats going in is settled. Hence, I'll keep focused on FDC3 for the web and other proposals out there for the time being.

Definitely, needs addEventLisatener checks. We need to decide on other proposals like matching private channel event listeners to that (I think it would be a good idea to get it done at the same time!). I think you might also check for a case that covers the receiving context on join/addContextListener (as we discussed earlier today) and make sure it covers cases with overlapping context listeners (two of same type or a type + null). The behaviour of the API is well-defined on that and as dsicussed it might be easy to get that wrong with FDC3 for the web

[kriswest]

superseded by #1425 which incorporates the new connection test, but also removes 1.2 and 2.0 labels and goes with just labelling new tests introduced in that version (so only 2.2 labels).