ahh - thx - so that explains why RFC 6749 OAuth 2.0 is ambiguous on the topic. I suspect that means that GNAP will take a dependency on 8259, Peace ..tom
On Mon, Jul 13, 2020 at 8:34 AM Carsten Bormann <c...@tzi.org> wrote: > On 2020-07-13, at 17:19, Tom Jones <thomasclinganjo...@gmail.com> wrote: > > > > What, exactly is json encoding? > > JSON is defined in RFC 8259. > The term “encoding” is ambiguous here, it could be used for the encoding > of a JSON text (which employs UTF-8) or the representation of an > application data model using the JSON generic data model. > > > It sounds like a python or java method. > > Many languages and platforms support JSON. > > > Afaik json can be encoded in utf 8 16 or 32. > > Early definitions of JSON said so, even though that practically never > happened in interchange. RFC 8259 supports UTF-8 encoding only. > > Grüße, Carsten > >
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
