Changes between Version 2 and Version 3 of AjaxEditorControlsAndValidation

Timestamp:

Mar 23, 2009, 5:37:36 AM (15 years ago)

Author:

simonp

Comment:

--

AjaxEditorControlsAndValidation

@@ -20 +20 @@
 === Proposal Type ===
  * '''Type''': User interface and core functionality additions
- * '''App''': GeoNetwork
+ * '''App''': !GeoNetwork
  * '''Module''': DataManager (support new services), EditLib (enhancements), Metadata Services, Jeeves, metadata XSLTs
 
 === Links ===
- * Enhancements to Jeeves to support changes to file upload, XSD validation exception and passing validation errors to GeoNetwork
- * This has been available in the BlueNetMEST sandbox for some time - tested by users in the BlueNet project
+ * Enhancements to Jeeves to support changes to file upload, XSD validation exception and passing validation errors to !GeoNetwork
+ * This has been available in the !BlueNetMEST sandbox for some time - tested by users in the !BlueNet project
 
 === Voting History ===
@@ -50 +50 @@
 '''4.''' No single editor can satisfy all users. An example of a plug-in GUI that replaces both the javascript layer and the XSLT layer used for the editor is the current Xforms based editor proposal. This editor runs external to GN (in Orbeon Xforms) and uses GN services to retrieve selected metadata documents plus editing information from GN's XSD parser, combined as a metadocument. Currently, after this editor has finished with the document, it is stored external to GN. However, the document could be returned to GN using any of the services GN currently provides.
 
-Two services are planned (and available for development in the BlueNet MEST):
+Two services are planned (and available for development in the !BlueNet MEST):
 
  * xml.metadocument.get?uuid=<uuid> - a service to retrieve the initial XML document plus XSD based editing information (a metadocument)