OASIS Darwin Information Typing Architecture (DITA) TC

1. Action item for the team:

1. 1. Look at the listing requests at Examples for conditional processing.
   2. Post to the DITA list your example.
   3. In the corresponding section on the Examples for conditional processing page, comment that you have posted an example on the DITA List. Click the Edit button to make this update. When you are done, click Save page.
2. Approve minutes from previous business meeting:
   • 11 March 2025 Kris approved the meeting minutes and Dawn second the motion.
3. Announcements
4. Regression in capabilities with chunk update

• • Use of chunking="to-content" at the top-level for single HTML pages, will not be impacted.

• • Robert would like to update the definition of chunk="combine" to clarify that once "combine" is in effect, only other "combine" values are used. Effectively, this changes the current language – "additional chunk attributes are ignored" – to something more like "other chunk tokens are ignored". Overall this would mean:

• • • Cleaning up the three bullets today that govern chunk="combine",  to clarify that additional chunks can be created, and

• • • Providing at least one good example of this behavior in the Examples section for chunking

• Kris would like to have a short review to review the chunking portion of the specification.

5. Walk through spec review feedback

• • DITA addressing

• • • id attribute

• Navigation

• Eliot Kimber, 18 March 2025

• Eliot rewrote content and entered his changes as a pull request. 

• For the navigation section in the TOC topic, Eliot tried to make the content more general. Tried to talk more that you can have a navigation tree and what contributes to a navigation tree, rather than how you would render it. 

• Eliot addressed gaps in the content. 

• Eliot looked at "Alternative titles" and broke into two subtopics: nominative behaviors and examples. 

• Conditional processing

• • • • Dawn Stevens, 18 March 2025

• • • • Dawn found the content needed to be clarified. 

• • • • "If I read most of the topics two or three times, given my already decent understanding of how it works, I could understand what it said. I don't think I would have had a prayer if I was reading it without pre-existing knowledge." 

• • • • Dawn found the examples very helpful and recommended adding links to the examples. If we could add even the resolution in the normative content that seems like it would help.

• • • • Dawn recommended normative text and then an example.

• • • • Dawn mentioned the need to mention pass through in "About conditional processing." 
    • Guidelines for reviewing the specification
      • Normative statements is a set of laws that the implementation has to follow, such as the rules a processor has to follow. 
      • Nonnormative statements are illustrations of how you apply the law, such as examples. 

• • These examples are not the rules. 

• Do not read more into these examples. 

• • • • Kris said the team is trying to move away from all the critical information being lumped only in examples. Want to have architectural topics that provide governance.