Template:Element-symbol-to-oxidation-state-data

common:
notable:
predicted:

Template documentation follows
Note: the template above may sometimes be partially or fully invisible.
Visit "Template:Element-symbol-to-oxidation-state-data/doc" to edit its documentation if it is available. (How does this work?)

Data for the oxidation state entry in each element's infobox and for the List_of_oxidation_states_of_the_elements. Data entries here affect at least two pages.

Editing oxidation state data

The oxidation state data appears in three sections:

common values from a single standard reference: Greenwood, N. N., Earnshaw, A. (2012). Chemistry of the Elements. Germany: Butterworth-Heinemann. Please see the Wikipedia talk:WikiProject Elements/Archive 63 § What is a "main oxidation state"?. These values should not be changed without consensus on the Elements Talk page.
notable values from experiments, with reliable sources
predicted values from theory, with reliable sources.

Each section has one entry for each element in the periodic table.

Each entry has strict limits to allow text processing.

Each element result in a string
Each string oxidation-state-number values
- an oxidation-state-number eg "+3," starts with
 - a space or a newline, followed by
 - a math minus sign (not a dash) OR
 - a plus OR
 - nothing
 - followed by number,
 - followed by comma (every entry including the last one),
- a referenced-oxidation-state-number is an oxidation-state-number followed by
 - a <ref>...</ref> tag,
 - a ? tag, or
 - a * tag creating the following reference:

Greenwood, Norman N.; Earnshaw, Alan (1997). Chemistry of the Elements (2nd ed.). Butterworth-Heinemann. p. 28. doi:10.1016/C2009-0-30414-6. ISBN 978-0-08-037941-8.

The common entries are oxidation-state-number values. Do not include 0 (zero) in the common set.

The notable and predicted entries are referenced-oxidation-state-number values. Do not include formatting.

How to add references

Find the element

Most of the time you want the second place the element is listed, for example for Titanium is the second place you see e"Ti=...".

If the ref has not been used before

Add it as normal.

If the reference already used in the element page or in Oxidation state

Make an exact character for character copy of the ref and include it with the new oxidiation state data.

OR

Note the value of the name= parameter. If there is none, add one using "Author-year".

In this template add a self-closing "reference reference" with an name like "Author-date",eg

6,<ref name="Smith-2006"/>

Add the reference definition in two places

In the element page and in Oxidation state add the "reference definition" as a List-defined_reference:

==References==
{{Reflist|refs=
<ref name="Smith-2006">content1</ref>
<ref name="Joe-1936">content2</ref>
}}

Check

Open the element page and Oxidation state references for red Cite Errors.

Template usage

This data template is designed for two use cases,

Parameters

os-formatter: a template that accepts symbol, common, notable, and predicted parameters and produces formatted wikitext.
symbol: element to be selected from the data.

The main-space pages that use these templates should include a definition of the reference named "cn" which might look like

<ref name="cn">Oxidation state{{citation needed}}</ref>

Formatters

See the doc pages of these templates for examples.

{{Element-symbol-to-oxidation-state-echo}}: debug output, used by default
{{Element-symbol-to-oxidation-state-entry}}: formats for {{Infobox element}}
{{Element-symbol-to-oxidation-state-row}}: formats for one row of {{List of oxidation states of the elements}}

Example debug output

The examples use the "echo" formatter and the calls look like {{Element-symbol-to-oxidation-state-data|symbol=C}}

C

common:−4, −3, −2, −1, 0, +1, +2, +3, +4
notable:
predicted:

Fe

common:+2, +3
notable:−2,^* −1,^* 0,^* +1,^[1] +4,^* +5,^[2] +6,^* +7^[3]
predicted:

He

common:
notable:
predicted:

Sg

common:
notable:0,^[4] +6^[5]
predicted:(+3), (+4), (+5), (+6)^[6]

Usage

This template can be used to make a standard navigation box. It is intended for use within another template that standardises the title and contents of the box (see Template:ShipNavbox). This template SHOULD NOT be used directly within articles, as it creates a maintenance burden to do so whenever the contents of the box have to be updated.

