Proposed agenda for 01/08/18 call

[Carlos Evia <cevia@vt.edu>]

Dear Lightweight DITA subcommittee members,

Happy new year!

The proposed agenda for our Monday call is simple: we will look at comments received during the committee note public review and make a plan to address them or send them to the TC.

If you need an agenda, here’s the link: https://wiki.oasis-open.org/dita/LightweightDITASubcommittee

The topic logging comments lives in GitHub (https://github.com/oasis-tcs/dita-lwdita/blob/master/CommitteeNote1/comment-resolution-log-lwdita-cn-01.dita), but I am attaching an HTML transform to this message for reference during our call.

Best,

Carlos

--

Carlos Evia, Ph.D.

Director of Professional and Technical Writing

Associate Professor of Technical Communication

Virginia Tech

Blacksburg, VA 24061-0112

(540)200-8201

Title: Comment resolution log

Comment resolution log

The table summarizes the comments that were received during the 30-day review of the committee note "Lightweight DITA: An Introduction" and their resolution. Comments came to the dita-comment, Lightweight DITA SC, and DITA TC mailing lists, and to Carlos Evia's email address.

A status of "Completed" in the Disposition column indicates that the editors have implemented the changes on which the TC decided, which are outlined in the Resolution column. It also is a hyperlink to the GitHub commit notice.

The item number is a hyperlink to the e-mail on the dita-comment or DITA TC mailing lists. Carlos Evia forwarded all relevant messages that he received to the DITA TC mailing list.

The following abbreviations are used:

• CE = Carlos Evia
• KJE = Kristen James Eberlein
• AH = Alan Houser

Item #	Date	Commenter	Description	Date acknowledged	Resolution	Disposition	Listed in committee note?
1	28 November 2017	Roger Hadley	List DITA elements not present in LwDITA: "How would LwDITA authoring be different in my content?"	7 December 2017
2	28 November 2017	Scott Prentice	Use the term "components" when referring to items like "Paragraph," and "elements" when talking about XML or HTML nodes (like "<p>")	7 December 2017
3	28 November 2017	Scott Prentice	Mention if image is always inline and fig/image is break	7 December 2017
4	28 November 2017	Scott Prentice	Note the need for map/topicmeta/navtitle in lieu of map/title	7 December 2017
5	28 November 2017	Scott Prentice	Include topicref/@processing-role	7 December 2017
6	28 November 2017	Scott Prentice	Add DITA-FMx to list of tools	7 December 2017
7	28 November 2017	Scott Prentice	Bold "Filtering attribute" subhead within attributes table	7 December 2017	Change implemented by CE	Completed
8	29 November 2017	Jang Graat	Do not mention any tools	7 December 2017
9	29 November 2017	Rodolfo Raya	Do not mention any tools	7 December 2017
10	11 December 2017	Keith Schengili-Roberts	Explain proper way to call keyrefs in MDITA (HDITA snippet or CommonMark shortcut reference link)	Not applicable
11	20 December 2017	Jang Graat	Explain (all?) design decisions?	Not applicable
12	4 December 2017	Fiona Hanington, via CE	Consider Restructured Text as authoring format	29 November 2017	It was considered but had no champion in SC	To be discussed in future version of LwDITA
13	4 December 2017	Chris Despopoulos, via CE	Spell out use cases in "Why LwDITA" topic ("collaboration with engineers, breaking into the Marketing silo, aggregating content to generate XDITA out of a mixed book that you can send to an OEM")	28 November 2017
14	4 December 2017	Chris Despopoulos, via CE	Clarify need for multimedia domain to be added to 1.3	28 November 2017
15	4 December 2017	Chris Despopoulos, via CE	Check references to DITA as a language instead of a grammar	28 November 2017
16	4 December 2017	Chris Despopoulos, via CE	Be consistent when using element types/elements	28 November 2017
17	4 December 2017	Chris Despopoulos, via CE	Rephrase "These authoring formats will enable and enhance collaboration across divisional silos" to present as hypothesis or claim	28 November 2017
18	4 December 2017	Chris Despopoulos, via CE	Fix redundant statement "can be aggregated together"	28 November 2017	Change implemented by CE	Completed
10	4 December 2017	Tom Johnson, via CE	Why not just one Markdown version?	30 November 2017	Needed to provide an easy entry point for Markdown users; also, Markdown has limitations as structured language that need HTML	Deferred
11	4 December 2017	Tom Johnson, via CE	Include definition list support in MDITA	30 November 2017	Not supported by GitHub-Flavored Markdown	Deferred
12	4 December 2017	Tom Johnson, via CE	Include conref support in MDITA (Markdown-based)	30 November 2017	Considered many approaches before proposing HDITA snippets	Deferred
13	4 December 2017	Radu Coravu, via CE	Add DITA-OT Markdown support to tools section	4 December 2017
14	4 December 2017	Radu Coravu, via CE	Support for both "keyref" and "conref" is a little bit strange. It becomes a mix of DITA 1.1 and 1.2 functionality	4 December 2017
15	4 December 2017	Radu Coravu, via CE	Specify element ID in MDITA for a conref without HDITA snippet	4 December 2017	Considered Pandoc-like identifiers, but only work for headings and sections	Deferred
16	4 December 2017	Radu Coravu, via CE	Add multimedia elements later to keep LwDITA as a subset of DITA 1.3	4 December 2017