atomic-data-docs
atomic-data-docs copied to clipboard
Atomic Data is a specification to make it easier to exchange data.
Current spec as it exists, doesn't distinguish between information resources and concept resources. I.e, as every subject's identifier has to deref to an information resource representation(like json-ad doc), the architecture...
Currently, the get started section is a small part of the overview page. This could be improved by making it a larger page that feels more like a tutorial.
There should be a way to change multiple subjects in one commit to guarantee data integrity. There could either be a new `BatchCommit` class or a new property on `Commit`...
See https://github.com/atomicdata-dev/atomic-data-browser/issues/172 Having a [Class for Errors](https://atomicdata.dev/classes/Error) helps to standardize how we communicate Errors from back-end to front-end. I suppose other usecases will present themselves later.
There currently only is a `resource-array` datatype, which requires using nested resources if there are multiple values. Often I would want to have a property with multiple plain values though....
Define a datatype for specifying a duration. The main question is if millisecond precision is enough, or if sub-millisecond precision is required often enough. I lean towards just specifying it...
Values can often be one of several datatypes (like string or int, class A or class B, ...). There should be a way to model unions (anonymous or tagged). Describing...
A datatype for representing unique sets of values. Similar justification and problems as in #127 .
Define a canonical datatype for UUIDs. String serialization is the common UUID string format. Binary serialization is a bit trickier since there doesn't seem to be an official representation, but...
Having machine readable errors is essential for getting a good user experience while dealing with forms. For example, if some username has been taken, we want to show an error...