12 UI add support for platform urls

[OwenR-York]

1. Added support for the use of Platform URLs when configuring a Model.
2. Updated the Model Edit Dialogue, adding from Workspace creates a platform: URL.
3. Tests were added to cover URL processing and model loading under an Eclipse Project space.

For platform: URL support an EclipseRDFModel class should be used instead of RDFModel. The EclipseRDFModel has some additional processing added for converting incompatible platform: URLs to file: (both data and schema lists checked and converted). Processing of the Model URL lists (data & schema) is done using existing Java and Eclipse facilities, notably, Eclipse's runtime FileLocator, is used to resolve the location of a Model file on the system's file system.

With the platform: protocol support, changes to the Model Edit dialogue have been made. Adding model files from the Workspace (button) now adds a platform: URL instead of a file:. This should help improve the portability of launch configurations between systems.

To test the processing of the URLs an additional set of Junit tests have been added. This also required the addition of a small class that can create an Eclipse Project workspace for tests to be run. When testing under an Eclipse Project space any model files being accessed by Jena in the tests must be copied into the project workspace and the file system must be synchronised with the project, before the test is executed.

• Tests for the platform: URLs check the conversion of a good URL by loading and model then querying with Jena.
• A set of checks for failures to load a model because of a badly formed platform: URL is performed, and the errors report "no file path" which vaguely refers to the URL conversion process not finding the files at the given URL (i.e. platform URL doesn't point to a file).
• Expected to work file: '.' '/' URLs are tested to confirm they work, again a model is loaded and queried.