The following people participated in the review:
|
TC voting members + volunteers
|
Participation in review S
|
|
Dawn Stevens
|
X
|
|
Kris Eberlein
|
X
|
|
Stan Doherty
|
|
|
Nancy Harrison
|
|
|
Eric Sirois
|
X
|
|
Robert Anderson
|
|
|
Gershon Joseph
|
|
|
Carsten Brennecke
|
|
|
Eliot Kimber
|
X
|
|
Scott Hudson
|
X
|
|
Zoe Lawson
|
|
|
Bill Burns
|
X
|
|
Frank Wegmann
|
|
The following comments were marked as “ACCEPTED”:
|
Topic
|
Work to be done
|
Disposition
|
Page in (commented) PDF
|
|
E “Element-by-element recommendations for translators”
|
Definition of subflow
|
Accepted
|
9
|
The following comments were marked as “REFERRED”:
|
Topic
|
Work to be done
|
Disposition
|
Page or pages in (commented) PDF
|
|
A.1 “File naming conventions
|
Conventions for names of document-type shells
|
Referred
|
4 - 5
|
|
E “Element-by-element recommendations for translators”
|
Why do we have a specialization base column? Is it needed?
|
Referred
|
9 - 10
|
|
Block/inline (presentation) column: Why do we have this? What is its purpose? What values should be permitted? Eliot suggests block|inline|metadata|subflow.
|
Referred
|
10 - 11
|
|
List the few attributes that might need translation in a separate section
|
Referred
|
12
|
|
Values for “Translatable content?” column – Eliot suggests adding container.
|
Referred
|
13
|
|
Block/inline (translation) column – <image> -- What does it mean for an element to be a block? Can an image be a block or is just a container (as Eliot suggests)?
|
Referred
|
16-17
|
|
Map elements: Values for “Block/inline (presentation) – Eliot suggests that all should be n/a, since fundamentally metadata.
|
Referred
|
20 - 21
|
The two 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