Re: [Json] Possible next work for the WG

R S <sayrer@gmail.com> Fri, 18 October 2013 02:30 UTC

Return-Path: <sayrer@gmail.com>
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 71D8011E813B for <json@ietfa.amsl.com>; Thu, 17 Oct 2013 19:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level:
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[AWL=0.327, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 0jQmuZbcR1PB for <json@ietfa.amsl.com>; Thu, 17 Oct 2013 19:30:16 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 2F76C11E8135 for <json@ietf.org>; Thu, 17 Oct 2013 19:30:08 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id n7so478453qcx.27 for <json@ietf.org>; Thu, 17 Oct 2013 19:30:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=X0ihz7f5P8HxV2IdvXXYn+EMtpuwCcILE8TcsXqCGPs=; b=wJ3O/zyxIvLhVGRoI3nNoJTJWa21avCGbfq7/dLc2/q338JFOMpEw/3Td/VYoQZuc6 UeSG/m98+/MD6qEVuio/0nA3SkfQta4td1jm3UEXbAwCTJaFp/T7sHWKMPzBRRBXW5Fp 8I8mToInTMEtvqIo/eGwWIkr2L9W0eeQtQbdHIES2QAISijHxLN+opypacKRcndyJkOH aELKySfOJh4eTbQEX5nIk+GyyXIdawW97XWKEehbqpt83ZGDwkEe6SAq5PaqdwxORFAH 17vWNNwk6jXH2iWyQ0O6fxKIZm7EKK514MyeTNQlHHmlVALSIcOnSjdiOSsYYOM3/+v0 5a9g==
MIME-Version: 1.0
X-Received: by 10.224.79.71 with SMTP id o7mr1485133qak.36.1382063407639; Thu, 17 Oct 2013 19:30:07 -0700 (PDT)
Received: by 10.224.7.9 with HTTP; Thu, 17 Oct 2013 19:30:07 -0700 (PDT)
In-Reply-To: <20131016172831.GC9701@mercury.ccil.org>
References: <29850F92-23F1-4859-BB5A-BB5F1F20DD38@vpnc.org> <20131016172831.GC9701@mercury.ccil.org>
Date: Thu, 17 Oct 2013 19:30:07 -0700
Message-ID: <CAChr6SxdLkCAHnz5ZqxU7KiMZMY_AN7kgF_KA0cayrwMYadMHg@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: John Cowan <cowan@mercury.ccil.org>
Content-Type: multipart/alternative; boundary=047d7bf0f31e784c0404e8fab619
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, 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: Fri, 18 Oct 2013 02:30:17 -0000

There's already an RFC for that. <http://tools.ietf.org/html/rfc6901>

- Rob


On Wed, Oct 16, 2013 at 10:28 AM, John Cowan <cowan@mercury.ccil.org> wrote:

> Paul Hoffman scripsit:
>
> > Greetings again. While our AD ponders the 4627bis document (probably on
> > its way to IETF Last Call), the Working Group can start to think about
> > what it wants to do next, if anything. The chairs have heard of at least
> > four topics that the WG might or might not want to add to its charter:
>
> application/json fragment identifiers should be added to this list.
> There seems to be a fairly mature proposal along the lines of the XPointer
> "element" scheme.  Some people don't like it because you can't tell by
> examining a fragment id what type of JSON value it references.  By the
> same token, however, you can't tell by examining a URI pointing to a
> JSON document what JSON type it references either.
>
> --
> John Cowan    cowan@ccil.org    http://ccil.org/~cowan
> The whole of Gaul is quartered into three halves.
>         --Julius Caesar
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>