tweaks

Author: alimanfoo

slides/v3-update-20190619.md

@@ -606,8 +606,8 @@ Currently nothing but extensions and attributes:
 
 ### [Bootstrap metadata](https://zarr-specs.readthedocs.io/en/core-protocol-v3.0-dev/protocol/core/v3.0.html#bootstrap-metadata)
 
-Bootstrap metadata is a new concept, not present in either Zarr v2 or
-N5. Why add it?
+* Bootstrap metadata is a new concept, not present in either Zarr v2
+  or N5. Why add it?
 
 * Provides metadata about metadata, e.g., what core protocol version
   is being used, what metadata encoding is being used.
@@ -727,15 +727,12 @@ read-only.
 
 * As with current Zarr v2 and N5 protocols, goal of v3 store interface
   is to enable a range of store implementations using different
-  storage technologies, e.g.:
+  storage technologies:
 
-  * Local memory
-  * File systems
-  * Zip files
-  * Local key-value databases (e.g., BDB, LMDB, Kyoto/Tokyo, LevelDB, ...)
-  * Distributed key-value databases (e.g., mongo, redis, ...) 
-  * Relational databases
-  * Cloud object stores (S3, GCS, ABS, ...)
+  * Local memory; file systems; zip files; local key-value databases
+    (BDB, LMDB, Kyoto/Tokyo, LevelDB, ...); distributed key-value
+    databases (e.g., mongo, redis, ...); relational databases; cloud
+    object stores (S3, GCS, ABS, ...); ...
 
 * Core protocol does not specify how to implement any of these. Leave
   that for **storage specs**.
@@ -786,7 +783,11 @@ Operation | Implementation
   * Check if a group exists at path "/foo", if not then create it.
 
   * Check if a group exists at path "/", if not then create it.
-  
+
+===
+
+### Zarr v2 problem 1 - race conditions
+
 * But if multiple arrays are being created in parallel, can lead to
   race conditions.
 
@@ -865,9 +866,6 @@ Operation | Implementation
   and/or it could implement some mechanism for checking consistency
   after node creation.
 
-  * But neither of these are the responsibility of a Zarr core
-    protocol implementation.
-
 ===
 
 ### Making hierarchy discovery more efficient