summaryrefslogtreecommitdiffstats
path: root/guide/src/style_guide.md
diff options
context:
space:
mode:
authorBryan Newbold <bnewbold@robocracy.org>2019-02-14 16:19:26 -0800
committerBryan Newbold <bnewbold@robocracy.org>2019-02-14 16:19:26 -0800
commit70b4bc18b13f59c9d42c8e44ef872dfd2e1abef3 (patch)
tree1c4706394047bce6a086228e2efe8632d8bc1a23 /guide/src/style_guide.md
parent56edebe7c2e090c4f25179f03a2d77d78ba59219 (diff)
downloadfatcat-70b4bc18b13f59c9d42c8e44ef872dfd2e1abef3.tar.gz
fatcat-70b4bc18b13f59c9d42c8e44ef872dfd2e1abef3.zip
more guide tweaks; not a full review/rewrite
Diffstat (limited to 'guide/src/style_guide.md')
-rw-r--r--guide/src/style_guide.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/guide/src/style_guide.md b/guide/src/style_guide.md
index 7f819c8d..d670691a 100644
--- a/guide/src/style_guide.md
+++ b/guide/src/style_guide.md
@@ -19,12 +19,12 @@ treated as an entirely separate `release`.
documentation (such as DOI `10.5555/12345678`) are allowed (and the entity
should be tagged as a fake or example). Non-registered "identifier-like
strings", which are semantically valid but not registered, should not exist in
-fatcat metadata in an identifier column. Invalid identifier strings can be
+Fatcat metadata in an identifier column. Invalid identifier strings can be
stored in "extra" metadata. Crossref has [blogged]() about this distinction.
[blogged]: https://www.crossref.org/blog/doi-like-strings-and-fake-dois/
-#### DOI
+#### DOIs
All DOIs stored in an entity column should be registered (aka, should be
resolvable from `doi.org`). Invalid identifiers may be cleaned up or removed by
@@ -38,9 +38,9 @@ formatted strings.
[number of examples]: https://www.crossref.org/blog/dois-unambiguously-and-persistently-identify-published-trustworthy-citable-online-scholarly-literature-right/
-In the fatcat ontology, DOIs and release entities are one-to-one.
+In the Fatcat ontology, DOIs and release entities are one-to-one.
-It is the intention to automatically (via bot) create a fatcat release for
+It is the intention to automatically (via bot) create a Fatcat release for
every Crossref-registered DOI from a whitelist of media types
("journal-article" etc, but not all), and it would be desirable to auto-create
entities for in-scope publications from all registrars. It is not the intention