RE: [docbook-tc] DocBook Technical Committee Meeting Agenda: 20 July 2016

["Rowland, Larry" <larry.rowland@hpe.com>]

Hello, Bob,

This is in regards to item 5.d, investigation of ISO standards for admonitions.

The term that ISO uses is "signal words" for the various types of warning messages.  There are currently three:

+ DANGER
+ WARNING
+ CAUTION

ANSI added NOTICE, which is italicized in the representations I have found.  The signal words are all presented all caps.  The best description of the set of them I have found is on a Web site for a sign company (the discussions become complex and tiresome on most of the formal sites).  Check page 2 of the PDF at http://www.safetysign.com/content/PDF/ANSI_SafetyHeaders.pdf.  For the first three rows of signs, you will see that the signs with the exclamation point in a yellow triangle are identified as ISO compliant.  ISO says to use the CAUTION signal work with no hazard icon (the triangle with exclamation point) for the equivalent of what NOTICE is used for by the ANSI standards.  I would assume

The only one we are missing is DANGER, although there may be a need for a generic admonition mechanism to represent things like SAFETY INSTRUCTIONS from the last row of signs on page 2.

We may also want to look at providing a flag (perhaps role or class?) that would allow accessing localized standard signal words in all-caps for DANGER, WARNING and CAUTION, since we do our labels initial cap; we also don't use ISO or ANSI standard icons (I know that's actually a transform issue, but coming up with a standard way to indicate what is wanted is probably a markup issue, particularly since there are some differences between the two, and differences even within the ANSI standard -- there is also a "harmonization" of the European standards out there someplace).  Turns out the EU is moving to using icons for a lot of what gets covered by text in traditional admonitions.  Some of the signs end up being just pictures nowadays.  Otherwise, they have to be localized into all the official EU languages in the originating and destination countries.

Regards,
Larry Rowland

-----Original Message-----
From: docbook-tc@lists.oasis-open.org [mailto:docbook-tc@lists.oasis-open.org] On Behalf Of Bob Stayton
Sent: Monday, July 18, 2016 12:10 PM
To: DocBook Technical Committee <docbook-tc@lists.oasis-open.org>
Cc: docbook@lists.oasis-open.org
Subject: [docbook-tc] DocBook Technical Committee Meeting Agenda: 20 July 2016

DocBook Technical Committee Meeting Agenda: 20 July 2016
=============================================================

The DocBook Technical Committee will meet on Wednesday,
20 July 2016 at 2:00pm ET for 90 minutes.

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
  Code: 902213

The DocBook TC uses the #docbook IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 17 August 2016
4. Review of the agenda.
5. Review of open action items

    a. Norm to review the non-normative XML Schema version of 5.1
       to make sure it has all the latest changes.

    b.  Norm to complete his XInclude implementation.

    c.  Bob to investigate assembly for XInclude equivalents.

    d.  Larry will look into ISO standards for admonitions.

6.  Status of stagedir elements in Publisher's.  See [2].

7.  DocBook 5.1 release

8.  Review of Requests for Enhancement

     To browse a specific RFE, enter the URL (on one line):

       https://sourceforge.net/p/docbook/rfes/300/

     RFEs to revisit for 6.0

     247   1907003  biblioid content model too broad

    RFEs under discussion

    Ticket  Tracker
     260   2820947  Ability to transclude text
     273   3035565  Allow sections at any level
     291   3491860  license tag  (hold for 5.2)
     306            Allow Block Elements inside abstract

     Github Issues
     6     Add buildtarget element
     7     Allow revnumber inline.
     53    Extend article @class with other and otherclass
     54    Add XIncludes to Assembly Schema
     55    Add <danger> to list of admonitions
     58    Allow Block Elements inside <abstract>
     59    Allow <modifier> within <paramdef>?
     60    Allow <void> within <funcdef>?

No new RFEs.


-----

[1] https://lists.oasis-open.org/archives/docbook-tc/201606/msg00023.html
[2] https://lists.oasis-open.org/archives/docbook-apps/201607/msg00002.html

-- 
Bob Stayton
Sagehill Enterprises
bobs@sagehill.net

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php