IETF Logo Mail Archive

Re: [xmpp] Consensus Call on Adoption of POSH

Alexander Holler <holler@ahsoftware.de> Thu, 30 January 2014 10:55 UTC

Return-Path: <holler@ahsoftware.de>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 943481A042C for <xmpp@ietfa.amsl.com>; Thu, 30 Jan 2014 02:55:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.208
X-Spam-Level:
X-Spam-Status: No, score=0.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] 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 GCThN9UYoP_t for <xmpp@ietfa.amsl.com>; Thu, 30 Jan 2014 02:55:07 -0800 (PST)
Received: from mail.ahsoftware.de (h1446028.stratoserver.net [85.214.92.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1081A01BC for <xmpp@ietf.org>; Thu, 30 Jan 2014 02:55:07 -0800 (PST)
Received: by mail.ahsoftware.de (Postfix, from userid 65534) id 2A6CC423C293; Thu, 30 Jan 2014 11:55:03 +0100 (CET)
Received: from eiche.ahsoftware (p57B2361D.dip0.t-ipconnect.de [87.178.54.29]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ahsoftware.de (Postfix) with ESMTPSA id 5E825423C26F for <xmpp@ietf.org>; Thu, 30 Jan 2014 11:55:01 +0100 (CET)
Received: by eiche.ahsoftware (Postfix, from userid 65534) id D085A8CFD8; Thu, 30 Jan 2014 11:54:56 +0100 (CET)
Received: from [IPv6:feeb::c685:8ff:fe12:175d] (unknown [IPv6:feeb::c685:8ff:fe12:175d]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by eiche.ahsoftware (Postfix) with ESMTPS id 9DD218C441; Thu, 30 Jan 2014 10:54:24 +0000 (UTC)
Message-ID: <52EA2F60.4070103@ahsoftware.de>
Date: Thu, 30 Jan 2014 11:54:24 +0100
From: Alexander Holler <holler@ahsoftware.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Tobias Markmann <tmarkmann@googlemail.com>
References: <3E197582-9715-4FE9-AA4A-322FDC18F301@nostrum.com> <52EA1171.9010604@ahsoftware.de> <CAJ9A0VsVorYJu7sW_uevpakbZ0UeGQ0A+3NyystRB5=NJgmaLw@mail.gmail.com>
In-Reply-To: <CAJ9A0VsVorYJu7sW_uevpakbZ0UeGQ0A+3NyystRB5=NJgmaLw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: 7bit
Cc: Ben Campbell <ben@nostrum.com>, XMPP Group <xmpp@ietf.org>
Subject: Re: [xmpp] Consensus Call on Adoption of POSH
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 10:55:08 -0000

Am 30.01.2014 10:13, schrieb Tobias Markmann:
> On Thu, Jan 30, 2014 at 9:46 AM, Alexander Holler <holler@ahsoftware.de>wrote:

> The JSON[2] spec referenced by JWK doesn't mention comments at all. I guess
> the JSON you'll use in JWK simply can't include any comments.

Thats why I said POSH should define how comments shpuld be defined.
Almost any JSON parser provides a syntax for comments (e.g. using # or
//) and I'm unable to understand why comments in JSON aren't standardized.

And if I read the draft for POSH, e.g. setion 8. shows why one (human)
would like to have comments.

Regards,

Alexander Holler

v2.23.0 | Report a Bug | By Email