XML Workflow Summary

From AAUPwiki
Jump to: navigation, search

Contents

Overview and case study

As part of an ongoing project of the AAUP Design & Production Committee to research and outline a digital workflow that facilitates production of scholarly content in several delivery formats, Terri O'Prey (Princeton UP) has developed an XML Workflow Summary word document. This is an outline of best practices for XML workflow based on the Princeton experience of transitioning to an XML-first workflow using the Scribe Well-Formed Document Workflow. This outline gives a brief history and description of XML and its value as a flexible, stable, editable format to store and transport data. It offers specific tips in manuscript processing that, while described relative to Scribe's DTD, can be applied in other workflows.

Products

XML-first

  • Open Typesetting Stack (formerly the PKP XML Parsing Service): (sourcecode, beta site) -- can be used to convert from Word documents

XML-middle

  • eXtyles – a set of related products supporting composition in Word and subsequent conversion to XML. Can be used with Typefi Publish to import into InDesign. One implementation is P-Shift, a service from the University of Toronto Press that allows you to pay them to carry out production using these tools.
  • Scribe Well-Formed Document Workflow – composition in Word, then conversion to XML, then import into InDesign. Scribe also offers service where you pay them to carry out production using these tools.
  • Typesetera – composition in Word, then automatic creation (using XML) of sample, student, and scholar editions in PDF and e-book formats

XML-last

vendors

  • Newgen
  • BiblioVault

tools

Some of these and others are listed with short annotations on the tools section of "Jailbreaking the PDF" website. The convenor of that workshop reported on jats-list that Crocodoc became available after the workshop, and that he has found it to be more reliable than the others.

HTML-based workflows

Many people feel that for publishing you can get nearly all of the benefits of XML but just relying on clean HTML code.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox