The following people participated in the review:
TC voting members + volunteers
|
Participation in review A
|
Dawn Stevens
|
X
|
Kris Eberlein
|
X
|
Stan Doherty
|
X
|
Nancy Harrison
|
|
Eric Sirois
|
|
Robert Anderson
|
|
Gershon Joseph
|
|
Eliot Kimber
|
X
|
Scott Hudson
|
|
Zoe Lawson
|
X
|
Bill Burns
|
X
|
Frank Wegmann
|
|
The following comments were marked as “REFERRED”.
Topic
|
Comment
|
Disposition
|
Page in (commented) PDF
|
General task
|
Two comments from Zoe:
- Suggests that we use the same organizational structural for both general task and strict task topic
- Post-requisites is not a real word …
|
Referred
Referred
|
|
Task elements
|
Eliot: Suggests we use passive voice for the short descriptions, rather than using the term “user” or “users”.
|
Referred
|
|
<choices>
|
Two comments from Eliott:
- Need for a “Usage information” section” that distinguishes <choices> from <choicetable>
- Utility of element? Expected presentation? Need for better example.
|
Referred
Referred
|
|
<choption>
|
Can we come up with an alternate way to describe the content of this element? Eliot does not like “names the option,” but Kris thinks that “labels or describes the option” overlaps too much with how we define <chhead> and <chdesc>.
|
Referred
|
|
<prereq>
|
Shall we keep (or remove) the statement that “Processors might render prerequisite links from the related-links section together with the content of the element”?
|
Referred
|
|
The following comments were marked as “ACCEPTED”. All other comments have been handled.
Topic
|
Work to be done
|
Disposition
|
Page in (commented) PDF
|
General task
|
New example: Dawn to develop
|
Accepted
|
|
<taskbody>
|
New example of general task: Dawn to develop
|
Accepted
|
|
<turorialinfo>
|
New example: Dawn to develop
|
Accepted
|
|
The relevant PDF files are attached.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Owner, Eberlein Consulting LLC
kris@eberleinconsulting.com
Skype: kriseberlein; voice: +1 (919) 622-1501