 |
It wasn't a big surprise that most people (56%) indicated that Re-creating / re-formatting the same information for multiple outputs was their biggest issue. This issue has been a significant reason why people look at Single Source Publishing (from one source of content, automatically publish or generate your documentation to print, help, web, presentation, XML, or any other output format without having to modify or make different versions of your content) as a solution. Most organizations look to utilization of XML technology to implement single source publishing.
Other reasons to consider an XML implementation include:
Separation of Content from Format
Traditional documents combine words and pictures with format and layout. In XML, content and format are separated and stored independently so they can be combined in different ways to produce different types of documents in different output formats.
Translation into Other Languages
Reduce the time and cost of translation into other languages by translating re-used content once and have it automatically reflected wherever it is used.
Reduce Cost
XML improves efficiency of creation, maintenance, and management of documentation content. Time taken to produce a page through traditional authoring tools can be halved with XML.
Reduce Time-Market
Reduction in production times are achieved through more efficient use of resources, re-use of content, controlling standards, eliminating duplication, and effectively managing creation, localization, and publishing processes.
Competitive Advantage
Lower overall costs and increased customer satisfaction through consistent, accurate documentation of all types, resulting in fewer calls to customer support. These advantages are achieved through providing the right information, at the right time, in the right format.
|
2.
In evaluating potential improvements to how you handle information,
please rate the importance of these issues: (check one per row) |
|
|
|
 |
Very Important |
Somewhat Important |
Not Important |
| Ease of maintaining information |
 |
|
90% |
10% |
0% |
| Using Microsoft™ applications |
 |
|
32% |
60% |
8% |
| Review and approval process |
 |
|
69% |
29% |
2% |
| Reusing content across applications |
 |
|
65% |
33% |
2% |
| Distributing information to many outputs |
 |
|
47% |
47% |
6% |
| Solving the issues sooner vs. later |
 |
|
78% |
20% |
2% |
|
|