Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of jbondc@gdesolutions.com
 designates 207.46.163.153 as permitted sender)
From: Jonathan Bond-Caron <jbondc@gdesolutions.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Subject: RE: XML Namespaces
Thread-Topic: XML Namespaces
Thread-Index: AQHPKD392W+BJWekVk6pXYQrHku3upqyMkuggAEPZwCAAAFP8IAB4uoAgAF/avA=
Date: Sat, 15 Feb 2014 18:34:46 +0000
Message-ID: 
 <5786ff99cd2249b5ac5f21062393c7c1@BN1PR07MB135.namprd07.prod.outlook.com>
References: 
 <CABiQX1UCDv0QLA37Js_rKQfSP6LhasGAgUMDtVW7BY8_AvcSiQ@mail.gmail.com>
 <625597b81d584977ba20656fd09466bd@BN1PR07MB135.namprd07.prod.outlook.com>
 <CABiQX1WHQhe8Q06mKmyEwZL56khbn+oh33DHspH2i49Z=XrfGQ@mail.gmail.com>
 <aacffd78d09042599bba508f2238603d@BN1PR07MB135.namprd07.prod.outlook.com>
 <53BB8282-24D2-40BD-8988-A7AA5E4660BC@gmail.com>
In-Reply-To: <53BB8282-24D2-40BD-8988-A7AA5E4660BC@gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On Fri Feb 14 02:30 PM, Marcel Kinard wrote:
>=20
> On Feb 13, 2014, at 10:04 AM, Jonathan Bond-Caron
> <jbondc@gdesolutions.com> wrote:
>=20
> > IBM most likely would prefer XML for the XSD & tooling...
>=20
> Not necessarily. Schema validation is nice, but XML for the sake of XML d=
oesn't
> make sense. What makes more sense is following standards where reasonably
> possible. But if the widget spec is deprecated and we are making a consci=
ous
> decision to abandon it, then the leaning for XML goes away. Given the aud=
ience
> of web devs, and the use of json config in other places, my preference wo=
uld be
> for json config.=20

Great to have your opinion, my guesswork was that for a plugman based proje=
ct on android for example, xml would be preferred.

>=20
> > Note about xml vs. json config, Cordova could support both.
>=20
> Cordova could, but that seems to me like overkill. If someone really want=
s xml,
> how about providing an xslt that translates the xml to json, so they can =
author in
> xml and Cordova could read json. But even that sounds like overkill too.

It turns out there's a great node lib called 'xml2js', the code to do this =
is pretty simple:
https://github.com/jbondc/cordova-labs/blob/master/cordova-lib/test.js

https://github.com/jbondc/cordova-labs/blob/master/cordova-lib/config.ts
https://github.com/jbondc/cordova-labs/blob/master/cordova-lib/config.js

So the idea here is:
- config.xml, config.json
- plugin.xml, plugin.json=20

Would both be supported, with json being looked for first.