IETF Logo Mail Archive

Re: [xmpp] Consensus Call on Adoption of POSH

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Thu, 30 January 2014 12:25 UTC

Return-Path: <jhildebr@cisco.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 2B8B81A038E for <xmpp@ietfa.amsl.com>; Thu, 30 Jan 2014 04:25:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level:
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 2JwngPbrO6bt for <xmpp@ietfa.amsl.com>; Thu, 30 Jan 2014 04:25:50 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id B51D11A0207 for <xmpp@ietf.org>; Thu, 30 Jan 2014 04:25:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1052; q=dns/txt; s=iport; t=1391084747; x=1392294347; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=KtO469fgvEt2JTzToJ2+9IB4y4M7xxDfSoA18/7xBO8=; b=F7kipWXDjZeedcvWGqal7qlfKHvG9dmexQiWAoARIThtBNpFRcVt26W7 C0Gs7mzu10D0kYR7J4C2B50yd1zDB7yO4Z1hbaEQlMNxNQQeDv4zkoZ7c TcUNwfSI6pX65XEu6u8LiXST2dNHXf7n64WjLJhtAc2pKqVjOtkT3Tz1C U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFAH9D6lKtJV2Z/2dsb2JhbABZgww4V70fgQgWdIImAQEEAQEBNzQLEAIBCDYQJwslAgQBDQWIBQ3LXhMEjwIHhDgEmCiSH4Mtgio
X-IronPort-AV: E=Sophos;i="4.95,749,1384300800"; d="scan'208";a="16677683"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-4.cisco.com with ESMTP; 30 Jan 2014 12:25:45 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0UCPj7k019589 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Jan 2014 12:25:45 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.227]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Thu, 30 Jan 2014 06:25:45 -0600
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Alexander Holler <holler@ahsoftware.de>, Tobias Markmann <tmarkmann@googlemail.com>
Thread-Topic: [xmpp] Consensus Call on Adoption of POSH
Thread-Index: AQHPCyu6QFvRsDOa10+27Lcff5D0k5qdfdSAgAAHcACAABw/AIAAKkWA
Date: Thu, 30 Jan 2014 12:25:44 +0000
Message-ID: <CF1002CE.377C7%jhildebr@cisco.com>
References: <3E197582-9715-4FE9-AA4A-322FDC18F301@nostrum.com> <52EA1171.9010604@ahsoftware.de> <CAJ9A0VsVorYJu7sW_uevpakbZ0UeGQ0A+3NyystRB5=NJgmaLw@mail.gmail.com> <52EA2F60.4070103@ahsoftware.de>
In-Reply-To: <52EA2F60.4070103@ahsoftware.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.149.12.25]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <398E6480555B904E8F15F09B499AB462@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 12:25:52 -0000

(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.


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
>

v2.23.0 | Report a Bug | By Email