Skip to content

Commit

Permalink
glossary: Specify UTF-8 for all our JSON
Browse files Browse the repository at this point in the history
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]: #146 (comment)
[3]: #146 (comment)

Signed-off-by: W. Trevor King <[email protected]>
  • Loading branch information
wking committed Dec 23, 2015
1 parent 1873498 commit 0f9ec22
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

0 comments on commit 0f9ec22

Please sign in to comment.