Tuesday, June 23, 2026

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.

Monday, December 16, 2024

I was absolutely honored with an Outstanding Volunteer Award for Colorado FIRST Lego League!



I am the Head Referee for Colorado FIRST Lego League, which is certainly a passion of mine! I've been involved with FLL since 2008.

We also coached 6 teams this year at Up-A-Creek Robotics. Three of them made it to State, and one of them one 2nd place Innovation Project!

Docbook nominated for 2024 Outstanding Approved Standard

DocBook has been nominated for the 2024 OASIS Open Standards Cup awards. The Cup Award is in recognition of exceptional advancements within the OASIS technical community. Two groups will be awarded the Cup, one for Outstanding Approved Standard and another for Outstanding New Initiative.


For 2024, the nominees for Outstanding Approved Standard are:



And the nominees for Outstanding New Initiative are:


Winners will be announced at the virtual OASIS Open Annual Awards Ceremony on Wednesday, 5 February 2025.

Tuesday, April 11, 2023

DocBook Schema v5.2, CSD 01 is available for public review

The DocBook Schema Version 5.2, Committee Specification Draft 01 is available for public review starting 04 April 2023 at 00:00 UTC and ends 03 May 2023 at 23:59 UTC.

You can download the ZIP file at:

https://docs.oasis-open.org/docbook/docbook/v5.2/csd01/docbook-v5.2-csd01.zip

"Send A Comment" at (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=docbook). #docbook

Thursday, March 09, 2023

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 

Thursday, May 28, 2020

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!

Monday, April 02, 2018

DocBook Schema Version 5.0 Errata 01 approved

OASIS is pleased to announce that The DocBook Schema Version 5.0 Errata 01 from the OASIS DocBook TC [1] has been approved as an OASIS Approved Errata.

The Errata updates the Schematron syntax that had caused the DocBook 5.0 RelaxNG schema to fail to parse properly with updated Schematron validators.

The prose specifications and related files are available here:

The DocBook Schema Version 5.0 Errata 01
OASIS Approved Errata
29 March 2018

Editable source (Authoritative):

HTML: 

PDF: 

Distribution ZIP file

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:


Members of the DocBook TC [1] approved this specification by Full Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Friday, June 23, 2017

DocBook v5.1 nominated for Outstanding Approved Standard award

Nice to get a nomination in the fourth annual Open Standards Cup!


This year's Outstanding Approved Standard award nominees were DocBook v5.1 from the DocBook TC, KMIP Specification and KMIP Profiles v1.3 from the OASIS Key Management Interoperability Protocol (KMIP) TC, Business Document Naming and Design Rules v1.0 from the OASIS Universal Business Language (UBL) TC, and XLIFF Version 2.0 from the OASIS XML Localisation Interchange File Format (XLIFF) TC.


Congrats to the TOSCA TC on winning the award.


https://www.oasis-open.org/open-standards-cup

Tuesday, April 18, 2017

Scaling quality using Schematron

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.


I'll be presenting on this topic at the CMS / DITA North America conference in San Diego, April 24-26, 2017. Please plan to attend!

URL: https://cm-strategies.com/2017-cms-conference/agenda-day-3-2/hudson-schultz/

Monday, January 16, 2017

Seattle/Kirkland-area DITA listening session on Jan 24/25

In addition to the downtown Seattle DITA listening session on Jan 24, we've added an additional listening session in Kirkland on Jan 25.
RSVP:
When:
  • Wednesday, January 25, 2017
  • 03:30-06:00 PM
Where:
Who:
  • Members of the OASIS DITA Adoption Technical Committee (local and video remote).
  • Area DITA writers, architects, managers, and tool smiths.
  • Company reps at all stages of a DITA implementation.
Goals:
  • 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. They are an opportunity for the Committee to 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/ The DITA Adoption Technical Committee focuses on identifying and removing obstacles to initial DITA adoption and long-term DITA investments. See https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita-adoption
What:
  • The format is informal within the following structure:
    • 30 minutes meet n' greet
    • 60 minutes attendee roundtable -- how is DITA doing at your company?
    • 30 minutes Q&A - OASIS TC members asking attendees
    • 30 minutes Q&A - local attendees asking OASIS TC members
    • (Optional) Dinner and refreshments at a local watering hole
RSVP:

Tuesday, January 03, 2017

Favorite Quote of the New Year

My favorite quote of the new year comes from the OASIS members newsletter:
However, the magnitude of your 2016 achievements cannot be denied, so we must begin with a brief look back. Here are just a few of last year's highlights:
- The indefatigable DocBook broke the record for the most downloaded spec in OASIS history. Barring cat videos and Adele's latest songs, DocBook 5.1 is one of the healthiest downloads on the Internet.

