Please explain. :)
I didn't image that the Schema would change for each build file. (Unless they define new taskdefs) I also don't expect that you would want to keep the instance hierarchy data for any specific build file in a schema. My understanding of the XSD was really to help define tasks. Not the order of them in the build file. -----Original Message----- From: Ian MacLean Subject: Re: [nant-dev] XML Schema Def (XSD) Gerry Shaw wrote: [snip] >* Tasks have access to the XmlDocument object that represents the build >file. >* You might want to do some really funky stuff in the future, exporting >the .xsd is an obvious feature. >* No special code needs to change inside nant. > Why not have the element class have a default implementation based on the Attributes and if a task chooses to override this for some reason it can. that way each element class can specify how to validate itself (by element class I mean those derived from class Element ) It would seem a bit weird to me to have the schema changing based on different build files that use the same tasks. Or am I missing somthing Or are you thinking of imposing the order of the document instance in the schema ? Ian > _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
