dita, semantics, content management, dynamic documents, and linked data – a marriage made in...

Dynamic Information Now for Everyone©2008 JustSystems

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

Linked Data Planet June 18, 2008

Amber Swope, Senior Solutions Consultant, JustSystemsPaul Wlodarczyk, VP Solutions Consulting, JustSystems

2Dynamic Information Now for Everyone©2008 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


Print/PDF

Wireless

Handheld

Web/HTML

CD-ROM

MultipleOutputs

Content Management System

Technical Authors,Subject Matter Experts,

and Reviewers

XML Assemblyand Publishing

MultipleDocument

Types

Manuals

Training

Help

WebContent

PromotionalMaterials

Knowledge Bases

Why XML Documents?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

MultipleOutputs

Content Management System

Technical Authors,Subject Matter Experts,

and Reviewers

XML Assemblyand Publishing

MultipleDocument

Types

Manuals

Training

Help

WebContent

PromotionalMaterials

Knowledge Bases

The rise of semantics in XMLThe 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.


Rising use of semantics in XMLRising 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 Use cases for Semantics in XML DocumentsSemantics in XML Documents

• Authors: Discover existing documents • Authors: Classify new documents • Authors: Tag items inline• Consumers: Navigate, search, retrieve

Author ConsumerDocuments

DiscoverClassifyTag

NavigateSearchRetrieve


DITA Standard 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 ModelDITA Maturity Model


Level 1: Level 1: TopicsTopics

• Single file (document) that contains multiple topics

• Topics are different types, hence the different shapes and colors

• Achieve simple single sourcing


Level 2: Level 2: Scalable ReuseScalable 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: Level 3: Specialization and CustomizationSpecialization 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 ReportProposal

Services Proposal Product Proposal


Level 4:Level 4:Automation and IntegrationAutomation and Integration

• Multiple users can create/share/use content from multiple repositories

• Multiple repositories contain multiple topics

• Achieve speed and efficiency


Level 5: Level 5: Semantics On-DemandSemantics 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:Level 6:Universal Semantic EcosystemUniversal Semantic Ecosystem

• All content become usable by all stakeholders• Achieve universal knowledge management

Publishing Company

Product Company

Government


DITA Paradigm ShiftsDITA 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 Use cases for Semantics in DITA DocumentsSemantics in DITA Documents

• Authors: Discover topics• Authors: Classify topics• Authors: Tag elements• Consumers: Inquire (answered with topics)• Consumers: Navigate, search, retrieve topics

Author ConsumerTopics

DiscoverClassifyTag

InquireNavigateSearchRetrieve


Classes of contentClasses of content

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

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)?


DMM revisited: DMM revisited: Organizations mature to leverage semanticsOrganizations 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 Dynamic Documents and Dynamic Publishingand Dynamic Publishing

• 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

• Dynamic Publishing: Using automation, content (structured and unstructured) is “pushed” to the point of consumption.• Examples: RSS feeds, portals, active / dynamic documents


Process Example: Process Example: Healthcare payer policies and proceduresHealthcare payer policies and proceduresStep 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: Product Example: Technical Service ManualsTechnical 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: Brand Example: Customer Response ManagementCustomer 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)


SummarySummary• 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

2,500 Customers,Marquee Brands

About JustSystemsAbout JustSystems


For more informationVisit our website:

http://na.justsystems.com/lifesciences

DITA Maturity Model landing page:http://gw.vtrenz.net/?T5XNTHG59J

Email us:[email protected]

Call us:(866) 793-1542