dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Groups - DITA TC Meeting Minutes 7 July 2015 uploaded
- From: Nancy Harrison<nharrison@infobridge-solutions.com>
- To: dita@lists.oasis-open.org
- Date: Fri, 10 Jul 2015 11:57:28 -0700 (PDT)
Submitter's message
ActionItems:
1. Kris will add reminder to memebers at top of TC wiki page on how we'll be handling voting membership.
2. Kris will turn her email on "Things we can do during the forthcoming public review" into a wiki page, so it's easier to track.
=================================================
Minutes of the OASIS DITA TC
Tuesday, 7 July 2015
Recorded by Nancy Harrison
link to agenda for this meeting:
https://wiki.oasis-open.org/dita/PreviousAgendas
Regrets: Eliot Kimber
Standing Business
=================
Approve minutes from previous business meetings:
https://lists.oasis-open.org/archives/dita/201506/msg00374.html (Nancy Harrison, 30 June 2015)
Proposed by Kris, seconded by Bob, approved by TC
Subcommittee Reports
Lightweight DITA (LD) SC (Michael)
The SC has been meeting bi-weekly plus running an active mailing list; they're looking at a deliverable consisting of topic and map doctypes plus a super-simple specialization architecture that's a subset of the regular specialization architecture. They have a topic and a map that are being debated, and the goal is to have it validated by industry-specific DITA SCs, i.e., software developers, machine industry, Learning&Training, etc. For the first release, their task goals are:
1. get to a mimimum viable set of elements asap,
2. validate for domains,
3. push for standardization of LightweightDITA parts,
4. adjust as necessary,
5. publish domain examples as proof of concept (but not try to standardize them. just use them as proof points to be used a examples by others).
Kris; comments?
Nancy; is there an ETA?
Michael; no, we're just trying to work fast. I did the orignal port of concept/task/ref to LD, Carlos Evia (sp?) and Mark Giffin haver refined those. The question we're trying to answer is: "How can we make it easier for people to create specializations?" So we don't have a commited schedule.
Joann; why are you not including concept/task/reference topics?
Michael; because they were extraneous, we wanted to be as lightweight as we could. we still put out how to use them, but we don't claim that they're part of the LD standard. L&D and TechComm will be examples, but not canonical.
Joann; you're envisioning a different specialization process?
Michael; yes. how can we make it easier? It would be a subset of DITA specialization, so still a valid DITA specialization, but simpler. It could be something that allows you to document the spec in a way that creates the actual specialization code. Another possibility is a template-based specialization; you'd create a template for what you want, then annotate it with data to create specialization.
Joann; so it wouldn't be compatible with a regular DITA specialization?
Michael; It would be compatible. So, e.g. task in LD will be lighter weight version of corresponding topics in regular DITA, but all elements in it are simpler versions of identically named elements in regular DITA task elements.
Joann; what direction will the examples provides?
Michael; specifically about task/concept/reference examples?
Joann; no, examples in general
Michael; examples will be mostly to validate that you can create new specializations that are useful. If someone wants to start authoring using the examples, they can, but they won't be a standard, or canonical/normative. So LD task/concept/reference would have the same level of 'normality' as the various task/concept/reference published by various tool vendors.
Kris; other questions/comments? [none]
Kris; sounds like good work in the LD SC, this will enable more people to be able to do DITA specialization.
Michael; it's a sweet spot; broadly useful, but not broadly useless. :-)
Kris; a dream would be to get it adopted in Google Docs...
Eric; let me know if you need a Google Docs contact; I may have a contact at Google, a former IBM-er, so I'll ping him.
Announcements
None
Business
========
1. Action items
- Action items from 30 June 2015
Nancy: Upload minutes from TC meeting on 30 June (Completed)
Kris: Initiate a TC Admin support request ticket for"Committee Specification Draft Creation / Upload Request" (Completed)
Kris: all done; uploaded both drafts (CPRSD and CSD)
2. Update on Committee Specification Public Review Draft 01
Kris; Bob, Robert and I all did some work to get the spec, source, and style sheets to work as per OASIS requirements.
Robert; OASIS went thru and found several tiny issues, mostly with link construction, there was a lot of back and forth. Kris did a lot of work on both source and style sheets, as did Bob; this was complicated by haing to have 2 different drafts; CSD and CSPRD.
Kris; I didn't understand till now how all the different drafts have different sets of links pointing to different places. The other stuff we fixed were minutia. I'm hoping that what I uploaded this morning meets all their requirements. Thanks and kudos to Bob for late, last-minute fixes.
[TC members expressed appreciation to Kris, Robert, and Bob for their work.]
3. Calendar for critical dates to enable DITA 1.3 to be released in 2015
Schedule: July - December 2015 (https://wiki.oasis-open.org/dita/ScheduleJuly-December2015)
Robert reviewed the calendar.
Kris; Note that wrt OASIS rules for voting;
- you lose voting rights by being absent at 2 meetings;
- you regain voting rights by being present at 2 meetings, and you can't vote at your second of those meetings, only after that.
Please keep that in mind so you can vote.
Nancy; can we indicate on the calendar which days are votes?
Robert; places where it says "open ballots"
kris; We want this voting eligibility issue to be very clear, so folks aren't blindsided, like they were in 1.2. Any other questions about this?
ActionItem; Kris will add reminder to memebers at top of wiki page on how we'll be handling voting membership.
4. Comments received during the public review, 7 July - 5 September
Public review #1 comments (https://wiki.oasis-open.org/dita/DITA-1.3-public-review-1)
[the page is just a placeholder; no commments yet]
Kris; we'll be tracking those comments as they come in. If you're a member of the TC, you can comment on dita-tc list, or the 'dita-comments' list. People who aren't on the TC can only use the dita-comments list.
Don; And we can tell people where to post, but we can't forward comments for them.
Robert; that fact is important; it relates to OASIS IP rules; if you submit to the comments, you're agreeing that you're not contributing IP.
Kris; for 1.2 we just created a PDF from the comments wiki page. that will be the log we formally post before we move on to the next stage.
5. Continuing item: Things we can do during the forthcoming public review
https://lists.oasis-open.org/archives/dita/201506/msg00368.html (Eberlein, 30 June 2015)
Kris; please look over the items on the list and volunteer if you can. Tom; I'll add your name to the graphics item.
ActionItem; Kris will turn her email into a wiki page, so it's easier to track.
6. New item: Index in the PDF version of the spec?
https://lists.oasis-open.org/archives/dita/201507/msg00026.html (Eberlein, 7 July 2015)
https://lists.oasis-open.org/archives/dita/201507/msg00027.html (Kimber, 7 July 2015)
Kris; one thing we can do is to index the spec. During 1.2 we decided not to index the spec, because it was so poor a spec. Robert and I have some ideas, some plans, and some volunteers. we've been removing inline indexes and putting them in the prolog. One big question is "should they be in prolog, inline, or a combination?"
Bob; I think it ought to be both; any index term that correlates with scope of topic goes in prolog; those that don't should be inline.
Robert; I think with this time, with smaller, more modular topics, just about every thing that's worthy of an index item applies to the whole topics, unless it applies to a titled section.
Bob; if you've done a good job with topic organization, they shouldn't have to go inline.
Robert; problem with inline index terms is that, if you have things in the middle of a line, or in a figure, they get lost. Kris did most of the cleanup; she's done some high-quality indexing of part of it.
Kris; I'm old school; I think indexes are invaluable, not replaced by online search. but, I always indexed only in the prolog, partly because I was working on short focused topics. If you have long reference topics, you need point-specific terms, but point-specific entries are much harder to manage. and I don't know if DITA-OT allows for them.
Robert; it would be fixable, if not...
Kris; comments?
Dick; when we did Eliot's book, we had entries thruout; I'm a strong advocate of indexes so we should do it. But I really think entries should be where they belong, it's harder to manage, but easier for reader.
Robert; but for 90%, the whole topic is where they belong
Scott; does DITA-OT do a range?
Robert; it points to the title of a topic if the entry is in the prolog. we tend to think that entries point to the whole topic, otherwise maybe sections.
Kris; for example, if an index entry is for the definition of a term defined in a topic, should it be in the prolog, or at the term?
Scott; I'll volunteer, but would like an offline seesion to discuss it.
Nancy; We should at least get the low hanging fruit by indexing topics, inline entries aren't low-hanging fruit.
Robert; actually, a lot of the work is in removing entries; there are hundreds of inconsistent, element level entries that obscured real conceptual info at 1.2.
Krisl volunteers?
[volunteers were: Scott, Bob, Dick, Stan, Keith, Nancy, Kris]
12:00 ET Close
-- Ms. Nancy Harrison
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]