DOCSLIB.ORG

Μitron4.0 Specification (Ver

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Μitron4.0 Specification (Ver µITRON4.0 Specification Ver. 4.00.00 ITRON Committee, TRON ASSOCIATION Supervised by Ken Sakamura Edited by Hiroaki Takada Copyright (C) 1999, 2002 by TRON ASSOCIATION, JAPAN µITRON4.0 Specification (Ver. 4.00.00) The copyright of this specification document belongs to the ITRON Committee of the TRON Association. The ITRON Committee of the TRON Association grants the permission to copy the whole or a part of this specification document and to redistribute it intact without charge or with a distribution fee. However, when a part of this specification document is redistributed, it must clearly state (1) that it is a part of the µITRON4.0 Specification document, (2) which part it was taken, and (3) the method to obtain the whole specifi- cation document. See Section 6.1 for more information on the conditions for using this specification and this specification document. Any questions regarding this specification and this specification document should be directed to the following: ITRON Committee, TRON Association Katsuta Building 5F 3-39, Mita 1-chome, Minato-ku, Tokyo 108-0073, JAPAN TEL: +81-3-3454-3191 FAX: +81-3-3454-3224 § TRON is the abbreviation of “The Real-time Operating system Nucleus.” § ITRON is the abbreviation of “Industrial TRON.” § µITRON is the abbreviation of “Micro Industrial TRON.” § BTRON is the abbreviation of “Business TRON.” § CTRON is the abbreviation of “Central and Communication TRON.” § TRON, ITRON, µITRON, BTRON, and CTRON do not refer to any specific product or products. µITRON4.0 Specification Ver. 4.00.00 A Word from the Project Leader Fifteen years have passed since the ITRON Sub-Project started as a part of the TRON Project: a real-time operating system specification for embedded equipment control. During this time, there has been a high degree of technological innovation on micro- processors, and the range of applications the ITRON Specifications cover has broad- ened considerably. The range of applications includes industrial usage such as control of robots and manufacturing equipment in factories, and consumer usage such as office automation (OA) and home appliances. The application range has even extended to new areas such as new information and communication tools and advanced digital con- sumer appliances. There is no doubt that the technological advantages of the ITRON Specifications such as real-time response, compactness to maximize usage of system resources, and flexible adaptability in specification has greatly contributed to the steady expansion of the ITRON Specifications adaptable applications. The open architecture policy of the TRON Project has also contributed to achieve a high degree of actual use of the ITRON Specifications. The µITRON4.0 Specification, which is based on the µITRON3.0 Specification, has been developed to reorganize concepts and terms, to improve compatibility and con- formance level, to increase productivity in software development, to allow reuse of application software, and to achieve more portability. The increasing cases where communication and GUI focusing on modern network applications, internet and intranet equipments, and debugging related middleware are used on the ITRON-Specification operating system serves as the background of the µITRON4.0 Specification. This trend created a demand for more rigorous compatibil - ity and higher conformance level. The ITRON Specifications are designed on a con- cept called loose standardization and level for allowing applicability to low-end CPUs with relatively scarce resources. However, strict standardization is required for soft- ware portability purposes. The specification satisfying these two contradictory demands is the µITRON4.0 Specification. The µITRON4.0 Specification maintains the loose standardization, but develops the level concept to introduce a new property called the Standard Profile. The Standard Profile supports strict standardization to facilitate software portability. Profiles other than the Standard Profile is allowed to increase compatibility in each application field. The terms and concepts in the specification have been reorganized, defined, and explained in more details, reducing as much implementation-dependent portion as pos- sible in an effort to achieve completeness of the specification. The µITRON4.0 Specification reflects the rich experience on the ITRON Specifications and meets the actual users’ demands for new applications. Introduction and effective utilization of the µITRON4.0 Specification in many fields including newly created fields and applications is expected. i µITRON4.0 Specification Ver. 4.00.00 June, 1999 Ken Sakamura Project Leader, TRON Project ii µITRON4.0 Specification Ver. 4.00.00 Preface Fifteen years have elapsed since the ITRON Project started in 1984. By the efforts of those involved, the µITRON Specifications have developed into de-facto standards for the real-time kernel for embedded systems. Based on this achievement, sometime around 1996 the ITRON Project started working towards a second phase of standard- ization to expand the specification from real-time kernel to related specifications such as software components. The µITRON4.0 Specification is the result of two years of intensive effort by both the Kernel Specification WG of the Hard Real-Time Support Study Group (from April 1997 to March 1998) and its successor, the Kernel Specification WG of the µITRON4.0 Specification Study Group (from April 1998 to June 1999). The specifica- tion study held by both WGs was proceeded with monthly meetings and discussions through email. Eventually, more than 1,000 emails regarding the discussion of the specification were exchanged. Other standardization activities in the ITRON Project, especially those done by the RTOS Automotive Application Technical Committee and the Device Driver Design Guideline WG of the µITRON4.0 Specification Study Group, produced an important part of the µITRON4.0 Specification. During the second phase of the standardization, a new approach was adopted by the ITRON Project. The ITRON Project opened the discussion of the µITRON4.0 Specifi- cation. In other words, anyone could participate in the discussion regardless of qualifi- cation. This approach was a major factor in enabling many engineers to participate in the project. Prior to this, most of the engineers did not formerly participate in the dis- cussion. The participation of application engineers as well as the participation of ker- nel engineers was very significant in organizing the specification. Another new attempt of the µITRON4.0 Specification is defining the Standard Profile in order to insure the portability of the software. Under conventional loose standard- ization policy, there is no enforced implementation agreement among members. Com- promises are adopted, and it is up to the implementors to choose specific implementation options. However, when defining the Standard Profile specification, standardizing each and every feature of the µITRON Specifications was necessary and this caused many disagreements among the members. Most disagreements were based on the difference between application requirements rather than on the difference between company interests. Nevertheless, members shared a common vision to create a better specification. Through the process outlined above, the µITRON4.0 Specification was completed reflecting variety of ideas from a variety of point of views. I am personally proud of the level of accomplishment of the µITRON4.0 Specification. I believe that this level of accomplishment could not have been achieved by a single man or company. To the readers of the µITRON4.0 Specification, I would like to remark that in the inter- iii µITRON4.0 Specification Ver. 4.00.00 ests of adhering to strictness in the specification, some readability was sacrificed. The previous µITRON Specifications included tutorial-like contents for engineers who are unfamiliar with a real-time operating system. On the other hand, the µITRON4.0 Specification is written seeking strictness rather than easiness in reading in order to secure software portability. Hence, a criticism on a lesser understandability than the previous specifications is considered to be unavoidable. Therefore we would like to work on some complementary documents such as a reference or a guide book for this specification. However, the editor’s responsibility still spans to statements which are unnecessarily difficult to understand. As a roadmap for the ITRON Specifications, the µITRON4.0 Specification Study Group is working on the standardization of the debugging interface and creating guide- lines for device driver designs. The creation of a certification system for the µITRON4.0 Standard Profile is also under consideration in the near future. We are sure that these activities will increase the acceptance of the ITRON Specifications as de-facto real-time operating system standards. Finally, I would like to express my gratitude to those who contributed to the standard- ization of the µITRON4.0 Specification. This includes those who participated in the Kernel Specification WG of the µITRON4.0 Specification Study Group, those involved in the ITRON Project, and those who directly or indirectly supported the process to develop the µITRON4.0 Specification. I would also appreciate your continuous sup- port for the standardization activities of the ITRON Project. June 1999 Hiroaki Takada Secretary of the the µITRON4.0 Spefication Study Group Department of Information and Computer Sciences, Toyohashi University of Technology
Load more

Recommended publications
  • Sistemi Operativi Real-Time Marco Cesati Lezione R13 Sistemi Operativi Real-Time – II Schema Della Lezione
    Sistemi operativi real-time Marco Cesati Lezione R13 Sistemi operativi real-time – II Schema della lezione Caratteristiche comuni VxWorks LynxOS Sistemi embedded e real-time QNX eCos Windows Linux come RTOS 15 gennaio 2013 Marco Cesati Dipartimento di Ingegneria Civile e Ingegneria Informatica Università degli Studi di Roma Tor Vergata SERT’13 R13.1 Sistemi operativi Di cosa parliamo in questa lezione? real-time Marco Cesati In questa lezione descriviamo brevemente alcuni dei più diffusi sistemi operativi real-time Schema della lezione Caratteristiche comuni VxWorks LynxOS 1 Caratteristiche comuni degli RTOS QNX 2 VxWorks eCos 3 LynxOS Windows Linux come RTOS 4 QNX Neutrino 5 eCos 6 Windows Embedded CE 7 Linux come RTOS SERT’13 R13.2 Sistemi operativi Caratteristiche comuni dei principali RTOS real-time Marco Cesati Corrispondenza agli standard: generalmente le API sono proprietarie, ma gli RTOS offrono anche compatibilità (compliancy) o conformità (conformancy) allo standard Real-Time POSIX Modularità e Scalabilità: il kernel ha una dimensione Schema della lezione Caratteristiche comuni (footprint) ridotta e le sue funzionalità sono configurabili VxWorks Dimensione del codice: spesso basati su microkernel LynxOS QNX Velocità e Efficienza: basso overhead per cambi di eCos contesto, latenza delle interruzioni e primitive di Windows sincronizzazione Linux come RTOS Porzioni di codice non interrompibile: generalmente molto corte e di durata predicibile Gestione delle interruzioni “separata”: interrupt handler corto e predicibile, ISR lunga
    [Show full text]
  • Μitron 4.0 Specification (Ver. 4.03.00) TEF024-S001-04.03.00/En July 2010 Copyright © 2010 by T-Engine Forum
    μITRON 4.0 Specification Ver. 4.03.00 TEF024-S001-04.03.00/en July 2010 μITRON 4.0 Specification (Ver. 4.03.00) TEF024-S001-04.03.00/en July 2010 Copyright © 2010 by T-Engine Forum. This “μITRON 4.0 Specification (Ver. 4.03.00)” was originally released by TRON ASSOCIATION which has been integrated into T-Engine Forum since January 2010. The same specification now has been released by T-Engine Forum as its own specification without modification of the content after going through the IPR procedures. T-Engine Forum owns the copyright of this specification. Permission of T-Engine Forum is necessary for copying, republishing, posting on servers, or redistribution to lists of the contents of this specification. The contents written in this specification may be changed without a prior notice for improvement or other reasons in the future. About this specification, please refer to follows; Publisher T-Engine Forum The 28th Kowa Building 2-20-1 Nishi-gotanda Shinagawa-Ward Tokyo 141-0031 Japan TEL：+81-3-5437-0572 FAX：+81-3-5437-2399 E-mail：[email protected] TEF024-S001-04.03.00/en µITRON4.0 Specification Ver. 4.03.00 Supervised by Ken Sakamura Edited and Published by TRON ASSOCIATION µITRON4.0 Specification (Ver. 4.03.00) The copyright of this specification document belongs to TRON Association. TRON Association grants the permission to copy the whole or a part of this specification document and to redistribute it intact without charge or at cost. However, when a part of this specification document is redistributed, it must clearly state (1) that it is a part of the µITRON4.0 Specification document, (2) which part was taken, and (3) the method to obtain the whole specification document.
    [Show full text]
  • 21 Real-Time Operating Systems
    21 Real-Time Operating Systems This section is devoted to real-time operating systems (RTOS) for supporting applica- tions with real-time requirements. In these applications, most real-time requirements are derived form the physics of the environment that is being controlled or monitored and this implies that most real-time systems are embedded computer systems, and that an RTOS has to provide facilities for supporting embedded applications. There are many commercial products that can be categorized as an RTOS, even though there is a wide range of products, from very small real-time kernels for small embedded ap- plications with a memory footprint in the few kilobytes range, to the large multipur- pose systems controlling a very complex real-time system. Despite this broad range of systems, an RTOS always has the property of being able to provide the required level of service with bounded response times. In the past and even today, many real-time applications were built without an oper- ating system. They were usually simple applications with a simple cyclic scheduler and some interrupt driven routines, and with all the I/O drivers written directly by the application developer. However, with the cost and power of computers today, real- time applications are much more complex, and require full concurrency support, ad- vanced scheduling services, networking, advanced memory management, time man- agement, and in some cases even graphical user interfaces and file systems for secon- dary storage. These are the services typically provided by operating systems, and this has made their use more important in real-time systems.
    [Show full text]
  • A Comparative Study: RTOS and Its Application
    International Journal of Computer Trends and Technology (IJCTT) – Volume 20 Number 1 – Feb 2015 A Comparative Study: RTOS and Its Application Gaurav Rai#1, Sachin Kumar *2, 1,2Department of Electronics & Communication Engineering, Amity University Amity University Uttar Pradesh, Lucknow India Abstract— Over past few decades the idea and need of compatible Real time operating systems has emerged as one of the key factors in the development of Real time operating systems, because of the abundance of incompatible real-time operating systems in the market, each targeted towards a specific segment of the industry. There is a need therefore to draw the similarities and differences between these operating systems, so that a real-time system developer can make an intelligent choice for the application at hand. The primary role of an operating system is to manage resources so as to meet the demands of target applications. Traditional timesharing operating systems target application environments that demand fairness and high resource utilization. Real-time applications on the other hand demand timeliness and predictability, the design of a real-time operating system (RTOS) is essentially a balance between Fig1: High-level view of an RTOS, its kernel, and other components found in providing a reasonably rich feature set for application embedded systems. [2] development and deployment and, not sacrificing predictability and timeliness. This paper briefly discusses and describes various This paper briefly discusses and describes various features features of XENOMAI and RTAI in relation to compatibility, of XENOMAI and RTAI in relation to compatibility, features, features, multitasking and resource management. multitasking and resource management.
    [Show full text]
  • V850 Series Development Environment Pamphlet
    To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.com April 1st, 2010 Renesas Electronics Corporation Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry. Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
    [Show full text]
  • Compact, Low-Cost, but Real-Time Distributed Computing for Computer Augmented Environments
    Compact, Low-Cost, but Real-Time Distributed Computing for Computer Augmented Environments Hiroaki Takada and Ken Sakamura Department of Information Science, Faculty of Science, University of Tokyo 7-3-1, Hongo, Bunkyo-ku, Tokyo 113, Japan Abstract We have been conducting a research and development project, called the TRON Project, for realizingthe computer augmented environments. The final goal of the project is to realize highly functionally distributed systems (HFDS) in which every kind of objects around our daily life are augmented with embedded computers, be connected with networks, and cooperate each other to provide better living environments for human beings. One of the key technologies towards HFDS is the realization methods of compact and low-cost distributed computing systems with dependability and real-time property. In this paper, the overview of the TRON Project are introduced and various research and development activities for realizing HFDS, especially the subprojects on a standard real- time kernel specification for small-scale embedded systems Figure 1: Computerized Living Environment called ITRON and on a low-cost real-time LAN called "ITRON bus, are described. We also describe the future A typical example of “computing everywhere” envi- directions of the project centered on the TRON-concept ronment is the TRON-concept Intelligent House, which Computer Augmented Building, which is a pilot realization was built experimentally in 1989 (Figure 2). The purpose of HFDS and being planned to be built. was to create a testbed for future intensively computerized living spaces. The house with 330 m2 of floor space was 1 Introduction equipped with around 1000 computers, sensors, and actu- ators, which were loosely connected to form a distributed Recent advances in microprocessor technologies have computing system.
    [Show full text]
  • Japanese Semiconductor Industry Conference
    Japanese Semiconductor Industry Conference April 11-12, 1988 Hotel Century Hyatt Tokyo, J^an Dataoyest nn aaxraiaiwof JED IneOun&BradstRetCorpofation 1290 Ridder Plark Drive San Jose, CaUfonm 95131-2398 (408) 437-8000 Telex: 171973 Fax: (408) 437-0292 Sales/Service Offices: UNITED KINGDOM FRANCE EASTERN U.S. Dataquest UK Limited Damquest SARL Dataquest Boston 13th Floor, Ceittiepoint Tour Gallieni 2 1740 Massachusetts Ave. 103 New Oxford Street 36, avenue GaUieni Boxborough, MA 01719 London WCIA IDD 93175 Bagnolet Cedex (617) 264-4373 England France Tel«: 171973 01-379-6257 (1)48 97 31 00 Fax: (617) 263-0696 Tfelex: 266195 Tfelex: 233 263 Fax: 01-240-3653 Fax: (1)48 97 34 00 GERMANY JAPAN KOREA Dataquest GmbH Dataquest Js^an, Ltd. Dataquest Korea Rosenkavalierplatz 17 Tkiyo Ginza Building/2nd Floor 63-1 Chungjung-ro, 3Ka D-8000 Munich 81 7-14-16 Ginza, Chuo-ku Seodaemun-ku ^^fest Germany Tbkyo 104 Japan Seoul, Korea (089)91 10 64 (03)546-3191 (02)392-7273-5 Tfelex: 5218070 Tfelex: 32768 Telex: 27926 Fax: (089)91 21 89 Fax: (03)546-3198 Fax: (02)745-3199 The content of this report represents our interpretation aiKl analysis of information generally avail­ able to the public or released by responsible indivi(bials in the subject companies, but is not guaranteed as to accuracy or comfdeteness. It does not contain material provided to us in confidence t^ our clients. This information is not furnished in connection with a sale or offer to sell securities, or in coimec- tion with the solicitation of an offer to buy securities.
    [Show full text]
  • Constructing a Multi-OS Platform with Minimal Engineering Cost
    Constructing a Multi-OS Platform with Minimal Engineering Cost Yuki Kinebuchi1, Takushi Morita1,KazuoMakijima1, Midori Sugaya2, and Tatsuo Nakajima1 1 Department of Computer Science, Waseda University {yukikine,morita t,makijima,tatsuo}@dcl.info.waseda.ac.jp 2 Dependable Embedded OS Center, Japan Science and Technology Agency (JST) [email protected] Abstract. Constructing an embedded device with a real-time and a general-purpose operating system has attracted attention as a promising approach to let the device balance real-time responsiveness and rich func- tionalities. This paper introduces our methodology for constructing such multi-OS platform with minimal engineering cost by assuming asymmet- ric OS combinations unique to embedded systems. Our methodology con- sists of two parts. One is a simple hypervisor for multiplexing resources to be shared between operating systems. The other is modifying operat- ing systems to allow them to be aware of each other. We constructed an experimental system executing TOPPERS and Linux simultaneously on a hardware equipped with an SH-4A processor. The modification to each operating system kernel limited to a few dozen lines of code and do not introduce any overhead that would compromise real-time responsiveness or system throughput. 1 Introduction Software for embedded systems used to be small and simple, but nowadays it is dominating a large part of the system implementation for providing rich func- tionalities. For instance, modern cell-phones consist of control software (such as a radio transmitter device controller) and rich applications (such as a web browser, a video player, a mailer, etc.). Thus, development with traditional embedded real-time OSes (RTOSes) are unsuited for modern devices.
    [Show full text]
  • T-Engine Design Guidelines Ver
    T-Engine Design Guidelines Ver. 1.00.01 TEF010-S007-01.00.01/en June 2009 TEF010-S007-01.00.01/en 1 T-Engine Design Guidelines / Ver. 1.00.01 CONTENTS ■ Chapter 1 Overview of T-Engine specifications .................................................................................................... 3 1.1. Significance of the T-Engine project and standardization of hardware specifications ................................... 3 1.2. T-Engine system structure............................................................................................................................. 14 ■ Chapter 2 CPU-board design methods ................................................................................................................. 19 2.1. CPU .............................................................................................................................................................. 19 2.2. Memory (flash, RAM).................................................................................................................................. 20 ■ Chapter 3 CPU-board implementation................................................................................................................. 21 ■ Chapter 4 CPU-board interface circuitry design .................................................................................................. 22 4.1. Expansion bus connector design................................................................................................................... 22 4.2. Serial interface.............................................................................................................................................
    [Show full text]
  • COMPUTER ABBREVIATIONS [Copyright: TECHNOART Co
    COMPUTER ABBREVIATIONS [Copyright: TECHNOART Co. Ltd.] References: Magazines: Nikkei Electronics, Nikkei Microdevices, Nikkei Mechanical, etc. News papers: Nikkei Industrial Journal, Dempa Journal White papers: IEEE, IEC, SMPTE, Internet Websites, format specifications, etc. Others: encyclopedias, instruction booklets, catalogues, product spec., etc. ABBREVIATION DERIVATION OF ABBREVIATION 3D DDI 3 Dimensional Device Driver Interface 4GL 4th generation language A3D Aural 3D ABI application binary interface ABS air bearing surface ACSM Application Control State Machine ADB Apple Desktop Bus ADE automatic design engineering AIF application integration feature AOAC always on/always connected APIC Advanced Programmable Interrupt Controller APM Advanced Power Management APNIC Asia Pacific Network Information Center ARC Advanced RISC Computing ATMS Automated Traffic Management Systems AT-UD Unimodem Diagnostics Command AWT Abstract Window Toolkit BAR base address register BBS bulletin board system bcc blind carbon copy BCL bias compensation layer BIPS billion instructions per second BIS boot integrity services BLOB Binary Large Object BML Broadcast Markup Language BNF Backup Naur Form BPR business process reengineering BSDL Boundary Scan Description Language BTL backplane transceiver logic BTRON Business TRON C&C computer and communication CBQ class-based queuing CDA Compound Document Architecture CDB Command Description Block CDC Connected Device Configuration CDDI copper distributed data interface CDF Channel Definition Format CDFF Common
    [Show full text]
  • Ken Sakamura
    2014 TRON Symposium. 30th Anniversary TRON Project 30th Anniversary and Its Future Outlook Embedded systems technology to support the utilization of the IoT big data and future plan for T-Engine Ken Sakamura Professor, Graduate School of Interdisciplinary Studies, The University of Tokyo Director of YRP Ubiquitous Networking Laboratory Chair of T-Engine Forum / uID Center 2014 TRON Symposium. 30th Anniversary ① TRON Project The Real-time Operating system Nucleus The 30th anniversary in 2014 One of the longest lasting projects related to Japanese computing Copyright © 2014 by Ken SAKAMURA 2 2014 TRON Symposium. 30th Anniversary What is TRON? RTOS for system control, and has different basic architecture from Windows and Linux RTOS: Real-Time Operating System Copyright © 2014 by Ken SAKAMURA 3 2014 TRON Symposium. 30th Anniversary TRON RTOS Is Embedded in Many Things “HAYABUSA” (MUSES-C), an asteroid explorer “IKAROS, ” Interplanetary Kite-craft Accelerated by Radiation Of the Sun 4 2014 TRON Symposium. 30th Anniversary TRON Project’s Root Is in Embedded Systems 5 2014 TRON Symposium. 30th Anniversary ② 30 Years of TRON Copyright © 2014 by Ken SAKAMURA 6 2014 TRON Symposium. 30th Anniversary Started in 1984 Copyright © 2014 by Ken SAKAMURA 7 2014 TRON Symposium. 30th Anniversary Historical Background at the Time Copyright © 2014 by Ken SAKAMURA 8 I4004 by Intel (1971) 2014 TRON Symposium. 30th Anniversary Alto by Xerox (1973) 2014 TRON Symposium. 30th Anniversary 2014 TRON Symposium. 30th Anniversary ③ Future Design Copyright © 2014 by Ken SAKAMURA 11 2014 TRON Symposium. 30th Anniversary How the Society Will Change Based on Newly Available Computers? Copyright © 2014 by Ken SAKAMURA 12 2014 TRON Symposium.
    [Show full text]
  • U.S. Government Publishing Office Style Manual
    Style Manual An official guide to the form and style of Federal Government publishing | 2016 Keeping America Informed | OFFICIAL | DIGITAL | SECURE [email protected] Production and Distribution Notes This publication was typeset electronically using Helvetica and Minion Pro typefaces. It was printed using vegetable oil-based ink on recycled paper containing 30% post consumer waste. The GPO Style Manual will be distributed to libraries in the Federal Depository Library Program. To find a depository library near you, please go to the Federal depository library directory at http://catalog.gpo.gov/fdlpdir/public.jsp. The electronic text of this publication is available for public use free of charge at https://www.govinfo.gov/gpo-style-manual. Library of Congress Cataloging-in-Publication Data Names: United States. Government Publishing Office, author. Title: Style manual : an official guide to the form and style of federal government publications / U.S. Government Publishing Office. Other titles: Official guide to the form and style of federal government publications | Also known as: GPO style manual Description: 2016; official U.S. Government edition. | Washington, DC : U.S. Government Publishing Office, 2016. | Includes index. Identifiers: LCCN 2016055634| ISBN 9780160936029 (cloth) | ISBN 0160936020 (cloth) | ISBN 9780160936012 (paper) | ISBN 0160936012 (paper) Subjects: LCSH: Printing—United States—Style manuals. | Printing, Public—United States—Handbooks, manuals, etc. | Publishers and publishing—United States—Handbooks, manuals, etc. | Authorship—Style manuals. | Editing—Handbooks, manuals, etc. Classification: LCC Z253 .U58 2016 | DDC 808/.02—dc23 | SUDOC GP 1.23/4:ST 9/2016 LC record available at https://lccn.loc.gov/2016055634 Use of ISBN Prefix This is the official U.S.
    [Show full text]