The following 1-page extract from a fairly large specification http://webpki.org/papers/keygen2/jcs-application-sample.pdf hopefully shows why there may be a rationale for YAJSS (Yet Another JSON Signature Scheme) as well.
The @context and @qualifier properties are not related to JCS but serve as "emulation" of XML namespaces and top-level element respectively. It is sort of a hack but if you have something like KeyGen2's 10 potentially revised messages belonging to the same specification (@context) I think you'll end-up doing similar things. The parser implementation automatically instantiates the right object which is how I have to date used XML. Unless somebody finds some really ugly drawback I will leave my 12Y+ intensive relationship with XML-standards behind, and stick to JSON from now on. JSON surely isn't pretty but that's only a problem for me as an overly esthetic engineer; computers probably don't care :-) Anders https://mobilepki.org/jcs <https://mobilepki.org/jcs/home> _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
