OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Groups - DITA TC Meeting Minutes 14 May 2019 uploaded

Submitter's message

Minutes of the OASIS DITA TC
Tuesday, 14 May 2019
Recorded by Hancy Harrison
link to agenda for this meeting:

Robert Anderson, Deb Bissantz, Carsten Brennecke, Bill Burns, Stan Doherty, Kris Eberlein, Carlos Evia, Hancy Harrison, Alan Houser, Scott Hudson, Eliot Kimber, Zoe Lawson, Tom Magliery, Chris Nitchie, Keith Schengili-Roberts, Joyce Lam, Briana Stevens


1. Roll call
Regrets: Dawn Stevens

2. Approve minutes from previous business meeting:
07 May 2019
https://lists.oasis-open.org/archives/dita/201905/msg00038.html (Harrison, 10 May 2019)
moved by Kris, 2nd by Scott, approved by TC

3. Announcements: none

4. Action items
11 September 2018
Kris: Review conversation with Joe Pairman, e-mails about metadata, and TC discussion in late 2017/early 2018; summarize to TC: due 09 April Overdue
- Kris; by next week I'll have this item done.
13 November 2018
Eliot: Test refactoring of grammar files; due 21 Mary
18 December 2018
Eliot: Investigate issue re earningAggregationsTopicrefConstraintMod.xsd; due 21 May
05 March 2019:
Alan: Update DITA 2.0 files for appropriate elements with LwD hint values for @format and create a pull request; due 23 April Overdue
- Alan; I created a pull request, then got some objections, I need to address those objections and re-submit.
02 April 2019
All voting TC members: Look through 1.3 normative statements listed in Nitchie's e-mail: What's missing? What's duplicative? What's nonsensical? How should we mark them up so we can get a clean extraction to build a (non-normative by definition) appendix?
09 April 2019
Eliot: Does SVG zip file need to be in techcomm grammar folder?
Kris and Tom: Finish up any discussion about examples in ArchSpec files
Nancy: Review LwDITA e-mail threads; create a Wiki page to track items, so that we can ensure that all items have been discussed and resolved
30 April 2019
Kris: Request OASIS Open repository for tools/scripts to aid users in moving to DITA 2.0
07 May 2019
Kris: Talk to Eric Sirois about bookmap proposal and future stage work
Dawn: Respond to Radu Coravu on dita-comment COMPLETED
Robert: Respond to Chris P on dita-comment
- Kris; halfway thru my conversation w/ Eric

5. DITA 2.0 stage one proposals
Continuing discussion "normal if used" Value for @processing-role
https://lists.oasis-open.org/archives/dita/201904/msg00020.html (Kimber, 23 April 2019)
- Kris; Eliot, you were going to consider things more, any updates?
- Eliot; as I remember discussion, Chris and Robert need to consider URI references when something is used, and I now think that's right. So shall I consider that as a refinement to original proposal?
- Kris; do we need more discussion? do we need email from Eliot to list?
- Robert; it's a stage 1 proposal, so not fully fleshed out yet; I think it wil be hard to define it in a way that's crisp and clear now.
- Eliot; I share that concern, but I think it's important enough functionality to work on. It's inherent in the way glossary was intended to work, even if it wasn't put in at the beginning. So I think it's something that needs to be codifed, but there are fuzzy areas that will need to be considered carefully.
- Chris; I think it will be a very hard proposal to do, especially at stage 3.
- Kris; point of process; we can't advance this to stage 2 till we have an owner, and Eliot isn't available, since he already owns 3 proposals at either stage 2 or 3, and that won't be the case even after today's votes. So you'll have to clear your plate.
- Kris; we need a stage one card for this.
[created by Robert]

