Specialization

ABOUT THIS SITE

The following is a list of pages on this site that are tagged with specialization.

Alexej Spas DITA blog

Common errors in DITA specializations

Blog entry: Submitted by wildwildleha on Mon, 2009-03-30 16:06.

DITA Specialization opens a new dimension for customizing DITA to needs of different enterprises. But doing a valid specialization is not a trivial process. It requires rather deep understanding of DITA internals and command in technologies like DTD, XML Schema and s.o.

But even with sufficient knowledge of DTD (or XML Schema) coding, doing a valid specialization requires knowledge of certain DITA principles and rules. Just designing a valid DTD will not necessarily mean that you have a valid DITA model.

Math Domain Requirements

Wiki page: Submitted by bnordgren on Sat, 2009-02-21 19:16. Last updated on Mon, 2009-02-23 19:54.

The fundamental premise of DITA is to provide a framework within which
reusable content may be authored without regard to how that particular
content is rendered on a particular target. DITA strives to be target
neutral in as many ways as possible: thus at the time a topic is
written, no assumptions are made as to whether that topic will be
presented on a web page, in a book or on a poster. Content can thus be
naturally shared between web and print forms. Content can also be

Workspace to develop a math domain for DITA

Wiki page: Submitted by bnordgren on Sat, 2009-02-21 19:08. Last updated on Sat, 2009-02-21 21:21.

Collects all the topics related to integrating mathematical expressions into DITA and the DITA-OT.

Introduction to specialization

Book page: Submitted by Bruce Esrig on Fri, 2006-02-10 21:21. Last updated on Mon, 2015-10-05 20:54.

Specialization is the process by which new designs are created based on existing designs, allowing new kinds of content to be processed using existing processing rules.

It is the means by which the standard DITA language may be extended for new semantic or structural roles.

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.