CBOR is specified in an Internet Standard RFC. RFCs that serve as Internet Standards are generated by the IETF based on an extensive technical review and quality control process. These are meant to last.
Concise Binary Object Representation (CBOR)
The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack. This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format.
How to Read an RFC
Requests for Comments (RFCs) are how we specify many protocols on the Internet. These documents are alternatively treated as holy texts by developers who parse them for hidden meanings, then shunned as irrelevant because they can’t be understood. This often leads to frustration and – more significantly – interoperability and security issues. However, with some insight into how they’re constructed and published, it’s a bit easier to understand what you’re looking at.
rfcs/atproto/001-private-content.md at main · knasher/rfcs
Technical RFCs and design proposals for protocols and systems - knasher/rfcs
DASL: DRISL — Deterministic Representation for Interoperable Structures & Links
DRISL is a serialization format that is deterministic (so that the same data will have the same CID) and that features native support for using CIDs as links. It is based on CBOR, using a narrow profile of CBOR's "Core" featureset called "[[cborc-42]]", specified formally in this IETF document.
Taking AT to the IETF - AT Protocol
We recently posted two drafts to the IETF Data Tracker. This is the first major step towards standardizing parts of AT in an effort to establish long-term governance for the protocol.
RFC - Request for comments
RFC - Request for comments
RFC - Request for comments
RFC - Request for comments
RFC - Request for comments
Introduction · Standard Reader
Build on Standard — an open reading network on the AT Protocol. What the developer docs cover.
Proposal: standard.site.declaration
Proposal: standard.site.declaration Draft for Discussion Abstract AT Protocol provides portable identity, portable content, and portable social graphs. What it currently lacks is a standard mechanism for discovering machine-readable declarations associated with digital content. Today, creators and organisations publish declarations about digital assets through websites, registries, the C2PA provenance framework, and other systems. These declarations may describe provenance, copyright ownership...
DASL — Data-Addressed Structures & Links
A small set of simple, standard primitives to work on content-addressed data.
