diff --git a/README.md b/README.md
index 66803b2..77022cd 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,23 @@
 # GeoZarr-Spec
 
-GeoZarr Spec aims to provide a geospatial extension to the Zarr specification. Zarr specifies a protocol and format used for storing Zarr arrays, while the present extension defines **conventions** and recommendations for storing **multidimensional georeferenced grid** of geospatial observations (including rasters). 
+GeoZarr Spec aims to provide a geospatial extension to the Zarr specification in the form of a _zarr convention_. Zarr specifies a protocol and format used for storing Zarr arrays, while GeoZarr defines **conventions** and recommendations for storing **multidimensional georeferenced grid** of geospatial observations (including rasters). See this draft [Zarr Enhancement Proposal](https://github.com/zarr-developers/zeps/pull/28/files?short_path=53e442a#diff-53e442aa938ca18ba1a94f845f264c5df0e4650f8f6abda856c3cd819f70abca) for further detail of the Zarr Convention process.
+
+## Scope
+
+* Easy compatibility with popular mapping and data analysis tools like GDAL, Xarray, ArcGIS, and QGIS.
+* Combining different types of geospatial data, like satellite images, elevation maps, and weather models.
+* Creating and displaying geospatial data in web browsers without complex workarounds
+* Helping users discover, access, and retrieve the data they need, including subsets or different arrangements of the data
+* Supporting advanced geospatial features for more accurate data representation and analysis.
+* Allowing scientists and researchers to work with diverse data types and projections in their preferred software and programming languages.
+* Supporting serverless, cloud-native data analytics patterns on geospatial datacubes, including timeseries analysis.
+## Deliverable
+
+The geozarr-spec is a community effort to establish conventions for geospatial use cases in the cloud-native ZARR binary carrier. It is built from existing data standards, conventions, and implementation patterns. The outcome of this work will be an implementable set of conventions. Next steps for formalization of a normative version of the conventions will be refined as the work progresses. Some key considerations follow.
+
+* A ZARR Convention according to the draft described in [Zarr Enhancement Proposal 0004](https://github.com/zarr-developers/zeps/pull/28/files?short_path=53e442a#diff-53e442aa938ca18ba1a94f845f264c5df0e4650f8f6abda856c3cd819f70abca). 
+* An OGC standard that describes the GeoZarr-spec convention. ([See two track standards process here for requirements of a full vs community standard](https://docs.opengeospatial.org/pol/05-020r27/05-020r27.html#the-two-track-standards-process-characteristics))
+* Contribution of any extension that is best housed in the CF-Convention.
 
 ## Status