edit later sections

Author: alimanfoo

_posts/2019-05-02-zarr-2.3-release.md

@@ -118,53 +118,58 @@ ds = cat.atmosphere.gmet_v1.to_dask()
 ...and [here's the underlying catalog
 entry](https://github.com/pangeo-data/pangeo-datastore/blob/aa3f12bcc3be9584c1a9071235874c9d6af94a4e/intake-catalogs/atmosphere.yaml#L6).
 
+
 ## Compatibility with N5
 
 Around the same time that development on Zarr was getting started, a
-separate team led by Stephan Saafeld at the Janelia research campus
-was experiencing similar frustrations trying to use HDF5 for storing
-brain imaging data, and developed a software library called
-N5. Although N5 was originally implemented in Java, it has strong
-similarities to Zarr in the approach it takes to storing both metadata
-and data chunks. We became aware of each others' work around a year
-ago and have been learning about the two approaches.
-
-The bottom line is that there is a lot of commonality and we are
-working jointly to bring the two approaches together. As a first
-experimental step towards that goal, the Zarr 2.3 release includes a
-storage adapter which allows reading and writing of data on disk in
-the N5 format. Here's an example:
+separate team led by [Stephan
+Saafeld](https://www.janelia.org/lab/saalfeld-lab) at the Janelia
+research campus was experiencing similar challenges storing and
+computing with large amounts of neural imaging data, and developed a
+software library called [N5](https://github.com/saalfeldlab/n5). N5 is
+implemented in Java but is very similar to Zarr in the approach it
+takes to storing both metadata and data chunks, and to decoupling the
+storage backend to enable efficient use of cloud storage.
+
+There is a lot of commonality between Zarr and N5 and we are working
+jointly to bring the two approaches together. As a first experimental
+step towards that goal, the Zarr 2.3 release includes an [N5 storage
+adapter](https://zarr.readthedocs.io/en/stable/api/n5.html#zarr.n5.N5Store)
+which allows reading and writing of data on disk in the N5
+format. 
 
-{% highlight python %}
-TODO
-{% endhighlight %}
 
 ## Future developments
 
 There is a growing community of interest around new approaches to
-storage of array-like data, and we'd like to do what we can to build
-connections and share knowledge and ideas between these
-communities. We've started a [regular teleconference](@@TODO) which is
-open to anyone to join, and there is a new [gitter channel](@@TODO)
-for general discussion.
+storage of array-like data, particularly in the cloud. For example,
+Theo McCaie from the UK Met Office Informatics Lab recently wrote a
+series of blog posts about the challenges involved in [storing 200TB
+of "high momentum" weather model data every
+day](https://medium.com/informatics-lab/creating-a-data-format-for-high-momentum-datasets-a394fa48b671). This
+is an exciting space to be working in and we'd like to do what we can
+to build connections and share knowledge and ideas between
+communities. We've started a [regular
+teleconference](https://github.com/zarr-developers/zarr/issues/315)
+which is open to anyone to join, and there is a new [gitter
+channel](https://gitter.im/zarr-developers/community) for general
+discussion.
 
 The main focus of our conversations so far has been setting up work
 towards development of a new set of specifications that support the
-features of both Zarr and N5, and the requirements of key user groups,
-including Earth and climate sciences, bioimaging and microscopy, and
-data derived from large scale DNA and RNA sequencing experiments. It
-is still relatively early days and there are lots of open questions to
-work through, both on the technical side and in terms of how we
-organise and coordinate efforts. However, the community is very
-friendly and supportive, and anyone is welcome to participate, so if
-you have an interest please do consider getting involved.
-
-If you would like to stay in touch with where things are going, keep
-an eye on the [zarr](@@TODO) and [zarr-specs](@@TODO) GitHub
-repositories, join the [gitter channel](@@TODO), and please feel free
-to raise issues or add comments if you have any questions or ideas.
-
-## Further reading
-
-* [Zarr Python 2.3 release notes](@@TODO)
-* anything else...
+features of both Zarr and N5, and provide a platform for exploration
+and development of new features, while also identifying a minimal core
+protocol that can be implemented in a range of different programming
+languages. It is still relatively early days and there are lots of
+open questions to work through, both on the technical side and in
+terms of how we organise and coordinate efforts. However, the
+community is very friendly and supportive, and anyone is welcome to
+participate, so if you have an interest please do consider getting
+involved.
+
+If you would like to stay in touch with or contribute to new
+developments, keep an eye on the
+[zarr](https://github.com/zarr-developers/zarr) and
+[zarr-specs](https://github.com/zarr-developers/zarr-specs) GitHub
+repositories, and please feel free to raise issues or add comments if
+you have any questions or ideas.