DITA & iiRDS for a Blog?!
Practical tips for your intelligent content
Intuitive Stack
Presented by
Lief Erickson — Intuitive Stack
www.intuitivestack.io
Goal
Group Participation
Results
Deserve more than manuals
Humans and machines
Semantic content maturity
iiRDS: The Good and Less Good
-
Standardized metadata
-
Vendor-neutral exchange
-
Component reusability
-
Enhanced findability through facets and personalization
-
It’s about the delivered experience
-
High learning curve
-
Technical overhead
-
Specialized expertise
-
Toolchain limitations
-
Limited awareness
iiRDS: Suitable Industries
-
Anyone producing large volumes of user assistance content
-
Manufacturing & Industrial Automation
-
Automotive & Aerospace
-
Medical Devices, Healthcare, & Pharmaceuticals
-
Software & Hi-Tech
-
Anyone with simple needs
-
Retail & E-Commerce
-
Publishing & Media (Other tools already exist suited for them)
-
Creative & Design Agencies
-
Personal Services (Wellness, Beauty, etc.)
iiRDS: Characteristics for suitable use
-
Complex technical ecosystems
-
Modular, reusable content needs
-
Integration with IoT, AR, or smart documentation delivery systems
-
Strong regulatory or interoperability requirements
-
Anyone with simple needs
-
Primarily marketing, editorial, or creative content
-
Low modularity and minimal reuse
-
Simple customer-facing FAQs or service descriptions
Vision: Use iiRDS to improve metadata-driven delivery within DITA workflows
What metadata do we care about?
Audience: Decision maker, Practitioner
Authors: Author1, Author2
Event: Conference, Webinar
Page type: Blog, Case study
Service: Content strategy, Information architecture
Subject scheme
<subjectdef keys="services" translate="no">
<subjectdef keys="intstack">
<topicmeta>
<navtitle>Intuitive Stack Services</navtitle>
</topicmeta>
<subjectdef keys="services.intstack.content-strategy">
<topicmeta>
<navtitle>Content Strategy</navtitle>
</topicmeta>
</subjectdef>
<subjectdef keys="services.intstack.ia"> [4 lines]
<subjectdef keys="services.intstack.ux"> [4 lines]
<subjectdef keys="services.intstack.workshops"> [4 lines]
</subjectdef>
</subjectdef>
Topic metadata
<metadata otherprops="relations">
<data name="parties">
<data name="content-creator" value="parties.company.author1"/>
</data>
<data name="page-types">
<data name="page" value="page-types.blog"/>
</data>
<data name="services">
<data name="service" value="services.intstack.content-strategy"/>
<data name="service" value="services.intstack.ia"/>
</data>
</metadata>
Align DITA to iiRDS metadata
iirds:InformationUnit: Deliverable, topic, or block.
iirds:ProductMetadata: Products, components, lifecycle phases, and product features.
iirds:Qualification: Audience (for us).
iirds:Party: Authors, OEM vendors, partners, etc.
iirds:Event: Error conditions in a product, not like this conference.
iiRDS Generator
iiRDS Consumer - Delivery Portal
Is this a good idea? Should you use this approach?
iiRDS vs other metadata standards
Find this presentation at
Intuitive Stack