Re: [Json] Possible next work for the WG

"Markus Lanthaler" <markus.lanthaler@gmx.net> Wed, 16 October 2013 17:20 UTC

Return-Path: <markus.lanthaler@gmx.net>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33D7611E8192 for <json@ietfa.amsl.com>; Wed, 16 Oct 2013 10:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.248
X-Spam-Level: *
X-Spam-Status: No, score=1.248 tagged_above=-999 required=5 tests=[AWL=0.490, BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449, RCVD_ILLEGAL_IP=1.908]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fQCcRdS9Lvhr for <json@ietfa.amsl.com>; Wed, 16 Oct 2013 10:20:15 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id BAD8011E8118 for <json@ietf.org>; Wed, 16 Oct 2013 10:20:05 -0700 (PDT)
Received: from Vostro3500 ([2.34.217.54]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lxxw4-1VrF7X2wCq-015Jrn for <json@ietf.org>; Wed, 16 Oct 2013 19:20:04 +0200
From: "Markus Lanthaler" <markus.lanthaler@gmx.net>
To: "'John Cowan'" <cowan@mercury.ccil.org>, "'Paul Hoffman'" <paul.hoffman@vpnc.org>
References: <29850F92-23F1-4859-BB5A-BB5F1F20DD38@vpnc.org> <20131016165406.GA9701@mercury.ccil.org>
In-Reply-To: <20131016165406.GA9701@mercury.ccil.org>
Date: Wed, 16 Oct 2013 19:19:59 +0200
Message-ID: <01ab01ceca93$f2281740$d67845c0$@lanthaler@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac7KkFkkzzT47RoXSnOKEQQUghe8FwAAyk/g
Content-Language: de
X-Provags-ID: V03:K0:GR2vSOvEGbJV8jTkPGOt+obIWYTkknza43+JPAYzaHCCCdznnTI 87a/FEI1O2wTIGzGbyBP/bWv1CANQQTBdHCBn2ncOILixFjIeWUjnxbSR92irYxxPwf5Rp4 5fETLxia7wDfll6+8HTmFzrtTwD2h4WL9xZ4OPJKaBND05bUlgcYJSgQYby+yJKsZL3KCNS N1JNHjI8Jnxi35ICOvhig==
Cc: 'JSON WG' <json@ietf.org>
Subject: Re: [Json] Possible next work for the WG
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 16 Oct 2013 17:20:20 -0000

On Wednesday, October 16, 2013 6:54 PM, John Cowan
> Paul Hoffman scripsit:
> 
> > - I-JSON (a profile of JSON with some interoperability issues nailed
down)
> >
> > - Best practices document for JSON implementers and folks who use JSON
> > in protocols
> 
> I think these are both worthy ideas, though perhaps they can be merged.

Completely agree


> > - Canonicalization rules so that two JSON texts can be compared for
> equality
> 
> I think we should explore this, but it's going to be tricky.

+0


> > - Requirements for JSON schema (which will be needed before the WG
> > considers working on an actual schema)
> 
> As reinvented wheels are often hexagonal, I think if we are going to
> do this we should adopt draft-zyp-json-schema-04 as a base document
> for further work.  This has now expired, but is still available at
> <https://raw.github.com/fge/json-schema-
> validator/master/misc/specs/draft-zyp-json-schema-04.txt>.

I don't think we should start work on this without someone (better yet, a
group of people) actively pushing for it. Just look at the history of JSON
Schema..


> I note that this draft proposes "application/schema+json" as the media
> type for JSON schemas.  That leads me to believe we should make
> "*/*+json"
> official, parallel to "*/*+xml" per RFC 3023.  I'll post on that
> separately.

That has already been done in RFC6839


--
Markus Lanthaler
@markuslanthaler