At the heart of the Hypermedia protocol is the immutable data that is signed by authors and then distributed over @IPFS
Aside from files/attachments, every @Data Blob utilizes IPLD DAG-CBOR format to produce structured IPFS blocks identified by CID.
Here we introduce you to the @Signed Data Blob and all of the data it can produce. Then you can reference the @Protocol which builds on this knowledge to offer many different RPCs for exchanging the signed data and the interpreted results.
Resources
All mutable data in the Hypermedia ecosystem is either a @Resource or a @ChangeResource
Data Blob Definitions
Each of these @Signed Data Blobs are objects with a "type" field that discriminates against the following types:
@Ref — A "commit" to a Document in a certain location
@Change — Describes an update or creation of Document content
@Comment — A Resource that describes a comment
@Capability — A Resource that gives permission from one account to another
Profile — Provides metadata for the Account
All Definitions
Document
A Document is the primary data structure for knowledge in the Hypermedia ecosystem. Every Document is a , so it is modeled with Refs and Change blobs. The main building block for knowledge in the Hypermedia network is the Document. Each Document is identified by the Site Id + Path Content Metadata
Capability
The Capability is a signed blob used to delegate new permissions to read, write, or author as another identity. It is used to grant signing permissions to other devices or people. Each capability is a . Shape Chaining A capability might be granting permissions to another account, which might require a chain of capabilities.
ChangeResource
This Resource is created by forming a graph of Changes and then using Refs to point to the latest heads of the change graph. Currently, the protocol's only ChangeResource is the  The Change blobs describe the operations to add/remove data from the resource. They depend on other Changes, and you can walk through all changes, applying operations, until you reach the current state of the Resource. Changes are the raw data with version history, and a Ref specifies the actual location. Unlike basic Resources, the ChagneResource allows easy branching, redirecting, and re-publishing. Branching Deleting Redirecting Generations
Ref
A Ref is a  that points to the latest state of a  according to the signer. Version Location Generation Tombstone/Deletes Redirect
Change
A Change is a  that specifies some set of operations against a  Deps Ops
Signed Data Blob
A Signed Data Blob is a  which has the "sig" and "signer" fields
Data Blob
A generic data blob is any IPFS file which is encoded using DAG-CBOR and has a "type" field that references this documentation.
Contact
A Contact is metadata that an Account uses to describe itself or another Account. Each Contact is a  .
Comment
A small unit of content that comes from a single author. Each Comment is a .
Resource
The base mutable entity in the system