DITA, Semantics, Content Management, Dynamic Documents, and Linked Data – A Marriage Made in Heaven?
Upcoming SlideShare
Loading in...5
×
 

DITA, Semantics, Content Management, Dynamic Documents, and Linked Data – A Marriage Made in Heaven?

on

  • 7,340 views

DITA was conceived as a model for improving reuse through topic-oriented modularization of content. Instead of creating new content or copying and pasting information which may or may not be current ...

DITA was conceived as a model for improving reuse through topic-oriented modularization of content. Instead of creating new content or copying and pasting information which may or may not be current and authoritative, organizations manage a repository of content assets – or DITA topics – that can be centrally managed, maintained and reused across the enterprise. This helps to accelerate the creation and maintenance of documents and other deliverables and to ensure the quality and consistency of the content organizations publish. But the next frontier of DITA adoption is leveraging semantic technologies—taxonomies, ontologies and text analytics—to automate the delivery of targeted content. For example, a service incident from a customer is automatically matched with the appropriate response, which is authored and managed as a DITA topic. Learn how organizations can leverage DITA, semantics, content management, dynamic documents, and linked data to fully utilize the value of their information.

Statistics

Views

Total Views
7,340
Views on SlideShare
7,255
Embed Views
85

Actions

Likes
10
Downloads
194
Comments
0

3 Embeds 85

http://thecontentguy.net 63
http://www.slideshare.net 18
http://www.linkedin.com 4

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

