diff options
| author | Bryan Newbold <bnewbold@robocracy.org> | 2019-02-14 16:19:26 -0800 |
|---|---|---|
| committer | Bryan Newbold <bnewbold@robocracy.org> | 2019-02-14 16:19:26 -0800 |
| commit | 70b4bc18b13f59c9d42c8e44ef872dfd2e1abef3 (patch) | |
| tree | 1c4706394047bce6a086228e2efe8632d8bc1a23 /guide/src/implementation.md | |
| parent | 56edebe7c2e090c4f25179f03a2d77d78ba59219 (diff) | |
| download | fatcat-70b4bc18b13f59c9d42c8e44ef872dfd2e1abef3.tar.gz fatcat-70b4bc18b13f59c9d42c8e44ef872dfd2e1abef3.zip | |
more guide tweaks; not a full review/rewrite
Diffstat (limited to 'guide/src/implementation.md')
| -rw-r--r-- | guide/src/implementation.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/guide/src/implementation.md b/guide/src/implementation.md index 33a53c21..8d1830b6 100644 --- a/guide/src/implementation.md +++ b/guide/src/implementation.md @@ -15,14 +15,14 @@ A cronjob will create periodic database dumps, both in "full" form (all tables and all edit history, removing only authentication credentials) and "flattened" form (with only the most recent version of each entity). -A goal is to be linked-data/RDF/JSON-LD/semantic-web "compatible", but not -necessarily "first". It should be possible to export the database in a +One design goal is to be linked-data/RDF/JSON-LD/semantic-web "compatible", but +not necessarily "first". It should be possible to export the database in a relatively clean RDF form, and to fetch data in a variety of formats, but -internally fatcat will not be backed by a triple-store, and will not be bound -to a rigid third-party ontology or schema. +internally Fatcat is not backed by a triple-store, and is not tied to any +specific third-party ontology or schema. Microservice daemons should be able to proxy between the primary API and -standard protocols like ResourceSync and OAI-PMH, and third party bots could +standard protocols like ResourceSync and OAI-PMH, and third party bots can ingest or synchronize the database in those formats. ### Fatcat Identifiers |