Re: package.xml 2.0 dilemma

Greg Beaver wrote:

package.xml 2.0 currently has a specific tag ordering. I made this choice because XSchema has only three kinds of ordering indicators, sequence, choice and all. sequence allows very fine-grained control over elements, choice says "any of these elements can occur here" and all says "any of these elements can occur in any order". Opinions?

I think you should leave it as a sequence. There is no technical reason to allow flexible ordering. Keeping a strict order makes the files more readable. The package name should be at the top of the file so that I don't have to go searching for it. The same thing applies to the change log. If it is always at the bottom, I can easily find it. Think of the strict sequencing as a forced coding standard for package files. PEAR has other standards like this. Just try committing something to CVS with an @access tag before an @param tag. The CS police will be on you before the message makes it to the mailing list. We have very strict standards to make our code readable why should we treat package file XML any differently? -- Scott Mattocks scott@crisscott.com http://www.crisscott.com