This link has been bookmarked by 44 people . It was first bookmarked on 26 Jul 2006, by Lo Go.
-
26 Oct 12
-
15 Nov 11
-
21 Jan 11
-
10 Mar 10
-
17 Jan 10
-
03 Jul 09
-
29 Oct 08
-
05 Oct 08
-
22 Jul 08
-
27 Mar 08
-
29 Jan 08
-
24 Oct 07
-
29 Jul 07
-
04 May 07
-
24 Oct 06
-
23 Sep 06
-
18 Sep 06
-
20 Jun 06
-
17 Jun 06
-
05 May 06
jeanjordaanDITA defines an XML architecture for designing, writing, managing, and publishing many kinds of information in print and on the Web. DITA consists of a set of design principles for creating 'information-typed' modules at a topic level. DITA enables organi
dita XML documentation standards oasis markup Metadata format agile publishing standard
-
21 Feb 06
-
29 Jan 06
-
22 Dec 05
-
21 Nov 05
-
Overview DITA is an architecture for creating topic-oriented, information-typed content that can be reused and single-sourced in a variety of ways. It is also an architecture for creating new information types and describing new information domains based on existing types and domains. This allows groups to create very specific, targeted document type definitions using a process called specialization, while still sharing common output transforms and design rules developed for more general types and domains. DITA supports a unique transclusion mechanism that is validated under DTD processing rules: an element "can replace itself with the content of a like element elsewhere, either in the current topic or in a separate topic that shares the same content models. DITA's conref 'transclusion' mechanism is similar to the SGML conref mechanism, which uses an empty element as a reference to a complete element elsewhere. However, DITA requires that at least a minimal content model for the referencing element be present, and performs checks during processing to ensure that the replacement element is valid in its new context. This mechanism goes beyond standard XInclude, in that content can be incorporated only when it is equivalent: If there is a mismatch between the reusing and reused element types, the conref is not resolved. It also goes beyond standard entity reuse, in that it allows the reused content to be in a valid XML file with a DTD. The net result is that reused content gets validated at authoring time, rather than at reuse time, catching problems at their source." Note: Michael Priestley (IBM) has provided several key documents for this DITA reference collection; his assistance in creating this document is gratefully acknowledged.
-
-
20 Oct 05
-
14 Oct 05
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.