I am not liking it. JBoss tools actually maintains a w3c xsd and maps the " http://www.w3.org/ns/widgets"; namespace to that XSD. Through this mapping tools can provide content assist, validation etc. When this namespace disappears we loose all the benefits. I would be OK with a planned replacement of the namespace as suggested on B as long as we can maintain an XSD for it.
Validation against an XSD is probably the main benefit of using xml on config.xml at least for me. On Wed, Feb 12, 2014 at 5:00 PM, Andrew Grieve <agri...@chromium.org> wrote: > Maybe I'm crazy, but I can't stand them. I don't think they add any value, > and are a cause of confusion. > > 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. > > This will allow us to add new tags & attributes to cordova.xml without > "violating" XML namespace rules. > > Does anyone hate this idea? >