Tuesday, December 20, 2016

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!

Wednesday, November 23, 2016

DocBook v5.1 is now an official OASIS Standard!

OASIS is pleased to announce that DocBook Version 5.1. has been approved by the membership as an OASIS Standard [1].

The call to vote was made on 09 November 2016 [2] and the ballot closed on 22 November 2016. A minimum of 42 affirmative votes was needed in order to win approval. The finally vote tally was 63 affirmative votes with 4 abstentions. 

Our congratulations to the members of the TC and to the community of implementers, developers and users who have brought the work successfully to this milestone

DocBook is a general purpose [XML] schema particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications).

The Version 5.1 release introduces assemblies for topic-oriented authoring. It also addresses a selection of bugs and feature requests.

The Technical Committee provides the DocBook 5.1 schema in other schema languages, including W3C XML Schema and an XML DTD, but the RELAX NG Schema is the normative schema.

URIs:

The prose specifications and related files are available here:

DocBook Version 5.1

HTML (Authoritative): 

PDF: 

Editable source:

Schemas: 

DocBook V4.x conversion tools: 

Distribution ZIP files

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:



Wednesday, November 09, 2016

Voting opens for DocBook v5.1 as an OASIS Standard

The ballot to approve DocBook v5.1 as an OASIS standard is now open, starting at 09 November 2016 at 00:00 UTC. The ballot closes at 22 November 2016 at 11:59 UTC. 


This is a call to the primary or alternate representatives of OASIS Organizational Members to vote. 

If your company is a member of OASIS, please encourage your representative to vote in favor of this standard at: https://www.oasis-open.org/committees/ballot.php?id=3010 


The Version 5.1 release introduces assemblies for topic-oriented authoring. It also addresses a selection of bugs and feature requests.

To view the specification, please see:

Thursday, August 04, 2016

Media Standards for XML

Please excuse the vanity post, but I'm proud to be a contributing author to The Language of Technical Communication! My article is entitled, "Media Standards for XML" on pg 78. Lots of great information in this book compiled by Ray Gallon. Check it out!

Tuesday, June 14, 2016

A Geek Force for Good

I want to give a shout out to the Information Technology Disaster Resource Center (ITDRC), which helps communities with their technology infrastructure after a disaster.


I found out about the group during the 2013 floods in Colorado, where we specifically deployed to Lyons, Jamestown and Boulder.



The ITDRC has Field Disaster Response Teams (FDRT) and Remote Response Teams (RRT) from all across the United States and are comprised of service oriented IT and AV Professionals from many technology disciplines who volunteer their expertise and skills in times of disaster. We use our tech skills to help communities and small businesses continue operations and successfully recover from disaster.

If you have any technical expertise (especially with wifi, networking, radio communications), we would love to get you on board! Visit http://itdrc.org/volunteer.html for more info. We also love equipment and financial donations. See if your company would be willing to help us help those in need!

This past weekend, we held an Operations Field Exercise in Richardson, Texas. It was a great time to connect with other tech geeks and learn about our deployment kits and mobile command centers.






Monday, February 01, 2016

DITA 1.3 is now an official OASIS Standard

I'm pleased to announce DITA 1.3 is now an official OASIS standard!


From the press release:
 "The OASIS open standards consortium today announced that its members have approved the Darwin Information Typing Architecture (DITA) version 1.3 as an OASIS Standard, a status that signifies the highest level of ratification. DITA defines an XML architecture for designing, writing, and publishing information in numerous formats, including print, Web-based, mobile, and electronic publications. DITA is widely used for professionally-published books and magazines, technical documentation, online help, training and course development, marketing materials, and medical information because of its modular, topic-based approach and its ability to support content reuse.
This release of DITA comes in three parts, optimized for different audiences:
  • Base Edition is designed for application developers and users who need only the most fundamental pieces of the DITA framework.
  • Technical Content Edition includes specializations usually used by technical communicators.
  • All Inclusive Edition is designed for implementers who want all OASIS-approved specializations, as well as users who develop learning and training materials."
 For the spec or to download the schemas, go to: http://docs.oasis-open.org/dita/dita/v1.3/os/

The latest version of the DITA Open Toolkit also has support for v1.3, and can be downloaded here:
http://www.dita-ot.org/download

Several XML Editors have also added support for DITA v1.3, including:
  • oXygen XML Editor
  • XMetaL