DITA talks

More vAInity, but here is a list of all of the conferences I have presented at for DITA:

2006

XML 2006 > DocBook vs DITA

2007

DITA West > A Document Standards Interoperability Framework for DocBook, DITA, ODF and More!

Abstract:

An interoperability strategy is critical to allow the use of content from multiple standards and sources. This presentation will describe an approach to defining a Doc Standards Interoperability Framework, supporting DocBook, DITA and ODF. 

• https://www.slideserve.com/harlow/a-document-standards-interoperability-framework-for-docbook-dita-odf-and-more

2009

XML-in-Practice DC > Professional Publishing on a Shoestring Budget

Abstract:

Professional Publishing on a Shoestring Budget, will discuss how to optimize your multi-channel publishing processes using the latest approved DocBook v5.0 schema and the DocBook Publishers schema.

2015

Optimizing the DITA Authoring Experience

Abstract:

This webinar compares and contrasts the ways of customizing your authoring environment and provides guidelines for their use.

CIDM 2015 Chicago > Browser Power: Client-side rendering of DocBook and DITA

Abstract:

What do Chrome, Firefox, Safari, Opera, Vivaldi, and Internet Explorer all have in common? Today’s modern browsers can dynamically render DITA and DocBook. Why use a separate rendering step in the publishing process, when the XML can be delivered directly from the server and rendered in any modern browser, including mobile? In this session, you will learn how to customize the browser presentation layer and some of the caveats for the content.

2017

CIDM 2017 San Diego > Scaling quality using Schematron

Abstract:

Do you have limited editorial staff or resources? How do you ensure content quality in spite of an ever-expanding set of content and the unrelenting pressure to deliver that content quickly? In this presentation, we’ll get you started using Schematron to scale your quality control initiatives! When integrated with an XML editor, Schematron provides real-time analysis and feedback to authors to ensure that content follows defined editorial rules. (Remember, we rely on DITA to establish and control structure, but DITA is silent regarding the overall linguistic quality of content.)

You will learn about the process of converting editorial style guide rules to Schematron, including what makes a good Schematron rule. We will provide tips and best practices based on how we implemented Schematron at Jeppesen. You’ll learn which editorial challenges lend themselves to Schematron solutions and which are too linguistically complex and require a human editor.

2018

CIDM 2018 Denver > LwDITA - The Reuse Zone

Abstract:

Your software developers document their code, but how do you reuse that information in your technical documentation with minimal effort? For some developers, it’s a very strange idea to reuse their code comments as tech doc. Today, we will take you on a journey to explore this very idea…

CIDM 2018 Denver > The ABCs of Plain English with Schematron

This presentation explains the process of converting Plain English rules to Schematron, and gives tips and best practices for how to use these rules along with your own editorial style rules. We cover the various levels of guidance available in Schematron, so you canIn this presentation, we'll demonstrate how to use Schematron to enforce Plain English guidelines. When integrated with an XML editor, Schematron gives real-time analysis and feedback to authors to make sure that content uses plain English.

2019

CIDM 2019 Raleigh > Farewell to style errors - using Schematron and Vale

Abstract:

The technical Julius Caesar. Act III, scene II: [Enter OmniMark Antony]

Friends, Countrymen, Editors, Writers, lend me your Style Guides! I come to bury Errors, not to praise them. The errors that men do lives after them (especially in print); The good is oft left unread. But let it not be with your content! Is error-free content ambitious? Perhaps. But here I am to speak what I do know...

*cited in a 2019 paper "The Role of Taxonomy and Search in Content Usability"

2020

ConVEx 2020 [online] > The Metrics Dashboard: A “cross-check” for quality issues

Abstract:

We will demonstrate how a metrics dashboard assembles the important quality information from your metrics reports and creates a complete picture of your content quality. We will examine best practices to identify potential quality issues.

2021

ConVEx 2021 [online] > There and back again: An early adoption of DITA 2.0

Abstract: 

DITA 2.0 introduces advances in content reuse, simplification of authoring, and improved user experience. The DITA Open Toolkit has also improved and added early support for many DITA 2.0 features. This presentation discusses the content model analysis, DITA constraints, tool integration, and migration approaches necessary for early adoption of the specification.

