Submitter's message ActionItems: none
===============================================
Minutes of the OASIS DITA TC
Tuesday, 18 August 2026
Recorded by Nancy Harrison
link to agenda for this meeting:
https://github.com/oasis-tcs/dita/wiki/Previous-agendas
Attendance:
===========
Robert Anderson, Kristen Eberlein, Nancy Harrison, Bob Johnson, Zoe Lawson, Christina Rothwell, Leroy Steinbacher, Dawn Stevens
Business
========
Regrets: Stan Doherty
1. Minutes
11 August 2026 (Harrison, 17 August 2026)
https://groups.oasis-open.org/discussion/dita-tc-minutes-11-august-2026-uploaded
Kris moved, 2nd Dawn, approved by TC
2. Announcements; new items for agenda
- Zoe; making progress on OASIS membership issues.
- Kris; Dawn, how about DITA Europe?
- Dawn; deadline was officially Friday, but folks can still submit; right now we have 36 slots and 60 proposals, so I'm about to start doing the program.
3. Committee notes effort (Doherty)
Committee Notes.
https://github.com/oasis-tcs/dita/wiki/DITA-TC-Committee-Notes Updated description of mission
https://groups.oasis-open.org/discussion/updated-mission-description
[regrets from Stan, so no updates]
4. Update on spec progress (Anderson)
- Robert; we're ready for our review of keys, but we don't intend to open it till end of month; sometime during next week, Kris and I should get Content Fusion (aka CF) set up for that.
- Kris; I've been assuming that we want to continue using CF the way we have before?
- Robert; I agree, we just need to do the setup.
- Kris; given the changes Oxygen has made in CF since the last time we used it, I hope we'll be able to continue using it the same way; we'll test it this week.
- Christina; can you clarify details of how you've used it?
- Robert; we manage reviews by creating a separate branch map for each separate review, build a PDF of that map, then load that map into CF and open it to TC, so you can place comments right in the spec, BUT only as draft-comments, not as 'live' CF comments or as actual changes to the spec. We then leave it open for a couple of weeks. It can be useful to refer to the version of the spec on Jarno's site, but we don't review that; we only review our stuff, because stylistics are different. During the review, Kris and I often start to respond to some trivial comments, e.g. typos.
- Kris; Robert and I will have to test the current version of CF. Most companies using CF review content directly from their Github repos, so when people make changes in response to review, changes are actually pushed back to Github. We don't do that because we need an actual record of the original comments and text of our responses.
- Robert; that need relates to OASIS requirements; they let you use external tools for review, but they require an archive of all interaction at the end.
- Kris; this goes back to early reviews that were really painful; we first used webhelp->ditaweb by Mekon->Congility, then shifted to using CF, and with CF we use a different method for archiving.
- Nancy; so we'll start the actual review around beginning of September?
- Kris; right.
close 11:16am ET
-- Ms. Nancy Harrison
---------------------------------
Nancy Harrison
Principal, Infobridge Solutions
Nancy Harrison (Personal)
---------------------------------