Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Live Search
spaceKeyEUDR
placeholderSearch this space

On this space

Table of Contents
minLevel1
maxLevel3

In this section

Child pages (Children Display)
pageNISO 1.0 Export Filter

Example 1: Meta Notes

The following example shows a properly styled Meta Note section.

Meta Notes can be single paragraphs of text that describe general information about the document; in those cases, the Meta Note Title is not required.

Info

Meta Notes can be placed in either the front or back of the Word document, but they will always export to the <front> in the XML.

Word Sample

Screenshot in Draft View of one heading and two paragraphs. The visible paragraph styles from top to bottom are MetaNoteTitle, MetaNote, MetaNoteImage Added

XML Sample

The following XML is derived from the above Word content. The Meta Note content is exported to <std-doc-meta> in the <front>.

Meta Note with Title

Code Block
<meta-note>
<title>Special Notes</title>
<p>API publications necessarily address problems of a general nature. With respect to particular circumstances, local, state, and federal laws and regulations should be reviewed.</p>
<p>Neither API nor any of API's employees, subcontractors, consultants, committees, or other assignees make any warranty or representation, either express or implied, with respect to the accuracy, completeness, or usefulness of the information contained herein, or assume any liability or responsibility for any use, or the results of such use, of any information or process disclosed in this publication. Neither API nor any of API’s employees, subcontractors, consultants, or other assignees represent that use of this publication would not infringe upon privately owned rights.</p>
</meta-note>

Example 2: Keywords

For subject term or keyword listings, Keywords is applied to the appropriate paragraph in the document's front matter.

The strongest symbols to separate keywords are semicolons, em dashes, and bullets. These characters are highly unlikely to occur within the text of a single keyword. If eXtyles finds one of these characters within the keywords paragraph, it will use that character to separate the paragraph into individual keywords.

If eXtyles fails to find semicolons, em dashes, or bullets in the keyword paragraph, it will try weaker characters in an attempt to parse the list. These characters are tabs, em spaces, commas (followed by a space), and slashes with spaces on either side.

Word Sample

Screenshot in Draft View of the Keywords paragraph, styled with the paragraph style 'Keywords'Image Added

XML Sample

eXtyles automatically parsed out the Keyword title and individual keywords using the semicolon separators in the Word document.

Keywords

Code Block
<kwd-group><title>Keywords: </title><kwd>computer security incident</kwd><kwd>incident handling</kwd><kwd>incident response</kwd><kwd>information security</kwd></kwd-group>

Example 3: Front Matter Sections

Following is an example of a properly styled front matter section (in this case, Introduction).

Info

This example shows that Front Matter Text is used for the main text of the section, but regular list styles from the Body or List tabs can be used as needed.

Word Sample

Screenshot in Draft View of the Introduction section. The visible paragraph styles from top to bottom are FrontMatterH1, FrontMatterText, Num_Bul_List_1, FrontMatterTextImage Added

XML Sample

The Introduction <sec> is located in the <front> of the XML.

Introduction (Front Matter)

Code Block
<sec sec-type="introduction">
<title>Introduction</title>
<p>Post-combustion NOx control systems reduce levels of NOx emissions by converting the NOx formed during the combustion process to nitrogen (N<sub>2</sub>) gas. The chemical reactions required to convert the NOx to N<sub>2</sub> for the systems described in this standard are applied downstream of the combustion zone. These techniques introduce a reactant into the flue gas stream to react with the NOx. The reaction may be completed with or without the use of catalyst.</p>
<p>It may be necessary to combine more than one method of post-combustion control to achieve the desired level of NOx reduction.</p>
<p>The application of any NOx reduction technique and control technology is most often in compliance with an environmental regulation requirement, which include both instantaneous and time averaged performance criteria. Reliable and effective performance of the NOx control systems and related mechanical systems and components are critical in meeting regulatory requirements and environmentally responsible operation.</p>
<p>The fundamental elements that are required to provide the expected reliability and performance requirements for post-combustion NOx control systems specified and supplied through the use of this standard include the following:</p>
<list id="L1" list-type="bullet">
<list-item><label>—</label><p>process definition;</p></list-item>
<list-item><label>—</label><p>process performance expectations;</p></list-item>
<list-item><label>—</label><p>system design selection;</p></list-item>
<list-item><label>—</label><p>mechanical definition of systems and components.</p></list-item></list>
<p>The selected post-combustion NOx control systems and equipment should be capable of the specified performance for a design period for the run length specified in the data sheets without the need for an unplanned outage of the post-combustion NOx treatment control systems and equipment or the associated combustion equipment.</p>
</sec>

Example 4: Acknowledgments and Committee Information

The following example shows the correct styling of Acknowledgments and Committee information.

Info

The two sections do not necessarily need to appear in this order in the document.

Word Sample

Screenshot in Draft View of the Acknowledgements section of the document. The visible paragraph styles from top to bottom are Acknowledgement_Head, Acknowledgement, CommTitle, CommMember, CommAffilImage Added

XML Sample

The acknowledgments (<ack>) is located in the <front> of the XML.

Acknowledgements and Committee Information

Code Block
<ack>
<title>Acknowledgements</title>
<p>This publication was developed by the <italic>Joint Task Force Transformation Initiative</italic> Interagency Working Group with representatives from the Civil, Defense, and Intelligence Communities in an ongoing effort to produce a unified information security framework for the federal government. The National Institute of Standards and Technology wishes to acknowledge and thank the senior leaders from the Departments of Commerce and Defense, the Office of the Director of National Intelligence, the Committee on National Security Systems, and the members of the interagency technical working group whose dedicated efforts contributed significantly to the publication. The senior leaders, interagency working group members, and their organizational affiliations include:</p>
<list list-type="simple" list-content="committee">
<title>U.S. Department of Defense Office of the Director of National Intelligence</title>
<list-item>
<p content-type="committee-member">Teresa M. Takai Adolpho Tarasiuk Jr.</p>
<p content-type="affiliation">Assistant Secretary of Defense for Networks and Assistant Director of National Intelligence and</p>
<p content-type="affiliation">Information Integration/DoD Chief Information Intelligence Community Chief Information</p>
<p content-type="affiliation">Officer (Acting) Officer</p>
</list-item>
<list-item>
<p content-type="committee-member">Gus Guissanie Charlene P. Leubecker</p>
<p content-type="affiliation">Deputy Assistant Secretary of Defense (Acting) Deputy Intelligence Community Chief</p>
<p content-type="affiliation">Information Officer</p>
</list-item>
<list-item>
<p content-type="committee-member">Dominic Cussatt Mark J. Morrison</p>
<p content-type="affiliation">Senior Policy Advisor Director, Intelligence Community Information</p>
<p content-type="affiliation">Assurance</p>
</list-item>
<list-item>
<p content-type="committee-member">Barbara Fleming Roger Caslow</p>
<p content-type="affiliation">Senior Policy Advisor Chief, Risk Management and Information</p>
<p content-type="affiliation">Security Programs Division</p>
</list-item>
</list>
</ack>