This repository contains a CBOR JavaScript API. The API loosely mimics the "JSON" object by exposing a single global object, unsurprisingly named "CBOR". To minimize the need for application developers having detailed knowledge of CBOR, the API provides a set of high level CBOR Wrapper Objects which also serve as "bridge" between CBOR and JavaScript.

The wrapper objects are used for encoding CBOR data items, as well as being the result of CBOR decoding.

Design Rationale

The proposed API is intended to provide CBOR [RFC8949] "baseline" functionality that can easily be implemented in standard platforms with an emphasis on computationally advanced systems like Web browsers, mobile phones, and Web servers. Due to the desire maintaining interoperability across different platforms, the API "by design" does not address JavaScript specific types like undefined and binary data beyond Uint8Array. See also: CBOR Everywhere.

"CBOR" Components

• Self-encoding wrapper objects
• Decoder
• Diagnostic Notation decoder
• Utility functions

Encoding Example

let cbor = CBOR.Map()
               .set(CBOR.Int(1), CBOR.Float(45.7))
               .set(CBOR.Int(2), CBOR.String("Hi there!")).encode();

console.log(CBOR.toHex(cbor));
------------------------------
a201fb4046d9999999999a0269486920746865726521

Note: there are no requirments "chaining" objects as shown above; items may be added to CBOR.Map and CBOR.Array objects in separate steps.

Decoding Example

let map = CBOR.decode(cbor);
console.log(map.toString());  // Diagnostic notation
----------------------------------------------------
{
  1: 45.7,
  2: "Hi there!"
}

console.log('Value=' + map.get(CBOR.Int(1)));
---------------------------------------------
Value=45.7

On-line Testing

On https://cyberphone.github.io/CBOR.js/doc/playground.html you will find a simple Web application, permitting testing the encoder, decoder, and diagnostic notation implementation.

NPM Version

For usage with Node.js, a NPM version is available: https://npmjs.com/package/cbor-object

Deterministic Encoding

The JavaScript API implements deterministic encoding based on https://datatracker.ietf.org/doc/draft-ietf-cbor-cde/.

To shield developers from having to know the inner workings of deterministic encoding, the CBOR.js API performs all necessary transformations automatically. This for example means that if the set() operations in the Encoding Example were swapped, the generated CBOR would still be the same.

Diagnostic Notation Support

Diagnostic notation as described in section 8 of RFC8949 permits displaying CBOR data as human-readable text. This is practical for logging, documentation, and debugging purposes. Diagnostic notation is an intrinsic part of the CBOR.js API through the toString() method.

However, the CBOR.js API extends the scope of diagnostic notation by supporting using it as input for creating CBOR based test data and configuration files from text. Example:

let cbor = CBOR.diagDecode(`{
# Comments are also permitted
  1: 45.7,
  2: "Hi there!"
}`).encode();

console.log(CBOR.toHex(cbor));
------------------------------
a201fb4046d9999999999a0269486920746865726521

Aided by the model used for deterministic encoding, diagnostic notation becomes bidirectional, while remaining faithful to the native CBOR representation.

Other Compatible Implementations

Language	URL
JDK 17+	https://github.com/cyberphone/openkeystore
Android/Java	https://github.com/cyberphone/android-cbor

Updated: 2024-04-29