Thanks for giving the document a review. For some background on applications of BBS.
There are other work items that I am aware of that bind the "claims structure" very tightly to a specific serialization. Namely: https://www.w3.org/TR/vc-di-bbs/ I worked on early versions of this approach, and the application preprocessing that is required to safely convert application/ld+json to application/n-quads, and then to binary messages that can be used with BBS interfaces is substantial. The early designs for BBS in JOSE and COSE tried to address this directly, by separating algorithms that take binary inputs... claims in a serialization that can be expressed in binary. The goal was to reduce, as much as possible the "application processing overhead". Of course for JSON, CBOR, we have to consider unicode, and CWT and JWT claims in registries, etc... It is therefore nice to have at least 1 place, where the algorithm and interfaces are defined without assuming serialization preferences. OS On Sun, Mar 3, 2024 at 2:06 PM Watson Ladd <watsonbl...@gmail.com> wrote: > Dear Joseans, > > I've read the recently revised complex of drafts, and have some > questions about how we envision profiling working. It seems like the > documents defer a lot of the capabilities to the algorithms document, > while imposing some convention on what the claims representation along > the lines of "the names of the claims are strings suitable for JSON > object keys and have an order, and the claim values can only be > selectively revealed". This matters for both developing more > algorithms and for profilng: it may be that we end up with a profile > having to pick an algorithm, and that new algorithms with new > capabilities end up needing special treatment at the level of say > SPICE. > > Secondly I'm curious where things like binding to upper level > protocols or enclaves are supposed to fit in here. > > Sincerely, > Watson Ladd > > -- > Astra mortemque praestare gradatim > > _______________________________________________ > jose mailing list > jose@ietf.org > https://www.ietf.org/mailman/listinfo/jose > -- ORIE STEELE Chief Technology Officer www.transmute.industries <https://transmute.industries>
_______________________________________________ jose mailing list jose@ietf.org https://www.ietf.org/mailman/listinfo/jose
