Difference between revisions of "XML Publishing Roadmap"

From PKP Wiki
Jump to: navigation, search
m (Protected "XML Publishing Roadmap" [edit=autoconfirmed:move=autoconfirmed])
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= XML Publishing Roadmap =
 
= XML Publishing Roadmap =
  
The PKP, in conjunction with RIT, and UNB ETC, will be extending our publishing support to include XML workflows. The goal is to have our software ingest XML (initially [http://dtd.nlm.nih.gov/publishing/2.3/ NLM Journal Publishing Tag Set Version 2.3] with Docbook, TEI and Erudit to follow) and render/display HTML and PDF.  
+
The PKP, in conjunction with [http://opl.rit.edu/ RIT OPL], and [http://www.lib.unb.ca/Texts/ UNB ETC], will be extending our publishing support to include XML workflows. The goal is to have our software ingest XML (initially [http://dtd.nlm.nih.gov/publishing/2.3/ NLM Journal Publishing Tag Set Version 2.3] with [http://www.docbook.org/ Docbook], [http://www.tei-c.org/index.xml TEI] and [http://www.erudit.org/documentation/doc_erudit.htm Erudit] to follow) and render/display HTML and PDF. [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3687 Bugzilla tracking entry for XML publishing]
  
 
== Goals ==
 
== Goals ==
Line 16: Line 16:
 
* Move XSL code from the plugin into the PKP WAL
 
* Move XSL code from the plugin into the PKP WAL
 
* Determine work required to refactor Molecular Vision XSL2.0 to XSL1.0
 
* Determine work required to refactor Molecular Vision XSL2.0 to XSL1.0
* Examine and refactor/merge XSL files for HTML generation from Monash, Open Medicine, Molecular Vision
+
* Examine and refactor/merge XSL files for HTML generation from [http://publications.epress.monash.edu/ Monash ePress], [http://www.openmedicine.ca/ Open Medicine], [http://molvis.cc.emory.edu/molvis/ Molecular Vision]
  
 
===Phase 2===
 
===Phase 2===
Line 27: Line 27:
 
===Phase 4===
 
===Phase 4===
 
* Extend/parameterize XSLs for HTML and PDF to produce customizable/SSH layout in addition to STM layout
 
* Extend/parameterize XSLs for HTML and PDF to produce customizable/SSH layout in addition to STM layout
 +
* Update XSL rendering to meet layouts developed by RIT
  
 
== Documentation ==
 
== Documentation ==
  
 
* Notes on [[Monash]] contribution
 
* Notes on [[Monash]] contribution
* Proposed XML rendering workflow: ('''TODO Image Upload''')
+
 
 +
<center>
 +
[[Image:Xml-rendering-current.jpg|500px|Current XML workflow]]
 +
[[Image:Xml-rendering-proposed.jpg|500px|Proposed XML workflow]]
 +
<br clear="all" />
 +
'''Current and proposed XML rendering workflows'''
 +
</center>
 +
<br clear="all" />
 +
 
 +
[[Image:Nlm-conversion.jpg|center|500px|Workflow for conversion to NLM DTD]]
 +
<center>
 +
'''Workflow for conversion to NLM DTD'''
 +
</center>
 +
 
 +
[[Image:Docbook-xslt.png|center|Sample XSLT customization process]]
 +
<center>
 +
'''Sample XSLT customization process'''
 +
</center>
  
 
== Feature List ==  
 
== Feature List ==  

Latest revision as of 11:06, 1 April 2009

XML Publishing Roadmap

The PKP, in conjunction with RIT OPL, and UNB ETC, will be extending our publishing support to include XML workflows. The goal is to have our software ingest XML (initially NLM Journal Publishing Tag Set Version 2.3 with Docbook, TEI and Erudit to follow) and render/display HTML and PDF. Bugzilla tracking entry for XML publishing

Goals

  • Support Science (NLM) and SSH (Erudit, Docbook, TEI) publishing formats
  • Produce both HTML and PDF rendering
  • Integrate, where appropriate, with: L8X (preview), OJS, and OMP

Roadmap

Phase 1

  • Bring XML galleys plugin up to date wrt. localization changes in OJS 2.x
  • Modify plugin to generate galleys from an uploaded "layout" file rather than "galley" file
  • Move XSL code from the plugin into the PKP WAL
  • Determine work required to refactor Molecular Vision XSL2.0 to XSL1.0
  • Examine and refactor/merge XSL files for HTML generation from Monash ePress, Open Medicine, Molecular Vision

Phase 2

  • Examine and refactor XSL files for PDF generation from Molecular Vision
  • Improvements to plugin/XSL classes for supporting XSL2.0 via Saxon

Phase 3

  • Extend the current xmlGalleys plugin (which already supports NLM) to support Docbook and TEI based on XSL from Monash, UNB, UVic

Phase 4

  • Extend/parameterize XSLs for HTML and PDF to produce customizable/SSH layout in addition to STM layout
  • Update XSL rendering to meet layouts developed by RIT

Documentation

  • Notes on Monash contribution

Current XML workflow Proposed XML workflow
Current and proposed XML rendering workflows


Workflow for conversion to NLM DTD

Workflow for conversion to NLM DTD

Sample XSLT customization process

Sample XSLT customization process

Feature List

Feature list broken down by level of difficulty

Procedural StepFeatureSimpleDifficult
1. Various XML to NLM Docbook->NLM transformation Requires proper XSL files

- have been provided by Monash

- can't handle Docbook 5
To support Docbook 5 we would have to substantially rework (or recreate) the files provided by Monash
TEI->NLM transformation Requires proper XSL files
- will be provided by UVic (will presumably handle Martin's TEIJournal modification; be back-portable to TEI P5)
 
Erudit->NLM transformation Requires proper XSL files
- possibly provided by UNB?
 
2. NLM to HTML/PDF galleys NLM->HTML transformation Requires proper XSLT 1.0 files

- Monash has provided XSLT 1.0 files

- Current plugin already using XSLT 1.0 files based on NLM's tools
XSLT 2.0 transformation

- UVic would prefer to work with XSLT 2.0 - Molecular Vision has provided XSLT 2.0 files

- XSLT 2.0 would require using Java to use a 2.0-compatible XSLT engine (ie. Saxon)
XML->XSL:FO->PDF Not possible Requires Java
- Sample XSLT 1.0 in current plugin