dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Groups - DITA TC Meeting Minutes 7 March 2023 uploaded
- From: Nancy Harrison<nharrison@infobridge-solutions.com>
- To: <dita@lists.oasis-open.org>
- Date: Sat, 18 Mar 2023 04:22:59 +0000 (UTC)
Submitter's message
ActionItems:
1. Eliot will return to original email and look more at effect of @scope and @format.
2. Kris and Robert will look at emails and spec and see if there are places they need to make adjustments.
=================================================
Minutes of the OASIS DITA TC
Tuesday, 7 March 2023
Recorded by Hancy Harrison
link to agenda for this meeting:
https://wiki.OASIS-open.org/dita/PreviousAgendas
Attendance:
===========
Robert Anderson, Tammy Crowley, Kris Eberlein, Nancy Harrison, Scott Hudson, Eliot Kimber, Zoe Lawson, Kathryn Torriano, Frank Wegmann, Jim Tivy, Todd Thorner
Business
========
1. Roll call
Regrets: Keith Schengili-Roberts, Robert Anderson (for last 30 minutes)
2. Approve minutes from previous business meeting:
Approve minutes from previous business meeting:
21 February 2023
https://lists.oasis-open.org/archives/dita/202302/msg00049.html (Schengili-Robert, 25 February 2023)
- Kris moved, 2nd Tammy, approved by TC
3. Announcements
Other announcements? none
4. Action items and volunteer tasks
[updates only; see agenda for complete list]
24 January 2023
Robert & Bill: Work on mentions of error conditions in body text; aggregated error conditions in appendix
- Robert; I've had email from Bill that we need to meet together about this item.
5. Re: Rework of cascading processing rules
https://lists.oasis-open.org/archives/dita/202302/msg00040.html (Kimber, 21 February 2022)
- Eliot; this came out of my task to rewrite rules for cascading. Kris had feedback on use of 'merge' and how to talk about how @s are specified. wrt merge, we introduced that term after @cascade="merge", so I think we can use it. In fact, I don't know how we can talk about it without using term 'merge'. wrt other issue, i.e., clarifying how @s get values, the rules as defined in the spec distinguish between values specified in markup, values set in a subjectScheme, and values provided by processors. Do we have specific rules on what you do for those values in any case? Do we need to distinguish between values specified in grammar and by users? I think there's no need, because XML does't make a distinction.
- Kris; Robert and I need to look at this, wrt your original suggestion for wording. How do processors have to handle @scope, not @format?
- Robert; they both matter,
- Eliot; that's a non-obvious edge case; I'll have to clarify that.
- Kris; I can take an AI to look at your emails, current spec wording, and current examples that illustrate cascading, and see whether we need a new example or changes to the current one; we have to pay very careful attention to not breaking current usage.
***ActionItem: Eliot will return to original email and look more at effect of @scope and @format.
***ActionItem: Kris and Robert will look at emails and spec and see if there are places they need to make adjustments.
- Kris; there are multiple examples in spec that pertain to this, and we need to look at them.
6. Technical content review C: Programming, software, and UI domains
https://lists.oasis-open.org/archives/dita/202301/msg00005.html (Anderson, 09 January 2023)
Status of review
Participation: Eliot, Kris, Robert, Tammy, Zoe, Stan, Bill, Frank, Nancy
Update (Anderson)
- Robert; no updates; should have more time starting this week.
7. Review E.2: Troubleshooting
Opening of review:
https://lists.oasis-open.org/archives/dita/202302/msg00035.html (Eberlein, 20 February 2023)
NEW Status of review:
https://lists.oasis-open.org/archives/dita/202302/msg00052.html (Eberlein, 28 February 2023)
NEW element
https://lists.oasis-open.org/archives/dita/202303/msg00006.html (Eberlein, 07 March 2023)
- Kris; We need to close loop with Stan wrt diagnostics-general for new #2. We're broadening use of responsibleParty; now, we want to let this element serve a bigger purpose, we want it to provide any info that people may need before providing steps for solving the problem. For example, do they need admin privileges? will a repair void a warranty? etc. etc. Is there anyone who will work with me to draft new language?
- Tammy; what can go into it?
- Kris; it's specialized from paragraph, so it can contain lots of stuff.
- Tammy; is there a generic title to be used in a rendering engine, or is it implementation dependent?
- Kris; it's 100% implementation-dependent. If anyone has ideas about this, especially about use cases, let me know.
- Tammy; I'll ask folks about it.
8. Review F: Syntax diagram domain
Opening of review:
https://lists.oasis-open.org/archives/dita/202302/msg00056.html (Eberlein, 28 February 2023)
Status of review:
https://lists.oasis-open.org/archives/dita/202303/msg00002.html (Eberlein, 07 March 2023)
- Kris; sent out a status closing it this morning; Robert will resolve comments from this review. Robert, can you give us a quick overview?
- Robert; I went thru some comments; some common themes, e.g., questions of how these things render, that it would be good to have samples. I agree, but these are not widely used, they're based on IBM's markup for syntax diagrams, which came from SGML. rendering for them. Someone did an SVG rendering of them, but I don't remember what these are supposed to look like (that processor is still out there, we should run some examples thru it to see what they look like). Also, a purely visual result isn't usable to a screen reader. We need to get the plugin running, but also to stress that these are only a visual representation and no more. And some knowledge about them is lost, so I'll need more thought on this.
- Frank; if you're going over tooling, I'd be willing to work on this;
- Robert; the plugin out there works pretty well, but I'll have to look at that to figure out what the real meaning of some of the elements are.
- Frank; I'm going to have to use this in the future, so I need to understand it.
- Kris; my knowledge is almost 20 years old, but I have some content I developed at IBM, if I can find it. Remember that for 1.3, all these were part of programming domain; we then put it into a separate domain because it was rarely used.
- Zoe; how does it relate to syntax highlighting?
- Kris; no relationship whatsoever.
9. Review G: xNAL domain
Opening of review:
https://lists.oasis-open.org/archives/dita/202303/msg00005.html (Eberlein, 07 March 2023)
- Kris; this review is now open; Robert and I have a question about these. Each example for every topic is quite long. Should more of the example sections for elements relate back to a single one? Put together, examples for elements add 20 pages to PDF.
- Nancy; for SVG, mathML and equation domains, examples are also long because they have to contain SVG or mathML code; I'd like to shorten them.
- Kris; has anyone used any xnal stuff?
- Zoe; maybe unintentionally...
- Kris; I used them a little at IBM, but not really.
10. Stan's comments about troubleshooting
[held till Stan is on call; see agenda for details]
11. Editorial work on DITA for Technical Content 2.0 element-reference topics
How much "context" to show in examples?
https://lists.oasis-open.org/archives/dita/202302/msg00023.html (Eberlein, 14 February 2023)
Editorial assignments, deadlines, review maps
https://lists.oasis-open.org/archives/dita/202301/msg00035.html (Eberlein, 31 January 2023)
Editorial guidelines
https://lists.oasis-open.org/archives/dita/202301/msg00036.html (Eberlein, 31 January 2023)
General resources:
Recording of 20 December 2022 session
https://lists.oasis-open.org/archives/dita/202212/msg00033.html
GitHub education that the TC did in 2018
https://lists.oasis-open.org/archives/dita/202212/msg00034.html (Eberlein, 21 December 2022)
Status?
https://wiki.oasis-open.org/dita/DITA2.0TechnicalContentReviews
***ActionItem: Kris will pester folks on updating deadlines.
- Nancy; I have some Git issues.
- Kris; we can talk later today. Kathryn, what about release mgmt?
- Kathryn; Tammy, are we ready for another pull request? yours is still open.
- Tammy; that pull request includes some non-release mgmt files.
- Kris; you'll need to pull those other files out.
- Tammy; let's put a date on bookmap of 2 weeks from now.
- Kris; we probably won't work on these at same time; so please make 2 diff branches to keep pull requests separate. if two items are scheduled differently, they should have different branches.
- Tammy; when I do a pull request, can I specify what I'm pulling?
- Kris; no; Git just says 'here's my branch I want to pull all of it.'
- Kris; I have a question re; ConVEX conf in Baltimore? what TC members will be there, since it will affect our quorum
[Kris, Robert, Eliot, Stan, Jim T. will be there]
- Frank; I wanted to go, but couldn't get approval, so I've pre-recorded my session.
- Kris; I'll cancel the call for that week.
12 noon ET close
-- Ms. Nancy Harrison
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]