#saranixI give them credit for "The rules defined below take the essence from the ES6 specification and describe what that means in practical terms." though
#aaronpki'm not super familiar with this, what are the downsides?
#saranixone of the hardest/most annoying things about the jose specs has always been "refer to other spec" littered throughout
#saranixjust that all it does is signatures, and I'm fairly certain the spec text is longer than the entire AP spec which obviously does a lot more than just signatures. IOW convoluted.
#aaronpkI mean the AP spec also refers out to other specs a lot... like activitystreams core plus activitystreams vocab
#aaronpkand it also doesn't link out to specs where it should, like http signatures :P
#saranixyeah, I suppose it helps that w3c specs look like actual documents and ietf rfcs look like they were transcribed by Samual B. Morse
#aaronpkanyway i'm more curious about whether that cleartext jws seems like an easier approach than LDS
#aaronpkit seems like it has a clear definition of the canonicalization method, although i'm not sure how hard that is to actually implement
#nightpool[m]harder then full rdf canonicalization?
#aaronpksounds like javascript (ES6) is the canonical JSON, so it's already built in to that platform
#saranixhah, well, both are off the meter for me... they've crossed the threshold of I can't be arsed to bother with it... tough to get a relative reading on how much I can't be arsed :-P