On Fri, Sep 7, 2012 at 3:01 AM, Rich Hickey <richhic...@gmail.com> wrote:
> I've started to document a subset of Clojure's data format in an effort to
> get it more widely used as a data exchange format, e.g. as an alternative to
> JSON.
>
> Please have a look:
>
> https://github.com/richhickey/edn
>
> Rich
A few questions or things I'm unclear on:
- The expected result of parsing { 1.0 :a, 1 :b, 1.0M :c } is unclear
to me. Since we're gonna have maps, some more information on expected
equality semantics of edn values is needed.
- nil is not a symbol. A parser seeing «(nil)» is expected to produce
a list of length one containing a single reference to nothing. The
collections used to represent the result of the parse must support
null elements (Google Guava's, for example, generally do not).
- edn is described as a textual format (sequence of characters). A
word on the expected encoding of serialized representations (sequence
of bytes) would be good. Mandate UTF-8?
- Are \uXXXX style Unicode escapes supported? In strings? elsewhere?
- Comments appear not to be supported. I know a deliberate choice was
made not to support comments as part of JSON. For use in configuration
files edited by humans, however, this is an inconvenience. Thoughts?
// Ben
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
