- Corporate publishing environments produce large volumes of content across many languages and formats under extreme budget constraints, requiring high levels of automation and reuse of content components. - Component content management systems (CCMS) break documents into reusable text and media components, enabling more efficient management of evolving content and easier composition of new publications. - Lessons from corporate publishers include using a simple common schema, minimizing exceptions, and keeping author interfaces simple while providing robust workflow support for distributed teams.

1. Component Content Management Systems: Lessons Learned from Corporate Publishing Marcus Kesseler StartWithXML – The British Library – London – 2009-09-02

4. What we can learn from Corporate Publishing

7. The Solution for Corporate Publishing: Component Content Management Systems (CCMS)

10. Publication of Evolving Content without CCM: Publication A 1st Edition Publication A 2nd Edition Editing

11. Publication of Evolving Content with CCM: New Component Changed Component: In a CCMS this is simply adds a newer version to the content version stack of the same component Components Unchanged Component: In a CCMS this is not a copy but a reference to the original, unchanged component Editing Publication A 1st Edition Publication A 2nd Edition

12. Composition of new Publications with CCM Publication A Composition (and Editing) Publication B Publication C Publication D Publication E New components specific to new publication

13. Functional Architecture of the IT Infrastructure for a Publishing House

14. Functional Solution Architecture Text and Media Editors MS Word, XML Editor, Graphics Programs CCMS Publication Tools XML Export, InDesign, 3B2, XSL:FO Render Engine, Ebook Format Exports Publisher‘s E-Business Portal Interface to ERP System Workflow Engine (optional) Workflow Server

15. Functional Solution Architecture Upstream Content Acquisition Dataflow Author[s] CCMS Word Files XML + Media Files Editor MS Word XML Editor (?) Author[s] XML + Media Files MS Word XML Editor (?) DOC to XML conversion

16. Functional Solution Architecture Downstream Content Publishing Dataflow CCMS Layouter Layout Programmer Adobe InDesign Quark XPress Automated Layout Engine (XSL.FO, 3B2, etc) XML-based Formats Export Needed for each single publication Needed only for each publication type Handcrafted Layout (PDF) Automated Layout (PDF) HTML, XML All Ebook formats (Epub, Moby, etc)

17. Case Study: Pilot´s On Board Route Manual

19. Productivity Benefits Editors Jan 2008: 4 Oct 2009: 3 Customers (Airlines) Jan 2008: 20 Aug 2009: 40 Mid 2010: 80-100 (Plan) Generated Media Jan 2008: Just print using laborious DTP-based process (Interleaf) Aug 2009: 1. Print automatically via ST4 / Flyer-Ex 2. HTML (day / night) via ST4 incl. Search 3. XML for GPS-filtered content (2010) Time needed per Jan 2008: Editing 2h, Layout 4h, QA 30min = 6,5h update Aug 2009: Editing 2h, Layout 1min, QA 30min = 2,5h

20. CCMS GUI

21. Editor: XMetaL (Tag View)

22. Editor: XMetaL (XML View)

23. PDF Publication

24. HTML Publication (day view )

25. HTML Publication (night view)

26. Lessons Learned

30. Thank you for your attention! Questions? [email_address] / http://www.schema.de/en