================================================= Minutes of the OASIS DITA TC Tuesday, 17 January 2023 Recorded by Keith Schengili-Roberts link to agenda for this meeting: https://wiki.OASIS-open.org/dita/PreviousAgendas Attendance: =========== Eliot Kimber, Keith Schengili-Roberts, Zoe Lawson, Frank Wegmann, Scott Hudson, Todd Thornton, Robert Anderson, Tammy Crowley, Dawn Stevens, Kathryn Torriano, Bill Burns Business ======== 1. Roll call Regrets: Stan Doherty, Nancy Harrison, Bill Burns (was able to join in later) 2. Approve minutes from previous business meeting: 10 January 2023 https://lists.oasis-open.org/archives/dita/202301/msg00010.html (Harrison, 16 January 2023) Kris moved to accept, 2nd Tammy, approved by TC 3. Announcement Dawn mentioned that there is now a draft agenda for ConVEx; just need final confirmation from the speakers that they can present and then it will be published 4. Action items and volunteer tasks Skipped to next section 5. Schedule for January 2023 reviews Current review of software domain open, to be followed by hardware domain, then an architectural topic about sorting. Feb 1-2 week will look at troubleshooting 6. Technical Content Review C: Programming, software, and UI domains Email comment from Eliot on codeblock element: "Font conventions and RFC-2119 terminology (page 3 in PDF): Where do we want to cover font and other formatting conventions? Currently they are in a non-normative appendix topic: Formatting conventions. Should they be in the “Rendering expectations” sections of individual topics instead? Or in both places?" Moved formatting comments out of the spec, and into a non-normative appendix called "Formatting Expectations". Kris brought up this up as a topic. Eliot: reason that I made these comments about why we make the distinction between layout (such as line breaks) and font choice Kris: if line breaks are missing, meaning can be loss Eliot: if indention is missing from code, this is can also break meaning - Rendering expectations these are not hard requirements, but what people expect and what we as architects of the DITA specification are what we intend Kris: we could move info about rendering expectations from the appendix and we could move it here as a separate paragraph Eliot: I would find that more useful, as I might not go to the formatting expectation appendix Robert: how it looks is formatting, how things are rendered describes how that the look is created; Robert also likes the idea of including the formatting content in the topic, and also have that info in a consolidated appendix Kris: liked the idea of a consolidated appendix Tammy: agreed with this idea Frank: given that the spec is aimed at implementors, would prefer having all of the formatting expectations in one spot (the appendix); but he would not be against having this information also in the topic Kris: also find it difficult to distinguish between rendering and formatting Robert: suggested that the info on formatting expectations in the topic become part of the appendix Eliot: difference between formatting expectations and what is required Kris: how much work would it take to do what's required to generate the appendix from the topic formatting expectations? Robert: this ought to be possible by creating some conrefs Kris: this material would repeat the normative statements Action Item: Kris to move the formatting items back into the individual topics From email: "What is the semantic distinction between