IETF Logo Mail Archive

Re: [apps-discuss] draft-saintandre-json-namespaces-00 comments

Mark Baker <distobj@acm.org> Wed, 09 November 2011 00:51 UTC

Return-Path: <mark@coactus.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22B2821F8AEA for <apps-discuss@ietfa.amsl.com>; Tue, 8 Nov 2011 16:51:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.727
X-Spam-Level:
X-Spam-Status: No, score=-104.727 tagged_above=-999 required=5 tests=[AWL=-1.750, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 xSn5f1Mbgs66 for <apps-discuss@ietfa.amsl.com>; Tue, 8 Nov 2011 16:51:08 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 95C7F21F8801 for <apps-discuss@ietf.org>; Tue, 8 Nov 2011 16:51:08 -0800 (PST)
Received: by iaeo4 with SMTP id o4so1496555iae.31 for <apps-discuss@ietf.org>; Tue, 08 Nov 2011 16:51:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.42.168.202 with SMTP id x10mr209863icy.4.1320799868077; Tue, 08 Nov 2011 16:51:08 -0800 (PST)
Sender: mark@coactus.com
Received: by 10.42.165.194 with HTTP; Tue, 8 Nov 2011 16:51:08 -0800 (PST)
In-Reply-To: <4EB981B6.1090003@gmx.de>
References: <4EB923CF.7080600@wp.pl> <566A345F-15CD-473B-8472-11EDF73A3862@vpnc.org> <9D5B00CA-9370-45D6-835B-3C7A1ADFEBBC@mnot.net> <4EB97122.7010206@gmx.de> <D75C8075-C8DF-4AA2-9DFC-CED719A0564E@mnot.net> <4EB98090.5020203@gmx.de> <6A0CCE36-5FBE-48E9-A307-1C59C155D8BB@mnot.net> <4EB981B6.1090003@gmx.de>
Date: Tue, 08 Nov 2011 19:51:08 -0500
X-Google-Sender-Auth: RHO0awihG_mNz9daxl48PS8bDZA
Message-ID: <CALcoZipiOC4ro_Mhhnu7VRAJdSU_N1AhwPa+0XCppQozWiOf0Q@mail.gmail.com>
From: Mark Baker <distobj@acm.org>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Mark Nottingham <mnot@mnot.net>, Paul Hoffman <paul.hoffman@vpnc.org>, apps-discuss Discuss <apps-discuss@ietf.org>, Dominik Tomaszuk <ddooss@wp.pl>
Subject: Re: [apps-discuss] draft-saintandre-json-namespaces-00 comments
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2011 00:51:09 -0000

On Tue, Nov 8, 2011 at 2:23 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> I think it's worthwhile to have a spec that says:
>
> "If you're identifiers are XML names, then this how to use them in JSON. But
> if you don't have identifiers like these, don't *start* using them if you
> want to use JSON."

Completely agreed, though XML names aren't the only ones grounded in
URI space (e.g. RDF).

> Which of course leaves the question open what to do instead :-) (and yes, I
> saw your proposal)

After working with it for a couple of weeks, I agree completely with
Manu (in the comments of Mark's blog post); JSON-LD is a terrific fit.
It uses the same basic approach suggested in the message which started
this thread, and has other features which make it easy to bolt-on to
existing JSON based formats, in many cases without breaking existing
recipients.

http://json-ld.org

Mark.

v2.23.0 | Report a Bug | By Email