Atomic Data Extended

Atomic Data is a modular specification, which means that you can choose to implement parts of it. All parts of Extended are optional to implement. The Core of the specification (described in the previous chapter) is required for all of the Extended spec to work, but not the other way around.

However, many of the parts of Extended do depend on eachother.

• Commits communicate state changes. These Commits are signed using cryptographic keys, which ensures that every change can be audited. Commits are also used to construct a history of versions.
• Agents are Users that enable authentication. They are Resources with their own Public and Private keys, which they use to identify themselves.
• Collections: querying, filtering, sorting and pagination.
• Paths: traverse graphs.
• Hierarchies used for authorization and keeping data organized. Similar to folder structures on file-systems.
• Invites: create new users and provide them with rights.
• WebSockets: real-time updates.
• Endpoints: provide machine-readable descriptions of web services.
• Files: upload, download and metadata for files.