Included AW's initial code in 'experimental' folder
AS's initial work on datanaming API
Various other changes to be commited now in case I'm away.
Some changes to names to differiencate Interfaces and Abstract classes from other classes.

A key thing I know that I've not thought through properly yet are all the issues around how a feature class or shapefile is renamed (ie syncing the renaming of the physical file or table, with the DataName Object).
Bit more tidying up of interfaces and abstract classes.
- IGeoDataListConnection, tidied up and commented
- AbstractDataNaming isNameValid function spelt out is puesdo-code
- Various other tidying up and making sure that abstract classes properly match the interfaces they claim to implenment etc...
First full attempt at implenmenting AbstractDataName.isNameValid()
plus various extra comments
completed, but not debugged AbstractDataNameClauseLookup expect for the isvalidDataThemeClause() function.
Two Factory classes added.
- Completed MDBDataNameClauseLookup, in read-only mode.
- Moved isNameValid() to AbstractDataNameClauseLookup and reworked parts of it.
- Changed IDataName isEditable() to isRenameable()
- tested testingCommandline
- lots of debugging
added in solution file
Version used for demo at March training weekend.
VS mockup of some user interfaces
Added a simple installer for the CLI testing tool
Corrected name for CLI_setup_v0.2.msi
Lots of changes (probably should have been half a dozen different commits - ekk
- Started a v1.0 project for the API
- Lots of changes to the experimental API
- changed int/long constants to enumerations
Added the DataNaming Constants (both as module and enumerations) to the v1.0 API
Added RenamingDataException to v1.0 api
Added the ErroreousDataNameException to teh v1.0 api
Added LookupTableException to v1.0 API