The name of the folder could be prepended to each key so that the module can be easily imported into other taf files without conflicts.
Sub-folders of the exported folder would need to be included so we can organise our libraries into sections.
This module should be directly useable as a "Library", and should not contain any part of the standard library, map etc.
As the items in the folder will certainly reference the standard library, and possibly other library modules, the exported file should contain a "Requires" xml section that lists the name (and minimum version number) of every other library that it references.
If you import the module or add it to your library list, ADRIFT should check that all of the required libraries are available and each are either the requested version or a later version.
If not then it should give the error message "This module requires library x version y"
As these libraries may be updated more often than the ADRIFT version they will need a separate version number.
Perhaps a "LibraryVersion" integer variable in the exported folder which is automatically incremented whenever that folder is exported.