Maintaining a DTD/XML driven client server environment
Author: firstname.lastname@example.org (Iain Sharp)
When we're setting up a DTD/XML client server application, the situation is relatively easy. We can use load fields to populate the DTD.
But, let's say we're six months down the line, we've multiple DTDs set up for multiple different scenarios (particularly on tables viewed as 'intersection entities') and we want to add a field or two.
How do you keep your DTDs in line? Missing this field can have massive complications if the entity is a down entity on the service (it blanks out the pre-existing data on update to that occurrence...), and there's no way of specifying 'all the fields in this entity'.
Is there a tool for identifying where DTDs are obsolete?