(Updated) Comments from the current review that we need to discuss

[Kristen James Eberlein <kris@eberleinconsulting.com>]

Hi, folks.

 

There are several comments from the current review that we need to discuss. The links below go to the topic in the Content Fusion review, so if you have not yet used Content Fusion, you’ll need to decide on how you want to log in. You can log in using your GitHub or Google credentials, or you can set up a Content Fusion user ID and password.

 

• <codeblock>
• Font conventions and RFC-2119 terminology (page 3 in PDF
• Where do we want to cover font and other formatting conventions? Currently they are in a non-normative appendix topic: Formatting conventions. Should they be in the “Rendering expectations” sections of individual topics instead? Or in both places?
• <option>: What is the semantic distinction between <option> and <parmname>? Can we be more precise in the DITA 2.0 spec? (pages 5-6 in PDF)
• <userinput>: Appropriate tagging for code samples in the “Example” section of element-reference topics (page 12 in PDF)

 

A PDF of the Content Fusion review is 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

 

Attachment: review-c-content-fusion.pdf
Description: review-c-content-fusion.pdf