DITA, Semantics, Content Management, Dynamic Documents, and Linked Data – A Marriage Made in Heaven? DITA, Semantics, Content Management, Dynamic Documents, and Linked Data – A Marriage Made in Heaven? Presentation Transcript

  • DITA, Semantics, Content Management, Dynamic Documents, and Linked Data – A Marriage Made in Heaven? Linked Data Planet June 18, 2008 Amber Swope, Senior Solutions Consultant, JustSystems Paul Wlodarczyk, VP Solutions Consulting, JustSystems
  • Introductions
    • Amber Swope
      • Senior Solutions Consultant, JustSystems
      • Almost 20 years of industry experience
      • Author of papers/presentations on information development and information architecture, including the DITA Maturity Model
      • Supported information developers producing DITA content in Rational group at IBM
      • Implements DITA solutions for JustSystems clients
    • Paul Wlodarczyk
      • Vice President, Solutions Consulting, JustSystems
      • 25 years experience in content lifecycle technologies
      • Author and speaker on various aspects of the content lifecycle
      • Background in software development, professional services, content management, document XML
      • Business experience in manufacturing, high tech, retail, aerospace, pharma, insurance
  • Agenda
    • Historical perspective: Document XML
    • Use cases for semantics in documents
    • DITA Maturity Model
    • DITA and Semantics
    • Dynamic Documents
    • Examples / Case Studies
  • Content Management System Technical Authors, Subject Matter Experts, and Reviewers XML Assembly and Publishing Why XML Documents?
    • XML separates content, structure, and format
      • XML documents are tagged for structure (e.g. Paragraph, Heading, List Item, etc.)
      • Structural tagging enables style sheet formatting
    Because it separates content, structure, and format, XML is perfectly suited for structured authoring and publishing – enabling single-source authoring / multi-channel publishing Print/PDF Wireless Handheld Web/HTML CD-ROM Multiple Outputs Multiple Document Types Manuals Training Help Web Content Promotional Materials Knowledge Bases
  • Content Management System Technical Authors, Subject Matter Experts, and Reviewers XML Assembly and Publishing The rise of semantics in XML XML adopters soon discovered that true single sourcing required shared or “reused” content Shared content requires metadata for the files that are shared. Semantic metadata facilitates XML content reuse by helping authors share and find shared content at the file level. Print/PDF Wireless Handheld Web/HTML CD-ROM Multiple Outputs Multiple Document Types Manuals Training Help Web Content Promotional Materials Knowledge Bases
  • Rising use of semantics in XML
    • Some XML adopters implemented sophisticated electronic documents
    • Semantic markup within the text (e.g. tagging procedures, part references, other named entities) enables dynamic document behaviors
      • Conditional text
      • Configurable manuals
      • Integrated search
      • Data driven fields
      • Context menu behaviors
      • Applications integration
      • Auto-linking
      • Embeddable into devices
      • Etc.
  • Use cases for Semantics in XML Documents
    • Authors: Discover existing documents
    • Authors: Classify new documents
    • Authors: Tag items inline
    • Consumers: Navigate, search, retrieve
    Author Consumer Documents Discover Classify Tag Navigate Search Retrieve
  • DITA Standard
    • Darwin Information Typing Architecture
    • A standardized framework for management and extensibility of XML document types
    • The Next Step in XML Manageability
      • Interoperability and tool independence
      • Reuse
      • Collaborative authoring
    • Originally developed by IBM
    • Published as an OASIS Specification in May 2005
    • 80%+ of all new document XML projects are DITA
  • DITA Maturity Model
  • Level 1: Topics
    • Single file (document) that contains multiple topics
    • Topics are different types, hence the different shapes and colors
    • Achieve simple single sourcing
  • Level 2: Scalable Reuse
    • Multiple maps referencing topics that are stored in individual files
    • Same topics can appear in multiple maps
    • Achieve flexible reuse
    Map 1 Map 2
  • Level 3: Specialization and Customization
    • All topic types are from Topic
    • You can develop specializations from any topic type
    • Achieve quality and consistency
    Create the right topic type for your content Topic Task Concept Reference Event Announcement or… Insurance Claim or… Use Case Specification or… Tutorial Policy Report Proposal Services Proposal Product Proposal
  • Level 4: Automation and Integration
    • Multiple users can create/share/use content from multiple repositories
    • Multiple repositories contain multiple topics
    • Achieve speed and efficiency
  • Level 5: Semantics On-Demand
    • Users can create/share/use information (content and data) stored in multiple content and data repositories
    • Combination of content and data allows dynamic publishing and mash-ups
    • Achieve dynamic personalization
    Content Repositories Data Sources Map Hubs Taxonomies Dynamic Publishing Mash-ups
  • Level 6: Universal Semantic Ecosystem
    • All content become usable by all stakeholders
    • Achieve universal knowledge management
    Publishing Company Product Company Government
  • DITA Paradigm Shifts
    • People
      • Writer  Knowledge Worker
      • Format  Structure
      • File  Tag
      • Create  Reuse
    • Technology
      • DTP  XML/DITA
      • Desktop  Enterprise
      • File system  Component CMS
    • Process
      • Publish  Render
      • Document-centric  Content-centric
      • Manual  Automated
    • Content
      • Application-specific  Standards-based
      • Monoliths  Compound documents
      • Structural mark-up  Semantic mark-up
    • Topics become the unit of content lifecycle management (semantic base)
    • Topics can become the publication in a dynamic publishing scenario
  • Use cases for Semantics in DITA Documents
    • Authors: Discover topics
    • Authors: Classify topics
    • Authors: Tag elements
    • Consumers: Inquire (answered with topics)
    • Consumers: Navigate, search, retrieve topics
    Author Consumer Topics Discover Classify Tag Inquire Navigate Search Retrieve
  • Classes of content
    • DITA changes the way all content is created, managed, and consumed
      • Component content management necessitates content classification
      • Think about how these would change in a component-oriented worlds, where everything is tagged at the topic level (and perhaps lower)?
    • Product content
      • Documentation
      • Technical Support
      • Help systems
      • Product Training
    • Process content
      • Policies & Procedures
      • SOPs
      • Training
      • Regulatory filings
    • Branded content
      • Web content
      • Customer correspondence
      • Data sheets, glossies
      • Advertising copy / media
  • DMM revisited: Organizations mature to leverage semantics
    • While many organizations adopt DITA initially for the benefits of single-source publishing, then in short order for the reuse (content management) benefits, they will ultimately mature to rely on DITA for its benefits as knowledge management technology
  • Dynamic Documents and Dynamic Publishing
    • Dynamic Publishing: Using automation, content (structured and unstructured) is “pushed” to the point of consumption.
      • Examples: RSS feeds, portals, active / dynamic documents
    • Dynamic Documents: Documents that are connected via database queries and web services to authoritative sources that can self-update. Data and documents are combined in a “document application.”
      • Content always up-to-date, authoritative, eliminates the need to publish
    • Dynamic publishing puts semantic DITA content to use
  • Process Example: Healthcare payer policies and procedures
    • Step 1: Convert to DITA for the benefit of faster search and retrieval of relevant topics in a call center / claims center environment (Level 1)
    • Step 2: Embed the DITA topics in a dynamic document interface that combines member, claim, provider data to create a context for recalling the appropriate policy/procedure topics (Level 5)
    • Step 3: Extend the dynamic document interface to capture information about the customer encounter (Level 6)
  • Product Example: Technical Service Manuals
    • Step 1: Convert to DITA for the benefit of content reuse across related products and multichannel publishing (Levels 1 and 2)
    • Step 2: Create a dynamic document viewer that renders the document based upon fault conditions and other data (e.g. diagnostics), and integrates enterprise data such as job ticketing, parts logistics, part catalogs, etc. (Level 5)
    • Step 3: Extend the semantic use of DITA to support multi-faceted taxonomies (classify training, documentation, and knowledge base by user/task, product, technology, and faults) to improve information reuse across publications and formats (Level 6)
    • Step 4: Provide improved discovery tools to improve relevancy of search to use the new taxonomy (Level 6)
  • Brand Example: Customer Response Management
    • Step 1: Convert customer responses to DITA for the benefit of content reuse across customer responses (e.g. across multiple proposals, inquiries, or correspondence) (Level 2)
    • Step 2: Create a dynamic document application for automatically generating consistent responses that combines DITA topics with enterprise data (e.g. a proposal generator) (Level 3-4)
    • Step 3: Extend the semantic use of DITA to support auto-responding (e.g. automated proposal generation, finding “questions” in RFPs and matching “answers” from the DITA topics in the CMS) (Level 5)
    • Step 4: Expose the auto-response system directly to customers through the web site (an instance of dynamic publishing) (Level 6)
  • Summary
    • DITA is fundamentally semantic technology
    • Migrating to DITA provides a foundation for a Universal Semantic Ecosystem
    • DITA has applicability to Product, Process, and Brand content
    • DITA sets the stage for a migration away from static to dynamic publishing
    • Dynamic documents can combine semantically tagged DITA content with enterprise data to create context-rich, content-rich applications
    • Global Presence
      • 1,000 employees, ‘07 revenues of $110M
      • HQ in Japan; Corporate Offices in NJ, Vancouver and London; Sales Offices Worldwide
    • Our Experience
      • Established in 1979
      • Market leader with over 2,500 customers
    • Our Expertise
      • Global provider of office productivity, information management, consumer & enterprise software
      • Framework for XML-based content creation, integration, visualization and delivery
    • Our Credibility
      • Gartner “Cool Vendor” in CM 2008
      • KM World “100 Companies that Matter” 2007
      • IBM CTO Innovation Award 2006
    About JustSystems 2,500 Customers, Marquee Brands
  • For more information
    • Visit our website:
      • http:// na.justsystems.com/lifesciences
    • DITA Maturity Model landing page:
      • http://gw.vtrenz.net/?T5XNTHG59J
    • Email us:
      • [email_address]
    • Call us:
      • (866) 793-1542