Re: [Json] Working Group Last Call on draft-ietf-i-json-02

"Markus Lanthaler" <markus.lanthaler@gmx.net> Wed, 16 July 2014 14:45 UTC

Return-Path: <markus.lanthaler@gmx.net>
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 783561B29CE for <json@ietfa.amsl.com>; Wed, 16 Jul 2014 07:45:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 7s6gEckJv6eh for <json@ietfa.amsl.com>; Wed, 16 Jul 2014 07:45:15 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7653A1B28AB for <json@ietf.org>; Wed, 16 Jul 2014 07:45:15 -0700 (PDT)
Received: from Vostro3500 ([188.216.226.67]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LlUZz-1WWhvb40Ax-00bJZS; Wed, 16 Jul 2014 16:45:13 +0200
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: 'IETF JSON WG' <json@ietf.org>
References: <53B21F69.7010101@cisco.com> <53C066AE.9050104@cisco.com> <0c3601cf9fa6$6f79bb30$4e6d3190$@gmx.net> <CAHBU6iuZk8XU1ctYyLJzWBQ_5G7AKeMJn4X9NuaJxjhVu2+3Hw@mail.gmail.com>
In-Reply-To: <CAHBU6iuZk8XU1ctYyLJzWBQ_5G7AKeMJn4X9NuaJxjhVu2+3Hw@mail.gmail.com>
Date: Wed, 16 Jul 2014 16:45:08 +0200
Message-ID: <02d801cfa104$8cdda1f0$a698e5d0$@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQKov2vhk56OUbYXKcowgYH+SabU7AKM8BuiAidkqSIBftnvzpm+8Bzw
Content-Language: de
X-Provags-ID: V03:K0:kXGfeUFUoFZJUllgwlcrzK726B2hY19w2AK/DyQPlklz7i2UpgD J4b3D88ThDZxjD3l77R/HnitNMn8DQLIFFITgVKdi4804mMzfpL5aiDmmYK1AXL+uxpMwmg 3N0COOmUTn4CXHRTJMCn+Hc/cl4Kq4F7DyXAtjzhblHRGjRORM2KdfN04SuKxOAkembeffY aMLwgdmUKurfd0L+LVHlw==
Archived-At: http://mailarchive.ietf.org/arch/msg/json/J-afAQPSq6gtK1VZwU5ioYdmRxU
Cc: 'Tim Bray' <tbray@textuality.com>
Subject: Re: [Json] Working Group Last Call on draft-ietf-i-json-02
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: Wed, 16 Jul 2014 14:45:20 -0000

On Tuesday, July 15, 2014 4:40 PM, Tim Bray wrote:
> Is there an example of such a profile proving useful to application
> builders?  Haven’t encountered one myself but I assume there must be
> some out there.

We defined some profiles for JSON-LD [1] which make it possible for app developers to request the data to be serialized in a specific way (there are typically multiple ways to serialize the same graph).


> On Mon, Jul 14, 2014 at 1:58 PM, Markus Lanthaler <markus.lanthaler@gmx.net> wrote:
> On Saturday, July 12, 2014 12:35 AM, Matt Miller wrote:
> > Note that Working Group Last Call ends on Monday (07/14).  What has
> > been brought to the list to date is:
> >
> > * correction on the reference to RFC 7149 (should be RFC 7159)
> > * some discussion about a profile URL
> >
> > We want to hear from as many as possible, even if the comment is
> > "looks good to me".
> As already said, I think it would be a good idea to mint and register a
> profile URI. 

[1] http://www.w3.org/TR/json-ld/#iana-considerations


--
Markus Lanthaler
@markuslanthaler