DITA Machine: Proposals for full implementation of hazard statement

[dita@seicodyne.ch]

On behalf of Gerald Gtz I am uploading this email.

Proposed changes and requirements to the full implementation of hazardstatement (DTD fragment in issue5.pdf) by Gerald Goetz

 1. The required attribute "type" of the element hazardstatement should 
    be renamed to "level" because it indicates the degree of the hazardstatement.
    
 2. An optional attribute "type" should be added to the element hazardstatement 
    to inicate the type of hazard. Examples for type: "Hazardous Electrical
    Voltage", "Laser Light", ...

    The type of the hazardstatement is not directly bound to the level.
    
    The DTD should allow to specialize the element "hazardstatement" to leave
    out the element "symbol" for applications where the user should only be
    allowed to pick from a predefined number of symbols (= types).

 3. The DTD should allow to specialize the element "messagepanel" to a 
    stricter content model where "typeofhazard" is mandatory and at least
    one element "howtoavoid" must appear:

    <!ELEMENT messagepanel ( (%typeofhazard;), (%consequence;)*, (%howtoavoid;)+ ) >

 4. The DTD should allow to specialize the element "hazardstatement" to a 
    stricter content model where "messagepanel" is mandatory (and the
    symbol is controled via the type attribute)

 5. The content model of the element "howtoavoid" should allow an optional intro for
    text like: "Before you turn on power".
    One alternative would be to change the content model from phrase to paragraph level.
    Alternatively howtoavoid could include commands:

    <!ELEMENT howtoavoid ( intro?, cmd+ )>