On 12/23/2013 05:37 PM, Luke Howard wrote: >> We're considering dropping support for the use of JOSE in the >> Persona implementations that we're going to do for the Web Payments >> work. We are probably going to support both in the beginning, but >> see if folks will want to migrate to SM in the long run for the Web >> Payments use cases. > > Forking the Persona specification and code because base64 is > putatively harder to debug seems a high price to pay -- just my 2c.
If the base64 issue was the only issue, I'd agree with you. However, the review that was done outlined a number of other issues[1] that IMHO, when combined with the goals of Persona, make JOSE a questionable fit. JOSE was picked at the time because there really wasn't a viable alternative. Now that there may be one, things might change. Persona doesn't seem to need any of the more complex functionality brought by JOSE (resulting in unnecessarily complex and hard to debug messages). Secure Messaging could achieve the same level of functionality, more simply, for Web developers. -- manu [1] http://manu.sporny.org/2013/sm-vs-jose/ -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: The Worlds First Web Payments Workshop http://www.w3.org/2013/10/payments/ _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
