Let me try this one more time and hopefully I don't cause you further hair loss. <g>

I may have worded it wrong, but what I meant by "competing technologies" is that they, for the mostpart, do the same thing ... they serve the same purpose.

In other words, the only reason I would need to use both XSD & DTD is if different external partners had different needs for validation. If all I need to satisfy is our own internal requirements we can decide on one or the other (preferably XSD ... since it seems to be becoming the new standard?) but don't need both.

Sorry if I'm still missing the point. Hopefully I'm catching on here. Thanks for taking the time to help me understand this.

Rodd


>---
>It sounds like they're pretty much competing technologies where you use either one or the other but not necessarily both.
>---
>
>No, that's not what I meant to imply. Arrggh.
>
>I answered the way I did because most Xbase developers start using schema because they are required to, by an external partner.
>
>If you are defining the requirements here, there is no question about it: you should use XSD.
>
>You can*also* create a more-or-less equivalent DTD for the use of anybody who would like to have it and who does not yet support XSDs.
>
>The DTD is roughly equivalent to a translation of your published novel <s>. It serves as a reasonable facsimile for people who can't read the original.
>
>But your standard for your own internal validation as well as for publication of your messaging requirements would be the XSD.
>
>They are not "competing technologies". This is a question of chronology in the development of technology, not competition.
>
>HTH,
>
>>L<