b. New proposal: Drop domains (the attribute, not the concept, and only mostly)
https://lists.oasis-open.org/archives/dita/201905/msg00024.html (Anderson, 07 May 2019)
Lots of responses ...
- Robert; the suggestion is to remove or rename @domains, we've done all sorts of mods to the original @domains, and result is a mess that no one can figure out. I can't say what people do with it, and it's mostly not used, except for filterable @s. So, either restrict it to filterable @s, or remove and replace with something much simpler (just for filterable @s). In general, if you don't get it right, nothing happens for constraints with strict and loose constraints, anytime someone implements strict constraints, people are unpleasantly surprised.
- Eliot; I don't object; @domains was well intentioned, but no processor uses it except for the application of strict constraints. The fact that it's not really used is an argument for getting rid of it. If we get rid of it entirely, we lose abilty to use it in future. but we could always bring it back if we want, so I'd be happy with either limiting its value, or replacing it with a new @ for that.
- Robert; Chris has suggested that an @ that just had the @ names, rather than the groupings, would work,. I wonder about that related to subjectscheme.
- Chris; we could consider simplifying grouping syntax. A bunch of what's in @domains was carried over from specialization, so it would be better to simplify.
- Robert; if we do that, I'd change the name from @domains, so it was new, and make single tokens, rather than complex ones (x+x).
- Eliot; so do we get rid of it entirely, or say 'if @domains is present, no processor is obligated to do anything with it'?
- Robert; I'd rather remove it completely, not include an @ with no processing expectations.
- Kris; so this will be a change for eveyone's doc shells and specializations.
- Robert; yes, but not a large one, just deleting things, rather than changing things.
- Kris; but the required deletions would be just from modules, not from DITA sources.
- Robert; you might have delete it in certain circumstances.
- Kris; but some processors make @ evident, so ...
- Eliot; but most DITA processors don't use them. anyone who's maintaining shells will have to touch them for 2.0, but they'll have to touch their shells for 2.0 anyway, so that's not a big deal.
- Kris; I agree, my only concern is where it touches actual source content; if processors are making @s explicit rather than implicit.
- Eliot; they're used when RSuite loads content into its internal store, but then it filters them back out.
- Kris; how do we want to proceed?
- Robert; I'm now free to take it on.
- Kris; so I move to move the proposal to stage 2. [2nd by Eliot] Any objections? [none]
[moved to stage 2 with Robert as champion]

6. DITA 2.0 stage two proposals
21: Resolve inconsistent class values for shortdesc, linktext, and searchtitle
https://www.oasis-open.org/apps/org/workgroup/dita/download.php/65247/Issue21-ResolveInconsistentClassValues.pdf (Kimber, 04 May 2019)
Eliot moved to advance this to stage 3, 2nd by Bill
yes votes: 14 (Robert Anderson, Deb Bissantz, Carsten Brennecke, Bill Burns, Stan Doherty, Kris Eberlein, Carlos Evia, Hancy Harrison, Alan Houser, Scott Hudson, Eliot Kimber, Zoe Lawson, Chris Nitchie, Keith Schengili-Roberts)
no votes: 0

34: Remove topicset and topicsetref
https://www.oasis-open.org/apps/org/workgroup/dita/download.php/65246/Issue34-RemoveTopicsetTopicsetref.pdf (Kimber, 04 May 2019)
Eliot moved to advance this to stage 3, 2nd by Robert
yes votes: 14 (Robert Anderson, Deb Bissantz, Carsten Brennecke, Bill Burns, Stan Doherty, Kris Eberlein, Carlos Evia, Hancy Harrison, Alan Houser, Scott Hudson, Eliot Kimber, Zoe Lawson, Chris Nitchie, Keith Schengili-Roberts)
no votes: 0

Continuing discussion: None
Initial discussion: None

7. DITA 2.0 stage three proposals
Issue #105: Simplify chunking
https://lists.oasis-open.org/archives/dita/201905/msg00018.html (Anderson, 06 May 2019)
Robert moved to advance this to 'completed', 2nd by Kris
yes votes: 15 (Robert Anderson, Deb Bissantz, Carsten Brennecke, Bill Burns, Stan Doherty, Kris Eberlein, Carlos Evia, Hancy Harrison, Alan Houser, Scott Hudson, Eliot Kimber, Zoe Lawson, Tom Magliery, Chris Nitchie, Keith Schengili-Roberts)
no votes: 0

Initial discussion: None

8. Review of DITA 2.0 proposal deadlines
- Kris; Keith,yours is due at end of month, as well as Eric's bookmap.
- Keith; think that's still in plan.
- Chris; wrt @ loosening, I want to coordinate with @domains proposal, since they interact.
- Kris; if you own a proposal, please update this page.

