[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] <cause> short description
Hi Dawn, I suspect the spec is trying to tell users that if their <cause> is too long, they need *another* troubleshooting topic instead of dropping the detailed and complex âcauseâ into the current
topic. Personally, Iâm OK if you delete it
😊
I donât think the red text youâre asking about belongs in a specâ Cheers, Gershon Gershon Joseph | Senior Information Architect | Precision Content Unlock the Knowledge in Your Enterpriseâ
From: <dita@lists.oasis-open.org> on behalf of Dawn Stevens <dawn.stevens@Comtech-serv.com> While writing the topics for the <diagnostics> proposal stage 3, I was looking at the topics for the rest of the troubleshooting topic elements to ensure I modelled the writing there. <cause> is described as follows: The <cause> element
describes a potential source of the problem that is described in the <condition> element,
the topic <title> element, or the <shortdesc> element.
This information should be brief; if it is not possible to make the information brief, this might be a sign that a full troubleshooting topic is needed. I donât understand the last sentence, after the semi-colon. <cause> is part of a full troubleshooting topic. What is it trying to tell me to do if my cause
is long? |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]