ENH: Add Name property to XdmfArray and accessor functions for getting and setting the name.  If no name is specified it is not written to XML.  Modify test to verify reading and writing is working.

ENH: Modify XdmfWriter to insert XdmfArray content into most recently created child to allow for creation of multiple XdmfArray children.

ENH: Rename get/set ItemProperties for conciseness.  e.g. getAttributeCenter ---> getCenter .  This follows
what is done for XdmfArray (getType).

ENH: Add python wrapping for XdmfUtils and modify some swigisms to get reader working properly in python.

ENH: Allow XdmfArrayType to correctly read old xdmf files containing "NumberType" XML attribute, which is the same as DataType.

ENH: Begin implementing XdmfTopologyConverter.  Fix typo in XdmfArray that incorrectly initialized UInt32() type.

ENH: Move XdmfCore into its own subdirectory.  Move XdmfCore specific tests into core subdirectory and modify
swig wrapping to create two separate libraries (Xdmf and XdmfCore).

ENH: Split Xdmf into XdmfCore and Xdmf libraries in anticipation of NetDMF development.  Create a couple abstract base classes
in order to support generic reading from disk.

destructors to be publicly accessible.  Modify tests to work with new wrapping.

between XdmfArray and XdmfHDF5Controller a bit more robust.

location previously written to) and append (write data to end of previously written
dataset).

ENH: Modify ItemProperties to use shared pointers like the rest of Xdmf.  Modify swig wrapping to correctly
handle both non const and const shared pointers.

ENH: Add XdmfHDF5Controller so that heavy data can be written and released before light data is written.
Modify XdmfWriter to accept an XdmfHDF5Writer to use for heavy data writing and allow users to specify
XML file name to write to.  Add a test that performs the write release write release workflow.

was structured when the dataset was written and we want to fully separate dealing with light and heavy
data when creating Xdmf files.  This will allow us to move towards complete separation of
heavy and light data writing, a Create -> Write -> Release -> Create -> Write -> Release -> Write XML
workflow.

ENH: Add tests using new XdmfHDF5Writer exclusively.  Modify some methods in XdmfHDF5Writer to get everything working as expected.

ENH: Remove getHDF5Type from XdmfArray and move into XdmfHDF5Writer so all hdf5 interaction is isolated
in XdmfHDF5Writer.  Friend the XdmfHDF5Writer from XdmfArray so that it can access the variant to perform
typesafe operations on the data stored.  Variable macro generation didn't work so reverted the modified code.
We may just have to write ugly static New() methods when required.

ENH: Split heavy data writing from XdmfWriter into XdmfHDF5Writer.  This paves the way for the possiblity of having multiple
heavy data and light data writers.  Modify New() macro to accept parameters.

to write out the Xdmf graph.  Modify some random include statements for style.

ENH: Add pure virtual getItemTag method to XdmfItem working to return the tag (same as in XML terminology) for the specific item.

ENH: Add XdmfItemProperty to genericize properties attached to XdmfItems.  Add a pure virtual getItemProperties() method
to XdmfItem to force children to implement a way to retrieve properties.

ENH: Create a generic XdmfVisitor class and move writing operations to XdmfWriter.  Incorporate Loki library to perform asymmetric visitor operation (allows customizable behavior for eventual Xdmf / NetDMF library split).  Modify Loki
Visitor to work happily with boost::shared_ptr and modify swig wrapping to properly handle boost::shared_ptr inheritance.

ENH: Rename write() operation to accept() which is more consistent for the Visitor pattern.  Also, we can
do much more to our Xdmf graph structure than just write it using Visitor operations.