DOCSLIB.ORG

Federal Information Processing Standards

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Federal Information Processing Standards abDi-flfl | MflsiioB ootaan ? | T-£5-£& ISO INTERNATIONAL STANDARD 8601 First edition 1988-06-15 INTERNATIONAL ORGANIZATION FOR STANDARDIZATION ORGANISATION INTERNATIONALE DE NORMALISATION MEJKAi'HAPOflHAR OPTAHH3A14HPI HO CTAHflAPTM3AI4MH Data elements and interchange formats — Information interchange — Representation of dates and times Elements de donnges et formats d’Schange — Echange d'information — ReprSsentation de la date et de I'he u re Reference number LSO 8601: 1988 (E> Copyright bg the INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO) Thu Mar 30 13:10:24 1995 .V * ISO 6LQ1 66 4651103 0104337 S INTERNATIONAL STANDARD ISO 8601 : 1988 TECHNICAL CORRIGENDUM 1 Published 1991-05-01 INTERNATIONAL CRGANIZAtlON FOR STANDARDIZATION-MEJKfiyHAPOfiHAH OPrAHH3AltHtt nOCTAHflAPTH3AUHM-OIIGANISATiaN INTERNATIONALS DE NORMALISATION Data elements and interchange formats — Information interchange — Representation of dates and times TECHNICAL CORRIGENDUM 1 EtSments de donndes et formats d‘6c turn go — Echange d'information — Representation de la date et de I'heure RECT/F/CA TIF TECHNIQUE 1 Technical corrigendum 1 to International Standard ISO 8601 : 1988 was prepared by Technical Committee ISO/TC 154, Documents and data elements in administration, commerce and industry. Subclause 5.3 Lines 3 and 4, delete “[01] to [241" and "[01] to [60]" and insort "(003 to [24]" and "1001 to 1591" Subclause 5.3.1.3 Last line, delete "shall be preceded by a zero" and insert "shall be preceded by two zeros in accordance with 4.6" Page 11 Annex B Clause B.1, Calendar week — 15th week of 1985, extended format column, delete "-5W15" and insert "-5-W15" UDC 529 : 003.62 Ref. No. ISO 8601 : 1988/Cor.l : 1991 (E) Descriptors: Information interchange, documentation, data representation, calendar dates. © ISO 1991 Printed in Switzerland Copyright by the INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO) Thu Mar 30 13:10:24 1995 BbOl-Afl | IfiSnoa QQL3BED 3 | ISO 8601 : 1988 (E) fc Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees Each membei body interested in a subject for which a technical committee has been established has the right to be reprosented on that committee. International organizations, govern¬ mental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters ot electrotechnical standardization Draft International Standards adopted by the technical committees are circulated to the member bodies for approval before their acceptance as International Standards by the ISO Council. They are approved in accordance with ISO procedures requiring at least 75 % approval by the member bodies voting. International Standard ISO 8601 was prepared by Technical Committee ISO/TC 154, m Documents and data elements in administration, commerce and industry. It cancels and replaces International Standards ISO 2014 : 1976, ISO 2015 : 1976, ISO 2711 : 1973, ISO 3307 1975 and ISO 4031 : 1978, of which it constitutes a technical revision. Users should note that all International Standards undergo revision from time to time and that any reference made herein to any other International Standard implies its latest edition, unless otherwise stated. © International Organization lor Standardization, 1988 • Printed in Switzerland i! Copyright by the INTERNRTIOHRL ORGANIZATION FOR STANDARDIZATION (ISO) Thu Mar 30 13:10:24 1995 auoi-a& | 4&SLHD3 DObBaei s | ISO 8601 : 1988 (E) Contents Page 0 Introduction. 1 1 Scope and field of application. 1 2 References. 2 3 Terms and definitions. 2 4 Fundamental principles. 3 4.1 Concept. 3 4.2 Common features, uniqueness and combinations . 3 4.3 Characters used in the representations. 3 4.4 Use of separators .. 3 4.5 Truncation . 3 4.6 Leading zero(s). 3 5 Representations. 3 5.1 Explanations. 3 5.2 Dates. 4 5.3 Timeofdsy. 6 5.4 Combinations of date and time of the day representations . 7 5.5 Periods of time.. 8 Annexes A Relationship to ISO 2014, 2015, 2711,3307 and4031 . 10 B Examples of representation of dates, time of the day, combinations of date end time, and periods of time . 11 c Copyright by tho INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO) Thu Nar 30 13:10:24 1995 ■ BbQl-flfl 4551^03 00L3S22 7 INTERNATIONAL STANDARD ISO 8601 : 1988 (E) Data elements and interchange formats — Information interchange — Representation of dates and times 0 Introduction national Standard will not only facilitate interchange across international boundaries, but will also improve the portability of 0.1 Although ISO Recommendations and Standards in this software, and will ease problems of communication within an field have been available since 1971, different forms of numeric organization, as well as between organizations. representation of dates and times have been in common use in different countries. Where such representations are inter¬ 0.6 Several of tho alphabetic and graphic characters used in changed across national boundaries misinterpretation of the the text of this International Standard are common both to the significance of the numerals can occur, resulting in confusion representations specified and to normal typographical presen¬ and other consequential errors or losses. The purpose of this tation. International Standard is to eliminate the risk of misinterpret¬ ation and to avoid the confusion and its consequences. 0.7 To avoid confusion betwenn tho representations and the actual text, its punctuation marks and associated graphic 0.2 This International Standard includes specifications for characters, all the representations are contained in brackets [ ]. the numeric representation of information regarding date and The brackets are nof part of the representation, and should be tima of the day. omitted when implementing the representations. All matter outside the brackets is normal text, and not part of the 0.3 In order to achieve similar formats for the representations representation. In the associated examples, the brackets and of calendar dates, ordinal dates, dates identified by week typographical markings are omitted. number, periods of time, combined date and time of tha day, and differences between local time and Coordinated Universal Time, and fo avoid ambiguities between these representations, 1 Scope and field of application it has been necessary to use, apart from numeric characters, either single alphabetic characters or one or more other graphic This International Standard specifies the representation of characters or a combination of alphabetic and other characters dates in the Gregorian calendar and times and representations in some of the representations. of periods of time. It includes a) calendar dates expressed in terms of year, month and 0.4 The above action has had the benefit of enhancing the day of month; versatility and general applicability of previous International Standards in this field, and provides for the unique represen¬ b) ordinal datos expressed in terms of year and day of tation of any date or time expression or combination of these. year; Each representation can be easily recognized, which is cl dates identified by means of year, week numbers and beneficial when human interpretation is required. day numbers; 0.5 This International Standard retains the most commonly d) tima of the day based upon the 24-hour timekeeping used expressions for date and time of the day and their system; representations from the earlier Internationa! Standards and e) differences between local time and Coordinated Univer¬ provides unique representations for soma new expressions sal Tima (UTC); used in practice. Its application in information interchange, especially between data processing systems and associated f) combination of date and time; equipment will eliminate errors arising from misinterpretation g) periods of time, with or without either a start or end and the costs these generate. The promotion of this Inter¬ date or both. 1 Copyright bg the INTERHfiTIOHflL ORGANIZATION FOR STANDARDIZATION (ISO) Thu Mar 30 13:10:24 1995 flta’l-afl 4^51^03 0Dfe.3fl23 T | ISO 8601 : 1988 <E) 0 This International Standard is applicable whenever dares and 3.8 Gregorian calendar: A calendar in genera! use intro¬ times are included in information interchange. duced in 1582 to correct an error in the Julian calendar. In tho Gregorian calendar common years have 365 days and leap This International Standard does not cover dates and times years 366 days divided into t2 sequential months. where words are used in the representation. 3.9 hour: A period ot time of 60 minutes. This International Standard does not assign any particular meaning or interpretation to any data element that uses 3.10 local time; The clock time in public use locally. representations in accordance with this International Standard. Such meaning will be determined by the context of the appli cation. 3.11 minute: A period of time of 60 seconds. 3.12 month, calendar: A period of time resulting from the 2 References division of a calendar year in twelve sequential periods of time, each with a specific name and containing a specified number of ISO 31-0 : 1981, General principles concerning quantities, units days. In the Gregorian calender, the months of the calendar anti symbols. year, listed in their order of occurrence, are named and contain the number of days as follows: January (31), February (28 In ISO 31-1 : 1978, Quantities and units of space and time common years; 29 in leap years), March (3f), April (30), May (31), June (301, July (31), August (311, September (30), ISO 646: 1983, Information processing — ISO 7 bit coded October (31), November (30), December (31). character set for information interchange. NOTE — In certain applications a month Is regarded as a period of 3 Terms and definitions 30 days For tha purposes ot this International Standard, the following 3.13 period: A duration of time, specified terms and definitions apply. a) as a defined length of time (e.g.
Load more

