To approach learning the Hypermedia protocol, we can break the learning down into different areas:

Signed Data Schema

Signed Data

At the heart of the Hypermedia protocol is the immutable data that is signed by authors and then distributed over Aside from files/attachments, every utilizes IPLD DAG-CBOR format to produce structured IPFS blocks identified by CID. Here we introduce you to the and all of the data it can produce. Then you can reference the which builds on this knowledge to offer many different RPCs for exchanging the signed data and the interpreted results. Resources Data Blob Definitions All Definitions

How to Receive and Distribute the Data

There are two APIs you can use to interact with data in the Hypermedia network.

RPC

The Hypermedia Protocol relies on several RPC interfaces that may be used interchangeably depending on your use case. Important: the Hypermedia RPC protocols are highly unstable right now. Eventually we will stabilize these under a unified schema system. For now we are using a messy mix of gRPC and JSON REST APIs. These RPCs are not yet documented, as they are very prone to change.

Validating the Data

Regardless of how you get access to Hypermedia data, you might want to validate it to ensure the integrity. A full node will always validate it, while a light node can validate as much as it wants to.

Some data in the system is self-validating- when the signer matches the address of the Entity. But you will often need to find Capabilities that supports the integrity of the content.

There are many important mechanisms for data validation: format compliance, signature validation, and capability checking.