Skip to content

Commit 5a3ab2b

Browse files
committed
move mdbook
1 parent 6f027f5 commit 5a3ab2b

File tree

7 files changed

+1
-1
lines changed

7 files changed

+1
-1
lines changed
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

rdf.md renamed to src/rdf.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,14 @@ Because of that, Atomic Data is also highly compatible with RDF - **all Atomic D
88
Atomic Data can be thought of as a **more constrained, type safe version of RDF**.
99
However, it does differ in some fundamental ways.
1010

11+
- Atomic only allows those who control a resource's `subject` URI endpoint to edit the data. This means that you can't add triples about something that you don't control.
1112
- Atomic has no seperate `datatype` field, but it requires that `Properties` (the resources that are shown when you folllow a `predicate` value) specify a datatype
1213
- Atomic has no seperate `language` field, but it does support language strings as a Datatype in Properties.
1314
- Atomic has a native Event (state changes) model ([Atomic Mutations](/ATOMIC-MUTATIONS.md)), which enables communication of state changes
1415
- Atomic has a native Schema model ([Atomic Schema](/ATOMIC-SCHEMA.md)), which helps developers to know what data types they can expect (string, integer, link, array)
1516
- Atomic does not support `graph` fields in statments.
1617
- Atomic does not support `blank nodes`.
1718
- Atomic does not support having multiple statements with the same `<subject> <predicate>`, every combination should be unique.
18-
- Atomic only allows those who control a resource's `subject` URI endpoint to edit the data.
1919

2020
## Why these changes?
2121

File renamed without changes.

0 commit comments

Comments
 (0)