aboutsummaryrefslogtreecommitdiff
path: root/BinaryEncoding.md
diff options
context:
space:
mode:
authortitzer <titzer@google.com>2016-02-09 09:26:14 +0100
committertitzer <titzer@google.com>2016-02-09 09:26:14 +0100
commit9c59a694bfaf116ba63312529dd5031310b2a7c3 (patch)
tree18b60201820560d26f9c8dcdd7b551f0aa545f8f /BinaryEncoding.md
parent685111b3b7a1bf05938d5c55bc8358d483de400a (diff)
downloadnanowasm-design-9c59a694bfaf116ba63312529dd5031310b2a7c3.tar.gz
Update BinaryEncoding.md
Diffstat (limited to 'BinaryEncoding.md')
-rw-r--r--BinaryEncoding.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/BinaryEncoding.md b/BinaryEncoding.md
index 72f44e5..5e265ef 100644
--- a/BinaryEncoding.md
+++ b/BinaryEncoding.md
@@ -24,8 +24,10 @@ The encoding is split into three layers:
to deliver dramatically smaller files.
Most importantly, the layering approach allows development and standardization to
-occur incrementally, even though production-quality implementations will need to
-implement all of the layers.
+occur incrementally. For example, Layer 1 and Layer 2 encoding techniques can be
+experimented with by application-level decompressing to the layer below. As
+compression techniques stabilize, they can be standardized and moved into native
+implementations.
# Data types