Recommended publications
  • Rotational Motion (The Dynamics of a Rigid Body)
    University of Nebraska - Lincoln DigitalCommons@University of Nebraska - Lincoln Robert Katz Publications Research Papers in Physics and Astronomy 1-1958 Physics, Chapter 11: Rotational Motion (The Dynamics of a Rigid Body) Henry Semat City College of New York Robert Katz University of Nebraska-Lincoln, [email protected] Follow this and additional works at: https://digitalcommons.unl.edu/physicskatz Part of the Physics Commons Semat, Henry and Katz, Robert, "Physics, Chapter 11: Rotational Motion (The Dynamics of a Rigid Body)" (1958). Robert Katz Publications. 141. https://digitalcommons.unl.edu/physicskatz/141 This Article is brought to you for free and open access by the Research Papers in Physics and Astronomy at DigitalCommons@University of Nebraska - Lincoln. It has been accepted for inclusion in Robert Katz Publications by an authorized administrator of DigitalCommons@University of Nebraska - Lincoln. 11 Rotational Motion (The Dynamics of a Rigid Body) 11-1 Motion about a Fixed Axis The motion of the flywheel of an engine and of a pulley on its axle are examples of an important type of motion of a rigid body, that of the motion of rotation about a fixed axis. Consider the motion of a uniform disk rotat­ ing about a fixed axis passing through its center of gravity C perpendicular to the face of the disk, as shown in Figure 11-1. The motion of this disk may be de­ scribed in terms of the motions of each of its individual particles, but a better way to describe the motion is in terms of the angle through which the disk rotates.
    [Show full text]
  • Government Open Systems Interconnection Profile Users' Guide, Version 2
    NIST Special Publication 500-192 [ Computer Systems Government Open Systems Technology Interconnection Profile Users' U.S. DEPARTMENT OF COMMERCE National Institute of Guide, Version 2 Standards and Technology Tim Boland Nisr NATL INST. OF STAND & TECH R.I.C, A111D3 71D7S1 NIST PUBLICATIONS --QC- 100 .U57 500-192 1991 C.2 NIST Special Publication 500-192 . 0)0 Government Open Systems Interconnection Profile Users' Guide, Version 2 Tim Boland Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 Supersedes NIST Special Publication 500-163 October 1991 U.S. DEPARTMENT OF COMMERCE Robert A. Mosbacher, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director Reports on Computer Systems Technology The National Institute of Standards and Technology (NIST) has a unique responsibility for conriputer systems technology within the Federal government. NIST's Computer Systems Laboratory (CSL) devel- ops standards and guidelines, provides technical assistance, and conducts research for computers and related telecommunications systems to achieve more effective utilization of Federal information technol- ogy resources. CSL's responsibilities include development of technical, management, physical, and ad- ministrative standards and guidelines for the cost-effective security and privacy of sensitive unclassified information processed in Federal computers. CSL assists agencies in developing security plans and in improving computer security awareness training. This Special Publication 500 series reports CSL re- search and guidelines to Federal agencies as well as to organizations in industry, government, and academia. National Institute of Standards and Technology Special Publication 500-192 Natl. Inst. Stand. Technol. Spec. Publ. 500-192, 166 pages (Oct. 1991) CODEN: NSPUE2 U.S.
    [Show full text]
  • Create an Absence/OT Request (Timekeeper)
    Create an Absence/OT Request (Timekeeper) 1. From the Employee Self Service home page, select the drop-down at the top of the screen, and choose Time Administration. a. Follow these instructions to add the Time Administration page/tile to your homepage. 2. Select the Time Administration tile. a. It might take a moment for the Time Administration page to load. Create Absence/OT Request (Timekeeper) | 1 3. Select the Report Employee Time tab. 4. Click on the Employee Selection arrow to make the Employee Selection Criteria section appear. Enter full or partial search items to refine the list of employees, and select the Get Employees button. a. If you do not enter search criteria and simply click Get Employees, all employees will appear in the Search Results section. Create Absence/OT Request (Timekeeper) | 2 5. A list of employees will appear. Select the employee for whom you would like to create an absence or overtime request. 6. The employee’s timesheet will appear. Navigate to the date of the leave request using the Date field or Previous Period/Next Period hyperlinks, and select the refresh [ ] icon. Create Absence/OT Request (Timekeeper) | 3 7. Select the Absence/OT tab on the timesheet. 8. Select the Add Absence Event button. Create Absence/OT Request (Timekeeper) | 4 9. Enter the Start and End Dates for the absence/overtime event. 10. Select the Absence Name drop-down to choose the appropriate option. Create Absence/OT Request (Timekeeper) | 5 11. Select the Details hyperlink. 12. The Absence Event Details screen will pop up. Create Absence/OT Request (Timekeeper) | 6 13.
    [Show full text]
  • So Many Date Formats: Which Should You Use? Kamlesh Patel, Jigar Patel, Dilip Patel, Vaishali Patel Rang Technologies Inc, Piscataway, NJ
    Paper – 2463-2017 So Many Date Formats: Which Should You Use? Kamlesh Patel, Jigar Patel, Dilip Patel, Vaishali Patel Rang Technologies Inc, Piscataway, NJ ABSTRACT Nearly all data is associated with some Date information. In many industries, a SAS® programmer comes across various Date formats in data that can be of numeric or character type. An industry like pharmaceuticals requires that dates be shown in ISO 8601 formats due to industry standards. Many SAS programmers commonly use a limited number of Date formats (like YYMMDD10. or DATE9.) with workarounds using scans or substring SAS functions to process date-related data. Another challenge for a programmer can be the source data, which can include either Date-Time or only Date information. How should a programmer convert these dates to the target format? There are many existing Date formats (like E8601 series, B8601 series, and so on) and informants available to convert the source Date to the required Date efficiently. In addition, there are some useful functions that we can explore for deriving timing-related variables. For these methods to be effective, one can use simple tricks to remember those formats. This poster is targeted to those who have a basic understanding of SAS dates. KEYWORDS SAS, date, time, Date-Time, format, informat, ISO 8601, tips, Basic, Extended, Notation APPLICATIONS: SAS v9.2 INTRODUCTION Date and time concept in SAS is very interesting and can be handled very efficiently if SAS programmers know beyond basics of different SAS Date formats and informats along with many different Date functions. There are various formats available to use as per need in SAS.
    [Show full text]
  • ASN.1. Communication Between Heterogeneous Systems – Errata
    ASN.1. Communication between heterogeneous systems – Errata These errata concern the June 5, 2000 electronic version of the book "ASN.1. Communication between heterogeneous systems", by Olivier Dubuisson (© 2000). (freely available at http://www.oss.com/asn1/resources/books‐whitepapers‐pubs/asn1‐ books.html#dubuisson.) N.B.: The first page number refers to the PDF electronic copy and is the number printed on each page, not the number at the bottom of the Acrobat Reader window. The page number in parentheses refers to the paper copy published by Morgan Kaufmann. Page 9 (page 8 for the paper copy): ‐ last line, replace "(the number 0 low‐weighted byte" with "(the number 0 low‐weighted bit". Page 19 (page 19 for the paper copy): ‐ on the paper copy, second bullet, replace "the Physical Layer marks up..." with "the Data Link Layer marks up...". ‐ on the electronic copy, second bullet, replace "it is down to the Physical Layer to mark up..." with "it is down to the Data Link Layer to mark up...". Page 25 (page 25 for the paper copy): second paragraph, replace "that all the data exchange" with "that all the data exchanged". Page 32 (page 32 for the paper copy): last paragraph, replace "The order number has at least 12 digits" with "The order number has always 12 digits". Page 34 (page 34 for the paper copy): first paragraph, replace "it will be computed again since..." with "it will be computed again because...". Page 37 for the electronic copy only: in the definition of Quantity, replace "unites" with "units". Page 104 (page 104 for the paper copy): ‐ in rule <34>, delete ", digits"; ‐ at the end of section 8.3.2, add the following paragraph: Symbols such as "{", "[", "[[", etc, are also lexical tokens of the ASN.1 notation.
    [Show full text]
  • Understanding JSON Schema Release 2020-12
    Understanding JSON Schema Release 2020-12 Michael Droettboom, et al Space Telescope Science Institute Sep 14, 2021 Contents 1 Conventions used in this book3 1.1 Language-specific notes.........................................3 1.2 Draft-specific notes............................................4 1.3 Examples.................................................4 2 What is a schema? 7 3 The basics 11 3.1 Hello, World!............................................... 11 3.2 The type keyword............................................ 12 3.3 Declaring a JSON Schema........................................ 13 3.4 Declaring a unique identifier....................................... 13 4 JSON Schema Reference 15 4.1 Type-specific keywords......................................... 15 4.2 string................................................... 17 4.2.1 Length.............................................. 19 4.2.2 Regular Expressions...................................... 19 4.2.3 Format.............................................. 20 4.3 Regular Expressions........................................... 22 4.3.1 Example............................................. 23 4.4 Numeric types.............................................. 23 4.4.1 integer.............................................. 24 4.4.2 number............................................. 25 4.4.3 Multiples............................................ 26 4.4.4 Range.............................................. 26 4.5 object................................................... 29 4.5.1 Properties...........................................
    [Show full text]
  • Europe Co P Er Anu Ctu Ers Associ On
    EUROPE CO P ER ANU CTU ERS ASSOCI ON l June 1986 Free copies of this document are available from EC:\lA, European Computer :\Iannfadnrers Association I H Rue dn Hhi'me 1201 Geneva (Switzerland) BRIEF HISTORY The first version of the language BASIC, acronym for Beginner 1 s All-purpose Symbolic Instruction Code, was produced in June 1965 at the Dartmouth Col lege in the USA. In January 1978, ECMA published a Standard for Minimal BASIC, ECMA-55, prepared in coopera­ tion with ANSI X3J2 and fully compatible with the corresponding ANSI standard . This Stan­ dard ECMA-55 served as a basis for the ISO Standard on Minimal BASIC. With the continuation of the work, a draft Standard for full BASIC was agreed by ANSI X3J2 , EWICS TC2 and ECMA/TC21 in January 1985 . This draft is composed of a mandatory Core module and five optional modules . Starting from this draft, ECMA/TC21 prepared a Standard for fully defined subsets of the language . These subsets , called ECMA BASIC-! and ECMA BASIC-2, are designed for business applications , requiring extended file facilities . ECMA BASIC-1 has no exception handling facilities and a reduced set of file operations . In addition, all the keywords in ECMA BASIC-1 are reserved words, reducing the comp lexity of the interpreter or compiler needed . ECMA BASIC-2 provides full exception handling capabilities , full file operations and fixed decimal capabilities . The set of reserved words is minimal . Both subsets provide the full flow control capabilities provided in the ANSI standard . An additional module (ECMA GRAPHICS) provides a minimum of graphic capabilities and can be used with either subset .
    [Show full text]
  • Welcome to Random Moment Time Survey (RMTS) for School-Based Medi-Cal Administrative Activities (SMAA)
    Welcome to Random Moment Time Survey (RMTS) for School-Based Medi-Cal Administrative Activities (SMAA) 2018-2019 Quarter 4 (April – June 2019) Your program administrator(s) has selected you to be a Time Survey Participant (TSP) in the SMAA program. Due to the random nature of the RMTS methodology there is a possibility that you may or may not receive one or more moments in a given quarter. If selected, you will receive your first email notification 5 student attendance days prior to the moment and another email 1 hour prior to the moment. Once each random moment occurs, you will have 5 student attendance days to respond to three simple questions: 1. Who were you with? • DO NOT use proper names, use job title or category 2. What were you doing? • Be specific, detailed and precise for your one minute moment • Do not use abbreviations or acronyms 3. Why were you performing this activity? • Again be specific. This part of the response makes clear to an outside reviewer the purpose of your activity for the moment, and why you did it. Things to Remember: . A response from you is required whether or not you are performing SMAA. Check your email regularly. Notification of pending random moments will be made via email from [email protected] Please ‘white-list’ this email address. You do not need a user log-in or password. Time study notification email contains a unique link to access the system to record your response. The unique link is locked until your moment has passed. Links can be accessed on any computer or smartphone with web capabilities.
    [Show full text]
  • Array Databases: Concepts, Standards, Implementations
    Baumann et al. J Big Data (2021) 8:28 https://doi.org/10.1186/s40537-020-00399-2 SURVEY PAPER Open Access Array databases: concepts, standards, implementations Peter Baumann , Dimitar Misev, Vlad Merticariu and Bang Pham Huu* *Correspondence: b. Abstract phamhuu@jacobs-university. Multi-dimensional arrays (also known as raster data or gridded data) play a key role in de Large-Scale Scientifc many, if not all science and engineering domains where they typically represent spatio- Information Systems temporal sensor, image, simulation output, or statistics “datacubes”. As classic database Research Group, Jacobs technology does not support arrays adequately, such data today are maintained University, Bremen, Germany mostly in silo solutions, with architectures that tend to erode and not keep up with the increasing requirements on performance and service quality. Array Database systems attempt to close this gap by providing declarative query support for fexible ad-hoc analytics on large n-D arrays, similar to what SQL ofers on set-oriented data, XQuery on hierarchical data, and SPARQL and CIPHER on graph data. Today, Petascale Array Database installations exist, employing massive parallelism and distributed processing. Hence, questions arise about technology and standards available, usability, and overall maturity. Several papers have compared models and formalisms, and benchmarks have been undertaken as well, typically comparing two systems against each other. While each of these represent valuable research to the best of our knowledge there is no comprehensive survey combining model, query language, architecture, and practical usability, and performance aspects. The size of this comparison diferentiates our study as well with 19 systems compared, four benchmarked to an extent and depth clearly exceeding previous papers in the feld; for example, subsetting tests were designed in a way that systems cannot be tuned to specifcally these queries.
    [Show full text]
  • Advanced Sql Programming Third Edition
    JOE CELKO’S SQL FOR SMARTIES: ADVANCED SQL PROGRAMMING THIRD EDITION The Morgan Kaufmann Series in Data Management Systems Series Editor: Jim Gray, Microsoft Research • Joe Celko’s SQL for Smarties: Advanced SQL Programming, Third Edition, Joe Celko • Moving Objects Databases, Ralf Güting and Markus Schneider • Foundations of Multidimensional and Metric Data Structures, Hanan Samet • Joe Celko’s SQL Programming Style, Joe Celko • Data Mining, Second Edition: Concepts and Techniques, Ian Witten and Eibe Frank • Fuzzy Modeling and Genetic Algorithms for Data Mining and Exploration, Earl Cox • Data Modeling Essentials, Third Edition, Graeme C. Simsion and Graham C. Witt • Location-Based Services, Jochen Schiller and Agnès Voisard • Database Modeling with Microsft® Visio for Enterprise Architects, Terry Halpin, Ken Evans, Patrick Hallock, Bill Maclean • Designing Data-Intensive Web Applications, Stephano Ceri, Piero Fraternali, Aldo Bongio, Marco Brambilla, Sara Comai, and Maristella Matera • Mining the Web: Discovering Knowledge from Hypertext Data, Soumen Chakrabarti • Advanced SQL: 1999—Understanding Object-Relational and Other Advanced Features, Jim Melton • Database Tuning: Principles, Experiments, and Troubleshooting Techniques, Dennis Shasha and Philippe Bonnet • SQL:1999—Understanding Relational Language Components, Jim Melton and Alan R. Simon • Information Visualization in Data Mining and Knowledge Discovery, Edited by Usama Fayyad, Georges G. Grinstein, and Andreas Wierse • Transactional Information Systems: Theory, Algorithms,
    [Show full text]
  • Date and Time Terms and Definitions
    Date and Time Terms and Definitions Date and Time Terms and Definitions Brooks Harris Version 35 2016-05-17 Introduction Many documents describing terms and definitions, sometimes referred to as “vocabulary” or “dictionary”, address the topics of timekeeping. This document collects terms from many sources to help unify terminology and to provide a single reference document that can be cited by documents related to date and time. The basic timekeeping definitions are drawn from ISO 8601, its underlying IEC specifications, the BIPM Brochure (The International System of Units (SI)) and BIPM International vocabulary of metrology (VIM). Especially important are the rules and formulas regarding TAI, UTC, and “civil”, or “local”, time. The international standards that describe these fundamental time scales, the rules and procedures of their maintenance, and methods of application are scattered amongst many documents from several standards bodies using various lexicon. This dispersion makes it difficult to arrive at a clear understanding of the underlying principles and application to interoperable implementations. This document collects and consolidates definitions and descriptions from BIPM, IERS, and ITU-R to clarify implementation. There remain unresolved issues in the art and science of timekeeping, especially regarding “time zones” and the politically driven topic of “local time”. This document does not attempt to resolve those dilemmas but describes the terminology and the current state of the art (at the time of publication) to help guide
    [Show full text]
  • Kyoto Convention
    KYOTO CONVENTION GENERAL ANNEX GUIDELINES Chapter 7 APPLICATION OF INFORMATION AND COMMUNICATION TECHNOLOGY WORLD CUSTOMS ORGANIZATION Version 7 March 2014 Kyoto Convention – General Annex – Chapter 7 Guidelines on Application of Information and Communication Technology “Copyright © 2014 World Customs Organization All rights reserved. Requests and inquiries concerning translation, reproduction and adaptation rights should be addressed to [email protected]”. 2. Kyoto Convention – General Annex – Chapter 7 Guidelines on Application of Information and Communication Technology Table of Contents TABLE OF CONTENTS ...................................................................................................................................... 3 1. MANAGEMENT SUMMARY .................................................................................................................... 8 1.1. PURPOSE ....................................................................................................................................................... 8 1.2. THE STRATEGIC ROLE OF ICT....................................................................................................................... 8 1.3. FUTURE TRENDS ......................................................................................................................................... 12 1.4. SCOPE ......................................................................................................................................................... 15 1.5. CROSS REFERENCE
    [Show full text]