 | | DITA 45 found. Page 1 of 2. |
#27076
Adobe Systems Speaks Out on DITA: Internal use of FrameMaker, CMS, and DITA
Asks Puny Sen, Project Lead, Instructional Communications at Adobe Systems to talk about the software giant's foray into the world of the Darwin Information Typing Architecture (DITA). Sen shares details about Adobe's recent DITA documentation project, the pro's and con's of using DITA with FrameMaker, as well as lessons learned of importance to anyone interested in adopting the DITA standard.
Ethier, Kay and Scott Abel. Bright Path Solutions (2005). Articles>Documentation>XML>DITA
#30230
Build-to-Order Documents with DITA
It is entirely possible to deliver custom, on-demand documentation that is precisely suited to a user's needs. It can be done today, using web-interface strategies and the right document format. This post shows how such a system could be implemented with the DITA format, and shows why it would be an ideal document-delivery system for programmers.
Armstrong, Eric. Sun Microsystems (2007). Articles>Documentation>XML>DITA
#30231
Building a Bridge: DITA, DocBook, and ODF
Some folks here are taking a very strong look at DITA. I'm certainly one of them. But we also have a huge legacy of documents in Solbook format (Sun's subset of DocBook). There are tools for editing such documents, and tools for processing them. and there are many people who are comfortable with those tools. So DITA isn't going to replace the world, just yet. But DITA makes extensive reuse possible. It's a format with a serious future, because "reuse" is a very big deal. It lets you single-source your information content so have one place to make an edit. That sort of thing becomes important when you have multiple revisions of a product, and/or multiple variations. It becomes important when different tools and different products use the same information in different ways. It can drastically improve quality, ensure uniformity of presentation. Finally, structured formats like DITA and DocBook create the kind of consistently-tagged information that allows for useful automation.
Armstrong, Eric. Sun Microsystems (2007). Articles>Information Design>XML>DITA
#29635
By organizing information around the goals that users are trying to accomplish, you can provide task-based information that truly addresses user needs. This article walks through the steps for creating more useful information navigation by implementing information development best practices with examples in the Darwin Information Typing Architecture (DITA).
Swope, Amber and Michael Priestley. STC Proceedings (2005). Articles>Documentation>XML>DITA
#27374
Darwin Information Typing Architecture
Darwin Information Typing Architecture (DITA) is an XML-based architecture for authoring, producing, and delivering technical information. The architecture and a related DTD and a W3C-Schema was developed by IBM.
#27075
Darwin Information Typing Architecture (DITA) 
The purpose of this research note is to introduce the Darwin Information Typing Architecture (DITA) and highlight its relationship to other information architectures like DocBook and Information Mapping.
Namahn (2005). Articles>Documentation>XML>DITA
#27001
Darwin Information Typing Architecture (DITA XML)
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.
Cover Pages (2005). Articles>Information Design>XML>DITA
#29287
If you line DocBook and DITA up, I think DITA can point to four technical differences that are arguably features in its favor.
Walsh, Norman. DITA for DocBook. Articles>Information Design>DocBook>DITA
#29971
Can DITA be used as a Help authoring technology? Superficially, of course it can! The DITA Open Toolkit includes an HTML Help transformer, an Eclipse Help transformer, and an HTML transformer (which can also generate some sort of Table of Contents). So isn't it obvious then? DITA is perfect for Help authoring. Or is it? Looking a bit deeper, it's not so obvious. Can I include context-hooks in my content? Can I specify a popup link? Can I build a modular Help system? If I can't, then DITA is probably not suitable for Help.
Self, Tony. HyperWrite (2007). Articles>Documentation>XML>DITA
#27456
This presentation addresses a low-effort-required solution for users looking to take a step into XML for their technical documentation. The Darwin Information Typing Architecture (DITA) and its associated public toolkit provide you with the DTDs, stylesheets and other tools you require to make your steps into XML.
Kravogel, Christian and Boris Horner. IDEAlliance (2005). Articles>Document Design>XML>DITA
#27048
The DITA Knowledge Base pages provide a reliable basis of technical and educational information on the standard.
XML.org (2006). Resources>Information Design>XML>DITA
#29285
#29286
The DITA Open Toolkit is an implementation of the OASIS DITA Technical Committee's specification for Darwin Information Typing Architecture (DITA) DTDs and Schemas. The Toolkit transforms DITA content (maps and topics) into deliverable formats.
Sourceforge (2007). Resources>Software>XML>DITA
#29391
DITA Users is a membership organization that includes: individuals learning DITA; organizations moving to single-source authoring and multi-channel publishing; vendors of XML Editors and XML Content Management Systems.
#29972
Two of the oft-quoted benefits of DITA, the Darwin Information Typing Architecture, are 'single-sourcing' and 'content re-use'. These benefits do not only apply to the commonly-accepted definition of technical documents, but to many other forms of documents from outside the technical communicator's realm.
Self, Tony. HyperWrite (2007). Articles>Documentation>XML>DITA
#27916
The abbreviation DITA stands for 'Darwin Information Typing Architecture', an information architecture based on XML. DITA is not a mere reinvention of the wheel: rather, it sets the standards for known structuring requirements. The most striking feature of this architecture is the clear orientation towards a technology for structuring, which has already proved its worth in online documentation.
Closs, Sissi. tekom (2006). Articles>Information Design>XML>DITA
#27373
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, books, and Web sites.
#29401
A gathering place for information about DITA.
#30232
Dynamic Content Delivery using DITA
This whitepaper defines a new publishing paradigm, which we will call dynamic content delivery. Dynamic delivery changes the rules, putting the reader in charge of what content is important and how it should be packaged. It transforms publishing to an audience of many to publishing to an audience of one.
Severson, Eric. Flatirons Solutions (2007). Articles>Content Management>XML>DITA
#27077
Frequently Asked Questions about the Darwin Information Typing Architecture
DITA experts Don Day, Michael Priestley, and Gretchen Hargis address the topic architecture of DITA, tips and techniques, and general DITA questions.
Day, Don, Michael Priestley and Gretchen Hargis. IBM (2001). Articles>Information Design>XML>DITA
#28230
Writing, compiling, and maintaining documentation is a necessary evil. While moving to DITA might not improve the quality of your documentation, it can streamline the process of creating and managing those documents.
Nesbitt, Scott. InformIT (2006). Articles>Documentation>XML>DITA
#29399
Introduction to DITA References
DITA is quickly becoming the dominant XML schema for topic-oriented authoring. DITA is a highly practical way of moving to XML authoring in general and granular content reuse in particular. DITA distinguishes itself from predecessor standards by explicitly rejecting the book paradigm in favour of a topic-oriented model.
Prescod, Paul. IDEAlliance (2004). Articles>Information Design>XML>DITA
#27000
Introduction to the Darwin Information Typing Architecture (DITA)
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. This document is a roadmap for DITA: what it is and how it applies to technical documentation.
IBM (2001). Articles>Information Design>XML>DITA
#28181
We seem to be heading in the right direction. The danger is that we keep talking to one another rather than evangelizing to a broader community.
Hackos, JoAnn T. Center for Information-Development Management (2005). Articles>Documentation>Standards>DITA
#27891
Lessons From The Trenches: DocZone.com Is Doing It With DITA
Interviews Chris Hill of DocZone.com and explores the lessons his firm learned while implementing the Darwin Information Typing Architecture (DITA).
Abel, Scott. Rockley Group, The (2006). Articles>Content Management>XML>DITA
| Copyright © 2001-08 by the EServer. All rights reserved. | Add a Work | Site Preferences | Discussion Forum | Habitués |
