Detalhamento e Comentários sobre as Normas BSI 

     The BSI (British Standard Institute) Definition 

     Year 2000 conformity shall mean that neither performance nor functionality is affected by dates prior to, during and after the year 2000. In particular: 

         Rule #1. No value for current date will cause any interruption in operation. 

         Rule #2. Date-based functionality must behave consistently for dates prior to, during and after 
         year 2000. 

         Rule #3. In all interfaces and data storage, the century in any date must be specified either 
         explicitly or by unambiguous algorithms or inferencing rules. 

         Rule #4. Year 2000 must be recognized as a leap year. 

   AMPLIFICATION OF THE DEFINITION AND RULES 

     1 General Explanation 

         1.1 Problems can arise from some means of representing dates in computer equipment and products and from date-logic embedded in purchased goods or services, as the year 2000 approaches and during and after that year. As a result, equipment or products, including embedded control logic, may fail completely, malfunction or cause data to be corrupted. 

         1.2 To avoid such problems, organizations must check, and modify if necessary, internally produced equipment and products and similarly check externally supplied equipment and products with their suppliers. The purpose of this document is to allow such checks to be made on a basis of common understanding. 

         1.3 Where checks are made with external suppliers, care should be taken to distinguish between claims of conformity and the ability to demonstrate conformity. 

     2 Amplification of the definition 

         2.1 PD2000-1 (all editions) is solely concerned with the performance and functionality of a single version, release or system. It does not address differences in performance or functionality between different versions, releases or systems. 

         2.2 Variations in performance immeasurably small in the context of use do not make a version, release or system non-conformant. 

     3 Amplification of the Rules 

 3.1 Rule 1 

             3.1.1 This rule is sometimes known as general integrity. 

             3.1.2 If this requirement is satisfied, roll-over between all significant time demarcations (e.g. days, months, years, centuries) will be performed correctly. 

             3.1.3 Current date means today's date as known to the equipment or product, i.e. the actual date of operation .. 

 3.2 Rule 2 

             3.2.1 This rule is sometimes known as date integrity. 

             3.2.2 This rule means that all equipment and products must calculate, manipulate and represent dates correctly for the purposes for which they were intended. 

             3.2.3 The meaning of functionality  includes both processes and the results of those processes. 

             3.2.4 If desired, a reference point for date values and calculations may be added by organizations; e.g. as defined by the Gregorian calendar. 

             3.2.5 No equipment or product shall use particular date values for special meanings; e.g. "99" to signify "no end value" or "end of file" or "00" to mean "not applicable" or "beginning of file" unless the values in question lie outside its possible date range. 

 3.3 Rule 3 

             3.3.1 This rule is sometimes known as explicit/implicit century. 

             3.3.2 It covers two general approaches: 

             (a) explicit representation of the year in dates: e.g. by using four digits or by including a century indicator. In this case, a reference may be inserted (e.g. 4-digit years as allowed by ISO 8601:1988) and it may be necessary to allow for exceptions where domain-specific standards (e.g. standards relating to Electronic Data Interchange, Automatic Teller Machines or Bankers Automated Clearing Services) should have precedence. 

             (b) the use of inferencing rules: e.g. two-digit years with a value greater than 50 imply 19xx, those with a value equal to or less than 50 imply 20xx. Rules for century inferencing as a whole must apply to all contexts in which the date is used, although different inferencing rules may apply to different date sets. Where any date element is represented without a century, the correct century shall be unambiguous for all manipulations involving that element. 

 3.4 Rule 4 

             3.4.1 A leap year is defined in ISO 8601:1988 (amended in 1991) as follows: "year, leap: In the Gregorian calendar, a year which has 366 days. A leap year is a year whose number is divisible by four an integral number of times, except that if it is a centennial year it shall be divisible by four hundred an integral number of times." 

             3.4.2 Thus, for example, 2000 is a leap year but 1900 is not. 

     4 General Notes 

         4.1 For Rules 1 and 2 in particular, it is recommended that the allowable ranges for values of current date and dates to be manipulated be documented, recognizing that all systems have some limitation on the valid date ranges. The ranges may relate to one or more of the feasible life-spans of equipment or products or the span of dates required to be represented by the organization's business processes. 

         4.2 Tests for specifically critical dates may also be added (e.g. for leap years, end of year, etc.). Organizations may wish to append additional material in support of local requirements. 

         4.3 Where the term "century" is used, clear distinction should be made between the "value" denoting the century (e.g. 20th) and its representation in dates (e.g. 19xx); similarly, 21st and 20xx.