The purpose of this template is to standardise the attributes of all navigation boxes, for example, their colours and other CSS attributes. The template is fairly simple, and could be extended to add other features in the future. Using this template allows changes to be implemented much quicker and easier than editing each template separately.

Syntax

{{navbox
|state      = uncollapsed, collapsed, plain, autocollapse (default)
|name       = mandatory - name of the template
|style      = optional - style for the whole table
|title      = mandatory - navbox header
|gtitleN    = optional - title of N-th group of items
|styleN     = optional - style for groupN; i.e. text-align
|groupN     = mandatory - list of groups of items
|fstyle     = optional - style for footer ; i.e. text-align
|footer     = optional - navbox footer
}}

Groups: Currently there is no technical limit to the maximum number of groups.
- Groups of items can be added as parameters: group1, group2, group3, ... up to groupN.
Group title: Each group has its own title parameter: gtitle1, gtitle2, gtitle3, ... up to gtitleN. Note that the default width for the first column is 15%.
Group style: Style may also be customised to each group in: style1, style2, style3, ... up to styleN.
- Note that neither the title nor the items have any wiki-links built into the template. As a result, users of the template are free to use wiki-links as they wish.
Line breaks: Line-breaks ( ) are unnecessary, as text wrapping is done automatically by the template. This also includes links and text in gtitleN and groupN.
Bullets: Create unordered lists with lines beginning with *.
Pipe links: Because of the nature of template syntax, it may be necessary to use Template:! ({{!}}).

States

Autocollapse: By default, the state of a navbox is "autocollapsed". This means that if the number of navboxes in a page exceeds the maximum allocation of the collapsible navboxes, then the remaining navboxes are collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
- Currently, the autocollapse allocation is 2 (see MediaWiki:Common.js). This means that if there are 3 navboxes in a page, the third and subsequent navboxes will be collapsed automatically.
Uncollapsed: Forces the navbox to be displayed.
- All of the navboxes in this documentation are in the uncollapsed state.
Collapsed: The reverse of uncollapsed. Forces the navbox to be hidden instead.
- Navboxes with a height of more than 300 pixels will also be collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
Plain: Removes the "show/hide" link.

Sub-groups

For larger navboxes, it may be necessary to include sub-groups within a particular group of items. It is also possible to collapsible navboxes within the parent navbox, see Collapsible sub-groups.
To create sub-groups within {{navbox}}, certain parameters are to be included:
- The parent navbox group (i.e. group2 in the example below) requires the type parameter (gtype2 = Subgroup).
- The nested navbox (sub-group) requires the inclusion of the sub-group parameter (subgroup = yes). This enables the template to differentiate between the sub-group and the parent navbox.

{{navbox
|name    =
|title   =
|gtitle1 =
|group1  =
|gtitle2 =  
|gtype2  = Subgroup (mandatory)
|group2  = 
  {{navbox
  |subgroup = yes (mandatory)
  |gtitle1  = 
  |group1   =
  |gtitle2  = 
  |group2   = 
  }}
}}

Collapsible sub-groups

For extremely long navboxes, it is recommended to use collapsible navboxes within the parent navbox. Further sub-groups can then be added to these collapsible navboxes.
To create collapsible sub-groups within {{navbox}}, these parameters need to be included:
- The parent navbox is almost always uncollapsed (state=uncollapsed).
- The parent navbox group (i.e. group1 in the example below) requires the type parameter (gtype1 = Subgroup).
- The nested collapsible navbox requires the inclusion of the collapsible parameter (collapsible = yes). This enables the template to differentiate between the collapsible navbox and the parent navbox.
- The nested collapsible navbox is forcefully collapsed (state=collapsed).

{{navbox
|state  = uncollapsed
|name   = 
|gtype1 = Subgroup
|group1 = 
  {{navbox
  |collapsible = yes
  |state   = collapsed
  |title   = 
  |gtitle1 = 
  |group1  = 
  |gtitle2 = 
  |group2  = 
  }}
}}

Use of images

