...
| Warning | ||
|---|---|---|
| ||
If the schema is changed to add a new required field then that field will still be required, even if data is imported using an older version of the schema. The use of legacy versions of the schema does not relieve the user of the requirement to honor all current business rules in the system. In general, interfacing systems should be upgraded within one year of the time when the schema they are using becomes superseded. |
For interfacing systems that export XML documents from eLandings, the user export feature on landing and production reports renders the XML document according to the current schema version. In the Spring of 2009 the eLandings system added a schema version preference to its user profile page. This allows users to specify a legacy schema version to use. This allows users to continue to export reports created with an older version of the schema while their system developers are enhancing their system to use the newer version of the reports.
...
XML is very much an IT standard, and many tools are available for reading and writing XML documents, and for extracting from XML documents the component data.
JAXB
The eLandings development team uses JAXB from Sun Microsystems for working with XML documents in Java.
Visual Studio
The Visual Studio integrated development environment from Microsoft includes tools to read an XML schema and provide programatic access to documents created from that schema.