Why make Atom XSD friendly?
From mailing list – * Usually provides a terse and concise description of the vocaublary [relative to the prose of the spec] * Enables software to validate that XML documents being received from clients or servers actually conform to the vocabulary. This prevents issues like each application hacking up its own validator or “liberal RSS parser”. * Allows vocabulary to co-exist with technologies and tools that already support features specific to a schema language such as relational to XML mapping, object to XML mapping, directed editting, etc. From mailing list – RSS went down the schema-less path. In fact, DTD support was originally built-in and abandoned over time. Without a schema, the only way to validate your RSS was to build the Feed Validator. And we thank the authors for that. But there’s still hundreds of bad RSS files out there. Other people tried to solve the problem by writing 10k line C++/Java/Perl/PHP/Python libraries that wrote valid RSS for you. In fact, everybody wrote
