changeset 14:2221a941abaa

Include a mention of CBOR in the README
author Norman Gray <norman@astro.gla.ac.uk>
date Mon, 09 Jun 2014 14:36:32 +0100
parents a593eddaf0a3
children 81e6d0fe8198
files README.md
diffstat 1 files changed, 9 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/README.md	Sun Feb 23 22:23:23 2014 +0000
+++ b/README.md	Mon Jun 09 14:36:32 2014 +0100
@@ -15,10 +15,16 @@
 and it doesn't attempt to handle ASN.1 types other than the subset
 which it generates.
 
-In that encoding, JSON integers, floats, booleans, and null, are
+In this encoding, JSON integers, floats, booleans, and null, are
 encoded to the DER analogues.  A JSON array is encoded to a DER
 `SEQUENCE`, an object to a `SET OF` two-element sequences, and strings
-to DER `ia5string` objects.
+to DER `ia5string` objects (the `ia5string` restriction is because this
+parser currently handles only ASCII).
+
+This may or may not be the best way to approach this problem.  There
+is an interesting comparison of approaches discussed in [RFC 7049][],
+which describes an alternative called _Concise Binary Object
+Representation_ (CBOR).
 
 DER is specified in ITU-T Rec. X.690, as part of the ASN/1 suite of
 standards.  See the [ITU-T recommendation][] and [Wikipedia][], and
@@ -142,6 +148,7 @@
 [ITU-T recommendation]: http://www.itu.int/rec/T-REC-X.690-200811-I/en
 [Wikipedia]: http://en.wikipedia.org/wiki/X.690
 [RFC 4627]: http://www.ietf.org/rfc/rfc4627.txt
+[RFC 7049]: http://www.ietf.org/rfc/rfc7049.txt
 [BSD 2-clause licence]: http://opensource.org/licenses/BSD-2-Clause
 [jasn]: https://code.google.com/p/jasn/
 [lcut]: https://github.com/bigwhite/lcut