If you want to make an XSD (XML Schema) definition you can create an "any" schema element to allow anything within an element. That is how you can allow arbitrary xml within the schema definition.
I'm pretty sure you can do something very similar in a DTD. ----- Original Message ----- From: Schnitzer, Jeff To: [EMAIL PROTECTED] Sent: Tuesday, December 24, 2002 1:27 PM Subject: RE: [Mav-user] is there a DTD for maverick.xml? There isn't a DTD, but there is a reason for that. Much of the configuration DOM is interpreted arbitrarily by optional pluggable modules (instances of ViewFactory, TransformFactory, etc). You could create a DTD/XSD which would validate all the known modules, but it would break as soon as someone added a custom module with different configuration. All the common elements (that the Maverick core understands) are documented in the manual, but there comes a point in the XML tree where even the manual has to say "see the javadocs for the particular view/transform/etc factory you are using". With a DTD, can you define at point in the tree and say "stop validating here"? Jeff Schnitzer [EMAIL PROTECTED] -----Original Message----- From: Mougenot Sylvain [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 24, 2002 2:03 AM To: Liste Maverick (E-mail) Subject: [Mav-user] is there a DTD for maverick.xml? Is there a DTD for maverick.xml? I'm looking for an existing DTD for maverick.xml config file. Where can I find one? If there is no DTD I'll build one. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf [INVALID FOOTER]
