From 0f9ec22bd45e11bd3bfc5fd523a8c893312ec532 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Fri, 25 Sep 2015 15:09:03 -0700 Subject: [PATCH] glossary: Specify UTF-8 for all our JSON MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I wish there was a cleaner reference for what UTF-8 was. But [1] seems too glib, and I can't find a more targetted link than just dropping folks into a Unicode chapter (which is what [1] does): The Unicode Standard, Version 6.0, §3.9 D92, §3.10 D95 (2011) With the current v8.0 (2015-06-17), it's still §3.9 D92 and §3.10 D95. I'd rather put this normative requirement in the configuration-spec files, but maintainer consensus was to put it in the glossary [2,3]. [1]: https://en.wikipedia.org/wiki/UTF-8 [2]: https://github.com/opencontainers/specs/pull/146#issuecomment-138970417 [3]: https://github.com/opencontainers/specs/pull/146#issuecomment-143348788 Signed-off-by: W. Trevor King --- glossary.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/glossary.md b/glossary.md index 8eaee1402..00075621c 100644 --- a/glossary.md +++ b/glossary.md @@ -13,7 +13,14 @@ The [`config.json`](config.md) and [`runtime.json`](runtime-config.md) files in An environment for executing processes with configurable isolation and resource limitations. For example, namespaces, resource limits, and mounts are all part of the container environment. +## JSON + +All configuration [JSON][] MUST be encoded in [UTF-8][]. + ## Runtime An implementation of this specification. It reads the [configuration files](#configuration) from a [bundle](#bundle), uses that information to create a [container](#container), launches a process inside the container, and performs other [lifecycle actions](runtime.md). + +[JSON]: http://json.org/ +[UTF-8]: http://www.unicode.org/versions/Unicode8.0.0/ch03.pdf