[FIG(quote)[
[FIGCAPTION[
[1] [CITE@en[meteor/DDP.md at devel · meteor/meteor]]
([TIME[2016-12-20 19:13:39 +09:00]])
<https://github.com/meteor/meteor/blob/devel/packages/ddp/DDP.md#user-content-appendix-ejson>
]FIGCAPTION]

> EJSON is a way of embedding more than the built-in JSON types in JSON. It supports all types built into JSON as plain JSON, plus the following:

]FIG]


[FIG(quote)[
[FIGCAPTION[
[2] [CITE@en[specs/ipld at master · ipld/specs]]
([TIME[2018-01-25 15:14:43 +09:00]])
<https://github.com/ipld/specs/tree/master/ipld>
]FIGCAPTION]

> On the subject of integers, there exist a variety of formats which represent integers as strings in JSON, for example, EJSON. These can be used and conversion to and from other formats should happen naturally-- that is, when converting JSON to CBOR, an EJSON integer should be transformed naturally to a proper CBOR integer, instead of representing it as a map with string values.

]FIG]


[FIG(quote)[
[FIGCAPTION[
[3] [CITE@en[EJSON | Meteor API Docs]]
([TIME[2017-12-12 10:39:04 +09:00]])
<https://docs.meteor.com/api/ejson.html>
]FIGCAPTION]

> EJSON is an extension of JSON to support more types. It supports all JSON-safe types, as well as:
> Date (JavaScript Date)
> Binary (JavaScript Uint8Array or the result of EJSON.newBinary)
> User-defined types (see EJSON.addType. For example, Mongo.ObjectID is implemented this way.)
> All EJSON serializations are also valid JSON.

]FIG]