Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2444110AB9 for ; Thu, 13 Feb 2014 09:03:42 +0000 (UTC) Received: (qmail 48738 invoked by uid 500); 13 Feb 2014 09:03:41 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 48705 invoked by uid 500); 13 Feb 2014 09:03:40 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 48696 invoked by uid 99); 13 Feb 2014 09:03:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Feb 2014 09:03:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ignisvulpis@gmail.com designates 209.85.160.176 as permitted sender) Received: from [209.85.160.176] (HELO mail-yk0-f176.google.com) (209.85.160.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Feb 2014 09:03:36 +0000 Received: by mail-yk0-f176.google.com with SMTP id 19so18483827ykq.7 for ; Thu, 13 Feb 2014 01:03:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=L/AVicJvwELklitEdGrcdNgOkul7YrFsozOahlEyWS4=; b=BRiL8ftofd3zkFdiToFwIruI0ESsJD/BLW85V862S9LKed69iIR8OUMrwH1X/MPu6W n8eO5GK5c8EQryVZlL0p+LK/LnCCXQz4mGGEqtUYI2suia0f9sla4DzXZLuI5GVB21t4 xFk20WfvhL3PTyorIb0Ox3x+b+MFP9fXbu8B8JVOujbsX4QYs0zRa9ny+FFIyJsMtR2E hJ1fiAgJHaDWKNijH05OtQXq0wkBS/BC2LXWNebbMApuyLrkgbsmHAO75lSH1F2dszQ4 4JUlxxImdhLvRaqU4FLm7vfbCz8UGSJlpDOeDhg4y/bvDPLSdFKKJxeSqt2Im2P4cn1w ppJg== MIME-Version: 1.0 X-Received: by 10.236.51.71 with SMTP id a47mr294132yhc.22.1392282196259; Thu, 13 Feb 2014 01:03:16 -0800 (PST) Received: by 10.170.77.194 with HTTP; Thu, 13 Feb 2014 01:03:16 -0800 (PST) In-Reply-To: References: <20140212225424.6606994.65608.11986@blackberry.com>

Date: Thu, 13 Feb 2014 10:03:16 +0100 Message-ID: Subject: Re: XML Namespaces From: Axel Nennker To: dev Content-Type: multipart/alternative; boundary=bcaec50dc618bc3a0204f245f51a X-Virus-Checked: Checked by ClamAV on apache.org --bcaec50dc618bc3a0204f245f51a Content-Type: text/plain; charset=ISO-8859-1 I would like to see CB-2606 https://issues.apache.org/jira/browse/CB-2606to be resolved soon. Moving from config.xml to config.json or package.json is a breaking change and rewards a major version number change. I would like to see phonegap buyin for that too if possible. 2014-02-13 5:10 GMT+01:00 Gorkem Ercan : > On Wed, Feb 12, 2014 at 10:42 PM, Andrew Grieve >wrote: > > > Sounds good to leave them in then. > > > > Why I ask now is for the and discussions / pull > > requests going on right now. > > > > We can call them: > > > > > > > There is also an element on the w3c specification (the default > namespace). You may want to reuse that one > > > > > And then start thinking about moving to JSON. > > > > I would not mind. > > > > > > > > On Wed, Feb 12, 2014 at 6:12 PM, Brian LeRoux wrote: > > > > > Ya I think my ambivalence stems from the same thinking Josh points out. > > I'd > > > love to move us to package.json personally. I think all agreed last > > meeting > > > that was solving problems we don't really have. > > > > > > And ultimately MANY downstreams are relying on both XML and namespaces > so > > > removing them will have be a noisy MAJOR update sort of thing. > > > > > > > > > On Wed, Feb 12, 2014 at 2:54 PM, Josh Soref > > wrote: > > > > > > > Andrew wrote: > > > > > Maybe I'm crazy, but I can't stand them. > > > > > > > > Most people can't > > > > > > > > > I don't think they add any value, > > > > > > > > They allow other products which are frozen ("released to an > audience") > > to > > > > interoperate in a defined manner with your software. And vice versa. > > > > > > > > If you don't care about that, then there isn't much reason to use XML > > > > (it's a horrible language). > > > > > > > > For the most part, I'd say that Cordova pretty much by definition > > doesn't > > > > care about this. Moving the file from www/ to www/../ broke existing > > > > software (amusingly including cordova serve). Cordova's view is > > basically > > > > that people will update their tools to work with the new version. And > > > > that's fine, but it isn't really a match for the promise of XML. > > > > > > > > > and are a cause of confusion. > > > > > > > > Absolutely > > > > > > > > > So... I'd like to: > > > > > A: Remove xmlns="http://www.w3.org/ns/widgets" from our config.xml > > > > template > > > > > B: Change xmlns:cdv="http://cordova.apache.org/ns/1.0" -> xmlns=" > > > > http://cordova.apache.org/ns/1.0" > > > > > C: Revert the commit that enforces the namespace to exist. > > > > > > > > > Does anyone hate this idea? > > > > > > > > I'm pretty sure we (BlackBerry) will have to do some work in response > > to > > > > this, but that isn't a big deal. > > > > > > > > If you're going to depart from the file format, why not switch to > JSON? > > > > > > > > > > > > > > http://blogs.msdn.com/b/visualstudioalm/archive/2014/02/06/json-debugger-visualizer-in-visual-studio-2013.aspxevenMicrosoftisoffering editors for it. > > > > > > > > Is there any value that you see in Cordova using XML? > > > > > > > > > > > > > > > > > > --bcaec50dc618bc3a0204f245f51a--