OASIS Darwin Information Typing Architecture (DITA) TC

 View Only
  • 1.  Minutes for 11 March 2025

    Posted 03-11-2025 12:23
    Agenda, 11 March 2025
    Attendees: Kristen Eberlein
    Dawn Stevens
    Nancy Harrison
    Bob Johnson
    Leroy Steinbacher
    Robert Anderson
    Eric Sirois
    Scott Hudson
    Stan Doherty
    Non-Voting:
    Leo Belchikov
    Action Itmes
    - Kris to talk with Bob about collaboration between DITA & IIRS (Harald Stadlbauer)
    - Kris to set up wiki page about conditional text examples
    Regrets:
    Christina
    Approve minutes from previous business meeting
    - Kris moves to approve minutes
    - Scott seconds
    - Minutes approved
    04 March 2025
    Announcements
    - Bob: Shared discussion with DITA & IIRS; potentially collaborate with Harold 
    - Kristen & Bob to discuss
    Walk through spec review feedback
    Conditional processing
    Robert - [RE: Conditional processing - https://dita-lang.org/dita/archspec/base/condproc]
       - 1st comment, grammar, easy
       - Reword shortdesc yes
       - Comment about adding link to how to specialize?
    Leroy - It would be nice
    Kris - Need to be careful about how many links we use.
    Leroy - maKris sense
    Robert - we have links elsewhere
    Robert - regarding "Do we want to mention the commonly used term "profile attributes"?"
    Leroy - There are official names, and then what people use. 
    Robert - Need to be consistent. But not certain if profile 
    Leroy - Library files, collection files, all sorts of terms.
    Kris - Reminder, this is a Spec, not a User Guide.
    Robert - We tend to do a less than optimal job at both when we try.
       - [RE: About the DITAVAL document - https://dita-lang.org/dita/archspec/base/aboutditavaldocuments]
         "Link to exclude all example (Example: Changing the default behavior to "exclude")?"
         Do we want a link to example? Just one Link? Three links.
    Leroy - Either way is fine. Sometimes issues with links at the bottom, but link heavy difficult so either is fine.
    Robert - [RE: Conditional processing attribute values - https://dita-lang.org/dita/archspec/base/usage-of-conditional-processing-attributes]
    "Why product="" ? When would you use this empty value, versus just removing or not using the attribute?"
         Within the topic "Empty Element = not there", so these examples are showing that Product="" is equivalent
    Leroy - was wondering why
    Robert - Showing example
    Kris - Do we want to rephrase When a conditional processing element has an empty value, it is equivalent to....
    Robert - Makes sense
    Kris - Avoid some confusing.
    Robert - If reading as user guide, confusing
    Eric - coming back to attributes - discussion from DITA-OT, for conditional processing, are there character limitations?
         Adding boolean stuff as values? Sometimes it works, sometimes it doesn't. Are there reserved words? 
    Things we strongly recommend not using.
    Robert - Thanks for reminder. We don't explicitly say anything.
         IF using Subject Schemes, you're limited by what's supported by Subject Schemes.
    If not, we don't supply guidance
    bad character = parenthesis, because of the grouping feature.
    Other than parenthesis, just reuse key?
    Eric - Will post example in chat. Are using subject scheme
        
    [Example from chat] (feature=deployment_and_platform=UNIX)_or_feature=EclDevOnUNIX_or_(feature=MainframeSubsystem_and_feature=development_and_interface=EclipseIDE)
    Some are worse, with double parenthesis.
    [Example from chat] (feature=NoMainframeSubsystem_and_(interface=VisualStudioIDE_or_(interface=EclipseIDE_and_platform=UNIX)_or_feature=deployment))_or_feature=DevelopmentHub
    Maybe use square brackets
    Kris - If we want to maKris a statement, we need to do it now.
    Robert - Now is the time to limit it.
    Kris - Today its "is it valid XML"
    Eric - Will send a note to the TC.
    Robert - [RE: Conditional processing and subject schemes - https://dita-lang.org/dita/archspec/base/conditional-processing-and-subject-schemes]
    What's in this topic, do we need it?
    Kris - Switching to PDF - more Draft Comments...including is this needed?
    Robert - Probably a sign topic is not needed
    Leroy - Some of it is Editor specific, but covered elsewhere.
    Kris - Covered more in the Subject Scheme area.
    Robert - [RE: Filtering based on metadata attributes - https://dita-lang.org/dita/archspec/base/filtering]
         First comment covered earlier.
    Do we want to include the logic of multiple attributes with multiple values? For example <p product="A B" audience="C">
    Leroy - Get the question all the time, and get confused and keep losing the cheat sheet.
    Robert - The topic tries to explain. 1. explains the algorithm. 
    [had to step away]
    Kris - Thinks scenario is covered.
         [RE: Example: Setting conditional processing values - https://dita-lang.org/dita/archspec/base/example-setting-condproc-values]
    Would it be helpful to include different example ditavaLeroy and show what rendered output is for each?
    Leroy - think it's done later on, but wonders if it would be helpful.
    Kris - What are you suggestion
    Leroy - Example of Include/Exclude flag rendered output.
    Kris - Other examples go into more detail. Example: Filtering and Flagging
    Leroy - Great
    Kris - Robert, these examples haven't been changed in a long time. Made up examples. Can we move towards actual examples?
    Robert - Yes, think we can do that.
    Kris - Inevitably, it takes work to come up with real world examples. Can TC Members volunteer examples?
         Non oasis memeber can get credit
    Zoë & Scott offer to come up with examples.
    Kris - Would it help to have a wiki page listing what example requirements are?
    Scott & Zoë - Yes please
    Scott - Can provide flagging examples.
    Kris - Want to provide more flagging options because many users weren't aware of flagging.
    Robert - Interesting that people don't know about it, since it's been around since 1.0
         Not surprised since there are so many features, but still...
    Kris - IBM always used it, so made sense. And there are CCMS that don't support flagging.
    Robert - In the DITA-OT context, many features exist that folks aren't aware of. "Advertise" Did you know this feature was there?
    Kris - After DITA-2.0 goes out, let's work on Committee notes that are more User Guide flavor, more "cool things you can do with DITA"
         More generic conversation of conditional
    Scott - Integral part of review process.
    Kris - How does that facilitate?
    Scott - Flag content by release date, color coded, so folks can see what's new for the next release.
    Kris - good example
    Zoë - Also use color coding.
    Stan - Example for badging (symbols) e.g. on prem vs cloud.
    Kris - Used flagging explicitly for intersection of DITA and LWDITA.
    Leroy - Link to exclude all example (Example: Changing the default behavior to "exclude")?
             [RE: Example: Filtering and flagging topic content - https://dita-lang.org/dita/archspec/base/evaluating-conditional-processing-attributes]
    Confusing that its "inside a topic" not filtering a topic out.
    Robert - Lets rephrase the title to clarify.
    Leroy - Why Non-Normative?
    Robert - all examples are non-normative. 
    Zoë - Jarno's spec rendering auotmatically includes the "This section is non-normative" which doesn't display in our pDFs
    Kris - Examples and Notes are non-normative. Not sure why not Notes, but been that way.
    Robert - Notes were additional explanations.
    Why are the example ditaval topics not close to each other in the structure.
    Robert - Maybe part of the subject scheme.
    Kris - Don't forget that there are Draft Comments in the PDF that have a bunch of information.
    Robert - Of course, we asked you to review using Jarno's HTML, so our oversight.
         Section is in pretty good shape. Some clean up.
    Kris - Could be an upcoming review.
         Thanks to Robert for taking point.
    [Kris to update the page.]
    Bob needs assistance adding an email via the OASIS site.  
    Thanks, good meeting, we did a lot. 


    ------------------------------
    Zoe Lawson
    Synopsys, Inc.
    ------------------------------