Abstract
Key discussion points covered in the draft are stated here in a few complete sentences, using passive rather than active voice. The more specific the better since the abstract often populates search engines and catalog databases.
Introduction
The introduction of the frontmatter is informative. It serves to give readers context, including background, key themes, history, etc.
Acknowledgements
Permissions have been granted as follows:
Recommended Practice for Preparing an IEEE Standards Draft
1. Overview
1.1. Scope
The scope shall be within the technical boundaries, as determined by the balloting group, of the scope submitted on the PAR. If the standard incorporated Open Source, this should be noted in the Scpe along with a link to the Open Source of the URL.
1.2. Purpose
The purpose shall be within the technical boundaries, as determined by the balloting group, of the purpose submitted on the PAR.
1.3. Word usage
The word shall indicates mandatory requirements strictly to be followed in order to conform to the standard and from which no deviation is permitted (shall equals is required to).67
The word should indicates that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required (should equals is recommended that).
The word may is used to indicate a course of action permissible within the limits of the standard (may equals is permitted to).
The word can is used for statements of possibility and capability, whether material, physical, or causal (can equals is able to).
2. Normative references
The following referenced documents are indispensable for the application of this document (i.e., they must be understood and used, so each referenced document is cited in text and its relationship to this document is explained). For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments or corrigenda) applies.
IEEE Std 91,
Accredited Standards, Accredited Standards Committee C2-2012, National Electrical Safety Code® (NESC®).89
IEEE P802.21/D14, IEEE P802.21™ (Draft 14, November 2003), Draft Standard for Local and Metropolitan Area Networks — Media Independent Handover Services.10
IEEE/ASTM SI, IEEE/ASTM SI 10™, American National Standard for Metric Practice.
NFPA 70, NFPA 70, 2011 Edition, National Electrical Code® (NEC®).1112
IEEE 260.1-2004 / IEEE 260.1™-2004, IEEE Standard Letter Symbols for Units of Measurement (SI Customary Inch-Pound Units, and Certain Other Units).
ISO/IEC 27002:2013, Information technology — Security techniques — Code of practice for information security controls.
3. Definitions, acronyms and abbreviations
3.1. Definitions
For the purposes of this document, the following terms and definitions apply. The IEEE Standards Dictionary Online should be consulted for terms not defined in this clause.13
acceleration-insensitive drift rate: The component of… See also: drift rate; systematic drift rate.
code set: See: coded character set.
coded character set: A set of characters. Syn: code set.
drift rate: The slope at a stated time of… (adapted from ISO/IEC 9945-1:2003 [B3])
input reference axis: The direction of an axis. Syn: IRA.
NOTE—See 6.7.14
IRA: See: input reference axis.
output: (A) Data that …(B) The process of …
systematic drift rate: That component of drift rate that… (IEEE 260.1-2004)
3.2. Acronyms and abbreviations
DER
distributed emission regeneration
DIS
distributed interactive simulation
ISDN
integrated services digital network
LAN
local area network
PDU
protocol data unit
4. Important elements of IEEE standards drafts
4.1. General
IEEE drafts should be created using one of the approved IEEE SA templates. The templates have built-in macro features that allow for easy tagging of each of the draft elements.15
Sources listed in the normative references clause shall also be cited in text. Explain the role and significance of each normative reference. Note that IEEE drafts may be included in the normative references clause as long as they are properly cited. See reference to IEEE P802.21 (Draft 14, November 2003) in Clause 2 of this sample.
NOTE 1—A normative reference is a document that users of the standard need to have on hand and understand in order to correctly implement the material contained in an IEEE draft.16
NOTE 2—Documents that serve as supplemental information that authors of the standard found useful when researching the material, but that do not carry the same weight as the normative references, are usually informative and therefore would belong in a bibliography (informative annex).
All IEEE standards shall use metric units as the primary units of measure. Customary equivalents may be included in the text after the metric units in parentheses. In the case of tables, separate tables for metric and customary units may be included. See National Electrical Safety Code® (NESC®) (Accredited Standards Committee C2-2012) and National Electrical Code® (NEC®) (NFPA 70, 2011 Edition) for examples. For more information on the use of metric in IEEE standards, see IEEE/ANSI SI 10. For guidance on the use of letter symbols for units of measurement, refer to IEEE Std 260.1-2004.
4.2. Lists
Lists in a clause or subclause may be ordered or unordered.
The following is an example of a properly formatted ordered list:
Name of the manufacturer
Connection chart showing
Full winding development
Taps
Self-impedance (for linear coupler transformers)
Reactance
Impedance
For volts
For amperes
The following is an example of a properly formatted unordered list:
Begin with a capital letter.
Include final punctuation for all items in the list if one item in the list is a complete sentence.
4.3. Tables
Tables should be cited in text and the significance of the tables explained. Table titles are positioned above the tables. Table 1 shows the nomenclature of a properly formatted table.
Table 1—Table formatting
Column heading | Column heading | Column headinga | |
---|---|---|---|
Column heading | Column heading | ||
Line heading Subheading Subheading | Tabulated data (individual positions within the body of the table are called cells) | ||
Line heading | |||
NOTE 1—This table is provided as an example. The structure of actual tables may vary depending on the data being displayed. NOTE 2—Use 0.75 Xd for hydrogenerators without amortisseur windings. a Table footnotes are considered to be a normative part of the document. |
Column headings are in bold and centered. If a table extends beyond one page, carry the title of the table over to each subsequent page with “(continued)” after the title. Table notes are informative; table footnotes are normative.
The following is an example of an informal table. Note that there is no title or table number. Use these sparingly. It is preferred that all tables are numbered and titled.
Cable type | Rated voltage (kV) |
---|---|
High pressure | 69–161 |
Low pressure Gas-filled | 10–29 30–46 |
Low and medium pressure Liquid-filled | 15–161 230 |
4.4. Figures
Figures should be cited in text and the significance of the figures explained. Figure titles are positioned below the figures themselves. Figures can be created using text or graphics software. Figure 1 and Figure 2 show properly formatted figures.
Figure 1—Typographical specifications for figure title
Figure 2-1—vibration test
Figure 2-2—shock test
Figure 2—A sample of figure presentation
NOTE—Notes to figures are formatted between the graphic and the figure caption.
4.5. Equations
Equations should be cited in text and the significance of each equation explained. The equation number should be right-aligned. See Equation (1).
(1)
is the amplitude of the Gaussian function at channel
is the height of the Gaussian at the centroid channel
is the channel number
is the centroid of the Gaussian
is the width of the Gaussian
Annex A
(informative)
Sample bibliography
Bibliographical references are resources that provide additional or helpful material but do not need to be understood or used to implement this standard. Reference to these resources is made for informational use only.
[B1] IEEE Std XXX™-YEAR, IEEE Standard for Something Industry Needs.
[B2] Name of Book Title in Italics. City of Publication, State: Name of Publisher, Year of Publication. First and Last Page of Reference.
[B3] ISO/IEC 9945-1:2003, Information technology — Portable Operating System Interface (POSIX) — Part 1: Base Definitions.
Annex B
(normative)
Structure of a sample annex
B.1. Overview
B.1.1. Title
Every annex shall be given a title and shall be designated either a normative or an informative annex. Notice that the numbering now contains the annex letter. See Equation (B.1):
(B.1)
is the amplitude of the Gaussian function at channel
is the height of the Gaussian at the centroid channel
is the channel number
is the centroid of the Gaussian
is the width of the Gaussian
B.1.2. Clause and subclause organization
The material in an annex should be organized into clauses and subclauses just like the body text. There should be at least two subclauses in any subdivision so that if there is one second-level header, there should be at a minimum one other one.
B.2. Material in annexes
Tables, figures, equations, lists, etc., in an annex are formatted like they would be in the body of the text except that
Tables are numbered according to the annex letter (see Table B.1).
Figures are labeled according to the annex letter (see Figure B.1).
Table B.1—Sample table in an annex
Column heading | Column heading | Column heading | |
---|---|---|---|
Column heading | Column heading | ||
Line heading Subheading Subheading | Tabulated data (individual positions within the body of the table are called cells) | ||
Line heading |
Figure B.1—Sample figure in an annex