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 F37D2105C1 for ; Wed, 10 Jul 2013 16:16:08 +0000 (UTC) Received: (qmail 92381 invoked by uid 500); 10 Jul 2013 16:16:08 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 92354 invoked by uid 500); 10 Jul 2013 16:16:08 -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 92346 invoked by uid 99); 10 Jul 2013 16:16:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 16:16:08 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cmarcelk@gmail.com designates 209.85.219.53 as permitted sender) Received: from [209.85.219.53] (HELO mail-oa0-f53.google.com) (209.85.219.53) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 16:16:04 +0000 Received: by mail-oa0-f53.google.com with SMTP id k14so10006962oag.12 for ; Wed, 10 Jul 2013 09:15:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=3pD74+I1XCtbvDzJZ8WBbvfRig7583qcbMIiO/2+LLY=; b=inqXsydYpC/PmzEFDKZX06XxlC4AEd4O/ARlpEzmm/3APjBrjq6jst7LQShf8CxRIZ +honMnkq2tnB5KPU3gBqdplzhlfnuZP5CNGhWqrF5zVjg0g3sHjaZbRAVni71sDJbsL6 bVWU2YsyA/xRqlbjKplHNPw/iTQzs4oJyyXebrI7BAG1cCZENgSBaypzSUE0DgK+R5Yo HESNFuzFkCykcm8Z1Am4cq62W/HpNMjPkDMWjKccTdQql5/JY0VGCkgl/JANpnzfPIcx GBmt3c1bV/DfbbqMjcUZyx73ASCVwrmgo3BrrDgNzcKf3CpfRkNTQ9Gk7XOY9pYNQsqP 34OA== X-Received: by 10.182.214.39 with SMTP id nx7mr28635831obc.20.1373472943551; Wed, 10 Jul 2013 09:15:43 -0700 (PDT) Received: from marcelk-macbook.raleigh.ibm.com ([129.33.49.237]) by mx.google.com with ESMTPSA id rs4sm44230843obc.10.2013.07.10.09.15.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 09:15:42 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: XML schema for plugin.xml and config.xml? From: Marcel Kinard In-Reply-To: Date: Wed, 10 Jul 2013 12:15:41 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <801D34E7-6145-4487-81C0-46D9FF524741@gmail.com> References: <84E61268-BC1E-438F-AF0D-9032CF7D473B@gmail.com> To: dev@cordova.apache.org X-Mailer: Apple Mail (2.1508) X-Virus-Checked: Checked by ClamAV on apache.org On Jul 9, 2013, at 9:38 PM, Michal Mocny wrote: > Seriously though, if the schema is changing isn't that all the more = reason > to support validation so devs can get early confirmation? That is exactly my thought. Updating the xsd is relatively easy, and = it's just one file per schema. Handling a new attribute or element is = just a few lines of work. On Jul 9, 2013, at 5:56 PM, Brian LeRoux wrote: > =85there is pretty strong argument brewing to move to JSON. If that is going to happen, it would be post 3.0, because only 9 days = are remaining, right? I can see why JSON would be attractive, but that would also be forcing = plugin authors to re-do their config file that they recently created for = 3.0. Potentially we could use XSL to transform config.xml to config.json = automatically for a bridge period. I'll start playing with an XSD and put it out for review.