DOCSLIB.ORG

Information Technology — General-Purpose Datatypes (GPD)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Information Technology — General-Purpose Datatypes (GPD) © ISO 2005 – All rights reserved Reference number of working document: ISO/IEC JTC1 SC22 WG11 N0495 Date: 2005-01-11 Reference number of document: ISO/IEC FCD 11404 (revision) Committee identification: ISO/IEC JTC1 SC22 WG11 SC22 Secretariat: US Information technology — General-Purpose Datatypes (GPD) Warning This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard. Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. Document type: International standard Document subtype: if applicable Document stage: (30) Committee (FCD) Document language: E ISO/IEC FCD 11404 (revision) Copyright notice This ISO document is a working draft or committee draft and is copyright-protected by ISO. While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO, neither this document nor any extract from it may be reproduced, stored or transmitted in any form for any other purpose without prior written permission from ISO. Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO’s member body in the country of the requester: ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. +41 22 749 01 11 Fax +41 22 749 09 47 E-mail [email protected] Web www.iso.org Reproduction for sales purposes may be subject to royalty payments or a licensing agreement. Violators may be prosecuted. ii © ISO 2005 – All rights reserved ISO/IEC FCD 11404 (revision) Contents Page Foreword ............................................................................................................................................................ix Introduction.........................................................................................................................................................x 1 Scope......................................................................................................................................................1 2 Normative references............................................................................................................................2 3 Terms and definitions ...........................................................................................................................2 4 Conformance .........................................................................................................................................8 4.1 Direct conformance...............................................................................................................................8 4.2 Indirect conformance............................................................................................................................9 4.3 Conformance of a mapping standard..................................................................................................9 4.4 GPD program text conformance ........................................................................................................10 5 Conventions used in this International Standard ............................................................................10 5.1 Formal syntax ......................................................................................................................................10 5.2 Text conventions.................................................................................................................................11 6 Fundamental notions ..........................................................................................................................11 6.1 Datatype ...............................................................................................................................................11 6.2 Value space..........................................................................................................................................12 6.3 Datatype properties.............................................................................................................................12 6.3.1 Equality.................................................................................................................................................13 6.3.2 Order.....................................................................................................................................................13 6.3.3 Bound ...................................................................................................................................................14 6.3.4 Cardinality ............................................................................................................................................14 6.3.5 Exact and approximate .......................................................................................................................14 6.3.6 Numeric ................................................................................................................................................15 6.4 Primitive and non-primitive datatypes ..............................................................................................15 6.5 Datatype generator..............................................................................................................................15 6.6 Characterizing operations ..................................................................................................................16 6.7 Datatype families .................................................................................................................................17 6.8 Aggregate datatypes...........................................................................................................................17 6.8.1 Homogeneity........................................................................................................................................17 6.8.2 Size........................................................................................................................................................18 6.8.3 Uniqueness ..........................................................................................................................................18 6.8.4 Aggregate-imposed identifier uniqueness .......................................................................................18 6.8.5 Aggregate-imposed ordering .............................................................................................................18 6.8.6 Access method ....................................................................................................................................18 6.8.7 Recursive structure.............................................................................................................................19 6.8.8 Structured and unstructured..............................................................................................................19 6.8.9 Mandatory and optional components ...............................................................................................20 6.9 Provisions associated with datatypes ..............................................................................................20 7 Elements of the Datatype Specification Language..........................................................................22 7.1 IDN character-set.................................................................................................................................22 7.2 Whitespace...........................................................................................................................................23 7.3 Lexical objects.....................................................................................................................................24 7.3.1 Identifiers .............................................................................................................................................24 7.3.2 Digit-string ...........................................................................................................................................25 © ISO 2005 – All rights reserved iii ISO/IEC FCD 11404 (revision) 7.3.3 Character-literal and string-literal......................................................................................................25 7.3.4 Keywords .............................................................................................................................................25 7.4 Annotations..........................................................................................................................................26 7.5 Values ...................................................................................................................................................26 7.5.1 Independent values.............................................................................................................................27 7.5.2 Dependent values................................................................................................................................28 7.6 GPD program text................................................................................................................................29
Load more

