You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inspired partly by Carsten's work on the terminology, I noted this text:
There are many potential formats for payloads; for example, JSON [RFC8259], XML [XML], and CBOR [RFC7049]. Best practices for their use are out of scope for this document.
Applications should register distinct media types for each format they define;
So, "formats" is simultaneously used for the generic syntax (like ASN.1+DER), and for the distinct instantiation with the application-defined schema. I think that the first might instead be reworded as:
There are a few options that might be used in defining the format for payloads; for example, JSON ...
The text was updated successfully, but these errors were encountered:
Inspired partly by Carsten's work on the terminology, I noted this text:
So, "formats" is simultaneously used for the generic syntax (like ASN.1+DER), and for the distinct instantiation with the application-defined schema. I think that the first might instead be reworded as:
The text was updated successfully, but these errors were encountered: