Re: [Json] Meanwhile, out there...

"Pete Cordell" <petejson@codalogic.com> Sun, 02 March 2014 12:16 UTC

Return-Path: <petejson@codalogic.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE161A0923 for <json@ietfa.amsl.com>; Sun, 2 Mar 2014 04:16:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.537
X-Spam-Level: ***
X-Spam-Status: No, score=3.537 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, RDNS_DYNAMIC=0.982, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f5mcRjgUFmmw for <json@ietfa.amsl.com>; Sun, 2 Mar 2014 04:16:09 -0800 (PST)
Received: from ppsa-online.com (lvps217-199-162-192.vps.webfusion.co.uk [217.199.162.192]) by ietfa.amsl.com (Postfix) with ESMTP id 7F1AD1A0C99 for <json@ietf.org>; Sun, 2 Mar 2014 04:16:08 -0800 (PST)
Received: (qmail 7869 invoked from network); 2 Mar 2014 12:15:21 +0000
Received: from host81-155-177-242.range81-155.btcentralplus.com (HELO codalogic) (81.155.177.242) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (RC4-MD5 encrypted, authenticated); 2 Mar 2014 12:15:21 +0000
Message-ID: <211FD4E4CB37411AA3BA79156DEF9160@codalogic>
From: "Pete Cordell" <petejson@codalogic.com>
To: "JSON WG" <json@ietf.org>
References: <7FE4234C-25BC-4AB9-B0DD-9E1641DB9BE0@mnot.net> <4CA4E293-3252-4082-A40C-DE867D732209@vpnc.org> <CAHBU6is9aq4Ev6zMBRbu+ik0VVbCLmedU9QkKHjxbw9pRjmm2A@mail.gmail.com>
Date: Sun, 2 Mar 2014 12:15:34 -0000
X-Unsent: 1
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Vipre-Scanned: 001EA323006974001EA470
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Archived-At: http://mailarchive.ietf.org/arch/msg/json/71e8JejXVPuL4GLoLSsNrpV61oI
Cc: Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [Json] Meanwhile, out there...
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Mar 2014 12:16:11 -0000

Actually, I really wish the IETF would grab the bull by the horns and define 
a notation that is geared towards it's purposes rather than continually 
making do with everyone else's second-hand cast offs!

I think something JSON like would be good, but with a few modifications. 
For example SHON - Simple Humanized Object Notation:

// Implicit initial object - no {
// Comments are allowed
a_name_without_space: 12
// Unquoted whitespace without a comma separates records
"a name with spaces": 14
an_array: 15, 16, 17    // Commas implicitly create an array
an_array: 18    // Another member for an_array
a_string: "A string"
another_string: 'Another string'
an_object: { /* as JSON */ }

</rant>

Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com
----- Original Message ----- 
From: "Tim Bray" <tbray@textuality.com>
To: "Paul Hoffman" <paul.hoffman@vpnc.org>
Cc: "Mark Nottingham" <mnot@mnot.net>et>; "JSON WG" <json@ietf.org>
Sent: Sunday, March 02, 2014 9:58 AM
Subject: Re: [Json] Meanwhile, out there...


It says “this implementation doesn’t handle Unicode characters”.
 Unfortunately, that’s more or less all the characters I use.

Actually, quite sensible on the surface, aside from allowing +/-Infinity.


On Sun, Mar 2, 2014 at 1:46 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On Mar 2, 2014, at 8:38 AM, Mark Nottingham <mnot@mnot.net> wrote:
>
> >
> > <http://json5.org/>
> >
> >> JSON5 is a proposed extension to JSON that brings ES5 enhancements to
> its syntax. It remains a strict subset of JavaScript, adds no new data
> types, and is astrict superset of existing JSON.
>
> This appears to only be meant to work in a Javascript program, yes?
> Otherwise, what the heck does "Object keys can be unquoted if they're 
> valid
> identifiers" mean?
>
> --Paul Hoffman
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>



--------------------------------------------------------------------------------


> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>