Re: [xmpp] Consensus Call on Adoption of POSH

Ben Campbell <ben@nostrum.com> Thu, 30 January 2014 15:16 UTC

Return-Path: <ben@nostrum.com>
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 611C31A0398 for <xmpp@ietfa.amsl.com>; Thu, 30 Jan 2014 07:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level:
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] 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 mHLtcvU-MM_V for <xmpp@ietfa.amsl.com>; Thu, 30 Jan 2014 07:16:17 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2241A1A038E for <xmpp@ietf.org>; Thu, 30 Jan 2014 07:16:17 -0800 (PST)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0UFG5p8076996 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 Jan 2014 09:16:07 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <52EA4A19.5060103@ahsoftware.de>
Date: Thu, 30 Jan 2014 09:16:04 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <BDA2A11C-8128-423B-92AC-2AA4D1485F4D@nostrum.com>
References: <3E197582-9715-4FE9-AA4A-322FDC18F301@nostrum.com> <52EA1171.9010604@ahsoftware.de> <CAJ9A0VsVorYJu7sW_uevpakbZ0UeGQ0A+3NyystRB5=NJgmaLw@mail.gmail.com> <52EA2F60.4070103@ahsoftware.de> <CF1002CE.377C7%jhildebr@cisco.com> <52EA4A19.5060103@ahsoftware.de>
To: Alexander Holler <holler@ahsoftware.de>
X-Mailer: Apple Mail (2.1827)
Received-SPF: pass (shaman.nostrum.com: 173.172.146.58 is authenticated by a trusted mechanism)
Cc: 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 15:16:18 -0000

(As [the other] Chair)

Alexander, do you support (or object to)  adoption of POSH as a working group item? 

Keep in mind that adoption doesn't imply the draft is complete or even correct, just that it's the best way forward. I expect we would continue this discussion, among other technical discussions.

Thanks!

Ben.

On Jan 30, 2014, at 6:48 AM, Alexander Holler <holler@ahsoftware.de> wrote:

> Am 30.01.2014 13:25, schrieb Joe Hildebrand (jhildebr):
>> (As chair)
>> 
>> JSON comments are *out of scope* for the XMPP working group.  Please take
>> your suggestions to the JSON working group if you think you have an
>> approach that can be adopted.
> 
> Hmm, so you are going to define or adopt a standard which lacks the possibility to use comments (either to provide human readable descriptions or as a way to quickly deactivate something)?
> 
> I would't call this out of scope. If you adopt POSH without providing (defining) a way how to add comments to the JSON definitions, this will be a serious flaw (in my humble opinion).
> 
> I'm not calling that the XMPP working group fixes that serious problem of JSON, I'm calling that they will add a sentence like "comments may start with a #) to the POSH standard or it's adoption if the working group is going to adopt it. You might call it a "variant" of JSON.
> 
> Anyway, I've just wanted to provide a maybe useful comment for POSH and don't want to discuss JSON.
> 
> Regards,
> 
> Alexander Holler
> 
>> 
>> 
>> On 1/30/14 11:54 AM, "Alexander Holler" <holler@ahsoftware.de> wrote:
>> 
>>> 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
>>> _______________________________________________
>>> xmpp mailing list
>>> xmpp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xmpp
>>> 
>> 
>> 
> 
> _______________________________________________
> xmpp mailing list
> xmpp@ietf.org
> https://www.ietf.org/mailman/listinfo/xmpp