summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorAndre Polykanine A.K.A. Menelion ElensĂșlĂ« <andre@oire.org>2017-09-08 22:19:58 +0300
committerGitHub <noreply@github.com>2017-09-08 22:19:58 +0300
commit6e56aa136c4f409e77e63bf678a77922184301ab (patch)
treead675f051232af621c830ce815271d6fb0fb785e
parent2a3fbe26b6d77fff04b64c56f939e8338b9f800c (diff)
parent25eca3c52781c7be94b088fa6edaad8d7815aa6d (diff)
Merge pull request #2844 from jdjohnston/edn-change
[edn/en] Improve initial description of EDN
-rw-r--r--edn.html.markdown9
1 files changed, 6 insertions, 3 deletions
diff --git a/edn.html.markdown b/edn.html.markdown
index 79107269..04346eb8 100644
--- a/edn.html.markdown
+++ b/edn.html.markdown
@@ -3,13 +3,16 @@ language: edn
filename: learnedn.edn
contributors:
- ["Jason Yeo", "https://github.com/jsyeo"]
+ - ["Jonathan D Johnston", "https://github.com/jdjohnston"]
---
Extensible Data Notation (EDN) is a format for serializing data.
-The notation is used internally by Clojure to represent programs. It is also
-used as a data transfer format like JSON. Though it is more commonly used in
-Clojure, there are implementations of EDN for many other languages.
+EDN is a subset of the syntax used by Clojure. Reading data defined by EDN is
+safer than that defined by the full Clojure syntax, especially from untrusted
+sources. EDN is restricted to data, no code. It is similar in intent to JSON.
+Though it is more commonly used in Clojure, there are implementations of EDN
+for many other languages.
The main benefit of EDN over JSON and YAML is that it is extensible. We
will see how it is extended later on.