|
I like this article, because it shows some practicality (?). Let me add another side : editorial document point of vue.
I am a XML document professional, and the main use I have always seen on DTDs was editing guideline (and constraint). This is a way to ensure the document follow a certain model, therefore providing all the information you will need to use or publish this document afterward.
Now I know Schema were created more for Data exchange than document encoding. But I believe this is still a point to be looked upon : The schema is, for me, a way to guide a generic tool (editor, code generator, interface generator) for a suitable interaction with the user.
So more than validation (which I frankly don't care about that much : better produce a correct instance than refuse a incorrect one afterward), Schema should be seen as guidelines.
As for SOAP, I'd like someone to point out for me in which functionnal perspective it is better than REST-style interface...
|
Previous Message
