Re: [Json] [apps-discuss] JSON mailing list and BoF

Sadayuki Furuhashi <> Wed, 20 February 2013 20:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3ACF521E803C for <>; Wed, 20 Feb 2013 12:35:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PgM9DoDBloCJ for <>; Wed, 20 Feb 2013 12:35:34 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 74C0B21E8039 for <>; Wed, 20 Feb 2013 12:35:34 -0800 (PST)
Received: by with SMTP id kp14so4210654pab.19 for <>; Wed, 20 Feb 2013 12:35:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=x-received:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version:x-mailer; bh=IPeauHZHXWveTsJifyBy8IgDXkFHXekl5QVQ+GQu5bU=; b=suxayxNGLoHzQdWeA4ZMmvudSOo2Pjt3nUXTPmaHgHIPm0mEI/2Wwh868L4MyW9fWa r+UbrbRU2irwYn7Vrirqzo4SFYR4YhoT/WoGalt4myaNUryElsmW0q9f991DNsrz/SCD dYKLyjEmbVFx8qaB/n3WeNAJb4pVZlChH0+tl+q0n5DE7Ivg213XAQ3+j6S1N4EG/I0m wW2sj0uTc6uR41Z/a0oyxmgeBmFJ/1qgO2yD2KgDm6faXu+1B+NmF3gvWHf799hniUkK bPSktYFp3T1o/dEiMZ4Axdz768IEiA2kn9WtsYplb4YA9EmnfPrq2VvERa/5b5d2+Y+g R1tA==
X-Received: by with SMTP id gw9mr4501139pbc.200.1361392534224; Wed, 20 Feb 2013 12:35:34 -0800 (PST)
Received: from [] ( []) by with ESMTPS id qp13sm22686689pbb.3.2013. (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 Feb 2013 12:35:32 -0800 (PST)
From: Sadayuki Furuhashi <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
Date: Wed, 20 Feb 2013 12:35:29 -0800
To: "" <>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: Re: [Json] [apps-discuss] JSON mailing list and BoF
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Feb 2013 00:20:56 -0000

I'm frsyuki (Sadyuki Furuhashi), the initial designer of the MessagePack.
I found a mail about msgpack.

draft-bormann-apparea-bpack-00.txt is slightly modified version of msgpack
and it's not compatible with existent msgpack implementations for over 20+
Even if msgpack had a UTF-8 type, it will be different from the one proposed
by bpack-00.txt because specs without implementations don't make sense.

Thus today's msgpack is a stable format and future msgpack will be compatible
with it.

We're supposed to add user-defined custom type support as the part of its spec.
And the string type will be one of the custom types.

Here is a msgpack issue thread to discuss about the string type:

> On Feb 19, 2013, at 00:47, "Joe Hildebrand (jhildebr)" <jhildebr at> wrote:
>> As an individual, I'm +1 on that.  I love msgpack, and don't mind the
>> addition of UTF8 as a separate type.  Was frsyuki involved in the draft,
>> or at least know that it happened?
> I tried to involve him.
> Frsyuki doesn't like what I did with the binary strings vs. UTF-8, though.
> I didn't quite catch whether he is just focusing on maintaining compatibility with what's out there (today's msgpack) or whether he really doesn't see why that is a good idea.
> (For me, maintaining 100 % compatibility won't work anyway, because in the end that won't be the only change we'll want to make.  
> If we look a bit outside the space that msgpack is being applied to today, we might want to support, say, 16-bit floating point.)
> Grüße, Carsten

Sadayuki Furuhashi