Re: Relaxing package.xml v2 XSD

Philippe Jausions wrote: > Hi Brett, > > Brett Bieber wrote: >> Hey Philippe, >> >> On Thu, May 1, 2008 at 11:09 AM, Philippe Jausions >> <Philippe.Jausions@11abacus.com> wrote: >>> Hi, >>> >>> The current XSD for package.xml version 2 >>> (http://pear.php.net/dtd/package-2.0.xsd), doesn't allow simple nested >>> folder structures without files in them. > > [...snip...] > >> And a couple solutions...? >> 1. relax the schema >> 2. validate package.xml and reject releases that do not validate..? >> >> Given that we have so many releases out in the wild that do not >> validate, I think our efforts should focus on relaxing the schema. >> >> The numbers should make it obvious that strict validation does not >> matter to the current PEAR installer. But, this will change with >> Pyrus, as strict validation for package files is checked using >> DOMDocument::schemaValidate > > A lot of copy/paste is done when creating a package.xml file, so > depending on whether the original is correct, so most likely will be the > copy. > > I think checking the validity of the package.xml file at packaging time > is the best time to do it, i.e. "pear package-validate package.xml" > should inform the developer of all the issues and should refuse > packaging the package if the schema validation fails. It currently > partially catches gross errors, such as no <contents> element. Pyrus validates package.xml using the XSD. > Are there other dev out there having issues with, or are aware thereof, > the current XSD 2.0? > > So, what's the next step? RFC? Hell no :). This is a technical issue, not a political one. As long as the new XSD validates existing package.xml, there is no issue. Greg