DOM backward compatibility
This page lists changes to the DOM API.
Purpose
Sometimes the DOM API changes in a way that prevents client applications from working properly when they upgrade to the latest DOM version. Although the DOM maintainers minimize API breakage as much as possible, sometimes it's necessary. In most API breakage situations, the client application no longer compiles.
This page is used to record any changes that require clients to modify their code to work with a newer version of the DOM.
- Note: The revision numbers given below refer to the COLLADA DOM Subversion repository on SourceForge.
Core API changes
This section tracks changes made to the core API.
IO plug-in changes
This section tracks changes made to the I/O plug-in system. If you don't use custom I/O plug-ins then these changes won't affect your application.
Revision 8805
In revision 8805 (7 May 2007), changes were made to the atomic type and meta attribute systems that require changes in I/O plug-ins. Responsibility for handling whitespace when reading a document has been moved from the I/O plug-in to the atomic types. This should simplify I/O plug-ins. See the changes made to daeLIBXMLPlugin.cpp in revision 8805 for more details.