Submitter's message ActionItems:
1. Kris will look into our decisions on how we'd handle relatinship between copy-to and resourceid for 2.0
2. Kris and Robert will discuss @s in a call this week.
3. Kris will add links to Jarno's spec for items to look at for examples.
4. Kris will set up a call with Nancy re: conditional processing
y===============================================
Minutes of the OASIS DITA TC
Tuesday, 1 April 025
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, Bob Johnson, Zoe Lawson, Christina Rothwell, Leroy Steinbacher, Dawn Stevens, Frank Wegmann, Leo Belchikov
Business
========
Regrets: Eliot, Scott, Stan, Eric
1. Approve minutes from previous business meeting
18 March 2025 (Rothwell, 19 March 2025)
https://groups.oasis-open.org/discussion/dita-tc-minutes-18-march-2025
Kris moved, 2nd by Dawn, approved by TC
2. Announcements
- DITA TC call cancelled for 08 April 2025 (ConVEX)
- Bob; at next week's Boston Dita User's group meeting, Ashley Hardin, senior content strategist at Red Hat, will talk on their content strategy. If interested, send mail to
admin@bostondita.org to get info. Also, Bob wll post info on DITA wiki.
3. Walk through spec review feedback
a. DITA addressing
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; we'll need to hold off on b. and c. till Stan and Eliot are here, but let's start with a., even though Stan isn't here...
- Kris; this topic was first done in 1.2 or 1.3; we revised it for 2.0, but there's not a whole lot of info in the topic. Stan and Eliot both think it's time to retire this topic
- Robert; we can just give them an a topic to identify resourceid element, but we can't say anything about it; any tool could be using it. It's not that we need to get rid of it, just need to rewrite, and it could have a natural example that would make it more useful.
- Kris; I didn't read it carefully enough; I thought they wanted to get rid of it.
- Frank; why drop it? we use that feature.
- Christine; and we use it everywhere
- Robert; we're not taking out the element; the issue is 'what do we do with this topic?'
- Zoe; the topic is also inaccurate; resourceid isn't the only way you can link CSHs, we use othermeta to create topic ids. And with other tools, you just have to name the files a certain way. This topic should rather be: 'hey, there are ways to do this and here are some of them. And Eliot offered to do update it to say that.
- Christine; it would be helpful to have tie it in with key @s; CSH are tied in with those.
- Kris; so we need rewrite; this focuses too much on resourceid; other folks use other methods. There are infinite different ways that apps can implement CSH, and we can't possibly know them all to mention them here.
- Robert; we focused on resourceid because this is the one we specificically designed for it.
- Frank; and many people just don't know about resourceid. Dawn, do your clients know about it?
- Dawn; I have many clients using it, but most of them use it bacause we helped them learn how to use it.
- Kris; when was resourceid added to DITA?
- Robert; it's been there since 1.0, but it got expanded wrt @s related to user assistance in 1.2, so we added this topic.
- Kris; and in 1.2 we added @appname and @appid on this element.
- Robert; in 1.0, we had @appname, but @id on this element had a different meaning from @id on every other DITA element. so in 1.3 we added @appid, so the tinkering was primarily in 1.3. Also in 1.3 we opened it up to have nested data elements.
- Zoe; do we ever explain what processors are supposed to do with it?
- Robert; we can't; there's nothing that they're supposed to do, they're not required to do anything with it. And if they do something, we can't say what they'll do. We could create an imaginary example, but not a real one; it's outside of our scope.
- Zoe; since I haven't used a tool that uses this, I don't know how to use it.
- Robert; we can't say how you would do that; it would have to be specific to an application.
- Zoe; would it be useful to say what DITA-OT does with it?
- Robert; it ignores it, which is the default behavior; if we're not writing for a specific app, it can't use it.
- Kris; we very specifically avoid documenting specific app processing.
- Robert; so the only thing we can say is that there's not defined processing; it's simply for tools that can use it.
- Zoe; I'd like to see 'this is available; processors can do something with it but they don't need to; by default it's ignored unless they do something'.
- Robert; do we say that in the language ref?
- Kris; here's the info you're looking for; we should have a link from the arch info to the language ref for that.
- Christine; yeah, providing that link would be great.
- Leroy; yeah, the Ozygen version of the spec has that link.
- Kris; right, we've been looking at Jarno's version; we should look at our own version.
- Robert; in 1.3, we had that link.
- Kris; I bet we don't have updated info on using copy-to in conojunction with resourceid; I think we decided any info about that would need to be in a CN or migration guide for 2.0.
***ActionItem: Kris will look into our decisions on how we'd handle relatinship between copy-to and resourceid for 2.0
b. DITA processing
Branch filtering
Eliot Kimber, 24 March 2025 (https://groups.oasis-open.org/discussion/review-branch-filtering)
c. Element reference
DITAVAL reference domain
[Eliot Kimber, 24 March 2025] (https://groups.oasis-open.org/discussion/review-ditaval-reference-domain
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; for indirect key backed addressing, I'll get on a call with Bob, Frank, what about @id ?
- Frank; I think Eliot's comments make sense.
- Kris; Can you provide feedback on Eliot's draft? Or will you just hold it till we have our CF review?
- Frank; I'll probably hold it for a couple of weeks.
- Kris; Nancy, what about conditional processing?
- Nancy; I'd like to get on the phone with you.
- Kris; Dawn, how about branch filtering?
- Dawn; I was going to write a note on Eliot's feedback, but time slipped away. If it's still valuable for me to do it, then it has to be after ConVES.
- Kris; let's hold it till we can have our conversation on a TC call. Robert, you and I need to have a call about @s; let's do it this week.
***ActionItem: Kris and Robert will discuss @s in a call this week.
b. Examples for conditional processing
https://github.com/oasis-tcs/dita/wiki/DITA-2.0-base-specification-work#examples-for-conditional-processing
- Kris; we don't have anyone signed up for conformance; Robert, Eliot and I need to look at conformance and see what we have in 2.0.
- Robert; we need to talk to Eliot.
- Kris; we'll try for a 3-way call, if we can't do it, we'll put it on agenda for a TC call.
- Kris; we said these weren't really good examples; I put them in a wiki page so folks could look and think about what they could contribute. Please look at these and see if you have real content that can be shared, so Robert and I don't have to come up with them. Looking at the examples, I wasn't always sure about goals, e.g flagging with @outputclass, I thought we were trying to keep the focus on new 2.0 functionality, but we're missing simple example. Please take a look at the list, and I'll link to -parts of Jarno's spec.
***ActionItem: Kris will add links to Jarno's spec for items to look at for examples.
- Kris; please look at example topics and see if you have content you can contribute, or if things need to be added.
11:50am ET close
-- Ms. Nancy Harrison
---------------------------------
Nancy Harrison
Principal, Infobridge Solutions
Nancy Harrison (Personal)
Portland OR
978-505-9189
---------------------------------