Benefit:

Is DITA 2.0 a march into Mordor, or sailing into the Gray Havens? Gain insights into why you should adopt DITA 2.0, and some of the pitfalls to watch out for! This presentation covers content model analysis, DITA constraints, tool integration, and migration approaches. DITA implementers will be able to apply these techniques toward their own implementations.

2022

ConVEx 2022 Tempe > Lessons from the Git Trenches

Abstract:

One of the most prevalent methods for managing technical content today is using Git. Your content management and repository strategy and initial setup can have lasting impacts. Come listen to our “war stories” from the git trenches and learn how we transitioned our content management approach to better scale with over 80k topics!

ConVEx 2022 Tempe > Refactoring DITA Links at Scale

Abstract:

How do you refactor over 80k topics with a fragile link infrastructure? What are the impacts of major changes to authoring, training, and publishing? With more topics added daily, with our “keyification” strategy, we tame the content beast and cancel the apocalypse. Learn how to approach link migrations and understand the benefit of keys in DITA content.

2023

ConVEx 2023 Baltimore > Project Mirabel: Xquery DITA Information System

Abstract:

Project Mirabel is an XQuery-based DITA information system that provides comprehensive information about DITA content managed in multiple git branches along with validation information and history. Mirabel provides a “where used” index over all the DITA content. This presentation describes the Mirabel system and how we came to build it.

ConVEx 2023 Baltimore > Realize your Schematron Impact with Xquery

Abstract:

Have you ever created a clever rule with the Editorial team, only to find out too late that it’s flagging half of the entire documentation corpus? Conversely, have you created a rule that is so specific that it never gets triggered? Learn how to analyze the impact of your rules using XQuery and BaseX.

ConVEx 2023 Baltimore > Scaling the Everest of Link Refactoring

Abstract:

What are the impacts of “keyification” to authoring, training, and publishing? How do you automate a massive refactor involving over 100k topics and minimize manual rework? Learn how our team scaled an “Everest” of link refactoring as we implemented keys to meet business and customer needs.

2024

ConVEx 2024 Minneapolis > Using AI to Accelerate Authoring

Abstract: 

SyncroSoft added the AI Positron plugin to the oXygen XML Author tools, but should you use it? Can you use it? What kind of impact will it have on authors? Will authors lose their job?. This presentation discusses the corporate hurdles for using this plugin, and the resulting impacts to our Product Content organization.

Benefit:

Understand how using AI as part of your authoring process can impact your organization. Learn about the IP and security risks, adoption and training requirements, and technical infrastructure needed to use AI Positron. Get a glimpse of our benchmarking, satisfaction measurement, and productivity impacts as a result of implementing this plugin.

2025

DITA Europe / ConVEx 2025 > Office to DITA: Transforming Content for Reuse and Multichannel Publishing

Abstract:

Is your organization struggling with departments siloed in creating customer-facing content in MS Office? How do you enforce consistency in style, grammar, and structure to provide a unified customer experience? How do you keep pace with rapid product updates, ensuring your documents reflect the latest information? And more importantly, how can you easily adapt that content for multichannel publishing, localization, and accessibility?

In this session, we’ll explore a transformative solution: using AI-driven conversion tools to migrate MS Office content to DITA. This conversion is more than just moving files—it's a leap toward content reuse, faster updates, and a seamless publishing experience across formats and languages.

Attendees will learn how AI-powered transforms streamline this process, ensuring that your content is not only structured for efficiency but also positioned to scale effortlessly across regions, devices, and platforms.

This presentation will equip you with a clear roadmap to modernize your documentation workflows, making your content ready for the future of technical communication.

Benefit:

Key Takeaways:

• Improved Efficiency: Automate time-consuming tasks and reduce manual rework with smart transformations.

• Cost Savings: Cut down on translation, localization, and maintenance costs through reusable content.

• Content Agility: Easily update content with every product release without starting from scratch.

• Multichannel Publishing: Enable your content to flow into multiple outputs—web, mobile, print—with ease.

• Accessibility and Localization: Ensure compliance with accessibility standards and expand global reach with localized content at scale.

The Wizard of Docs: Finding the Magic Behind Taxonomy-Driven Documentation

