atomic-data-docs
atomic-data-docs copied to clipboard
atomicdata-dev
Atomic Data is a specification to make it easier to exchange data.
Consider the following: - User A invites B to append a resource somewhere (e.g. add one comment in a chat) - B gives themselves `write` rights in the resource they...
Being able to create a bunch of resources in one go can be really useful. In tools like Notion, Monday and Airtable we've got things like `templates` that do this....
At this point, [Endpoints](https://docs.atomicdata.dev/endpoints.html) exclusively use Query parameters for communicating something with the Server. This works great for things like Collections, but not for things like Uploading files. For the...
There's a lot of potential use cases for Atomic Data / Atomic Server. However, some of these are at an idea stage, whereas others can be used right now. Perhaps...
Some resources, such as Invites, _should_ be openable by their public URL, but _should not_ be visible in public indexes. If you open the `Invites` collection, you should not see...
Representing financial data has some interesting problems. In javascript, 0.3+0.6 = 0.899999999999. If you're building a webshop, and forget that this problem exists, you might make a painful mistake when...
- User has an Agent + server hosted on `sarah.pod.com` - User wants to use an app on `calendarapp.com`. This app only needs access to calendar data, for example. It...
Currently, in [HTTP auth](https://docs.atomicdata.dev/authentication.html#http-headers), we use the current timestamp and the server has a hard-coded max age for signed headers. This gives no control to the client regarding how long...
The `is-a` Property in Atomic Data is of the `resourceArray` URL. This means that any Resource can be an instance of mutiple `Class`es. However, at this moment, there is not...
Metadata
Owner
Metadata
Atomic Data is a specification to make it easier to exchange data.