| Next revision | Previous revision |
| dita [2015/09/15 18:18] – created cangione | dita [2015/09/15 18:24] (current) – cangione |
|---|
| <html> | |
| <h1> Darwin Information Typing Architecture DITA</h1> | |
| |
| IBM Intro: http://www-128.ibm.com/developerworks/xml/library/x-dita1 | <h1> Darwin Information Typing Architecture</h1> |
| |
| Oasis: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita#overview | :IBM Intro: http://www-128.ibm.com/developerworks/xml/library/x-dita1 |
| | |
| | :Oasis: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita#overview |
| |
| ---- | ---- |
| |
| <h2>Definitions</h2> | <h2>Definitions</h2> |
| : *Topic* - The highest standard structure in DITA. Topics are not nested. (Example: A topic within a topic) | : '''Topic''' - The highest standard structure in DITA. Topics are not nested. (Example: A topic within a topic) |
| |
| : *Section* - Used for internal organization of a Topic, these define or directly support the topic | : <b>Section</b> - Used for internal organization of a Topic, these define or directly support the topic |
| |
| : *Processing Context* - Any higher structure than a topic used to handle context. (*Examples:* Print-organizing structure or the helpset-like navigation) | : <b>Processing Context</b> - Any higher structure than a topic used to handle context. (*Examples:* Print-organizing structure or the helpset-like navigation) |
| |
| : *Reuse* - Two Levels | : <b>Reuse</b> - Two Levels |
| |
| :: * *Topic reuse or Course Grain Reuse* - Because of the non-nesting structure of topics, a topic can be reused in any topic-like context. | :: <b>Topic reuse or Course Grain Reuse</b> - Because of the non-nesting structure of topics, a topic can be reused in any topic-like context. |
| :: * *Content reuse or Fine Grain Reuse* - Via a _conref_ attribute that can point to any other equivalent element in the same or any other topic. | :: <b>Content reuse or Fine Grain Reuse</b> - Via a _conref_ attribute that can point to any other equivalent element in the same or any other topic. |
| |
| : *[Specialization|http://www-128.ibm.com/developerworks/xml/library/x-dita2/index.html]*. Allows any DITA element to be extended into a new element whose identifier gets added to the class attribute through its DTD. Therefore, a new element is always associated to its base, or to any element in its specialization sequence. | : <b>[http://www-128.ibm.com/developerworks/xml/library/x-dita2/index.html Specialization]</b>. Allows any DITA element to be extended into a new element whose identifier gets added to the class attribute through its DTD. Therefore, a new element is always associated to its base, or to any element in its specialization sequence. |
| |
| :: * *Topic specialization* - A way to extend the generic topic into new information types (or _infotypes_). (Example, a recipe, a material safety data sheet, and an encyclopedia article are all potential derivations from a common reference topic). | :: <b>Topic specialization</b> - A way to extend the generic topic into new information types (or _infotypes_). (Example, a recipe, a material safety data sheet, and an encyclopedia article are all potential derivations from a common reference topic). |
| |
| ::: *NOTE* By default, DITA has three specialized topic types: _Concept_, _task_, and _reference_. | ::: <b>NOTE</b> By default, DITA has three specialized topic types: _Concept_, _task_, and _reference_. |
| :::: [ http://www-128.ibm.com/developerworks/xml/library/x-dita2/basediag.gif ] | :::: <html><img src="http://www-128.ibm.com/developerworks/xml/library/x-dita2/basediag.gif"/> |
| |
| :: * *Domain specialization* - The element vocabulary within a topic (or set of infotyped topics) can be extended by introducing elements that reflect a particular information domain served by those topics. (Example a specialized domain, such as programming phrases, can be introduced by substitution anywhere that the root elements are allowed. | :: <b>Domain specialization</b> - The element vocabulary within a topic (or set of infotyped topics) can be extended by introducing elements that reflect a particular information domain served by those topics. (Example a specialized domain, such as programming phrases, can be introduced by substitution anywhere that the root elements are allowed. |
| |
| |
| <h2>Articles</h2> | <h2>Articles</h2> |
| |
| :[ 10 Lessons Learned Moving to DITA|http://thecontentwrangler.com/article/10_dita_lessons_learned/] | :[http://thecontentwrangler.com/article/10_dita_lessons_learned/ 10 Lessons Learned Moving to DITA] |
| |
| :[Lessons Learned Moving to DITA Article |http://thecontentwrangler.com/site/moving_to_dita_lessons_learned_from_mark_lewis_of_hyperwriters/] | :[http://thecontentwrangler.com/site/moving_to_dita_lessons_learned_from_mark_lewis_of_hyperwriters/ Lessons Learned Moving to DITA Article] |
| |
| :[Computer World Introduction Article|http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=285881&intsrc=article_pots_side] | :[http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=285881&intsrc=article_pots_side Computer World Introduction Article] |
| | |
| ---- | |
| |
| <h2>Additional Info</h2> | |
| |
| :S1000D and DITA Working TC e-mail list *dita-s1000d-discuss-subscribe@lists.oasis-open.org* | |
| </html> | |
