summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEllen Spertus <ellen.spertus@gmail.com>2018-05-24 17:13:59 +0000
committerEllen Spertus <ellen.spertus@gmail.com>2018-05-24 17:13:59 +0000
commit0274d68e92fd78415c7876d63e5a67d3f94fdab6 (patch)
tree71226586e13b7a302037b195b6a04e910de208f4
parent1cae13d448bec075e3b73968d3ca1693ceb1fb61 (diff)
downloadfatcat-0274d68e92fd78415c7876d63e5a67d3f94fdab6.tar.gz
fatcat-0274d68e92fd78415c7876d63e5a67d3f94fdab6.zip
Fixed typos with help from spell checker.
-rw-r--r--rfc.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/rfc.md b/rfc.md
index db75983e..21495f6d 100644
--- a/rfc.md
+++ b/rfc.md
@@ -36,8 +36,8 @@ content.
The goal is to have a very permissively licensed database: CC-0 (no rights
reserved) if possible. Under US law, it should be possible to scrape and pull
in factual data from other corpuses without adopting their licenses. The goal
-here isn't to avoid all attibution (progeny information will be included, and a
-large sources and acknowledgements statement should be maintained), but trying
+here isn't to avoid all attribution (progeny information will be included, and a
+large sources and acknowledgments statement should be maintained), but trying
to manage the intersection of all upstream source licenses seems untenable, and
creates burdens for downstream users.
@@ -90,13 +90,13 @@ increasing version number for the entire corpus, and should make interaction
with other systems easier (eg, search engines, replicated databases,
alternative storage backends, notification frameworks, etc.).
-## Itentifiers
+## Identifiers
-A fixed number of first class "entities" would be defined, with common
+A fixed number of first-class "entities" would be defined, with common
behavior and schema layouts. These would all be semantic entities like "work",
"release", "container", and "person".
-fatcat identifiers would be semanticly meaningless fixed-length random numbers,
+fatcat identifiers would be semantically meaningless fixed-length random numbers,
usually represented in case-insensitive base32 format. Each entity type would
have its own identifier namespace. Eg, 96-bit identifiers would have 20
characters and look like:
@@ -123,7 +123,7 @@ persistent identifiers.
Internally, identifiers would be lightweight pointers to actual metadata
objects, which can be thought of as "versions". The metadata objects themselves
-would be immutable once commited; the edit process is one of creating new
+would be immutable once committed; the edit process is one of creating new
objects and, if the edit is approved, pointing the identifier to the new
version. Entities would reference between themselves by identifier.