Changes between Version 6 and Version 7 of CustomFormatting

Timestamp:

Apr 27, 2012, 3:43:09 AM (12 years ago)

Author:

jesseeichar

Comment:

--

CustomFormatting

@@ -45 +45 @@
   * Format will have two services mapped to it (html and xml), with respective content types
   * Format services will be accessible by all users
- * RegisterXsl - Service for uploading an xsl file, it will require admin access
- * RemoveXsl - Service for deleting an xsl file, it will require admin access
+ * RegisterXsl - Service for uploading an xsl file or zip file, it will require admin access
+ * DownloadXsl - Service for downloading the zip file containing the XSL and associated resources, it will require admin access
+ * RemoveXsl - Service for deleting an xsl file and related resources, it will require admin access
 
-There will be an Administration User interface for managing the XSL files.
+There will be an Administration User interface for managing the Format bundles files.  Using the Administration user interface the  administrator (and only administrator) can upload either a single xsl file which is the formatter/transformer, or a zip file that contains a file called view.xsl and other resources required by the view.xsl.  
+
+The view.xsl will have the format (using the service metadata.formatter.xml?debug=true&id=<id>&xslid=<xslID> will show untransformed xml that can be used by transform): 
+
+{{{
+/root
+  / <metadata>
+  / schemas
+    ....
+  / strings
+    ....
+  / url
+  / viewURL
+  / viewStrings
+ }}}
+
+The schemas will have schema labels, codelists etc... (localised) and strings will be the normal localized strings as well.  
+
+If the uploaded zip file has a loc directory the files in loc/???/*.xml will be added to the xml under the viewStrings.
+
+The viewURL will be a path for loading resources like images and css files.
+
 
 === Backwards Compatibility Issues ===