With the exception of Stan and Dawn, please do not add additional comments to review E. We’ll open an updated review in a day or two and folks who did not participate in the first one will have a chance to comment.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Owner, Eberlein Consulting LLC
kris@eberleinconsulting.com
Skype: kriseberlein; voice: +1 (919) 622-1501
From: dita@lists.oasis-open.org <dita@lists.oasis-open.org>
On Behalf Of Kristen James Eberlein
Sent: Sunday, February 12, 2023 8:25 PM
To: Zoe Lawson <zoelawson17@hotmail.com>; DITA Technical Committee (dita@lists.oasis-open.org) <dita@lists.oasis-open.org>
Subject: [dita] RE: Review E: Troubleshooting
I’m trying to figure that out. I’ve spent most of today responding to comments and making changes to source files. My best guess is that we will close this review end-of-business tomorrow, and then reopen a review of revised content for
another week – but I won’t get a chance to talk to Robert about that until tomorrow.
Look for final info tomorrow.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Owner, Eberlein Consulting LLC
kris@eberleinconsulting.com
Skype: kriseberlein; voice: +1 (919) 622-1501
From: dita@lists.oasis-open.org <dita@lists.oasis-open.org>
On Behalf Of Zoe Lawson
Sent: Sunday, February 12, 2023 7:11 PM
To: DITA Technical Committee (dita@lists.oasis-open.org) <dita@lists.oasis-open.org>
Subject: [dita] Re: Review E: Troubleshooting
Are we aiming to have review comments in by Valentine's Day for this review?
The feeling I got from Stan's email was that the topics were going to be reworked. Or I might have missed something since I miss parts of meetings.
Thanks,
Zoë
From:
dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of Kristen James Eberlein <kris@eberleinconsulting.com>
Sent: Tuesday, February 7, 2023 10:45 AM
To: DITA Technical Committee (dita@lists.oasis-open.org) <dita@lists.oasis-open.org>
Subject: [dita] Review E: Troubleshooting
Please review the PDF, and then enter your comments in Content Fusion.
Please note that we have very, very specific requirements for how we need reviewers to use Content Fusion:
- Make all new comments as draft comments in the source.
Do not use the native Content Fusion comment function. This is necessary so that we can retain and archive a clear record of the discussion that took place in the review, as well as resolution of the comments.
-
To respond to a draft comment, edit the existing draft comment. We suggest specific markup to use.
See the information about using Content Fusion at the bottom of this e-mail.
Link to review PDF
https://www.oasis-open.org/committees/document.php?document_id=70740&wg_abbrev=dita
Link to Content Fusion review
https://fusion.oxygenxml.com/tasks/jg3ffq5j5qsplfioqo5hn7s20ar9vrvppsor7s9ju8pi4phk
Note that the topics in Content Fusion do not match the order of the topics in the review PDF. This is Content Fusion error that I do not know how to troubleshoot.
Link to latest version of the DITA 2.0 spec
https://www.oasis-open.org/committees/document.php?document_id=70741&wg_abbrev=dita
Information about using Content Fusion
Inserting a draft comment
1.
In the Editor pane, place your cursor where you want to insert the draft comment.
2.
Right-click Insert > Insert Element.
3.
Select Draft Comment.
4.
Add content to the draft comment, using standard DITA markup.
Ensure that the @author and @time attributes clearly indicate your name and the date that you added the draft comment.
Editing a draft comment
1.
In the Editor pane, place your cursor at the end of the content within the existing draft comment.
2.
Insert a <div> element:
a.
Right-click Insert >Insert Element.
b.
Select Division.
c.
Add markup, as indicated in the following screen capture:
--
Best,
Kris