際際滷

際際滷Share a Scribd company logo

Why DITA?

Download as PPTX, PDF
A
akashjd

This document discusses adopting the Darwin Information Typing Architecture (DITA) for content management. It provides an overview of DITA, including its focus on reusability through semantic tagging and topic-based writing. The key components of DITA like topics, maps, and the core reuse features of DITA maps, DITAVAL and conref are explained. The document also discusses strategies for implementing DITA like developing a tagging scheme, strengthening analysis and design processes, and training content editors.

1 of 18
Downloaded 20 times
Adopting DITALeaping Across the ChasmMathew VargheseContent Architect, Citrix
AgendaWhy DITABasics of DITA architectureContent reuse with DITASemantic tagging and topic-based writing
Why DITAIts all about adoptabilitythe chasm
Think Information not ContentCome at once. We have struck a berg.ContentContent is a symptom, not a solution!Knowledge
Can your product sell itself?
Knowledge StackInterfacesPeopleProductPortalsProcesses and ToolsPeopleContent DevelopersSubject Matter Experts
DITA Building BlocksTopicsConceptTaskReferenceMapsDitamapBookmap
Core Reuse Features (1.1)DitamapDitavalConref
DitamapTopic-level reuseCCRTRTCTTTT
DITAVALTopic-level reuseAttributeElementContent
ConrefElement-level reuseConrefElementTopic and locationElement IDTopic ID
Reuse ScenariosAcross releasesAcross deliverablesGuidesFormatsAcross audiencesAcross functions
Semantic Tagging and Topic-based WritingGet the specsDevelop your tagging schemeStrengthen your analysis and design processTagging and editing
Get the Right SpecsLanguage Specificationhttp://docs.oasis-open.org/dita/v1.1/langspec/ditaref-type.htmlArchitecture Specificationhttp://docs.oasis-open.org/dita/v1.1/archspec/archspec.html
Semantic TaggingBuild your tagging scheme
Analysis and DesignDesign WalkthroughsTopic Audits
Tagging and EditingEditors are your greatest assets!
QUestions

More Related Content

Why DITA?

Editor's Notes

  • #4: All the knowledge that the user needs to adopt the product should provided as efficiently as possible.
  • #5: We want to harness the knowledge that people within the organization possess. Content doesn'tt isn't a true representation of our products.Its time to pull the experts.Documentation lacks depth shows that somethings wrong in the knowledge sharing area.Creating lots of content is not the solution, We need to find a smarter way of pleasing the customer.
  • #7: This diagram illustrates the components of a knowledge ecosystem. The size of each component indicates the relative impact each component has on the efficiency of the ecosystem.