Abstract:

ServiceNow maintains a corporate taxonomy for its products, which was only weakly reflected in the product documentation. As part of a larger corporate information customer satisfaction improvement initiative, Product Content implemented a process to classify the ServiceNow Platform product documentation using the taxonomy. This process involved both automatic and authored classification, including the use of SubjectScheme maps to drive both authoring and delivery of content on servicenow.com/docs. This paper presents the implementation decisions we made, describes how our classification processes works, and outlines the governance and maintenance processes for managing the classifications as the taxonomy and content evolves.

2026

DITA Europe > Taxonomy For Good: Revisiting Oz With Taxonomy-Driven Documentation

Abstract:

As part of a larger corporate information customer satisfaction improvement initiative, Digital Content Delivery at ServiceNow implemented a process to classify the ServiceNow Platform product documentation using a product taxonomy. In the process of using SubjectScheme maps to drive both authoring and delivery of content on servicenow.com/docs, we gained several insights and modified our approach. This paper revisits the implementation decisions we made, describes how our classification processes work now, and shares our approach as we expand the use of classification using taxonomies.

DITA Europe > Building a Content Transmogrifier: Turning Reviews into Something Better

Abstract:

Calvin and Hobbes showed us the power of imagination with the Transmogrifier — a cardboard box that could transform anything into something new. In our organization, we needed the same kind of transformation for our content review process.

Traditional reviews were slow, fragmented, and hard to track across teams. To fix this, we built our own “Content Transmogrifier” using Git Pages, Jenkins automation, and oXygen Web Author. Together, these tools reshaped reviews from a frustrating chore into a transparent, collaborative workflow.

In this session, we’ll walk through how we:

• Automated publishing to eliminate manual overhead and errors

• Enabled real-time collaboration with in-browser editing

• Improved adoption by lowering the barrier for reviewers across groups

Attendees will leave with practical steps for building their own “Content Transmogrifier” — and a fresh perspective on how imagination, combined with the right tools, can turn reviews into something better.

Searching in vAIn

It used to be called a "vanity google" when you searched the web for mentions about yourself. What is that called now with AI? "vAInity search"? "Searching in vAIn"? "You're so vAIn"?

Here's what got when I asked Gemini to summarize the work I've done on DITA:

"Scott Hudson has actively worked on every major release of the DITA standard since 2006, contributing to DITA 1.1, DITA 1.2, DITA 1.3, Lightweight DITA (LwDITA), and DITA 2.0.

Because his tenure on the main OASIS DITA Technical Committee spans from April 2006 to the present day, his engineering footprint can be found across the entire evolutionary timeline of the standard:

1. DITA 1.1 (Released 2007)

Joining the committee right as DITA 1.1 was finalizing, Hudson contributed to early structural reviews and supported the rollout of the newly introduced Bookmap specialization, which allowed technical writers to organize standalone topics into formal book structures (chapters, notices, and appendixes).

2. DITA 1.2 (Released 2010)

This version marked his first major framework design. Serving as Secretary of the specialized subcommittee, Hudson co-architected OASIS Feature Proposal #12058, which officially integrated the Learning and Training specialization (learningPlan, learningAssessment) into the core DITA ecosystem. He also managed validation audits for the release's XML Schema Definitions (XSDs).

3. DITA 1.3 (Released 2015)

Hudson worked on managing the increased complexity of the DITA 1.3 release, which expanded the standard to include advanced troubleshooting maps, scoped keys, and structural domains for MathML and SVG graphic elements. He is formally credited in the standard's OASIS Acknowledgments for his review and grammar file testing across the Base and Technical Content editions.

4. Lightweight DITA / LwDITA (Released 2018)

Acting as a response to the massive 189-element footprint of DITA 1.3, Hudson co-developed LwDITA. He designed it as a highly constrained 48-element subset built specifically to bridge XML data seamlessly with web-native HTML5 (HDITA) and Markdown (MDITA) pipelines.

5. DITA 2.0 (Current Standard)

As a formal Feature Champion for the DITA 2.0 committee, Hudson focused on eliminating historic architectural pain points. He successfully sponsored schema updates that relaxed legacy constraints—allowing authors to use the <example> tag within sections or lists, and permitting phrase-level styling elements (<ph>) directly inside glossary terms."

