![]() |
||
|
February /March 2004 |
Volume 44, Number 4 |
|
||||||||||||||||
XML fundamentals for technical communicatorsThe new Professional Development series kicked off on November 15 with an XML training seminar by Richard Lander, a program manager in the Common Language Runtime group at Microsoft. Lander has been active in the XML field for many years and has developed many of the schemas used at Microsoft. After starting with a detailed description of what XML is (and isn’t), Lander focused on the advantages of implementing XML in the documentation process. XML is whatever you want it to beUsing detailed slides and code examples, Lander defined XML (Extensible Markup Language) and how it works. Although XML is a markup language like HTML, tags are defined by the user. This means that an XML content file must be described and interpreted by another file (a DTD or schema; see table below). Then the content file can be formatted for different output targets by using different style sheets (XSLTs).
Thus, XML is really a family of languages based on the XML syntax. Other languages include XPath (a syntax used in XSLTs), XForms (for creating Web forms), and XLink (allows XML elements to be linked so that content can be reused). Because XML is not a programming language, third-party applications are required to handle XML files and transformations. The list below includes software recommended by Rich Lander and by class participants. XML Editors:
XSLT Processors:
The benefits of authoring in XMLLander next described how XML authoring supports specific documentation goals. XML provides reusability, an important feature for document sets with large amounts of duplicate content. When multiple individuals are authoring or reusing content, using XML guarantees a consistent structure, and managing XML content with an application such as Visual SourceSafe® ensures source control.XML output is consistent and flexible (just add an additional XSLT for an additional output). XML can deliver highly customized content on demand using data-describing elements and metadata to enable complex filtering and searching. Implementation strategiesLander concluded the seminar with recommendations for successfully implementing XML technology into the documentation process. A DTD or schema must be chosen based on a well-defined content model. Will the DTD or schema have a strict or loose format; a content-based or format-based style? Other considerations include the types and requirements of deliverables and adequate in-house technical support. Finally, writers and editors must learn to use XML tools and embrace a new way of writing.Resources:Web sites
Books(recommended by Rich Lander)
Other books(thanks to Diane Boos)
|
||||||||||||||||
|
||||||||||||||||
|
© Copyright 2003 |
||||||||||||||||