DITA: Difference between revisions
(using an external editor) |
(using an external editor) |
||
Line 5: | Line 5: | ||
* {{quotation | The Darwin Information Typing Architecture (DITA) is an XML-based, end-to-end architecture for authoring, producing, and delivering technical information. This architecture consists of a set of design principles for creating "information-typed" modules at a topic level and for using that content in delivery modes such as online help and product support portals on the Web. }} ([http://www-128.ibm.com/developerworks/xml/library/x-dita1/ Introduction to the Darwin Information Typing Architecture], retrieved [[User:DSchneider|DSchneider]]). | * {{quotation | The Darwin Information Typing Architecture (DITA) is an XML-based, end-to-end architecture for authoring, producing, and delivering technical information. This architecture consists of a set of design principles for creating "information-typed" modules at a topic level and for using that content in delivery modes such as online help and product support portals on the Web. }} ([http://www-128.ibm.com/developerworks/xml/library/x-dita1/ Introduction to the Darwin Information Typing Architecture], retrieved [[User:DSchneider|DSchneider]]). | ||
Dita was originally developed at IBM by Don R. Day, Michael Priestley and others. It now is a [[OASIS]] standard. Its general architecture may be quite interesting for educational sites, because it (1) accomodates for topic-oriented organization and reuse (as opposed to long documents), (2) allows specialization and (3) therefore supports semantic markup (as opposed to Docbook which is typographic basically). | |||
== DITA in education == | == DITA in education == | ||
Line 19: | Line 19: | ||
* Smaller [[learning activity | learning activities]] | * Smaller [[learning activity | learning activities]] | ||
* [[Lesson plan]]s | * [[Lesson plan]]s | ||
* Feature lists of various [[:Category:technologies technologies]] (as different as for example [[microworld]]s, [[LMS]]s, [[cognitive tool]]s | * Feature lists of various [[:Category:technologies | technologies]] (as different as for example [[microworld]]s, [[LMS]]s, [[cognitive tool]]s | ||
* Websites like ''this'' wiki (e.g. pages that describe theories, concepts, methods, technology, etc.) and that are interlinked and categorized. | * Websites like ''this'' wiki (e.g. pages that describe theories, concepts, methods, technology, etc.) and that are interlinked and categorized. | ||
This kind of information is characterized by being structured | ; Searching | ||
This kind of information is characterized by being structured and it would be niced if it could be searched by "kinds of information". In theory this could be implemented with SQL. However, our experience shows that building SQL tables for each kind of information is very time consuming and not very flexible. The opposite alternative is unstructuredness, e.g. like a Wiki. Wikis allow to enter data very quickly, but have the disadvantage that one can't easly produce text on demands (it's not easy to make a wiki book) and that full text search has its limits once the wiki starts growing. In addition, Wiki engines don't produce text, but the spit back page names plus the search context. E.g. you can't say something like "let's have a list of all the references on pages that belong to the category "instructional design modelling". | |||
DITA can address some of the needs for flexible information | DITA can address some of the needs for flexible information retrieval architectures, in particular if combined with a xml-database web application like [eXist http://exist.sourceforge.net/]. | ||
; Flexible document production | |||
Now lets image that you are engaged in teacher training, or that you are interested in reading all information related to some topic, e.g. how do I design [[enquiry learning]]. DITA would allow to create print or web documents on the fly, on a per needed bases. | |||
; Authoring | |||
In some cases, it is desired that information entered be complete according to some standards. A typical example would be lesson plans. A flexible [[TTW]] DITA-based editor could address this issue. | |||
; A test case | ; A test case | ||
Line 33: | Line 40: | ||
=== Learner activities === | === Learner activities === | ||
== References == | |||
* [http://xml.coverpages.org/dita.html Darwin Information Typing Architecture (DITA XML)] Cover page article | |||
* [http://www-106.ibm.com/developerworks/xml/library/x-dita3/index.html DITA - XML-based Darwin Information Typing Architecture FAQ] | |||
* [http://www-106.ibm.com/developerworks/xml/library/x-dita1/index.html Introduction to the Darwin Information Typing Architecture] | |||
* [http://www-106.ibm.com/developerworks/xml/library/x-dita2/index.html Specialization in the Darwin Information Typing Architecture] | |||
[[Category: XML]] | [[Category: XML]] | ||
[[Category: Standards]] | [[Category: Standards]] |
Revision as of 11:31, 3 November 2006
Definition
- DITA is an XML [[document standard] (vocabulary) for authoring modular text.
- “The Darwin Information Typing Architecture (DITA) is an XML-based, end-to-end architecture for authoring, producing, and delivering technical information. This architecture consists of a set of design principles for creating "information-typed" modules at a topic level and for using that content in delivery modes such as online help and product support portals on the Web.” (Introduction to the Darwin Information Typing Architecture, retrieved DSchneider).
Dita was originally developed at IBM by Don R. Day, Michael Priestley and others. It now is a OASIS standard. Its general architecture may be quite interesting for educational sites, because it (1) accomodates for topic-oriented organization and reuse (as opposed to long documents), (2) allows specialization and (3) therefore supports semantic markup (as opposed to Docbook which is typographic basically).
DITA in education
DSchneider believes that DITA could play a role in education.
Here are to use case examples:
Pedagogical knowledge
- Educators and communities of practice are sometimes engaged in knowledge management tasks and thus constitute a knowledge-building community. In addition, there exist many structures financed to provide educators and other experts with structure information. Here are a few examples:
- pedagogical scenarios
- Smaller learning activities
- Lesson plans
- Feature lists of various technologies (as different as for example microworlds, LMSs, cognitive tools
- Websites like this wiki (e.g. pages that describe theories, concepts, methods, technology, etc.) and that are interlinked and categorized.
- Searching
This kind of information is characterized by being structured and it would be niced if it could be searched by "kinds of information". In theory this could be implemented with SQL. However, our experience shows that building SQL tables for each kind of information is very time consuming and not very flexible. The opposite alternative is unstructuredness, e.g. like a Wiki. Wikis allow to enter data very quickly, but have the disadvantage that one can't easly produce text on demands (it's not easy to make a wiki book) and that full text search has its limits once the wiki starts growing. In addition, Wiki engines don't produce text, but the spit back page names plus the search context. E.g. you can't say something like "let's have a list of all the references on pages that belong to the category "instructional design modelling".
DITA can address some of the needs for flexible information retrieval architectures, in particular if combined with a xml-database web application like [eXist http://exist.sourceforge.net/].
- Flexible document production
Now lets image that you are engaged in teacher training, or that you are interested in reading all information related to some topic, e.g. how do I design enquiry learning. DITA would allow to create print or web documents on the fly, on a per needed bases.
- Authoring
In some cases, it is desired that information entered be complete according to some standards. A typical example would be lesson plans. A flexible TTW DITA-based editor could address this issue.
- A test case
DSchneider made some DITA extensions to have a writing tool for the TECFA SEED catalog