John Gartner is a Portland, Ore.-based freelance writer and consultant. He is a regular contributor to Wired News and Technology Review.
Tips for Implementing an XML Publishing Solution
1. Build in extra time. Negotiating software licenses can take several months, especially if multiple vendors are involved.
2. Get on-site support. Questions invariably come up about producing stylesheets and data conversion, so pay for the technical expertise at the outset of project rather than dragging out the process.
3. Start with a single publication. It's better to get your XML processes perfected through one project instead of trying to enact a platform change on many fronts at the same time.
4. Pick the right project. Make sure that if your publication slips there will not be a ripple effect on other publications dependent on the data.
Snapshot: Lippincott Williams & Wilkins
Lippincott Williams & Wilkins (LWW) is a leading international publisher of professional health information resources for physicians, nurses, specialized clinicians and students. Nearly 275 periodicals and 1,500 books in more than 100 disciplines are published under the LWW brand, as well as content-based sites and online corporate and customer services. LWW is part of Wolters Kluwer Health, a leading provider of information for professionals and students in medicine, nursing, allied health, pharmacy and the pharmaceutical industry.
Wolters Kluwer Health is a division of Wolters Kluwer, a leading multinational publisher and information-services company with annual sales, as of 2004, of more than $4 billion and approximately 18,400 employees worldwide.
Larry Bryant, director of content management processes at Lippincott Williams & Wilkins. Converting to an XML-based publishing program cut several months off production time for creating a PDA version of the "Nursing Drug Handbook" and eliminated most of the $20,000 it spent annually on converting files to XML.