Matches in DBpedia 2015-10 for { ?s ?p "The Year 2000 problem (also known as the Y2K problem, the Millennium bug, the Y2K bug, or simply Y2K) was a problem for both digital (computer-related) and non-digital documentation and data storage situations that resulted from the practice of truncating a four-digit year to two digits. This made year 2000 indistinguishable from 1900. The former assumption that a twentieth-century date was always understood caused various errors concerning, in particular, the display of dates and the automated ordering of dated records or real-time events.In 1997, the British Standards Institute (BSI) developed a standard, DISC PD2000-1, which defines "Year 2000 Conformity requirements" as four rules: No valid date will cause any interruption in operations. Calculation of durations between, or the sequence of, pairs of dates will be correct whether any dates are in different centuries. In all interfaces and in all storage, the century must be unambiguous, either specified, or calculable by algorithm Year 2000 must be recognized as a leap yearIt identifies two problems that may exist in many computer programs.Firstly, the practice of representing the year with two digits becomes problematic with logical error(s) arising upon "rollover" from x99 to x00. This has caused some date-related processing to operate incorrectly for dates and times on and after 1 January 2000, and on other critical dates which were billed "event horizons". Without corrective action, long-working systems would break down when the "... 97, 98, 99, 00 ..." ascending numbering assumption suddenly became invalid.Secondly, some programmers had misunderstood the Gregorian rule that determines whether years that are exactly divisible by 100 are not leap years, and assumed the year 2000 would not be a leap year. Although 3 out of 4 years divisible by 100 are not leap years, if they are divisible by 400 then they are. Thus the year 2000 was a leap year.Companies and organizations worldwide checked, fixed, and upgraded their computer systems.The number of computer failures that occurred when the clocks rolled over into 2000 in spite of remedial work is not known; amongst other reasons is the reluctance of organisations to report problems."@en }
Showing triples 1 to 1 of
1
with 100 triples per page.
- Year_2000_problem abstract "The Year 2000 problem (also known as the Y2K problem, the Millennium bug, the Y2K bug, or simply Y2K) was a problem for both digital (computer-related) and non-digital documentation and data storage situations that resulted from the practice of truncating a four-digit year to two digits. This made year 2000 indistinguishable from 1900. The former assumption that a twentieth-century date was always understood caused various errors concerning, in particular, the display of dates and the automated ordering of dated records or real-time events.In 1997, the British Standards Institute (BSI) developed a standard, DISC PD2000-1, which defines "Year 2000 Conformity requirements" as four rules: No valid date will cause any interruption in operations. Calculation of durations between, or the sequence of, pairs of dates will be correct whether any dates are in different centuries. In all interfaces and in all storage, the century must be unambiguous, either specified, or calculable by algorithm Year 2000 must be recognized as a leap yearIt identifies two problems that may exist in many computer programs.Firstly, the practice of representing the year with two digits becomes problematic with logical error(s) arising upon "rollover" from x99 to x00. This has caused some date-related processing to operate incorrectly for dates and times on and after 1 January 2000, and on other critical dates which were billed "event horizons". Without corrective action, long-working systems would break down when the "... 97, 98, 99, 00 ..." ascending numbering assumption suddenly became invalid.Secondly, some programmers had misunderstood the Gregorian rule that determines whether years that are exactly divisible by 100 are not leap years, and assumed the year 2000 would not be a leap year. Although 3 out of 4 years divisible by 100 are not leap years, if they are divisible by 400 then they are. Thus the year 2000 was a leap year.Companies and organizations worldwide checked, fixed, and upgraded their computer systems.The number of computer failures that occurred when the clocks rolled over into 2000 in spite of remedial work is not known; amongst other reasons is the reluctance of organisations to report problems.".