Re: [apps-discuss] draft-saintandre-json-namespaces-00 comments

Julian Reschke <julian.reschke@gmx.de> Thu, 10 November 2011 09:50 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 001E521F8B3B for <apps-discuss@ietfa.amsl.com>; Thu, 10 Nov 2011 01:50:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.376
X-Spam-Level:
X-Spam-Status: No, score=-104.376 tagged_above=-999 required=5 tests=[AWL=-1.777, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 t0pu77QNvlxa for <apps-discuss@ietfa.amsl.com>; Thu, 10 Nov 2011 01:50:54 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 0239421F8B00 for <apps-discuss@ietf.org>; Thu, 10 Nov 2011 01:50:53 -0800 (PST)
Received: (qmail invoked by alias); 10 Nov 2011 09:50:52 -0000
Received: from p5DCC32E8.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.50.232] by mail.gmx.net (mp071) with SMTP; 10 Nov 2011 10:50:52 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+aeEoBi0WafIheA5MtpT1bKM2eQacWCUgzEKp2Ig mWgWMDpc3N7CZ2
Message-ID: <4EBB9E75.9060405@gmx.de>
Date: Thu, 10 Nov 2011 10:50:45 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Dominik Tomaszuk <ddooss@wp.pl>
References: <4EB923CF.7080600@wp.pl> <566A345F-15CD-473B-8472-11EDF73A3862@vpnc.org> <4EBB9BE1.6020802@wp.pl>
In-Reply-To: <4EBB9BE1.6020802@wp.pl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] draft-saintandre-json-namespaces-00 comments
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 09:50:56 -0000

On 2011-11-10 10:39, Dominik Tomaszuk wrote:
> On 08.11.2011 18:05, Paul Hoffman wrote:
>>> I propose to give possibility to declare namespace.
>>
>> -1. Actually, -10. While somewhat useful for XML, namespaces have also
>> proven to cause many headaches for corner cases.
> I do not propose to reject Clark Notation and add declarative XML-like
> namespaces. My proposal was optional. If like long Clark Notation URLs'

The added complexity is there, even if it's optional.

> you can use it (advantage: easy processing). If you want short and
> non-repeated namespace you can declare it and use only reference
> (advantage: smaller and easier to read file).

Again, why would you want it? In XML, manual editing and recomposing was 
a use case; do you think the same it true for JSON?

> ...

Best regards, Julian