N3 Editing improvements

This page describes some future improvements that should be made to the N3 editing system.

• Remove obsolete N3 editing code.  There are some java classes that are still around that are part of the first version of the N3 editing.  This system predated FreeMarker templating and lacked some other features. 
• Considering adding more places to insert custom 'hooks'.  The EditConfiguration has several places where custom java code can be added to implement unanticipated features. These are things like ModelChangePreprocessor and EditSubmissionPreprocessor. Consider additional places in the N3 edit process where custom hooks could exist.
• Add handling of multipart encoding for file uploads. It is not clear if this is a desirable improvement as it is unlikely that it will easily fit into the existing paradigm of substituting values into N3 templates. It may be useful to implement use of multipart parameters in custom hooks such as EditSubmissionPreprocessor or something similar.
• Configure EditConfiguration using RDF. Instead of defining the EditConfiguration values for a custom for in java as a EditConfigurationGenerator, consider defining them in RDF. This would enable the possibility of editing custom form definitions with the VIVO web interface.