Recommended publications
  • List of Aleph Tables
    List of Aleph Tables Version 22 CONFIDENTIAL INFORMATION The information herein is the property of Ex Libris Ltd. or its affiliates and any misuse or abuse will result in economic loss. DO NOT COPY UNLESS YOU HAVE BEEN GIVEN SPECIFIC WRITTEN AUTHORIZATION FROM EX LIBRIS LTD. This document is provided for limited and restricted purposes in accordance with a binding contract with Ex Libris Ltd. or an affiliate. The information herein includes trade secrets and is confidential. DISCLAIMER The information in this document will be subject to periodic change and updating. Please confirm that you have the most current documentation. There are no warranties of any kind, express or implied, provided in this documentation, other than those expressly agreed upon in the applicable Ex Libris contract. This information is provided AS IS. Unless otherwise agreed, Ex Libris shall not be liable for any damages for use of this document, including, without limitation, consequential, punitive, indirect or direct damages. Any references in this document to third-party material (including third-party Web sites) are provided for convenience only and do not in any manner serve as an endorsement of that third-party material or those Web sites. The third-party materials are not part of the materials for this Ex Libris product and Ex Libris has no liability for such materials. TRADEMARKS "Ex Libris," the Ex Libris bridge , Primo, Aleph, Alephino, Voyager, SFX, MetaLib, Verde, DigiTool, Preservation, URM, Voyager, ENCompass, Endeavor eZConnect, WebVoyage, Citation Server, LinkFinder and LinkFinder Plus, and other marks are trademarks or registered trademarks of Ex Libris Ltd.
    [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]
  • Evitalia NORMAS ISO En El Marco De La Complejidad
    No. 7 Revitalia NORMAS ISO en el marco de la complejidad ESTEQUIOMETRIA de las relaciones humanas FRACTALIDAD en los sistemas biológicos Dirección postal Calle 82 # 102 - 79 Bogotá - Colombia Revista Revitalia Publicación trimestral Contacto [email protected] Web http://revitalia.biogestion.com.co Volumen 2 / Número 7 / Noviembre-Enero de 2021 ISSN: 2711-4635 Editor líder: Juan Pablo Ramírez Galvis. Consultor en Biogestión, NBIC y Gerencia Ambiental/de la Calidad. Globuss Biogestión [email protected] ORCID: 0000-0002-1947-5589 Par evaluador: Jhon Eyber Pazos Alonso Experto en nanotecnología, biosensores y caracterización por AFM. Universidad Central / Clúster NBIC [email protected] ORCID: 0000-0002-5608-1597 Contenido en este número Editorial p. 3 Estequiometría de las relaciones humanas pp. 5-13 Catálogo de las normas ISO en el marco de la complejidad pp. 15-28 Fractalidad en los sistemas biológicos pp. 30-37 Licencia Creative Commons CC BY-NC-ND 4.0 2 Editorial: “En armonía con lo ancestral” Juan Pablo Ramírez Galvis. Consultor en Biogestión, NBIC y Gerencia Ambiental/de la Calidad. [email protected] ORCID: 0000-0002-1947-5589 La dicotomía entre ciencia y religión proviene de la edad media, en la cual, los aspectos espirituales no podían explicarse desde el método científico, y a su vez, la matematización mecánica del universo era el único argumento que convencía a los investigadores. Sin embargo, más atrás en la línea del tiempo, los egipcios, sumerios, chinos, etc., unificaban las teorías metafísicas con las ciencias básicas para dar cuenta de los fenómenos en todas las escalas desde lo micro hasta lo macro.
    [Show full text]
  • Descriptive Metadata Guidelines for RLG Cultural Materials I Many Thanks Also to These Individuals Who Reviewed the Final Draft of the Document
    ������������������������������� �������������������������� �������� ����������������������������������� ��������������������������������� ��������������������������������������� ���������������������������������������������������� ������������������������������������������������� � ���������������������������������������������� ������������������������������������������������ ����������������������������������������������������������� ������������������������������������������������������� ���������������������������������������������������� �� ���������������������������������������������� ������������������������������������������� �������������������� ������������������� ���������������������������� ��� ���������������������������������������� ����������� ACKNOWLEDGMENTS Many thanks to the members of the RLG Cultural Materials Alliance—Description Advisory Group for their participation in developing these guidelines: Ardie Bausenbach Library of Congress Karim Boughida Getty Research Institute Terry Catapano Columbia University Mary W. Elings Bancroft Library University of California, Berkeley Michael Fox Minnesota Historical Society Richard Rinehart Berkeley Art Museum & Pacific Film Archive University of California, Berkeley Elizabeth Shaw Aziza Technology Associates, LLC Neil Thomson Natural History Museum (UK) Layna White San Francisco Museum of Modern Art Günter Waibel RLG staff liaison Thanks also to RLG staff: Joan Aliprand Arnold Arcolio Ricky Erway Fae Hamilton Descriptive Metadata Guidelines for RLG Cultural Materials i Many
    [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]
  • 2903 Date: 2005-08-22
    ISO/IEC JTC 1/SC 2/WG 2 N2903 DATE: 2005-08-22 ISO/IEC JTC 1/SC 2/WG 2 Universal Multiple-Octet Coded Character Set (UCS) - ISO/IEC 10646 Secretariat: ANSI DOC TYPE: Meeting Minutes TITLE: Unconfirmed minutes of WG 2 meeting 46 Jinyan Hotel, Xiamen, Fujian Province, China; 2005-01-24/28 SOURCE: V.S. Umamaheswaran, Recording Secretary, and Mike Ksar, Convener PROJECT: JTC 1.02.18 – ISO/IEC 10646 STATUS: SC 2/WG 2 participants are requested to review the attached unconfirmed minutes, act on appropriate noted action items, and to send any comments or corrections to the convener as soon as possible but no later than 2005-09-05. ACTION ID: ACT DUE DATE: 2005-09-05 DISTRIBUTION: SC 2/WG 2 members and Liaison organizations MEDIUM: Acrobat PDF file NO. OF PAGES: 67 (including cover sheet) Mike Ksar Convener – ISO/IEC/JTC 1/SC 2/WG 2 Microsoft Corporation Phone: +1 425 707-6973 One Microsoft Way Fax: +1 425 936-7329 Bldg 24/2217 email: [email protected] Redmond, WA 98052-6399 or [email protected] Unconfirmed Meeting Minutes ISO/IEC JTC1/SC2/WG2 Meeting 46 Page 1 of 67 N2903 Jinyan Hotel, Xiamen, Fujian Province, China; 2005-01-24/28 2005-08-22 ISO International Organization for Standardization Organisation Internationale de Normalisation ISO/IEC JTC 1/SC 2/WG 2 Universal Multiple-Octet Coded Character Set (UCS) ISO/IEC JTC 1/SC 2/WG 2 N2903 Date: 2005-08-22 Title: Unconfirmed minutes of WG 2 meeting 46 Jinyan Hotel, Xiamen, Fujian Province, China; 2005-01-24/28 Source: V.S.
    [Show full text]
  • International Standard
    International Standard INTERNATIONAL ORGANIZATION FOR STANDARDIZATION’ME~YHAPO~HAR OPrAHM3ALMfl l-l0 CTAHC\APTH3ALM@ORGANISATION INTERNATIONALE DE NORMALISATION Extension of the Latin alphabet coded Character set for bibliographic information interchange Extension du jeu de caractkres latins Codes emplo yk pour l’khange d’information bibliographique Second edition - 1983-11-01iT eh STANDARD PREVIEW (standards.iteh.ai) ISO 5426:1983 https://standards.iteh.ai/catalog/standards/sist/0f2b9bea-a782-4ed0-9a42- eb77e52da752/iso-5426-1983 UDC 003.344 : 025.3 Ref. No. ISO 5426-1983 (E) Descriptors: documentation, data processing, information interchange, bibliographic records, Character Sets, Latin characters. Price based on 6 pages Foreword ISO (the International Organization for Standardization) is a worldwide federation of national Standards bodies (ISO member bedies). The work of developing Inter- national Standards is carried out through ISO technical committees. Every member body interested in a subject for which a technical committee has been authorized has the right to be represented on that committee. International organizations, govern- mental and non-governmental, in liaison with ISO, also take part in the work. 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. iTeh STANDARD PREVIEW International Standard ISO 5426 was developed by Technical Committee ISO/TC 46, Documen ta tion . (standards.iteh.ai) This second edition was submitted directly to the ISO Council,ISO 5in42 6accordance:1983 with clause 6.11.2 of part 1 of the Directiveshttps:/ /stforan dtheard stechnical.iteh.ai/c atworkalog /stofa ndISO.ard s/lts iscancelst/0f2b9 bandea- a782-4ed0-9a42- replaces the first edition (i.e.
    [Show full text]
  • ISO/IEC JTC1/SC2/WG2 N 2005 Date: 1999-05-29
    ISO INTERNATIONAL ORGANIZATION FOR STANDARDIZATION ORGANISATION INTERNATIONALE DE NORMALISATION --------------------------------------------------------------------------------------- ISO/IEC JTC1/SC2/WG2 Universal Multiple-Octet Coded Character Set (UCS) -------------------------------------------------------------------------------- ISO/IEC JTC1/SC2/WG2 N 2005 Date: 1999-05-29 TITLE: ISO/IEC 10646-1 Second Edition text, Draft 2 SOURCE: Bruce Paterson, project editor STATUS: Working paper of JTC1/SC2/WG2 ACTION: For review and comment by WG2 DISTRIBUTION: Members of JTC1/SC2/WG2 1. Scope This paper provides a second draft of the text sections of the Second Edition of ISO/IEC 10646-1. It replaces the previous paper WG2 N 1796 (1998-06-01). This draft text includes: - Clauses 1 to 27 (replacing the previous clauses 1 to 26), - Annexes A to R (replacing the previous Annexes A to T), and is attached here as “Draft 2 for ISO/IEC 10646-1 : 1999” (pages ii & 1 to 77). Published and Draft Amendments up to Amd.31 (Tibetan extended), Technical Corrigenda nos. 1, 2, and 3, and editorial corrigenda approved by WG2 up to 1999-03-15, have been applied to the text. The draft does not include: - character glyph tables and name tables (these will be provided in a separate WG2 document from AFII), - the alphabetically sorted list of character names in Annex E (now Annex G), - markings to show the differences from the previous draft. A separate WG2 paper will give the editorial corrigenda applied to this text since N 1796. The editorial corrigenda are as agreed at WG2 meetings #34 to #36. Editorial corrigenda applicable to the character glyph tables and name tables, as listed in N1796 pages 2 to 5, have already been applied to the draft character tables prepared by AFII.
    [Show full text]
  • Metadata Specifications Cablelabs VOD Content Specification Version 1.1 MD-SP-VOD-CONTENT1.1-C01-120803
    Metadata Specifications CableLabs® VOD Content Specification Version 1.1 MD-SP-VOD-CONTENT1.1-C01-120803 CLOSED Notice This specification is the result of a cooperative effort undertaken at the direction of Cable Television Laboratories, Inc. for the benefit of the cable industry and its customers. This document may contain references to other documents not owned or controlled by CableLabs. Use and understanding of this document may require access to such other documents. Designing, manufacturing, distributing, using, selling, or servicing products, or providing services, based on this document may require intellectual property licenses from third parties for technology referenced in this document. Neither CableLabs nor any member company is responsible to any party for any liability of any nature whatsoever resulting from or arising out of use or reliance upon this document, or any document referenced herein. This document is furnished on an "AS IS" basis and neither CableLabs nor its members provides any representation or warranty, express or implied, regarding the accuracy, completeness, noninfringement, or fitness for a particular purpose of this document, or any document referenced herein. Cable Television Laboratories, Inc. 2002-2012 MD-SP-VOD-CONTENT1.1-C01-120803 Metadata Specifications DISCLAIMER This document is published by Cable Television Laboratories, Inc. ("CableLabs®"). CableLabs reserves the right to revise this document for any reason including, but not limited to, changes in laws, regulations, or standards promulgated by various agencies; technological advances; or changes in equipment design, manufacturing techniques, or operating procedures described, or referred to, herein. CableLabs makes no representation or warranty, express or implied, with respect to the completeness, accuracy, or utility of the document or any information or opinion contained in the report.
    [Show full text]
  • Clean Rooms – Environmental Monitoring
    PhEn-602 Notes # 4 J. Manfredi Pharmaceutical Facility Design Spring 2009 1 Clean Rooms and Controlled Environments Basic definitions Clean Room: A room in which the concentration of airborne particles is controlled and contains one or more clean zones Clean Zone: A defined space in which the concentration of airborne particles is controlled to meet a specified airborne particulate class. Pharmaceutical Facility Design Spring 2009 2 Clean Rooms and Controlled Environments Federal Standard 209E (FS-209E) provides Clean Room Classes Rooms classified based on number of particles > 0.5 micron per cubic foot Class descriptions still in use today. FS 209E is concerned about the following particle sizes, in microns: 0.1, 0.2, 0.3, 0.5, 5.0 Pharmaceutical Facility Design Spring 2009 3 Clean Rooms and Controlled Environments Types of Contaminants Viable Particulates Non-Viable Particulates Pharmaceutical Facility Design Spring 2009 4 Controlled Environments - Types of Contaminants Non-viable Particulates Metal specks, fiber from clothing Obtained from: Equipment, people, tools Viable (micro-organisms) Bacteria Yeast, molds Obtained from: People, outside air, water, equipment, tools, excipients, active ingredients Pharmaceutical Facility Design Spring 2009 5 Clean Rooms and Controlled Environments Sources of particulate generation Internal: Personnel Normally the highest source of contamination Process Air conditioning system Introduction of raw materials Introduction of equipment and materials External Outside air Pharmaceutical Facility Design Spring 2009 6 Clean Rooms and Controlled Environments Some interesting facts: Visible indoor air particles constitute only about 10% of particles present in indoor air. It may be possible to see particles as small as 10 microns It may be possible to see particles as small as 10 microns under favorable conditions.
    [Show full text]
  • Patient Summary Standards Set
    Joint Initiative Council Patient Summary Standards Set GUIDANCE DOCUMENT JANUARY 2018 v1.0 Acknowledgements Whilst work to produce this first draft of the Patient Summary standards set has been coordinated through the JIC, members have been responsible for heading up Task Forces to deliver each of the sections of this Standards Set working with Subject Matter experts from across the world JIC Task Force Leads: • Elizabeth Keller – Use Case and Dataset • Don Newsham – Standards Identification and Analysis • Mike Nusbaum – Conformity Assessment • Stephen Kay – Guidance Coordination: • Jane Millar Task Group Members: • Use Case/Dataset • Tania Snioch – GS1 Global Office (+ Hans Lunenborg and Elisa Zwaneveld, GS1 Netherlands) • Gary Dickinson – CentriHealth, University of California • Charles Gutteridge – Barts Health, London • Ron Parker – Canada Health Infoway • Vince McCauley – Emerging Systems, Telstra Health • Marion Lyver – Kallo Inc • Don Newsham – Standards Identification and Analysis Task Force • Standards Identification and Analysis • Trish Williams – Flinders University, Adelaide • William Goossen – Results4Care • Beatriz de Faria Leao – Hospital Sírio-Libanês, Universidade Federal de São Paulo • Beverly Knight – Canada Health Infoway • Yongsheng Gao – SNOMED International • Ed Hammond – HL7 International • Conformity Assessment • Michelle Knighton – ISAC labs • Lapo Bertini – IHE Europe, IHE Conformity Assessment Steering Group (CaSC) co-chair • Amit Trivedi (ISCA Labs) – US, IHE CaSC co-Chair • Charles Parisot (GE Healthcare),
    [Show full text]