Search results
Results from the WOW.Com Content Network
All four codes default to blank, that is: no NFPA code is present or shown. There is no specific text (just a link to the NFPA color section). Note that a blank is not the same as code "0". Code "0" is an explicit statement, while a blank is the absence of any statement. A blank can also be enforced by entering =-(hyphen).
If the template has a separate documentation page (usually called "Template:template name/doc"), add [[Category:GHS templates]] to the <includeonly> section at the bottom of that page. Otherwise, add <noinclude>[[Category:GHS templates]]</noinclude> to the end of the template code, making sure it starts on the same line as the code's last ...
The absence of any hazard class or division or a blank space in the table indicates that no restrictions apply. X: These materials may not be loaded, transported, or stored together in the same transport vehicle or storage facility during the course of transportation.
NFPA 704 safety squares on containers of ethyl alcohol and acetone. "NFPA 704: Standard System for the Identification of the Hazards of Materials for Emergency Response" is a standard maintained by the U.S.-based National Fire Protection Association.
An example SDS, including guidance for handling a hazardous substance and information on its composition and properties. A safety data sheet (SDS), [1] material safety data sheet (MSDS), or product safety data sheet (PSDS) is a document that lists information relating to occupational safety and health for the use of various substances and products.
This explosives -related article is a stub. You can help Wikipedia by expanding it.
Signal word: "Danger" or "Warning" will be used to emphasize hazards and indicate the relative level of severity of the hazard, assigned to a GHS hazard class and category. Some lower level hazard categories do not use signal words. Only one signal word corresponding to the class of the most severe hazard should be used on a label.
This template is used on many pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage . Consider discussing changes on the talk page before implementing them.