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."