1、 INCITS/ISO/IEC 16509:19992010 (ISO/IEC 16509:1999, IDT) Information technology - Year 2000 terminology Reaffirmed as INCITS/ISO/IEC 16509:1999 R2015INCITS/ISO/IEC 16509:19992010 PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be
2、 printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts
3、no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the fi
4、le is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. Adopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard. Date of ANSI
5、 Approval: 11/18/2010 Published by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2010 by Information Technology Industry Council (ITI). All rights reserved. These materials are subject to copyright claims of International Standardization Organization
6、(ISO), International Electrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resale. No part of this publication may be reproduced in any form, including an electronic retrieval system, without the prior written perm
7、ission of ITI. All requests pertaining to this standard should be submitted to ITI, 1101 K Street NW, Suite 610, Washington DC 20005. Printed in the United States of America ii ITIC 2010 All rights reserved The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-
8、5997, USACopyright 1999 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 7 October 1999. Printed in the United States of America.Print:ISBN 0-7381-1803-6 SH94784PDF:ISBN 0-7381-1804-4 SS94784No part of this publication may be reproduced in any form, in an
9、electronic retrieval system or otherwise, without the prior written permission of the publisher.Abstract:This standard provides concepts, definitions, remediation techniques, and other support-ing terms fundamental to a lexicon for Year 2000 terminology. It addresses key topics pertinent tothe devel
10、opment of resolutions to the Year 2000 problem. The core of this standard is the definitionsClause which contains the definition for Year 2000 compliance. Two critical aspects of this definitionare: first, the acknowledgment of the significance of documentation associated with technology,and, second
11、, the recognition that compliance is a two-way street, i.e., the proper exchange of datedata is paramount for technology to remain compliant.Keywords:date exchange, remediation techniques, Year 2000 compliantiiANSI/IEEE 2000.1-1998IEEE Standardsdocuments are developed within the IEEE Societies and t
12、he Standards Coordinat-ing Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of thecommittees serve voluntarily and without compensation. They are not necessarily members of theInstitute. The standards developed within IEEE represent a consensus of the broad expertise o
13、n thesubject within the Institute as well as those activities outside of IEEE that have expressed an inter-est in participating in the development of the standard.Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not implythat there are no other ways to produce, tes
14、t, measure, purchase, market, or provide other goods andservices related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at thetime a standard is approved and issued is subject to change brought about through developments inthe state of the art and comments received from user
15、s of the standard. Every IEEE Standard is sub-jected to review at least every ve years for revision or reafrmation. When a document is morethan ve years old and has not been reafrmed, it is reasonable to conclude that its contents,although still of some value, do not wholly reect the present state o
16、f the art. Users are cautioned tocheck to determine that they have the latest edition of any IEEE Standard.Comments for revision of IEEE Standards are welcome from any interested party, regardless ofmembership afliation with IEEE. Suggestions for changes in documents should be in the form of apropos
17、ed change of text, together with appropriate supporting comments.Interpretations: Occasionally questions may arise regarding the meaning of portions of standards asthey relate to specic applications. When the need for interpretations is brought to the attention ofIEEE, the Institute will initiate ac
18、tion to prepare appropriate responses. Since IEEE Standards rep-resent a consensus of all concerned interests, it is important to ensure that any interpretation hasalso received the concurrence of a balance of interests. For this reason, IEEE and the members of itssocieties and Standards Coordinatin
19、g Committees are not able to provide an instant response tointerpretation requests except in those cases where the matter has previously received formalconsideration. Comments on standards and requests for interpretations should be addressed to:Secretary, IEEE-SA Standards Board445 Hoes LaneP.O. Box
20、 1331Piscataway, NJ 08855-1331USAAuthorization to photocopy portions of any individual standard for internal or personal use isgranted by the Institute of Electrical and Electronics Engineers, Inc., provided that the appropriatefee is paid to Copyright Clearance Center. To arrange for payment of lic
21、ensing fee, please contactCopyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA;(978) 750-8400. Permission to photocopy portions of any individual standard for educational class-room use can also be obtained through the Copyright Clearance Center.Note: Attention is
22、called to the possibility that implementation of this standard mayrequire use of subject matter covered by patent rights. By publication of this standard,no position is taken with respect to the existence or validity of any patent rights inconnection therewith. The IEEE shall not be responsible for
23、identifying patents forwhich a license may be required by an IEEE standard or for conducting inquiries intothe legal validity or scope of those patents that are brought to its attention.ISO/IEC 16509:1999(E)iiiInternational Standard ISO/IEC 16509:1999(E)ISO (the International Organization for Standa
24、rdization) and IEC (the International Electrotechnical Commission)form the specialized system for worldwide standardization. National bodies that are members of ISO or IECparticipate in the development of International Standards through technical committees established by therespective organization
25、to deal with particular fields of technical activity. ISO and IEC technical committeescollaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, inliaison with ISO and IEC, also take part in the work.In the field of information technology, ISO and
26、 IEC have established a joint technical committee, ISO/IEC JTC 1.Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting.Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote.Inter
27、national Standard ISO/IEC 16509 was prepared by Joint Technical Committee ISO/IEC JTC 1, Informationtechnology, Subcommittee SC 22, Programming languages, their environments and system software interfaces.Annexes A to C of this International Standard are for information only.International Organizati
28、on for Standardization/International Electrotechnical CommissionCase postale 56 Gb7 CH-1211 Genve 20 Gb7 SwitzerlandivCopyright 1999 IEEE. All rights reserved.ANSI/IEEE 2000.1-1998This introduction provides background on the rationale used to develop this international standard. Thisinformation is m
29、eant to aid in the understanding and usage of this standard.This international standard addresses the key industry concern over the existence of multiple terms andlexicons that carry varied meanings. IEEE has designed this standard to assist individuals and organiza-tions in their efforts to develop
30、 Year 2000 solutions. Having a base-line set of terms and denitions thatcan serve as a foundation for such efforts is vital.ParticipantsPASC Sponsor Executive CommitteeChair: Lowell G. JohnsonVice-Chair: Joseph GwinnFunctional Chairs: Andrew JoseyJay AshfordCurtis RoysterSecretary: Nick StoughtonAt
31、the time the IEEE Portable Applications Standards Committee revised this standard, the Year 2000 Termi-nology Working Group had the following membership:Kevin Lewis,Technical EditorMichael AisenbergSteve AllenMichael BerensLeonard BrushGeorge CherryCory ClaymonJoseph K. ClemaRobert CohenJohnetta Col
32、bertEldon ColbyDonald CragunJohn DaviesChristina DrukalaAmy Fliegelman-OlliTrutz FoelscheLee GallagherRobert GniewkowskiDebbie GoldbergJoeseph M. GwinnTim HarrisJoAnn HendersonRichard HollemanVincent HungJames D. IsaakPetr JanecekMargaret JedlickaAndrew JoseyYong KimC. W. KleinThomas KoenigCheryl La
33、iRex LintMickey LynnAustin J. MaherRobert MartinRoger MartinRichard McLeanJames MurrayJohn NapierAlan PeltzmanCarolyn PriceBill PritchettBill PutnamLarry SchwartzPhilip SimonsTerrill J. SlocumNick StoughtonRobert SwartzKeith ThurstonJohn TylerRoger TylerRichard VasquezMichael WheatleyLaurence WolfeD
34、ave WongGary YoungCopyright 1999 IEEE. All rights reserved.vThe following persons were on the balloting committee:When the IEEE-SA Standards Board approved this standard on 25 June 1998, it had the followingmembership:Richard J. Holleman,ChairDonald N. Heirman,Vice ChairJudith Gorman,Secretary*Membe
35、r EmeritusNoelle D. HumenickIEEE Standards Project EditorNote that editorial changes were made to the IEEE standard to accomodate concerns raised during the ISO/IEC/JTC 1 balloting process. These are indicated in the text by a change bar (such as shown at the left of thisparagraph.)Ida M. BerchtoldA
36、dam BlockMark BrownJoseph K. ClemaDonald CragunPhilip H. EnslowMichel GienLawrence M. GuntherCharles E. HammonsAndy HarrisonBarry HedquistJim D. IsaakRichard JaenickeJerry L. JohnsonLowell G. JohnsonAndrew JoseyLeon A. KappelmanJudith S. KernerLorraine C. KevraThomas KoenigKenneth C. KungThomas M. K
37、uriharaKevin LewisAustin J. MaherJames W. MooreFinnbarr P. MurphyJohn NapierJames T. OblingerMarc A. PearlAlan PeltzmanRoy ReedFrancois RicheCurtis RoysterAlan RusselMichael D. ShapiroKeith ShillingtonTerrill J. SlocumWilliam R. SmithSandra SwearingenAndrew D. TaitRoger TylerMichael W. VannierDale W
38、. WayThomas WilliamsDarren WolfPaul A. WolfgangJordan S. WoukOren YuenSatish K. AggarwalClyde R. CampJames T. CarloGary R. EngmannHarold E. EpsteinJay Forster*Thomas F. GarrityRuben D. GarzonJames H. GurneyJim D. IsaakLowell G. JohnsonRobert KennellyE. G. Al KienerJoseph L. Koepnger*Stephen R. Lambe
39、rtJim LogothetisDonald C. LoughryL. Bruce McClungLouis-Franois PauRonald C. PetersenGerald H. PetersonJohn B. PoseyGary S. RobinsonHans E. WeinrichDonald W. ZipseviCopyright 1999 IEEE. All rights reserved.Contents1. Overview 11.1 Scope 21.2 Purpose. 21.3 Conformance 32. References 33. Definitions 34
40、. Concepts. 34.1 Valid date interval (also known as compliance date range) 34.2 Time horizon to failure (also known as event horizon) . 44.3 Year 2000 life cycle. 4Annex ATechniques, terms, and special dates. 5Annex BBibliography 8Information technologyYear 2000 terminology1. OverviewThe Year 2000 i
41、ssue appears to be a simple problem that is intuitively understood. However, when examinedclosely, the solutions are varied and complex in nature. The essence of this problem is the representation ofthe year as a two-digit number in hardware and software elements of computer systems and other techno
42、lo-gies. This representation may, for example, cause hardware or software malfunctions to occur when a systemdate or application date crosses the year 2000 boundary (whether that is the actual arrival of the date or fordate processing purposes) or when the system or application must refer to a date
43、that occurs on, before, orafter 1 January 2000. These malfunctions can include the following: Incorrect arithmetic calculation, comparison, sorting, or sequencing resulting in the failure of logical,relational, and set-membership operations; Incorrect recognition of leap year; Conict with values in
44、data elds used for non-date purposes, e.g., no date provided, or neverexpires; and Date data eld overow.The two-digit date may not be the sole cause of these malfunctions. They may also result from poor pro-gramming practices or a lack of full understanding of the Gregorian calendar. The consequence
45、s of thesemalfunctions could range from immediate system failures to more insidious long-term data corruptions.The impact of the Year 2000 problem is potentially signicant to virtually any segment of the global digitalinfrastructure and the economies it supports. Among the environments in which crit
46、ical applications may beaffected by Year 2000 issues are: Bio-medical Telecommunications/transportation Finance/banking Aviation/aerospace National security/law enforcement Other critical infrastructureAs this standard is being prepared, many organizations are in various stages of addressing this pr
47、oblem.Some are just beginning to assess the impact on their own information technology (IT) environments. Others1ISO/IEC 16509: 1999IEEE Std 2000.1-1998 INFORMATION TECHNOLOGY2 Copyright 1999 IEEE. All rights reserved.have already begun to implement solutions. The rising need for solutions has creat
48、ed a market environmentwherein there are a growing number of organizations offering such solutions. These organizations have alsocreated a diverse set of terms. Many of the terms may seem similar, but will actually have multiple meaningswithin differing environments, which brings the potential for c
49、onfusion to what should be an easily under-stood problem.This standard identies common terms, denitions, and related concepts that have broad applicability to thisarea of work. Those presented herein may be applied wholly or in part to t a specic requirement.A lexicon within which the common terms, denitions, and related concepts are understood is vital. The ITindustrys use of the terms dened in this standard will minimize confusion. In additio