End of the DITA TC era (for me)

As I prepare for my final TC meeting, I want to thank the OASIS DITA Technical Committee for what it has meant to me over the past two decades. Since joining the DITA TC in 2006, I have had the privilege of learning from and working with people who care deeply about structured content, interoperability, and getting the details right. That spirit of rigor, generosity, and constructive debate is rare, and it is a big part of what has made this committee so meaningful to me.

I am especially grateful to have been able to contribute across several eras of the work. Early on, I explored interoperability through the DocTape framework, trying to bridge DITA, DocBook, and ODF in practical ways. That work shaped how I thought about making standards useful across systems and formats, and it eventually connected to later work on Lightweight DITA and cross-format mapping among XDITA, HDITA, and MDITA.

I am grateful to have actively worked on every major release of the DITA standard since 2006, contributing to DITA 1.1, DITA 1.2, DITA 1.3, Lightweight DITA (LwDITA) committee note, and DITA 2.0.

I was glad to help with the Learning and Training specialization work, schema review, and publication checks. Later with Lightweight DITA, I particularly enjoyed co-creating the B-25 training manual conversion that helped demonstrate what Markdown-based DITA could do in practice. I also enjoyed meeting directly with DITA users as part of the Listening Sessions outreach of the DITA Adoption subcommittee.

More recently, it has been rewarding to sponsor a few DITA 2.0 improvements that remove friction for authors, including updates to the example element and glossary formatting.

Just as important as the technical work has been the people. This committee has shaped how I think, how I design content systems, and how I collaborate. I am deeply grateful for the conversations, the shared problem-solving, and the friendships that came with the work.

Although I am stepping away from the TC because of changes in my company’s OASIS membership, I will continue to follow the work and cheer it on. Thank you for everything. It has been an honor to be part of this community.

ChatGPT explains DocBook vs DITA

ChatGPT is the latest rage in AI. I thought I'd put it to the test, so I asked it: Explain DocBook vs DITA.

Here is the response:

ChatGPT: DocBook and DITA (Darwin Information Typing Architecture) are both markup languages used to create structured content for technical documentation. While they share some similarities, they have distinct differences in their approach to document creation and management.

DocBook is a general-purpose markup language that can be used to create a wide range of technical documents, including books, articles, and manuals. It was developed in the late 1990s and is maintained by the DocBook Technical Committee, which is part of the OASIS (Organization for the Advancement of Structured Information Standards) consortium.

In contrast, DITA is a specialized markup language designed specifically for creating technical documentation. It was developed in the early 2000s by IBM and is now maintained by the OASIS DITA Technical Committee. DITA focuses on creating modular, reusable content components that can be assembled into different documents.

One of the main differences between DocBook and DITA is their approach to content reuse. DocBook provides some support for content reuse through its use of entities, but it is not as comprehensive as DITA's reuse mechanisms. DITA uses a topic-based approach, where each topic represents a modular, standalone unit of content. These topics can be combined and reused across different documents, making it easier to maintain consistency and reduce duplication.

Another difference is their support for different output formats. DocBook has broad support for a wide range of output formats, including HTML, PDF, and EPUB. DITA also has good support for different output formats, but its focus on modular content means that it is best suited for online help systems and other types of documentation that can be assembled dynamically.

In summary, while both DocBook and DITA are markup languages used for technical documentation, they have different approaches to content creation and management. DocBook is a general-purpose markup language, while DITA is specialized for creating modular, reusable content components. Both have their strengths and weaknesses, and the choice between them will depend on the specific needs of your documentation project.

My response: DocBook v5.0 introduced the concept of Assemblies, which resemble DITA Maps, and a topic  type which enables stronger reuse capabilities, similar to DITA.

ChatGPT: Yes, that is correct. In DocBook v5.0, the concept of Assemblies was introduced to improve the management and reuse of content. Assemblies are similar in concept to DITA Maps, allowing authors to create collections of topics and arrange them in a hierarchy to build larger documents.

