Submitter's message ActionItems:
1. Eliot wil write a new topic to replace the topic on context sensitive hooks, with a focus on @resourceid, but a mention of csh.
2. Kris and Robert will draft a definition of branch
3. Kris, Robert, and Eliot will do a 3-way call to discuss OASIS conformance requirements.
===============================================
Minutes of the OASIS DITA TC
Tuesday, 6 May 2025
Recorded by Nancy Harrison
link to agenda for this meeting:
https://github.com/oasis-tcs/dita/wiki/Previous-agendas
Attendance:
===========
Robert Anderson, Kris Eberlein, Nancy Harrison, Scott Hudson, Bob Johnson, Eliot Kimber, Zoe Lawson, Christina Rothwell, Leroy Steinbacher, Dawn Stevens, Frank Wegmann, Leo Belchikov
Business
========
Regrets: none
1. Approve minutes from previous business meeting
15 April 2025
https://groups.oasis-open.org/discussion/dita-tc-minutes-15-april-2025-uploaded
Kris moved, 2nd by Leroy, approved by TC
2. Announcements
- Leroy; Adobe DITAWorld is scheduled for June 3-5. If anyone's intereseted in speaking, let us know.
- Bob; continuing discussions with IIRDS, we're whether I'll be a member, or the consortium will open a seat for a DITA member.
3. Walk through spec review feedback
a. Context hooks for user assistance
Stan Doherty, 25 March 2025
https://groups.oasis-open.org/discussion/dita-20-spec-review-context-hooks-for-user-assistance Response by Eliot Kimber
- Kris; wrt Stan's comments, Stan says this arch spec discussion is really lightweight, 1.3 was focused on a specific implementation; for 2.0 we need to focus on @resourceid. Stan suggested removing section entirely.
- Eliot; Zoomin, which we originally used and which had a feature that used this, has gone away, but the structure we're using will not go away, since it's baked into the ServiceNow product, and FluidTopics, which is what we're now using, has the same feature, so @resourceid continues to be a pretty important feature, and other current/former Zoomin users will need it too.
- Christine; we don't use Zoomin, but we do use @resourceid a lot, and Oxygen recommends using it as well.
- Scott; would it be useful to have an example of the direct and indirect versions of a csh?
- Kris; what if we just added one or two examplss?
- Christine; right now, we're dealing with a team using anchor tags and trying to convert them to use @resourceid, and examples would be invaluable.
- Eliot; if we could generalize it, put emphasis on @resourceid as another way to identify topic, besides @id. Since we've extended its usage in 2.0 to replace @copy-to, we should talk about it.
- Kris; so you're suggesting not just retaining it, but expanding it to address various things that can be done with resourceid.
- Robert; I agree with Eliot.
- Kris; Eliot, will you rewrite/ write a topic for this? It would be broader in scope, focus on resourceid, mention csh, but broaden to include all the uses of resourceid.
- Eliot; yes, I will
***ActionItem: Eliot wil write a new topic to replace the topic on context sensitive hooks, with a focus on @resourceid, but a mention of csh.
b. DITA processing
Branch filtering
Eliot Kimber, 24 March 2025
https://groups.oasis-open.org/discussion/review-branch-filtering Stan Doherty, ? April 2025
https://groups.oasis-open.org/discussion/20-spec-feedback-branch-filtering-and Element reference
- Eliot; my main comment was about the need to define 'branch', we use it a lot, but it's not defined. Otherwise I just suggested some wording changes to technical language.
- Kris; Robert and I can take an AI to define branch
***ActionItem: Kris anf Robert will draft a definition of branch
- Eliot; we also need an example
- Kris; you also have some comments that would drive editorial revision before it's opened for review. They seem like straightforward points to change
- Eliot; in one place I suggested a paragraph, but it doesn't entirely make sense, not sure if that's the case.
- Kris; looking at Stan's review, he just had 2 questions for TC, one about moving a particular topic and another about adding an example, Robert, let's add Stan's comments as draft comments, if we can't work on them before the actual review.
- Frank; I'd appreciate getting a definition of branch, it has its own meaning in DITA, and a definition will be useful.
c. DITAVAL reference domain
Eliot Kimber, 24 March 2025
https://groups.oasis-open.org/discussion/review-ditaval-reference-domain Stan Doherty, ? April 2025
https://groups.oasis-open.org/discussion/20-spec-feedback-branch-filtering-and
- Kris; Eliot, did you review this?
- Eliot; yes, my main point is about the use of the term 'branch'; otherwise, basically agreeing with Robert that what we need is to just refer to arch spec rather than repeating info.
- Kris; and maybe we should move some examples that should be moved? Stan's feedback is very straightforward, no need to make changes to element ref.
4. Review of base spec sections
a. List of not reviewed sections
https://github.com/oasis-tcs/dita/wiki/DITA-2.0-base-specification-work
- Kris; wrt DITA map processing, it's just a dump of content; I can't commit to doing anything till after June 15th. Dawn, can you give a revised deadline?
- Dawn, can't get to it till after Memorial Day, so also mid-June
- Kris; what about conditional processing
- Nancy; I'll look at Dawn's and Leroy's comments and see if I think there's anything to add, I'll do it by next week (5/13)
- Kris; Dawn, what about branch filtering and ditaval?
- Dawn; I'll do those soon, since Eliot and Stan have already looked at them.
- Kris; attributes? Robert, you and I need to set a deadline to do an assessment of how much work needs to be done on @s, and whether we can do it, or need help.
- Kris; wrt conformance, we've already had one call on this, is this an area where Robert, Eliot and I just need a working call?
- Robert; unless Eliot wants to take a stab by himself, a three-way call would be best.
***ActionItem: Kris, Robert, and Eliot will do a 3-way call to discuss OASIS conformance requirements.
- Kris; 1/3 of our members are new since 1.3; we'll need to have a agenda section on conformance for OASIS to bring new folks up to speed.. Robert and Eliot, can you think of anything we need to cover that I've left out? Robert? '
- Kris; OASIS made conformance a req for specs, during 1.2 timeframe, but very late in cycle, so we were only able to do a little, and mostly left that unchanged for 1.3. Robert, Eliot and I should discuss it on a call before we bring it to the TC.
b. Examples for conditional processing
https://github.com/oasis-tcs/dita/wiki/DITA-2.0-base-specification-work#examples-for-conditional-processing
- Kris; still need people to provide examples for conditional processing, don't have any volunteers yet
- Scott; I'll try to get some.
12 noon ET close
-- Ms. Nancy Harrison
---------------------------------
Nancy Harrison
Principal, Infobridge Solutions
Nancy Harrison (Personal)
Portland OR
978-505-9189
---------------------------------