Loading
fix(028_06): ignore jsonldContext, as the subscription comparison already does
§ 10.5.2.4 MANDATES that jsonldContext be initialized when absent, so a broker that emits it is the compliant one. AssertionUtils' subscription-specific comparison has ignored the member since !269 for exactly that reason, but 028_06 reaches the GENERIC comparison, which carries no such ignore - so it failed against a broker that had just been fixed to comply. Same ignore, same reasoning, at the call site.