DITA Top oder Flop - Zindel AG
DITA Top oder Flop - Zindel AG
DITA Top oder Flop - Zindel AG
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>DITA</strong> als Strukturierungsmethode: <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong>?<br />
Februar 2008 V1.0<br />
Dieter Gust, itl <strong>AG</strong><br />
http://www.itl.eu
Wer spricht da?<br />
Dieter Gust<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
22 Jahre im Bereich Technische<br />
Dokumentation tätig<br />
Technischer Redakteur<br />
Dozent für technische Dokumentation<br />
Trainer für Publishingsysteme<br />
FrameMaker + Word<br />
(Ventura, PageMaker)<br />
Spezialist für PDF-Produktionen<br />
Information Architect:<br />
Desktop Publishing,<br />
Content Management,<br />
Übersetzungsprozesse<br />
Prokurist bei itl<br />
2
<strong>DITA</strong> – <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong>?<br />
<strong>DITA</strong> ist für technische<br />
Dokumentation ist aus USamerikanischer<br />
Sicht der Hype<br />
schlechthin.<br />
<strong>DITA</strong> ist top, <strong>DITA</strong> ist der<br />
Weltstandard für technische<br />
Dokumentation<br />
Vorteile<br />
] Standard-XML-Anwendung<br />
(keine Neuerfindung des Rades)<br />
] DTD +Tools „for free!“ inklusive<br />
Weiterentwicklung!<br />
] <strong>Top</strong>ic-Orientierung = ideal für<br />
Wiederverwendungs-Konzepte<br />
] Toolhersteller bieten out-of-the-<br />
box <strong>DITA</strong>-Lösungen<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
Praktische Erfahrung des Referenten<br />
<strong>DITA</strong> hat eine große Zukunft, aber:<br />
] Die Umsetzung eines Standards ist<br />
nicht automatisch billig, sondern<br />
zunächst sogar teurer, wenn man sich<br />
dem Standard erst anpassen muss.<br />
] Nomenklatur erzeugt Emotion und<br />
umgekehrt: Man muss <strong>DITA</strong> mögen.<br />
] <strong>DITA</strong> ist 2008 als Gesamtlösung nicht<br />
ausgereift<br />
] <strong>DITA</strong>-ROI-Berechnungen definieren<br />
oft Einsparpotenziale für<br />
Prozessschritte, die mit <strong>DITA</strong> nichts<br />
zu tun haben.<br />
] Wer hauptsächlich Dokumente für<br />
PDF/Papier erzeugt, für den kann<br />
<strong>DITA</strong> zum <strong>Flop</strong> werden.<br />
3
Very Quick Start: <strong>DITA</strong> Darwin Information Typing Architecture (1)<br />
Darwin<br />
] based on principles of<br />
inheritance and specialization<br />
Information Typing<br />
] supports topic-based<br />
methodologies<br />
Architecture<br />
http://dita-ot.sourceforge.net/<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
] expresses design principles for<br />
creating and delivering<br />
information-typed topics<br />
4
Very Quick Start: <strong>DITA</strong> Darwin Information Typing Architecture (2)<br />
<strong>DITA</strong> <strong>Top</strong>ic Inhaltsmodell<br />
<strong>Top</strong>ic Title<br />
<strong>Top</strong>ic Metadata<br />
<strong>Top</strong>ic Body<br />
Related Links<br />
Embedded <strong>Top</strong>ics<br />
<strong>Top</strong>ic title<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
Short description of the topic –<br />
optional but recommended<br />
Prolog<br />
(metadata about the topic)<br />
<strong>Top</strong>ic body<br />
] Sections, paragraphs, lists,<br />
tables, images, semantic<br />
elements<br />
Related Links<br />
(Embedded - nested - <strong>Top</strong>ics)<br />
5
<strong>DITA</strong><br />
<strong>Top</strong>ic<br />
Very Quick Start: <strong>DITA</strong> Darwin Information Typing Architecture (3)<br />
Dita Maps<br />
<strong>DITA</strong><br />
<strong>Top</strong>ic<br />
<strong>Top</strong>ic Reference<br />
<strong>Top</strong>ic Reference<br />
<strong>Top</strong>ic Reference<br />
(Sub-<strong>Top</strong>ic) <strong>Top</strong>ic<br />
<strong>Top</strong>ic Reference<br />
(Sub-Sub-<strong>Top</strong>ic)<br />
<strong>Top</strong>ic Reference<br />
<strong>DITA</strong><br />
<strong>Top</strong>ic<br />
<strong>DITA</strong><br />
<strong>Top</strong>ic<br />
<strong>DITA</strong><br />
<strong>Top</strong>ic<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
A heading doesn’t have to have a<br />
topic<br />
Title and properties can be<br />
assigned in the map<br />
The map organizes a set of topics<br />
in a hierarchy<br />
A topic can appear multiple times<br />
in the hierarchy<br />
6
Very Quick Start: <strong>DITA</strong> Darwin Information Typing Architecture (4)<br />
<strong>DITA</strong> Open Toolkit<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
7
Very Quick Start: <strong>DITA</strong> Darwin Information Typing Architecture (5)<br />
<strong>DITA</strong> 1.1 Elemente<br />
11 <strong>Top</strong>ic elements (topic , title, body<br />
section, example, related-links …)<br />
2 Concept elements (concept, conbody)<br />
12 Reference elements (reference, refbody<br />
elements …<br />
25 Task elements (task, taskbody, prereq,<br />
steps, cmd<br />
3 Glossentry elements<br />
29 Body elements (p, ol, ul)<br />
10 Table elements<br />
27 Prolog elements<br />
5 Related links elements<br />
11 Miscellaneous elements (dita,<br />
indexterm, unknown<br />
6 Specialization elements<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
6 Typographic elements (b,i, sub, sup<br />
25 Programming elements<br />
8 Software elements<br />
5 User interface elements<br />
4 Utilities elements (imagemap …)<br />
3 Indexing group elements<br />
10 Map elements<br />
2 Map group elements<br />
27 Bookmap content elements<br />
33 Bookmap metadata elements<br />
27 xNAL domain elements<br />
7 <strong>DITA</strong>VAL elements<br />
= 298 Elemente<br />
+ viele Attribute<br />
8
<strong>DITA</strong> Pioniere<br />
<strong>DITA</strong> Standard – Committee and Public Adopters<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
9
<strong>DITA</strong> kann kein <strong>Flop</strong> sein:<br />
Aberdeen Group Report und andere Stimmen<br />
Aberdeen Group Report<br />
„Publishing Technical<br />
Communications to a Multi-Channel<br />
World“.<br />
] „Die Nutzung von <strong>DITA</strong> ist unter<br />
den branchenführenden<br />
Unternehmen doppelt so hoch.<br />
Mit <strong>DITA</strong> können<br />
Produktdokumentationen<br />
präziser verfasst, deren Nutzung<br />
verbessert und Inhalte<br />
ortsunabhängig von Firmen<br />
wiederverwendet werden.<br />
] Ein empolis-Kunde berichtete<br />
kürzlich, dass bei einigen<br />
Produktlinien ganze 78 % der<br />
Themen und Grafiken in mehr als<br />
einer Produktdokumentation<br />
genutzt werden.<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
JoAnn Hackos of Comtech<br />
Services<br />
] "Companies often spend tens if<br />
not hundreds of thousands of<br />
dollars developing custom DTDs,<br />
yet they often turn out to be<br />
inflexible and costly to maintain,"<br />
says consultant JoAnn Hackos of<br />
Comtech Services.<br />
] "<strong>DITA</strong> promises enormous cost<br />
savings because it provides a<br />
ready-made set of DTDs that<br />
offers all the advantages of a<br />
standard."<br />
10
Best Practice Autodesk<br />
The project<br />
] Autodesk is five years into an ambitious<br />
project to reengineer and retool all of their<br />
mechanisms for creating and managing<br />
product support content.<br />
New Sytem and New Processes<br />
] They have made the transition from<br />
unstructured content to XML-structured<br />
content, and they have established a<br />
centralized system for managing their<br />
content, managing their workflow, and<br />
managing their and managing their<br />
processes for translation and localization.<br />
Localization<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
] AutoDesk is enjoying significant savings<br />
Desktop publishing and production of the<br />
various documents.<br />
] The new system replaced manual, time-<br />
intensive tools with automated XSL and<br />
XSL-FO scripts that take the <strong>DITA</strong>-encoded<br />
content and produce the final output<br />
automatically. For example, a single-<br />
chapter can be produced in 2 minutes<br />
using the automatic tools, and a full, 3000-<br />
page Help product can be generated in 45<br />
minutes.<br />
Reuse of the core AutoCAD documentation<br />
] The team is able to reuse the core platform<br />
content with only slight transformations.<br />
They are also able to share and modify<br />
content between the various vertical<br />
applications with minimal effort, thereby<br />
gaining further savings.<br />
11
Best Practice BMC<br />
While <strong>DITA</strong> provides a solid base,<br />
we still need to "make it fit" our<br />
BMC Software information<br />
models, meaning we have to<br />
develop numerous specializations<br />
for each information type.<br />
<strong>DITA</strong> is a solid architecture that<br />
offers a great head start, but it<br />
takes significant effort to make<br />
<strong>DITA</strong> work for a specific<br />
implementation.<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
One of the most difficult parts has<br />
been learning how to model the<br />
information and then learning how<br />
to write the specializations in <strong>DITA</strong><br />
to map the model. Learning has<br />
been the trickiest because we had<br />
to learn both modeling and how to<br />
code the model.<br />
Information modeling should<br />
focus solely on content,<br />
independent of technology.<br />
Information modeling takes an<br />
iterative approach and, thus,<br />
requires a significant amount of<br />
time. Factoring sufficient time into<br />
the project plan is essential.<br />
12
Best Practice Texas Engineering Extension Service<br />
The structured authoring<br />
environment delivers the added<br />
advantage of enabling TEEX to<br />
better leverage XML content in its<br />
Siberlogic CMS. For example,<br />
blocks of information in XML can<br />
be used and reused at the<br />
paragraph level, allowing<br />
curriculum developers to take<br />
frequently used safety processes<br />
and guidelines and insert them<br />
automatically into the appropriate<br />
pages.<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
“This is a tremendous efficiency<br />
gain for our staff,” says McCallie.<br />
“Now, we can revise and reuse<br />
content easily across manuals,<br />
and then automatically insert it<br />
everywhere it needs to appear.<br />
The efficiencies could accelerate<br />
creating manuals by as much as<br />
25%.”<br />
13
Best Practice Nokia<br />
Business objectives<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
] Reduce translation costs by 10-<br />
20% in the first year of<br />
implementation through re-use<br />
savings<br />
] Improve the consistency of the<br />
content delivered to customers<br />
through collaborative writing,<br />
single-sourcing and re-use<br />
] Reduce the cost of maintaining<br />
and managing DTDs and<br />
transformations<br />
14
Best Practice Symantec Corporation<br />
Pleasures<br />
[ reuse of content,<br />
[ ease of restructuring deliverables,<br />
[ simple export to multiple delivery<br />
formats.<br />
Pitfalls<br />
[ complex interaction of simultaneous<br />
reuse possibilities (for multiple<br />
platforms, releases, and OEM<br />
deliveries),<br />
[ completely rethinking the structure of<br />
administrative topics<br />
[ the need to be always aware of who<br />
else might be using a source content<br />
section.<br />
Restructuring the legacy content for<br />
optimal use became impossible. One<br />
attempt to restructure a large chunk<br />
of content for optimal reuse rendered<br />
the structure of that content<br />
incomprehensible to any of our<br />
writers.<br />
http://www.cm-strategies.com/abstracts.htm#Semmelmeyer<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
Lulled into complacency, we forgot to<br />
consider the other writers using our<br />
sources. One writer had an<br />
unpleasant surprise when a PDF<br />
extract (that was fine two weeks ago)<br />
had missing sections and content that<br />
no longer applied.<br />
Another challenge was consideration<br />
of all the possible uses of our source<br />
(for multiple platforms, releases, OEM<br />
deliveries, and products), which<br />
required months of planning around<br />
conditional text.<br />
Tracking hundreds of topics in<br />
various stages of completion<br />
expanded our use of Excel<br />
spreadsheets. And writing for topicbased<br />
reuse constantly challenged us<br />
to think differently than our past linear<br />
writing.<br />
15
Best Practice Medtronic (1)<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
16
Best Practice Medtronic (2)<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
17
10 <strong>DITA</strong> Lessons Learned From Tech Writers in the Trenches<br />
1. <strong>DITA</strong> Is NOT A Magic Wand (<strong>DITA</strong><br />
makes some things easier but<br />
adds its own issues as well.)<br />
2. Don’t Fall In Love With Software<br />
3. Don’t Jump in Without a Clear<br />
Business Case, a Repeatable<br />
Strategy, and Measurable Goals<br />
4. While You Are At It, Get A<br />
Content Management System<br />
5. <strong>DITA</strong> Needs to be Constrained.<br />
<strong>DITA</strong> allows authors to do things<br />
your business needs and<br />
authoring style guides may forbid<br />
6. Some Writers CANNOT Write<br />
Reusable Content<br />
7. Plan for Legacy Content<br />
Conversion Issues<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
8. Resist the Temptation to<br />
Specialize<br />
9. Hire an Expert<br />
10. <strong>DITA</strong> Changes Everything:<br />
Getting Up To Speed Requires<br />
Commitment, Effort, Skills, and<br />
Training<br />
When you make the move to<br />
<strong>DITA</strong>, there is no room for<br />
deviation. It is all for one and<br />
one for all. If you have loose<br />
cannons trying to do things<br />
differently, you ARE going to<br />
have problems and may have to<br />
make staffing changes.<br />
18
<strong>DITA</strong> – Was sagen TD-Dienstleister dazu (1)<br />
Comet<br />
] Comet hat als erster Service-<br />
Provider in Deutschland Projekte<br />
mit <strong>DITA</strong> umgesetzt. Diese <strong>DITA</strong>-<br />
Lösungen sind bereits seit zwei<br />
Jahren erfolgreich im Einsatz.<br />
Tanner<br />
] <strong>DITA</strong> ist die Zukunft!<br />
Kombinierte Vorteile von <strong>DITA</strong><br />
und TANNER-Funktionsdesign<br />
Cap-Studio<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
] <strong>DITA</strong> ist kein Allheilmittel für die<br />
Dokumentation. Ob XML-<br />
basierten Schreiben Vorteile<br />
bringt, muss geprüft werden.<br />
] <strong>DITA</strong> als Standard wirkt nur,<br />
wenn man möglichst wenig<br />
Spezialisierung benötigt.<br />
Anderenfalls steigt der<br />
Verwaltungsaufwand und die<br />
nicht-benötigten Teil des<br />
Standards können lästig werden.<br />
] XML-basierte<br />
Dokumentstrukturen können<br />
Widerstände bei den Autoren<br />
hervorrufen (Verweis auf Sarah<br />
O‘Keefe)<br />
http://www.scriptorium.com/palimpsest/2007/07/understanding-change-resistance.html<br />
19
<strong>DITA</strong> – Was sagen TD-Dienstleister dazu (2)<br />
Scriptorium (Sarah O-Keefe)<br />
"Once you start down the <strong>DITA</strong> path,<br />
forever will it dominate your destiny"<br />
] For technical writers, the transition from<br />
traditional desktop publishing to XML-<br />
based workflows requires a significant<br />
shift in mindset.(…) You should not<br />
underestimate the difficulty that this<br />
transition presents.<br />
] Just because it's free doesn't mean it's<br />
cheap. The default output from the <strong>DITA</strong><br />
Open Toolkit ranges somewhere between<br />
unattractive (HTML) and fugly (PDF). If you<br />
care about the appearance of your final<br />
documents, you are going to have to do a<br />
lot of work to get the look and feel you<br />
want.<br />
] And although the OT offers a starting point,<br />
customizing it is kind of like a trip to the<br />
dentist. The impacted-wisdom-tooth-<br />
removing kind of trip.<br />
Gordon McLean<br />
<strong>DITA</strong> is not the answer<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
] All of my research suggests that, rather<br />
than being a simple installation and<br />
conversion process, creating a <strong>DITA</strong><br />
solution requires a lot of technical know-<br />
how and a not insubstantial amount of time<br />
and resource. We can handle the first, the<br />
latter is (I believe) not yet at a level which<br />
makes it cost-effective.<br />
] Ultimately, for the moment, <strong>DITA</strong> costs too<br />
much.<br />
Norman Walsh<br />
] topic-oriented writing vs. book-oriented<br />
writing<br />
Barbara Stuhlemmer, ClearComm<br />
InformationDesign<br />
] Converting to XML - Some Point-form Pros<br />
and Cons<br />
20
<strong>DITA</strong> – Was sagen TD-Dienstleister dazu (3)<br />
Manfred Krüger,<br />
<strong>DITA</strong>-Praxis – die Sicht der Anwender<br />
] <strong>DITA</strong>-Informationsmodell 1.1enthält<br />
semantische (inhaltsbezogene)<br />
Strukturen lediglich für die Software-<br />
Dokumentation.<br />
] Ein Autor benötigt ein umfassende<br />
organisatorische Regelung für die<br />
Bildung seines <strong>Top</strong>ics und der ggf.<br />
neben- und untergeordneten muss<br />
kennen. <strong>DITA</strong> definiert hier völlige<br />
Freiheit. <strong>DITA</strong> ist wirklich keine gut<br />
den Autor führende Struktur!<br />
] Ohne ein formales CMS wird man in<br />
der Praxis der <strong>DITA</strong>-Anwendung nicht<br />
auskommen.<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
Manfred Krüger,<br />
<strong>DITA</strong>-Praxis – die Sicht der Anwender<br />
(Forts.)<br />
] Die Implementierung von <strong>DITA</strong> muss<br />
aus organisatorischen und<br />
wirtschaftlichen Gründen die<br />
angebotene Standard-Struktur<br />
verschlanken, und ggf. um<br />
spezifische Strukturen erweitern.<br />
] Die anwendungsspezifische<br />
Anpassung der <strong>DITA</strong>-Stylesheets<br />
erfordert auch für erfahrene<br />
Spezialisten einen erheblich höheren<br />
Aufwand als ein von Grund neues<br />
Stylesheet-Design..<br />
] Machen Sie sich nichts vor: Wenn Sie<br />
<strong>DITA</strong> in Ihrer Organisation eingeführt<br />
haben und meinen, es habe eigentlich<br />
nicht viel Geld gekostet, dann haben<br />
Sie etwas falsch gemacht!<br />
21
“Everything takes longer with <strong>DITA</strong>”<br />
Over coffee this week I heard the<br />
complaint “everything takes longer<br />
with <strong>DITA</strong>” from a tech writer at a<br />
company that recently converted from<br />
unstructured FrameMaker to <strong>DITA</strong>.<br />
Why? Well you just can’t do File<br />
Open, add a paragraph or two, and<br />
consider your update done.<br />
The Facts: The complaint may well be<br />
absolutely true – for the writer at the<br />
moment at the time of adding a<br />
paragraph.<br />
http://methodm.com/blog/category/dita/<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
But it is absolutely false for the total<br />
document cost because <strong>DITA</strong><br />
enables:<br />
] Delivery of the content to the user in<br />
multiple instances (e.g.<br />
troubleshooting, installation, FAQ,<br />
etc.).<br />
] Customization of the document for<br />
presentation to different types of<br />
users.<br />
] Easy updating of the content.<br />
] Definition of related topics (tasks that<br />
must be performed in a sequence, for<br />
example).<br />
] Focusing information on what the<br />
customer needs at a particular<br />
moment (how-to information, for<br />
example, or reference content)<br />
] And, of course, lower translation<br />
costs and much, much, much more.<br />
22
Was sagt Dieter Gust zu <strong>DITA</strong>?<br />
DTP- und XML-Redaktionssysteme im Vergleich<br />
Zeitaufwand<br />
Papier<br />
DTP-Editing XML-Editing<br />
PDF<br />
Konverter<br />
Vorteil: Instant Printing DTP-Editing<br />
HTML PDF HTML<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
Konverter Konverter Konverter<br />
Papier<br />
PDF<br />
Nachteil: DTP-Post-Processing<br />
Flexibilitätsverlust<br />
23
Was sagt Dieter Gust zu <strong>DITA</strong>?<br />
Besonders auf die Werkzeuge kommt es an!<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
Wunsch<br />
Worst Case?<br />
Produktivität mit XML<br />
nach einem Jahr<br />
auf dem alten Stand?<br />
http://www.elkera.com/cms/articles/seminars_and_presentations/planning_a_single_source_publishing_application_for_business_documents/<br />
24
Was sagt Dieter Gust zu <strong>DITA</strong>?<br />
Hatten Sie bisher keine Zeit zum Ausfüllen dieser Fenster?<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
<strong>DITA</strong> wird das ändern…<br />
25
<strong>Top</strong>ic-Orientierung / Modularisireung ist kein Selbstzweck<br />
Welche Granularität ist geeignet?<br />
Flexibilität<br />
für Wiederverwendung<br />
Verwaltungsaufwand<br />
Eine fiktive<br />
optimale Stelle<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
Redundanz<br />
bei Mehrfachverwendung<br />
Modulgröße: Datum, Wort, Satz, Absatz, <strong>Top</strong>ic, Abschnitt, Kapitel<br />
26
<strong>DITA</strong> und der Gesamtprozess für TD:<br />
Wichtig: Terminologie und „<strong>Top</strong>ics-im-Kontext“-Betrachtungen<br />
Produktentwicklung<br />
Redaktion<br />
Multithreading<br />
Übersetzung<br />
Multithreading<br />
Produktion<br />
Verwaltung<br />
Spezifikationen<br />
User-Interface-Texte<br />
Techn. Daten UI-Strings<br />
Single-Source Editing<br />
Sprachkontrolle<br />
Preflight Checks<br />
Übersetzungsprozess<br />
Kunden Review<br />
Finishing<br />
Produktion<br />
Datenmanagement/<br />
Dokumentenmanagement<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
Terminologie<br />
Terminologie<br />
Terminologie<br />
Terminologie<br />
Terminologie<br />
27
<strong>DITA</strong> / XML Vorteile: Termine, Kosten, Qualität?<br />
Es geht doch auch alles ohne <strong>DITA</strong>, <strong>oder</strong> gar ohne XML…<br />
Systemimplementierung: ? % ZKQ<br />
] DTD-Entwicklung<br />
] Templates für PDF/HTML<br />
] <strong>Top</strong>ic-Editor + Struktur/MAP-<br />
Editor<br />
] Zukunftssicherheit<br />
] Standard (Vorteil =??)<br />
Datenimport ? % ZKQ<br />
Informationserstellung ? % ZKQ<br />
Wiederverwendung ? % ZKQ<br />
Kontrolle der Wiederverwendung<br />
? % ZKQ<br />
Z = Zeit, K = Kosten, Q = Qualität<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
Dokumentzusammenstellung<br />
? % ZKQ<br />
Sprachkontrolle ? % ZKQ<br />
Übersetzung ? % ZKQ<br />
Kundenreview ? % ZKQ<br />
Finishing/Produktion ? % ZKQ<br />
Daten-/Dokumentmanagement ?<br />
ZKQ%?<br />
…<br />
Was meinen Sie?<br />
28
Jeder Hype kennt Höhen und Tiefen: Wo steht <strong>DITA</strong>?<br />
http://lighthouseseminars.com/gilbane_sf_06/presentations/Bill_Trippe_tutorial.pdf<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
29
DTA Maturity Model, hmm?<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
30
Anhang Informationshinweise<br />
Developing Quality Technical<br />
Information. A Handbook for<br />
Writers and Editors (IBM Press<br />
Series) 2nd ed, 2004<br />
Introduction to <strong>DITA</strong> Arbortext<br />
Edition<br />
Introduction to <strong>DITA</strong><br />
Sissi Closs, Single Source<br />
Publishing. <strong>Top</strong>icorientierte<br />
Strukturierung und <strong>DITA</strong>, 2006<br />
Johannes Hentrich, <strong>DITA</strong> - Der<br />
neue Standard für Technische<br />
Dokumentation<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
http://www.ditamap.com/ditaref/dit<br />
aref11-main.php<br />
http://dita.xml.org/<br />
http://www.ditainfocenter.com/<br />
http://www.ditawiki.org/<br />
Content Management<br />
Strategies/<strong>DITA</strong> North America<br />
(April 2008)<br />
www.tekom.de<br />
[ Tekom <strong>DITA</strong>-Entscheidungshilfe<br />
Comet Single Source Forum<br />
31
itl München Unternehmensdaten<br />
Firmengründung 1982<br />
Unternehmensform Aktiengesellschaft<br />
Vorstands- Christine<br />
vorsitzende Wallin-Felkner<br />
Prokuristen Dieter Gust,<br />
Peter Kreitmeier<br />
Regine Ceglarek<br />
über 50 fest angestellte Mitarbeiter<br />
ca. 150 freie Mitarbeiter weltweit<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
32
itl Dienstleistungsspektrum<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
Prozess- und System-<br />
Consulting:<br />
] Word, FrameMaker,<br />
Acrobat,<br />
] XML,<br />
] Einführung von<br />
Redaktionssystemen,<br />
(docuglobe, TIM-<br />
RS,…)<br />
] Tools für kontrollierte<br />
Sprachen<br />
] <strong>Top</strong>ic orientiertes<br />
Schreiben<br />
/Modularisierung<br />
] Kompaktsmeminar TD<br />
33
Vielen Dank für Ihre Aufmerksamkeit!<br />
Wir sehen Die Welt<br />
mit Ihren Augen!<br />
27.02.2008 <strong>DITA</strong> <strong>Top</strong> <strong>oder</strong> <strong>Flop</strong> Version 1.0 Februar 2008<br />
itl – Ihr Full Service Dienstleister<br />
Übersetzungsdienstleistungen<br />
Technische Dokumentation<br />
Produkt- & Prozesslösungen<br />
Wissenslösungen<br />
34