Additionally, DocBook v5.0 also introduced a new topic type, which allows authors to create reusable content modules that can be used in multiple documents. The new topic type provides stronger reuse capabilities, similar to the topic-based approach used in DITA.

These changes in DocBook v5.0 were designed to address some of the limitations of earlier versions of the markup language, particularly in the area of content reuse. By adopting some of the best practices and concepts from DITA, DocBook has become a more flexible and powerful tool for technical authors and publishers.

My response: Which is better?

ChatGPT: There is no definitive answer to which is better between DocBook and DITA, as the choice between the two depends on a variety of factors such as the specific needs of the project, the skillset of the team, and the intended audience.

DocBook is a general-purpose markup language that can be used for a wide range of technical documentation, including books, articles, and manuals. It has a wide range of output formats and a large user community, making it a good choice for projects that require a lot of flexibility and support.

DITA, on the other hand, is specifically designed for technical documentation and is highly modular, making it a good choice for projects that require a lot of content reuse and maintenance. It also has strong support for online help systems and other dynamic output formats.

Ultimately, the choice between DocBook and DITA will depend on the specific needs of the project and the preferences of the team. It's worth evaluating both options and selecting the one that is best suited for the specific needs of the project.

I found the responses quite accurate and interesting! Radu at oXygen also had an interesting experience with ChatGPT:  https://blog.oxygenxml.com/topics/using_chatgpt_in_a_dita_xml_project.html 

Clear skies, Jeppesen. Hello, ServiceNow!

Today is my last day at Boeing / Jeppesen. I will miss all of my colleagues in Information and Knowledge Services there. I'm excited for my new opportunity at ServiceNow, especially to work with such great folks as Toni Mantych, Tony Morales, and Dawn Bunting. I'm also excited to get to know the rest of the team and make work, work better!

Seattle-area DITA listening session on Jan 24, 2017

Are you interested in DITA want to provide feedback to the DITA community that might have an impact on its future? The OASIS DITA Adoption Technical Committee is extending an invitation to STC members and participants to attend a Seattle-area “DITA listening session” on Tuesday, January 24, 2017, 3:30-6:00 PM.

Where:

Xeditor (inside the Galvanize Building)
111 S. Jackson St.
Seattle, WA 98104

Although members of these Technical Committees interact with DITA prospects and DITA practitioners routinely at conferences and online, we suspect that our picture of how things are actually going for DITA companies is incomplete if we do not have venues for those DITA users and architects who have not had opportunity to attend conferences, local user groups (if they exist), or technical forums. These listening sessions are a form of outreach to DITA people where they live and work. The sessions are an opportunity for the Committee to obtain feedback from current, past and future DITA users. The Technical Committee recently released DITA Version 1.3 and is now assessing what sorts of features and/or capabilities might be important for DITA 2.0. See http://docs.oasis-open.org/dita/dita/v1.3/

Session Structures:

30 minute – meet n’ greet and then a 60 minute – attendee roundtable—how is DITA doing at your company?
30 minute – Q&A – OASIS TC members asking attendees
30 minute – Q&A – local attendees asking OASIS TC members
(Optional) Dinner and refreshments at a local watering hole (no host)

On site event but no registration required! Please RSVP by January 20th to:

Anthony Apodaca, Business Development
212 884 9402
a.apodaca@xeditor.com | http://www.xeditor.com 

I'd also like to find someone to host a Redmond/Kirkland/Bellvue-area session on Jan 25. Please let me know if your company would be willing to host!

DITA 1.3 released for Public Review

DITA V1.3 will be released for 30 day Public Review, starting 09 July 2015 at 00:00 UTC and ends 07 August 2015 at 23:59 UTC.
This has been a long journey, but I'm pleased to have been a part of this work. Please see the following links:

• http://docs.oasis-open.org/dita/dita/v1.3/csprd01/part0-overview/dita-v1.3-csprd01-part0-overview.html
• http://docs.oasis-open.org/dita/dita/v1.3/csprd01/part1-base/dita-v1.3-csprd01-part1-base.html
• http://docs.oasis-open.org/dita/dita/v1.3/csprd01/part2-tech-content/dita-v1.3-csprd01-part2-tech-content.html
• http://docs.oasis-open.org/dita/dita/v1.3/csprd01/part3-all-inclusive/dita-v1.3-csprd01-part3-all-inclusive.html