The use of images in navboxes is permitted, but please resize the images to keep them small. Inventory-sized images (25-30 pixels) are recommended.
Please use {{t|plink}} to create links with images. Use {{t|plink}} for any case where text is not desired after the link. It functions the same as {{t|plink}}, but it does not produce a wikilink in text. Use {{t|chatl}} to link chatheads. These templates create links for both the image and text (except for {{t|plink}}) using far less wikicode than the standard syntax.

Link and file share the same name

{{plink|Item}}

File name differs from the link

{{plink|Item|File}}

Link and file share the same name, but different text is desired to display

{{plink|Item|alt=Text}}

File name differs from the link and different text is desired to display

{{plink|Item|File|alt=Text}}

Categorising

Navboxes are very useful for transcluding categories onto a large number of pages that share both a trait and the navigation box. For example: Template:ShipNavbox transcludes Category:Ships onto every page that uses it.

There are 2 methods of categorising pages with navboxes:

The first way is with {{t|Ctg}}. This is the preferred method, and can be used in most cases. The rules and operations for the Category handler template are very simple; however, they are enough to produce the desired results on most pages.

Categorisation should only be used on a template for large-scale addition. It is unhelpful, for example, to use a rule that only applies to 1 page.

Examples

To see the following navboxes in action, see Template:Navbox.

Single line navbox with centered list

{{navbox
|name    = 
|title   = 
|style1  = text-align:center
|group1  =
}}

Navbox with standard footer

{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|footer  = Centered footer
}}

Navbox with styled footer

{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|fstyle  = text-align:right
|footer  = Right-aligned footer
}}

Multiple line navbox

{{navbox
|name    = 
|title   = 
|gtitle1 = Group title 1
|group1  = 
|gtitle2 = Group title 2
|group2  = 
|gtitle3 = Group title 3
|group3  = 
}}

Collapsed navbox

