Heinz Wittenbrink
2020-11-14
Bild: https://www.dita-ot.org/
Orientiert an: Sarah O’Keefe, DITA 101 webcast
Wiederverwendbarkeit von Inhalten
Wiederverwendbarkeit von Modellen
Trennung von Modell und Präsentation
Orientierung an digitaler Ausgabe statt an papier-basierten Formaten
die Veröffentlichung einer Menge von Informationsprodukten für unterschiedliche Benutzergruppen und über mehrere Releases hinweg unterstützen
neue Zusammenstellungen von Inhalten einführen, die neue Inhaltstypen erfordern (z.B. Hardware Dokumentation, Geschäftsprozesse usw.)
Bild: Adobe Systems
Minimalismus
Information Mapping
Vererbung/Objektorientierung
Nach JoAnn Hackos
Zitiert nach: What is Minimalism? | Every Page is Page One
People are situated in a world more real to them than a series of steps, a world that provides rich context and convention for everything they do. People are always already trying things out, thinking things through, trying to relate what they already know to what is going on, recovering from errors. In a word, they are too busy learning to make much use of the instructions. (J.M.Carrol)
Video: Information Mapping - What is it? Why use it? - YouTube
Information Mapping® provides a number of tools that help you to analyze, organize and present information:
Information Types […] Research-Based Principles […] Units of Information […] Presentation Modes […]
Quelle: The Information Mapping® Method - Information Mapping
Quelle: Wikimedia Commons, Urheber: User:Cactus26,
In object-oriented programming, inheritance is a way to form new classes using classes that have already been defined. …
In DITA, child topics or elements inherit attributes from their parents. For example, metadata applied to a section of a DITA file will automatically be applied to topics contained in the section.
Inheritance also plays an important role in DITA specialization, which allows you to extend a base topic to match your specific requirements by defining only the differences between it and its base topic; the bulk of the specialized definition is inherited.
(Quelle: Darwin Information Typing Architecture - Wikipedia)s
id
.audience
kann insgesamt oder bei einzelnen Elementen festgelegt werden.A topic is a unit of information with a title and content, short enough to be specific to a single subject or answer a single question, but long enough to make sense on its own and be authored as a unit.
Quelle: DITA topics
Topics are the basis for high-quality information. They should be short enough to be easily readable, but long enough to make sense on their own.
Quelle: DITA topics
Information typing is the practice of identifying types of topics that contain distinct kinds information, such as concepts, tasks, and reference information. Topics that answer different kinds of questions can be categorized as different information types. The base topic types provided by DITA ( a generic topic, plus concept, task, and reference ) provide a usable starter set that can be adopted for immediate authoring.
Quelle: DITA topics
Quelle: DITA topics
Quelle: DITA topics
Quelle: DITA topics
Struktur von Topics in der DITA-Dokumentation: Topic structure
Inhalte eines Topic in der DITA-Dokumentation: Topic content
Quelle: DITA Open Toolkit
Siehe zu den Maps: Purpose of ditamap files
Die Maps bestehen vor allem aus topicref-elementen. Sie können hierarchisch angeordnet sein und zu relationship tables gehören.
<map>
<title>DITA for the Impatient</title>
<topicmeta>
<author>Hussein Shafie</author>
<publisher>Pixware</publisher>
<critdates>
<created date="October 7, 2009"/>
</critdates>
</topicmeta>
<topicref href="introduction.dita"/>
<topicref href="topics_and_maps.dita"/>
<topicref href="topic.dita">
<topicref href="topic_structure.dita">
<topicref href="samples/sample_topic.dita" toc="no"/>
</topicref>
<topicref href="block_elements.dita"/>
<topicref href="inline_elements.dita"/>
<topicref href="link_elements.dita"/>
</topicref>
.
.
.
<topichead navtitle="Topic maps">
<topicref href="map.dita"/>
<topicref href="bookmap.dita"/>
</topichead>
<topicref href="conclusion.dita"/>
</map>
Quelle: DITA for the Impatient
The term collection is used to describe a potential publication in the DITA source. A ditamap collection is processed to become a publication. In other words, collection describes the source content, while publication describes the output format. A collection is defined in DITA through a ditamap, or multiple embedded ditamaps.
The process of transforming DITA source into an output format is known as publishing, processing, or transformation, and the software tools for the process are known as processors, transformers, or publishing engines.
Beispiele: Working with Variable Text in DITA
Specialization allows you to define new kinds of information (new structural types or new domains of information), while reusing as much of existing design and code as possible, and minimizing or eliminating the costs of interchange, migration, and maintenance.
März 2001: IBM stellt Kern-DTD und XML-Schema fertig
Mai 2002: Zur Topic-Spezialisierung kommt die Domain-Spezialisierung
2004 OASIS Technical Commitee
Februar 2005: IBM übergibt das DITA Open Toolkit an Sourceforge
Juni 2005: DITA 1.0
August 2007: DITA 1.1 (neue Bookmap-Spezialisierung)
2010: DITA 1.2 (Lernobjekte)
17.12.2015: DITA 1.3 (Troubleshooting-Topic, Scoped Keys, MathML und Equation-Domains, Relax NG für normative Schemas)
Material: History of DITA | DITA XML.org
Sarah O’Keefe: DITA 101 - YouTube
Sarah O’Keefe: DITA 101 - YouTube
For the average CCM system, the content is created in smaller-than-page chunks, and assembled, much like a content mashup, to create a larger-sized page for output. A change is made to a component, which can be a single word, phrase, paragraph, or larger, which is then compiled, much like a software “build”, which generates a presentation version of the specified sources. The aggregated content can be pushed out to a Web page, a PDF, or a print destination.
Rahel Bailie: Component content management as content mash-ups
DITA-Dokumente: dita-community/dita-demo-content-collection: DITA Demonstration Content Collection°°°°°
DITA-basierte Website: The Content Era is here
DITA-basiertes CMS: DITAToo DITA CCMS
LwDITA will provide:
Lightweight DITAis a simplified version of the Darwin Information Typing Architecture. In comparison to DITA 1.3, LwDITA has a smaller element and attribute set, stricter content models, and a reduced feature set. LwDITA also defines mappings between XML, HTML5, and Markdown.
# Installing and Setting up Remote Lighting
Installation of your lighting kit includes installing the light bulbs into light fixtures, preparing the remote control, and programming lighting groups.
## Steps
1. Install light bulbs.
2. Prepare remote control.
3. Program lighting groups.
## Example
![Image](remote.png)
---
id: install-and-setup
author: Kevin Lewis
---
# Installing and Setting up Remote Lighting
Installation of your lighting kit includes installing the light bulbs into light fixtures, preparing the remote control, and programming lighting groups.
Before you attempt to install your lighting kit, please turn off the power in your electrical circuit panel,
## Steps
1. Install light bulbs.
2. Prepare remote control.
3. Program lighting groups.
## Example
The following video demonstrates a recommended installation:
<video src="remote.mp4" controls poster="remote.png" />
Lightweight DITA: An Introduction
Markdown DITA syntax reference
Lightweight DITA and DITA 2.0 - DITA Now and in the Future - IXIASOFT
DITA XML.org is the official community gathering place and information resource for the DITA OASIS Standard, an XML architecture for designing, writing, managing, and publishing information. We encourage you to contribute content to this site.
DITA XML.org | Online community for the Darwin Information Typing Architecture OASIS Standard
“Gnostyx” - DITA Demonstration Content Collection
Siehe dazu: ThunderBird: A Sample DITA Documentation Set to Play With – DITA Writer
DITA Writer – Blog, Resource, Interviews and News Relating to DITA XML
Step by step process to create new DITA project - Oxygen XML Forum
DITA Maps Manager - Oxygen XML Editor
10 reasons for moving away from DITA | I’d Rather Be Writing
DITA Awareness Group: https://www.linkedin.com/groups/162465/ DITA for Small Teams: https://www.linkedin.com/groups/3968768/ DITA Metrics (for effort estimation and ROI calculations): https://www.linkedin.com/groups/2916249/
Last login: Fri Nov 10 10:47:09 on ttys005
M00087-3:~ heinz$ javac -version
javac 1.8.0_131
M00087-3:~ heinz$
M00087-3:~ heinz$ echo $PATH
/Users/heinz/DITA/dita-ot-3.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/TeX/texbin
M00087-3:~ heinz$ dita --version
DITA-OT version 3.0
M00087-3:~ heinz$
M00087-3:samples heinz$ dita --input=sequence.ditamap --format=html5 --output=output/sequence
[xslt] Warning at xsl:stylesheet on line 12 column 59 of map2html5Impl.xsl:
[xslt] Stylesheet module plugin:org.dita.html5:xsl/map2html5Impl.xsl is included or imported more
[xslt] than once. This is permitted, but may lead to errors or unexpected behavior
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN"
"../dtd/technicalContent/dtd/map.dtd">
<!-- This file is part of the DITA Open Toolkit project hosted on
Sourceforge.net. See the accompanying license.txt file for
applicable licenses.-->
<!-- (C) Copyright IBM Corporation 2001, 2005. All Rights Reserved.
*-->
<map title="Working in the garage">
<topicref href="tasks/changingtheoil.xml" type="task"></topicref>
<topicref href="tasks/organizing.xml" type="task"></topicref>
<topicref href="tasks/shovellingsnow.xml" type="task"></topicref>
<topicref href="tasks/spraypainting.xml" type="task"></topicref>
<topicref href="tasks/takinggarbage.xml" type="task"></topicref>
<topicref href="tasks/washingthecar.xml" type="task"></topicref>
<topicref href="concepts/lawnmower.xml" type="concept"></topicref>
<topicref href="concepts/oil.xml" type="concept"></topicref>
<topicref href="concepts/paint.xml" type="concept"></topicref>
<topicref href="concepts/shelving.xml" type="concept"></topicref>
<topicref href="concepts/snowshovel.xml" type="concept"></topicref>
<topicref href="concepts/toolbox.xml" type="concept"></topicref>
<topicref href="concepts/tools.xml" type="concept"></topicref>
<topicref href="concepts/waterhose.xml" type="concept"></topicref>
<topicref href="concepts/wheelbarrow.xml" type="concept"></topicref>
<topicref href="concepts/workbench.xml" type="concept"></topicref>
<topicref href="concepts/wwfluid.xml" type="concept"></topicref>
</map>
Dank an Lief Erickson für wertvollen Input!
heinz at fh-joanneum dot at