Optimizing the DITA Authoring Experience

I'll be giving a webinar tomorrow through the DCL Learning Series on "Optimizing the DITA Authoring Experience". There is still time to register: http://buff.ly/1J5iruk

Highlights from the CMS/DITA NA 2015 Conference

The Content Management Strategies/DITA North America 2015 conference was held April 20-22 in Chicago, Illinois. Over 350 attendees learned best practices in four tracks: Information Design & Development, Technical Solutions, Management, and Emerging Technologies.

As a member of the CIDM staff, I was fortunate to host the Emerging Technologies track and got a chance to learn about a few new technologies, myself! If you missed it, I tried to Live Tweet the key points from each of the sessions here: #cmsconference #emergingtechnologies

Several "game changer" presentations included:

• DITA Glass: Perceive everything as DITA (Radu Coravu, SyncroSoft; George Bina, SyncroSoft
• The dynamic information model (Dawn Stevens, Comtech Services, Inc.; George Bina, SyncroSoft)
• Preparing for Augmented Reality (AR) in technical communications (Rhonda Truitt, Huawei Technologies; Farhad Patel, Huawei Technologies)
• Ipad applications using visual search and Augmented Reality (Pim Bekker, Etteplan)
• Various presentations on Dynamic rendering of DITA

So what was game changing?

The guys at oXygenXML have developed a series of pipeline transforms (Project DITA Glass) that let you, for example, use a topicref (with a special url) to an Excel spreadsheet directly. That URL is transformed on-the-fly directly to DITA, which can then be rendered directly in a table as part of your document! It also can round-trip, so any changes made in the DITA are written back into the Excel sheet.

This is important for those times when you need information from a subject matter expert, but don't want to teach them DITA or have to manually convert their content so you can use it. It's a one-stop shop! They are working on many more transforms. My hope is that they will create one for PowerPoint to DITA for all of the Learning and Training folks out there. Most course developers still work in PowerPoint, but it would be much more powerful to use the DITA publishing tool chains for various outputs while letting the developers still create in their familiar tool.

Another one-stop shop technology is the Dynamic Information Model. Comtech and oXygenXML have partnered together to create an XML-based Information Model, where a company can document their editorial and content structures, while also enabling the automatic enforcement and expression of that Model in the authoring environment! It basically generates the schematron rules and tool tips for authors from the Information Model itself. Very powerful!

A consistent theme in emerging technologies and technical solutions was the dynamic rendering of DITA content (server-side and client-side). There were several approaches presented, but they basically eliminate the DITA-OT publishing step by using CSS+XSL to render DITA content directly or on-demand.

Another particularly interesting theme was presenting technical information in an Augmented Reality environment. In fact, there is a new technical committee being formed at OASIS to address this very subject area! There are some tools available today for creating AR, including DAQRI 4d Studio, Metaio creator and SDK, Wikitude SDK, nGrain. The benefits of this technology include: reduce quality errors, contextual instructions at point of use, remote expert support, increased productivity. AR statistically has been proven to improve first time quality on assembly tasks, with fewer errors. AR can provide procedural steps, along with an overlay of task location, assembly info and more to assist in the completion of a task.

Did you know that by 2020, 103 million cars will be AR-enabled? Are you aware of AR devices, such as Google Glass, Microsoft Hololens, and DAQRI? Now is the time to start preparing your technical content for use with these types of devices. The future is so bright, we need to wear AR shades!

Browser Power plug

Come to the CIDM 2015 CMS/DITA North America conference! I'll be presenting on:

Browser Power: Client-side rendering of DocBook and DITA

What do Chrome, Firefox, Safari, Opera, Vivaldi, and Internet Explorer all have in common? Today’s modern browsers can dynamically render DITA and DocBook. Why use a separate rendering step in the publishing process, when the XML can be delivered directly from the server and rendered in any modern browser, including mobile? In this session, you will learn how to customize the browser presentation layer and some of the caveats for the content.

Join CIDM in Chicago, Illinois, April 20-22, 2015 for the 2015 CMS/DITA North America conference, the premier content management event of the year. Meet with your colleagues and build new friendships and relationships.

At 2015 CMS/DITA North America, you'll find a superb line-up of more than 75 presentations and an Exhibition Hall bursting at the seams with the latest technology and product innovations. Each exhibitor offers technologies that help you create content, manage your content store, produce attractive and effective publications, and ensure the quality of what you deliver to customers. Remember, they are anxious to learn about your needs as well. 

Come for the community, experience new insights, and leave with a wealth of new ideas that help you reap the benefits of managing content in your organization. In its 17th successful year, CMS/DITA North America is the premier conference for everyone who manages technical and business content in both small departments and huge global enterprises.

For more information: http://www.cm-strategies.com

DITA Learning in the new Adobe Technical Communications Suite!

Adobe just announced a new Technical Communications Suite, and has included support for DITA Learning!

Full support for DITA standards

Take advantage of DITA 1.1, including support for Bookmap, Indexing, and Glossary specifications, and use the DITA 1.2 Learning and Training Content Specialization (beta) to develop compelling training content.

I'll definitely have to give this a try. The DITA Learning Content subcommittee is in the process of putting together more real-world examples using this standard that we've developed over the past several years. Maybe I'll try to put that together using the demo!

Metadata and Interoperability

Jim Earley has a very thoughtful post on metadata interoperability: http://jims-thoughtspot.blogspot.com/2008/04/metadata-interoperability.html

As part of DocBook v5, we added the ability to include content from other namespaces in the <info> block to support adding Dublin Core directly in your content. The <info> element's purpose is to house metadata that is not intended for display, so it's a really good fit.

Jim's argument, is that the various standards out there (DocBook, DITA, ODF at a minimum) should move to Dublin Core for metadata, and stop re-inventing the wheel. Dublin Core is an internationally accepted standard for metadata, so why not use it directly?!

I whole-heartedly agree. This approach would add more compatibility between standards, and maybe even facilitate better search! Along with that, Dublin Core is extensible, so it shouldn't be too difficult to add additional metadata fields if you need to.

more on DocBook vs. DITA

Teresa Mulvihill has written an article on DocBook vs. DITA at: http://www.dclab.com/dita_docbook.asp.

It's a well thought-out article, but I'd like to make a few clarifications:

As you may know, Jim Earley and I have presented on this topic and our Doc Standards Interoperability Framework at several conferences, and still hope to form an OASIS TC on document standards interoperability.

In the article, Teresa states:

"DocBook is hierarchical by nature, and must be developed to allow for single-sourced content. DocBook has a fixed element and attribute set."

I've successfully used and recommended single-sourcing approaches with DocBook, without additional development. It's quite easy to set up a book or article and use XIncludes or even file entity references to pull in content from a common pool of content structures (usually section or chapter).

It's also fairly easy to extend the elements and attributes in DocBook. This has been made even easier with DocBook v5.0 and RelaxNG. In fact, the DocBook Subcommittee for Publishers that I chair, has helped organize the source patterns for DocBook v5 with a modular approach, enabling easier customizations to be created. Our subcommittee has created a customization geared specifically to publishers, without all of the technical blocks and inlines in full DocBook. This significantly reduces the tag set for folks that do not produce software or technical documentation to use the DocBook standard for general publishing!

DocBook can generate more than PDF, HTML and HTMLHelp. The docbook-xsl-1.73.2 stylesheet distribution supports: html, htmlhelp, javahelp, manpages, xhtml, Word roundtrip, slides and websites!

I would also argue that DocBook can be used on very high volume documentation projects, as well as small and medium projects. Just ask Sun, HP, various Linux distros, and more listed here: http://wiki.docbook.org/topic/WhoUsesDocBook

You might also find Norm's blog on DocBook vs. DITA interesting: http://norman.walsh.name/2005/10/21/dita

We are also working on some exciting developments for the Interoperability Framework, so stay tuned!

DocBook vs. DITA: revisited

The Content Wrangler has published a very interesting article by Dick Hamilton on choosing an XML schema.

I get asked very similar questions all the time! I think I'll start sending folks to this article as recommended reading...

DITA Learning Content accepted for DITA 1.2

More big news in the standards world today! The DITA 1.2 feature proposal #12058, "Design and language specification for DITA learning and training content," submitted by the DITA Learning and Training Content sub-committee was approved at today's DITA TC meeting.

Congratulations to John Hunt and all the members of the DITA Learning Content SC! The specification and sample plugins are all publicly available. Next steps for us is to work on our Best Practices for Implementation and create some sample processing for the DITA OT. This effort will continue into the first quarter of 2008.

DITA Learning Content specialization open for review!

The OASIS DITA Learning and Training Content Specialization Subcommittee is proud to announce the availability of our specification for DITA Learning Content for public review.

The design and language specification for the DITA learning and training content is available here, and the DITA Open Toolkit plugin with working DTD, XSD, DITA content samples, and documentation is available here.

The goal of the subcommittee is to develop a general top-level design for structured, intent-based authoring of learning content with good learning architecture, following DITA principles and best practices.

This specification was formally submitted to the full OASIS DITA Technical Committee today, after we completed the designs, samples, and language specifications for the learning topic types, the learning map domain, the learning interaction domain, and IEEE LOM learning metadata. The intention is to have this specification approved by the TC for inclusion in DITA 1.2, though most of this work is built on the existing DITA 1.1 infrastructure.

Please send any review comments via the public comment facility.

Doc Standards Interoperability Framework whitepaper now available!

Jim Earley and I have presented about the Doc Standards Interoperability Framework at XML 2006, DITA West 2007, Open Publish 2007, OASIS Symposium 2007 and DITA West 2007.

The whitepaper is now available at:
http://www.flatironssolutions.com/downloads/Interoperability_Framework.pdf.
This whitepaper contains greater detail on the business case for interoperability, as well as specifics on the framework. If you are interested in exchanging content between DocBook, DITA, ODF and/or other document standards, you should definitely check it out!

We are still working on the charter for the proposed OASIS Doc Standards Interoperability TC. Hopefully we can get that finished soon to form the TC before year-end.

DITA 1.1 Officially Released!

It's been a lot of work, but we've finally released version 1.1 of DITA! I've been involved heavily in DITA 1.1, as well as the Learning Content specialization subcommittee.

The full press release is available here:
http://www.oasis-open.org/news/oasis-news-2007-08-13.php

Key features of this release include:

• Enhanced print publishing capabilities with the new DITA Bookmap specialization, including extended book metadata.
• New elements (<index-see>, <index-see-also>, and <index-sort-as>) for "see" and "see-also" references.
• New elements (<abstract>, <data>) for defining structured metadata, as well as the ability to add new metadata attributes through specialization.
• New elements for image scaling.
• The glossary specialization, adding new elements for glossary entries.
• Support for foreign content vocabularies (<unknown> element)

UPDATE: The DITA OpenToolkit 1.4 has also been released, including support for DITA 1.1. For more information, please see:
http://sourceforge.net/forum/forum.php?forum_id=724798

New DITA information resources

Bob Doyle has created several new DITA information resources:

• DITA News is a resource website and industry newsletter.
• DITA Blog - blogs about DITA
• DITA Wiki
• DITA infocenter - a searchable knowledgebase for DITA users
• DITA Users - helping authors get started with topic-oriented structured writing
• DITA Tutor - self paced and instructor led DITA tutorials and workshops

DITA News will also aggregate posts that use the tag DITA. Check 'em out!

Dynamic Publishing with DITA

With DITA's modular, reusable information elements, you can not only publish across different formats and media - but also flexibly recombine information in almost any way you like.

Initial DITA implementations have focused primarily on publishing to pre-defined PDF, HTML and Help formats - basically static publishing with DITA. The real promise of DITA, however, lies in supporting dynamic, personalized content delivery.

At Flatirons Solutions, we've developed a very cool application on top of Mark Logic to enable this dynamic publishing. We've written a whitepaper about it here:
http://www.flatironssolutions.com/Downloads/Whitepaper_DCD_Using_DITA.pdf
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".

What's Inside:

• Static vs. Dynamic Publishing
• DITA: Dynamic Assembly of Topics
• A Scalable Approach to Dynamic Content Delivery
• A Complete DITA Publishing Solution
• Bottom Line Benefits