9. DITA 2.0 editorial work
See Editorial work completed for a full summary
- Robert; we've been busy, weekly mtgs plus work outside of them; Kris and I are getting anxious, so we're cleaning up the spec, and reorganizing topics to remove duplicate content; we've incorporated all proposals already completed or at stage 3, except for latest chunking one.
- Kris; I put a working draft of the 2.0 spec in kavi; please look at it. In it, I removed the outer nesting topic for arch spec. We'll have much more work to do on what top-level and organization should be, please take a look.
- Robert; I'm thinking about trying to make whatever changes we've made reusable by LwD and techCcntent package files, as well as their doctypes.
- Kris; we talked about making the DITA TC repository available as a submodule to other githubs, like the ones for LwD and techContent.
- Robert; that's the appropriate way to do it, but it's currently theoretical, not implemented. Also, in any case, the techcomm repository needs to be cleaned up.
- Kris; also, if you go to the wiki page for editorial work, it also points to backlog pages.

10. Multimedia domain
Editorial reviews
Completed by Anderson and Eberlein
Edited topics reviewed by Nitchie
DITAweb review
Commitment from TC members
Committee note
Stub files and grammar files now in committee note repo, "multimedia-domain" branch
Outline of what the committee note needs to cover?
- Kris; we had some discussion last week, especially around how to handle grammar files in conjunction with CNs. I think we're almost ready for a DITAweb review of topics, so we need to get that done; once that's done, we can go ahead with CN. We've talked about this for a year, and I can't rmember who volunteered to edit the multimedia CN. Does anyone remember who volunteered, besides Carlos?
[no memory of who volunteered last year, but Bill volunteered to work on it.]
- Kris; we'll try to resolve conflicts in element ref topics so we can go ahead with CN.

11. New item: Keyref missing for filepath and userinput
https://lists.oasis-open.org/archives/dita/201905/msg00023.html (Stevens, 07 May 2019)
- Robert; this issue was probably created in 1.2, a decision was made, but not a good one, and not worth revisiting.
- Kris; so what do we want to do for 2.0?
- Robert; Eliot's right, it's a straightforward fix
- Kris; are there any other ones?
- Robert; don't know, that would come up with the proposal; for some reason, it was explicitly left off of thsse two, but it's no problem to fix.
- Kris; anyone opposed to making these?
- Robert; now I'm confused, the spec source says those elements take those @s, so it may be just the grammar files.
- Kris; but the grammar files are normative...
- Robert; but we thought they were there, so this could be treated as a bug fix.
- Nancy; I agree, if the spec says they're there, but they're not, that usually is considered a bug, and we should treat it that way, and just log it as a bug fix made to 2.0.
- Kris; we'll open up a card, treat it as a bug fix, and fix asap.

12. Stylesheets
OASIS has agreed to build actual style specifications, with our help
Updates on committee note:
Now runs on DITA-OT 3.3 (both PDF and HTML5)
Update on spec:
Now runs on DITA-OT 3.3
Latest: OASIS stylesheet update (PDF)
https://lists.oasis-open.org/archives/dita/201905/msg00014.html (Eberlein, 06 May 2019)
- Kris; OASIS agreed to build style specs; we have minimized differences between CN and spec, and now have a working PDF transform to generate both spec and CN.

Other: Report on STC 2019 Summit:
- Carlos; attendees fell into one of 2 groups, 1) very experienced and 2) very new to structured authoring; my talk was very good for newbies.
- Tom; I never even mentioned DITA; I did a talk as an intro to structured authoring for folks new to it. Liz Fraley thought there were more folks interested in structured authoring than before. Dawn was also there.
- Alan; last year, we had kind of a 'huh?' reaction to the conference, what was your impression this year?
- Tom; I had lots of good conversations at the booth, but it's hard to judge from that perspective. OTOH, I had slightly more people than usual wanting to know "what was struct authoring?"
- Alan; though Carlos's presentation was good, and had the right people in the room.
- Kris; Joyce?
- Joyce; we didn't go this year.
- Deb; Vasont was there; this was my first STC conf, so I have no context. Most people didn't understand what an XML CCMS was, but some did.
- Alan; I was on STC conf committee; this year, the team tried to do a hard shift from a 'soft skills' conference to more technical subjects, I'd like to think we managed to do that.
- Kris; thoughts, comments, questions?

12 noon ET close

-- Ms. Nancy Harrison
Document Name: DITA TC Meeting Minutes 14 May 2019

No description provided.
Download Latest Revision
Public Download Link

Submitter: Ms. Nancy Harrison
Group: OASIS Darwin Information Typing Architecture (DITA) TC
Folder: Meeting Notes
Date submitted: 2019-05-15 20:14:11

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]