I totally agree with Thomas. As Thomas pointed out, there is an industry standard in Europe (maybe in other parts of the world too?) saying that you actually must differentiate between hazard statements. And danger is used to express a high risk of injury and/or death, whereas "caution" is actually something else. We’ve been "solving" this kind of issue before by introducing <caution role="danger">.
However, a more "generic" element would feel much better. And Dave... no, it’s not about CSS or other styling. It’s actually an element something that lots of our clients need. Just my 2 cents… /frank Paligo - The truly user-friendly CMS for technical documentation www.paligo.se > 28 apr 2016 kl. 10:24 skrev Dave Pawson <[email protected]>: > > What is danger to you might be nothing to me? > I think caution is right or a good compromise. If presentation is an > issue use CSS? > > > regards > > > On 28 April 2016 at 09:15, Thomas Schraitle <[email protected]> wrote: >> Hi, >> >> a DocBook writer asked me why there is no "danger" element in DocBook. >> >> Currently, we have tip, note, important, warning, and caution as >> admonition elements. The list is sorted from lowest to highest >> "severity". >> >> However, for writers who want to give a warning about deadly >> consequences, caution seems to me a bit "tame". ;) >> >> Although I'm a bit hesitant to add new elements to the DocBook schema, >> maybe we should consider that. The element danger would also fit better >> to the ANSI standard (I think it was Z535, right?). >> >> What do you think? >> >> >> -- >> Gruß/Regards, >> Thomas Schraitle >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