{{navbox
|state   = collapsed
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox with Tnavbar

{{navbox
|state   = plain
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox without Tnavbar

{{navbox
|state   = plain
|title   = 
|style1  = text-align:center
|group1  = 
}}

Complicated navbox

{{navbox
|state   = uncollapsed
|name    = 
|title   = 
|gtitle1 = Level 1 Title 1
|group1  = 
|gtitle2 = Level 1 Title 2
|group2  = 
|gtitle3 = Level 1 Title 3
|group3  = 
|gtitle4 = Level 1 Title 4
|group4  = 
|gtitle5 = Level 1 Title 5
|gtype5  = Subgroup
|group5  = 
  {{navbox
  |subgroup = Yes
  |gtitle1  = Level 2 Title 1
  |group1   =
  |gtitle2  = Level 2 Title 2
  |group2   =
  |gtitle3  = Level 2 Title 3
  |gtype3   = Subgroup
  |group3   = 
    {{navbox
    |subgroup = Yes
    |gtitle1  = Level 3 Title 1
    |group1   =
    |gtitle2  = Level 3 Title 2
    |group2   =
    }}
  |gtitle4  = Level 2 Title 4
  |group4   = 
  }}
|gtitle6 = Level 1 Title 6
|group6  = 
|gtitle7 = Level 1 Title 7
|group7  = 
|fstyle  = 
|footer  = 
}}

Preventing unwanted documentation

The Navbox template's documentation is automatically transcluded under the navbox on any Template namespace page. It is not transcluded when used as a sub-group or collapsible sub-group template (subgroup= yes or collapsible=yes).

Should the documentation appear when it is unwanted, it can be hidden by setting the doc parameter doc=no on the template. In most cases, the doc parameter is NOT used and the parameter is removed completely.

↑ Ram, R. S.; Bernath, P. F. (2003). "Fourier transform emission spectroscopy of the g⁴Δ–a⁴Δ system of FeCl". Journal of Molecular Spectroscopy. 221 (2): 261. Bibcode:2003JMoSp.221..261R. doi:10.1016/S0022-2852(03)00225-X.
↑ Demazeau, G.; Buffat, B.; Pouchard, M.; Hagenmuller, P. (1982). "Recent developments in the field of high oxidation states of transition elements in oxides stabilization of six-coordinated Iron(V)". Zeitschrift für anorganische und allgemeine Chemie. 491: 60–66. doi:10.1002/zaac.19824910109.
↑ Lu, J.; Jian, J.; Huang, W.; Lin, H.; Li, J; Zhou, M. (2016). "Experimental and theoretical identification of the Fe(VII) oxidation state in FeO₄⁻". Physical Chemistry Chemical Physics. 18 (45): 31125–31131. Bibcode:2016PCCP...1831125L. doi:10.1039/C6CP06753K. PMID 27812577.
↑ Sg(0) has been observed in seaborgium hexacarbonyl (Sg(CO)₆); see Even, J.; Yakushev, A.; Dullmann, C. E.; Haba, H.; et al. (2014). "Synthesis and detection of a seaborgium carbonyl complex". Science. 345 (6203): 1491–3. Bibcode:2014Sci...345.1491E. doi:10.1126/science.1255720. PMID 25237098. S2CID 206558746.
↑ Sg(VI) has been observed in seaborgium oxide hydroxide (SgO₂(OH)₂); see Huebener, S.; Taut, S.; Vahle, A.; Dressler, R.; et al. (2001). "Physico-chemical characterization of seaborgium as oxide hydroxide" (PDF). Radiochim. Acta. 89 (11–12): 737–741. doi:10.1524/ract.2001.89.11-12.737. S2CID 98583998. Archived from the original (PDF) on 2014-10-25.
↑ Hoffman, Darleane C.; Lee, Diana M.; Pershina, Valeria (2006). "Transactinides and the future elements". In Morss; Edelstein, Norman M.; Fuger, Jean (eds.). The Chemistry of the Actinide and Transactinide Elements (3rd ed.). Dordrecht, The Netherlands: Springer Science+Business Media. ISBN 978-1-4020-3555-5.

[1] Ram, R. S.; Bernath, P. F. (2003). "Fourier transform emission spectroscopy of the g⁴Δ–a⁴Δ system of FeCl". Journal of Molecular Spectroscopy. 221 (2): 261. Bibcode:2003JMoSp.221..261R. doi:10.1016/S0022-2852(03)00225-X.

[2] Demazeau, G.; Buffat, B.; Pouchard, M.; Hagenmuller, P. (1982). "Recent developments in the field of high oxidation states of transition elements in oxides stabilization of six-coordinated Iron(V)". Zeitschrift für anorganische und allgemeine Chemie. 491: 60–66. doi:10.1002/zaac.19824910109.

[3] Lu, J.; Jian, J.; Huang, W.; Lin, H.; Li, J; Zhou, M. (2016). "Experimental and theoretical identification of the Fe(VII) oxidation state in FeO₄⁻". Physical Chemistry Chemical Physics. 18 (45): 31125–31131. Bibcode:2016PCCP...1831125L. doi:10.1039/C6CP06753K. PMID 27812577.

[4] Sg(0) has been observed in seaborgium hexacarbonyl (Sg(CO)₆); see Even, J.; Yakushev, A.; Dullmann, C. E.; Haba, H.; et al. (2014). "Synthesis and detection of a seaborgium carbonyl complex". Science. 345 (6203): 1491–3. Bibcode:2014Sci...345.1491E. doi:10.1126/science.1255720. PMID 25237098. S2CID 206558746.

[5] Sg(VI) has been observed in seaborgium oxide hydroxide (SgO₂(OH)₂); see Huebener, S.; Taut, S.; Vahle, A.; Dressler, R.; et al. (2001). "Physico-chemical characterization of seaborgium as oxide hydroxide" (PDF). Radiochim. Acta. 89 (11–12): 737–741. doi:10.1524/ract.2001.89.11-12.737. S2CID 98583998. Archived from the original (PDF) on 2014-10-25.

[Haire-6] Hoffman, Darleane C.; Lee, Diana M.; Pershina, Valeria (2006). "Transactinides and the future elements". In Morss; Edelstein, Norman M.; Fuger, Jean (eds.). The Chemistry of the Actinide and Transactinide Elements (3rd ed.). Dordrecht, The Netherlands: Springer Science+Business Media. ISBN 978-1-4020-3555-5.

[1]

[2]

[3]

[4]

[5]

[6]