dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Groups - DITA TC Meeting Minutes 31 August 2021 uploaded
- From: Nancy Harrison<nharrison@infobridge-solutions.com>
- To: <dita@lists.oasis-open.org>
- Date: Wed, 1 Sep 2021 19:47:04 +0000 (UTC)
Submitter's message
ActionItems: None
=================================================
Minutes of the OASIS DITA TC
Tuesday, 31 August 2021
Recorded by Hancy Harrison
link to agenda for this meeting:
https://wiki.OASIS-open.org/dita/PreviousAgendas
Attendance:
Robert Anderson, Deb Bissantz, Kris Eberlein, Carlos Evia, Nancy Harrison, Scott Hudson, Gershon Joseph, Zoe Lawson, Keith Schengili-Roberts, Dawn Stevens, Frank Wegmann, Jim Tivy
Business
========
1. Roll call
Regrets: Carsten Brennecke, Eliot Kimber, Eric Sirois
2. Approve minutes from previous business meeting:
24 August 2021
https://lists.oasis-open.org/archives/dita/202108/msg00028.html (Harrison, 26 August 2021)
moved by Kris, 2nd Scott, approved by TC
3. Announcements - none
4. Action items
06 April 2021
Dawn, Gershon, Nancy, Frank, Kris: Work on revised charter IN PROGRESS
Kris; work on revised charter still in progress.
13 July 2021
Nancy: Draft suggested URL string, short description, and purpose statement for OASIS open repo for specializations not part of the standard IN PROGRESS
- Kris; this is on the agenda.
27 July 2021
Carlo: Generate PDF of LwDITA spec; due 16 August 2021 DONE
- Carlos; not perfect, but it's in progresss
- Kris; can you generate it using spec styesheets?
- Carlos; yes.
- Kris; if you have problems, let us know, we need to see it in real spec format.
Kris: Refactor source for troubleshooting committee note; upload to committee note repo; due 16 August 2021
- Kris; the troubleshooting note is on agenda today.
Eliot: Draft revised description and purpose for RNG convertor repo
24 August 2021
Kris: Check out OASIS form for requesting new repo
Robert: Examine DITA 2.0 specs to what can be published (without draft comments if necessary) by 14 September 2021 Webinar
- Kris; Robert, have you had a chance to look at draft 2.0 specs?
- Robert; not yet, will look at them this week.
5. Health and well-being of voting membership
https://lists.oasis-open.org/archives/dita/202108/msg00037.html (Eberlein, 31 August 2021)
[discussion of plans for recruiting additonal active TC members, given recent and oossible upcoming resignation of some long-time TC members due to job changes (including retirement). Kris requested that TC members look at current TC roster to think about OASIS member companies to recruit more active members from, as well as non-OASIS member companies currently working with DITA to recruit for OASIS membership.]
6. Check-in: How are people doing in this difficult time? How is your state/country doing?
[no official business]
7. Review of DITA 2.0 proposal deadlines
https://wiki.oasis-open.org/dita/DeadlinesDITA2.0
[no updates]
8. DITA TC Open OASIS repos
a. Continuing New repo for specializations not part of the standard
https://lists.oasis-open.org/archives/dita/202107/msg00010.html (Eberlein, 13 July 2021)
We need the following to request a repo
URL string (part of URL, for example, dita-rng-converter
Short description (used on Web page)
Purpose statement (used in README)
Maintainer name, e-mail, GitHub ID: Carlos Evia, cevia@vt.edu, carlosevia
Proposed OS license
Draft info by Nancy:
https://lists.oasis-open.org/archives/dita/202108/msg00016.html (Harrison, 10 August 2021)
Description for new OASIS Open DITA specialization repository in GitHub
https://lists.oasis-open.org/archives/dita/202107/msg00019.html (Harrison, 21 July 2021)
https://lists.oasis-open.org/archives/dita/202108/msg00025.html (Harrison, 24 August 2021)
NEW https://lists.oasis-open.org/archives/dita/202108/msg00035.html (Eberlein, 31 August 2021
- Kris; please look at my revision above; I went thru Nancy' s draft and pared it down. How do folks feel about this?? I tried to give us sufficient wiggle room in the last sentence.
- Carlos; I like that wiggle room.
- Robert; wrt the statement about the files, they're not just 'compatible with 1.3', they are 1.3. Can we say 'our intention is to update these to be compatible with new releases'?
- Kris; so the sentence that inroduces the 3 pieces we're including needs to say they're part of 1.3.
- Robert; we definitely intend to keep grammar files up to date for 2.0; but what about spec files? That would take a huge amt of work.
- Kris; I thought the grammar files and spec files will both be there.
- Robert; I don't think anyone will want to put the effort in to update the document part of the spec.
- Kris; then we drop the word 'documentation'?
- Robert; that's better; 1.3 docs will be the valid definitions for these things.
- Kris; so I think we add 'the following 1.3 specializations.'
What do we want to say in the last sentence? Are we bringing this forward for 2.0?
- Deb; what if we can't update them by 2.0? What if we have to do a 2.1 before we can even look at these? I prefer the last sentence as it is.
- Kris; it says 'this is our intent.' So if we can dod it, great.
- Zoe; and if you want to get involved, reach out??
- Kris; that's implicit in the nature (and official descriptions) of OASIS open repos and of Github. And if you don't know Github, it would be very hard to work on any of these.
- Dawn; and what if someone wants to help update? Do we need to give some instructions if someone wants to help? Or be more inviting?
- Kris; we can take some text from OASIS about getting folks to work on it. Can we take a vote on it? We need to approve this repository with this description.
- Zoe; is this description set in stone, or can we tweak it?
- Kris; we don't want to tweak this.
- Zoe; but if we added another specialization, could we add it to the description?
- Kris; yes, we could.
Kris moved to accept this repo with this description
Zoe 2nd
Approved by TC
- Kris; our commitment is to the RNG & DTD grammar files, no XSD.
- Robert; is this where we want to generate a monolithic XSD?
- Kris; that might go in the other RNG->DTD tools repo.
- Robert; that repo is for the tools, I was thinking of e.g., a monolithic L&T XSD...
- Kris; we don't have to specify precisely what grammar files we're providing.
b. Continuing RNG converter
https://lists.oasis-open.org/archives/dita/202107/msg00008.html (Eberlein, 13 July 2021)
https://lists.oasis-open.org/archives/dita/202107/msg00009.html (Chet Ensign, 13 July 2021)
Need to revise statement of purpose to cover generating monolithic XSD (DTD also?)
- Kris; I need volunteers to look at what Eliot suggested for the RNG repo, and maybe remove some lofty ambitions. I need at least 2 volunteers, one to be Robert
[Zoe volunteered]
9. Equation domain and learning assessments
https://lists.oasis-open.org/archives/dita/202108/msg00027.html (Stevens, 26 August 2021)
https://lists.oasis-open.org/archives/dita/202108/msg00029.html (Kimber, 26 August 2021)
- Kris; this is germane to the specializations repo.
- Dawn; I saw this working with client. The client needs to put math and equations in L&T, but the domains aren't added.
- Kris; I think it was just an oversight, we just didn't think of those domains.
- Dawn; at 1.3 we did the L&T2, to change what things had been specialized from, but we didn't go in and add these domains. I think the intentions should have been to include these, but it just didn't happen.
- Kris; It might also be that John Hunt, who did a lot of work on L&T2, didn't think to put it in.
- Dawn; we'll be updating a lot of the L&T 1.3 to 2.0 for this to help our clients. We can discuss later if we make those updates to the repo at that point. I just wanted to make sure we weren't breaking any decision the TC had made.
- Kris; no, not at all. and we don't have to stick with a doc shell that was unintentionally restrictive.
10. Using DITA 2.0 Troubleshooting committee note
https://lists.oasis-open.org/archives/dita/202108/msg00034.html (Eberlein, 31 August 2021)
- Kris; in moving this into CN format, I see some weaknesses in the organization; rather than just shoehorning diagnostics info into the current document, maybe we should re-think about what is so useful about troubleshooting design. Dawn's comment was very good; one thing people don't think about is that, while the troubleshooting topic has a very structured format, it can easily be rendered in tabular format...
- Kris; do we think there are any best practices that have emerged?
- Carlos; I've done some work with it.
12 noon ET close
-- Ms. Nancy Harrison
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]