DOCSLIB.ORG

The 2016 SNIA Dictionary

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The 2016 SNIA Dictionary Storage Networking Industry Association (SNIA) SNIA is the globally recognized and trusted authority for storage leadership, standards, and technology expertise. Leading the storage industry by developing and promoting vendor-neutral architectures, standards and educational services that facilitate the efficient management, movement and security of information. The SNIA Dictionary, 18th Edition The SNIA Dictionary contains terms and definitions related to storage and other information technologies, and is the storage networking industry's most comprehensive effort to arrive at a common body of terminology for the technologies it represents. The terms go through a rigorous technical review and approval process by the SNIA Technical Council to assure their accuracy. The SNIA Technical Council is a group of technical experts elected by the members of SNIA to guide SNIA’s technical efforts. Their extensive individual technical backgrounds cover all aspects of storage. The reader should recognize that in this rapidly evolving field, new terminology is constantly being introduced, and common usage is shifting. SNIA regards this dictionary as a living document, to be updated as necessary to reflect a consensus on common usage, and encourages readers to treat it in that spirit. Suggestions for improvement are welcomed at any time and may be sent to [email protected]. SNIA owns the rights to all submitted comments and suggestions. Proposals for new terms or definitions, or modifications to existing ones, should be submitted on the form located at: http://www.snia.org/education/dictionary/submittal Periodically SNIA regional groups translate the SNIA dictionary into local languages. There are versions of the dictionary in Japanese, Portuguese, and Chinese. If you would like to lead a translation project, SNIA would be interested to help support this effort. Please contact [email protected]. SNIA Dictionary | 18th Edition i Terms of Use The SNIA hereby grants permission for individuals to use this glossary for personal use only, and for corporations and other business entities to use this glossary for internal use only (including internal copying, distribution, and display), provided that: Any definition reproduced must be reproduced in its entirety with no alteration, and, any document, printed or electronic, in which material from this glossary (or any portion hereof) is reproduced must acknowledge the SNIA copyright on that material, and must credit the SNIA for granting permission for its reuse. Other than as explicitly provided above, you may not make any commercial use of this glossary, sell any or all of this glossary, or distribute this glossary to third parties. All rights not explicitly granted above are expressly reserved to SNIA. In particular, the provisions above do not grant the rights to make any commercial use of this glossary, sell any or all of this dictionary, or distribute this dictionary to third parties. Permission to use this glossary for purposes other than those enumerated above may be requested by e-mailing [email protected]; please include the identity of the requesting individual and/or company and a brief description of the purpose, nature, and scope of the requested use. Copyright © 2004 - 2017 Storage Networking Industry Association, All Rights Reserved. Last updated July 28, 2017. Definition Format The format for definitions has changed as of the last half of 2008. Terms are now defined as much as possible using the substitution principle, which states that a term's definition should be substitutable for the term itself in a sentence. In the case that more text is required or deemed helpful, it is contained in one or more separate paragraphs after the definition itself. This text is informative in nature, and while intended to be accurate, is not technically part of the definition itself. ii SNIA Dictionary | 18th Edition Deprecated Synonyms In many cases, as technology develops, companies are forced to invent new terminology to describe innovations in their products. As the technology matures and vendors attempt to compete and compare their products with others, one or two terms become the most widely used, yet a number of other terms may remain in some use which are basically synonyms for the widely used terms. This causes confusion in the marketplace. To encourage crispness and uniformity in product descriptions, this dictionary lists synonyms of this type as "Deprecated synonym for xxxx," where xxxx is the term determined to have become canonical in the industry. This is to indicate both the meaning of xxxx and guide the reader toward use of the more canonical term. In cases where a synonym is not deprecated, the SNIA does not endorse the use of one synonym over another. Definitions Taken from Standards Documents The SNIA has a strong interest in keeping definitions harmonized across various industry groups and national and international standards bodies. Towards this end, some definitions, especially those pertaining to Fibre Channel and SCSI terms and technologies, have been quoted from the appropriate version of the INCITS standard. In all such cases, the INCITS standard is authoritative. The SNIA Dictionary may include terms defined in the the following standards and draft standards: INCITS 302-1998, SCSI Parallel Interface - 2 (SPI-2) INCITS 367-2003, SCSI Parallel Interface - 5 (SPI-5) INCITS 405-2005, SCSI Block Commands - 2 (SBC-2) INCITS 431-2007, Serial Attached SCSI - 2.1 (SAS-2.1) INCITS 447-2008, SCSI Architecture Model - 4 (SAM-4) INCITS 448-2008, SCSI Enclosure Services - 2 (SES-2) INCITS 461-2010, Fibre Channel - Switch Fabric-5 (FC-SW-5) INCITS 462-2010, Fibre Channel - Backbone-5 (FC-BB-5) INCITS 466-2011, Fibre Channel - Single-Byte Command Code Sets - 4 (FC-SB-4) INCITS 467-2011, SCSI Stream Commands - 3 (SSC-3) INCITS 470-2011, Fibre Channel - Framing and Signaling - 3 (FC-FS-3) INCITS 475-2011, Fibre Channel - Inter-Fabric Routing (FC-IFR) SNIA Dictionary | 18th Edition iii INCITS 476-2011, SAS Protocol Layer (SPL) INCITS 476/AM1-2012, SAS Protocol Layer Amendment #1 (SPL-AM1) INCITS 477-2011, Fibre Channel – Link Service - 2 (FC-LS-2) INCITS 478/AM1-2014, Serial Attach SCSI - 2.1 Amendment #1 (SAS-2.1-AM1) INCITS 479-2011, Fibre Channel - Physical Interface - 5 (FC-PI-5) INCITS 481-2012, Fibre Channel Protocol for SCSI - 4 (FCP-4) INCITS 484-2012, SCSI Media Changer Commands - 3 (SMC-3) INCITS 497-2013, Automation/Drive Interface – Commands - 3 (ADC-3) INCITS 505-2013, SAS Protocol Layer - 2 (SPL-2) INCITS 509-2014, Fibre Channel - Backbone - 6 (FC-BB-6) INCITS 514-2014, SCSI Block Commands - 3 (SBC-3) INCITS 516-2014, SCSI Stream Commands - 4 (SSC-4) INCITS 519-2014, Serial Attached SCSI - 3 (SAS-3) INCITS 556-201x, Fibre Channel NVMe (FC-NVMe) The SNIA wishes to thank ANSI and INCITS for their cooperation in this matter. Copies of INCITS standards may be purchased at ANSI's online store at http://webstore.ansi.org. iv SNIA Dictionary | 18th Edition Context Hierarchy Most of the terms in this dictionary have meaning primarily in specific sub-contexts of storage networking, such as SCSI or File Systems. The following categories are used to declare the context in which a given definition in this dictionary is held to be valid. No attempt has been made to date to rigorously define these categories, so they remain a guide to understanding, not a formal system. General --Hardware ----Network -------SCSI -------iSCSI -------Fibre Channel -------NVMe -------Infiniband ----Data Communication --Computer System ----Storage System --- Operating System -------Windows --Services Cloud --Management ----Data Management -------Backup -------Data Recovery -------Data Security -------Database -------File System -------Long Term Retention -------Capacity Optimization ----Storage Management --Energy --Standards --Legal The context hierarchy is a work in progress. In part, we are constrained by practice in previous editions of the dictionary. In the above hierarchy representation, context labels indented beneath other context labels represent specializations of the higher-order label concept. Below is an example of how context is indicated: context example [Context] The context is called out in square brackets at the beginning of each definition, as in this example. SNIA Dictionary | 18th Edition v Authors The following SNIA volunteers contributed to this version of the SNIA Dictionary: Carlos Pratt, Chair of Dictionary Team Mark Carlson, Toshiba John Crandall, Brocade Fred Knight, NetApp Bill Martin, Samsung Peter Murray, Virtual Instruments Tom Talpey, Microsoft David Thiel Past contributors include: David Black, EMC Corporation Roger Cummings, Symantec Don Deel, NetApp Eric Hibbard, HDS Leah Schoeb, Intel Steve Wilson, Brocade Alan G. Yoder Thanks also to the many unsung contributors who have submitted suggestions through the online submission portal. vi SNIA Dictionary | 18th Edition # Numbers 3DES [Data Security] Acronym for Triple DES. This algorithm is obsolete. 64B/66B [Data Communication] An algorithm for encoding data for transmission in which each 64-bit data word is converted to a 66-bit transmission character. Each transmission character is prefixed with either binary "01" or binary "10". This, combined with scrambling, gives the signal desirable engineering properties, yet incurs a much lower overhead than the traditional 8b/10b encoding. 8B/10B encoding [Data Communication] An algorithm for encoding data for transmission in which each eight-bit data byte is converted to
Load more

Recommended publications
  • Odata Services Company
    PUBLIC 2021-03-09 OData Services company. All rights reserved. All rights company. affiliate THE BEST RUN 2021 SAP SE or an SAP SE or an SAP SAP 2021 © Content 1 SAP Cloud for Customer OData API..............................................4 2 New Features.............................................................. 13 2.1 What's New in OData API v2 Reference.............................................13 2.2 Add Public Solution Model (PSM) Fields to Standard OData Services........................15 2.3 Transport Custom OData Services with Transport Management............................16 2.4 Compatibility Mode for READ Operations........................................... 16 2.5 Support for User-Friendly IDs in Standard OData Services................................16 2.6 Constant Values to Function Imports...............................................17 3 OData API Reference.........................................................18 3.1 OData API v2 Reference........................................................18 3.2 OData API v1 Reference (Deprecated)..............................................20 Account Contact Relationship.................................................21 Account EntityType........................................................22 Appointment Entity Type....................................................40 BusinessPartner Entity Type..................................................46 CodeList Entity Type....................................................... 47 Contextual CodeList Entity Type...............................................48
    [Show full text]
  • Pyslet Documentation Release 0.6.20160201
    Pyslet Documentation Release 0.6.20160201 Steve Lay February 02, 2016 Contents 1 What’s New? 1 2 Compatibility 7 3 IMS Global Learning Consortium Specifications 13 4 The Open Data Protocol (OData) 101 5 Hypertext Transfer Protocol (RFC2616) 207 6 Other Supporting Standards 247 7 Welcome to Pyslet 357 Python Module Index 359 i ii CHAPTER 1 What’s New? As part of moving towards PEP-8 compliance a number of name changes are being made to methods and class at- tributes with each release. There is a module, pyslet.pep8, which contains a compatibility class for remapping missing class attribute names to their new forms and generating deprecation warnings, run your code with “python -Wd” to force these warnings to appear. As Pyslet makes the transition to Python 3 some of the old names will go away completely. It is still possible that some previously documented names could now fail (module level functions, function arguments, etc.) but I’ve tried to include wrappers or aliases so please raise an issue on Github if you discover a bug caused by the renaming. I’ll restore any missing old-style names to improve backwards compatibility on request. Finally, in some cases you are encouraged to derive classes from those defined by Pyslet and to override default method implementations. If you have done this using old-style names you will have to update your method names to prevent ambiguity. I have added code to automatically detect most problems and force fatal errors at runtime on construction, the error messages should explain which methods need to be renamed.
    [Show full text]
  • ISO/IEC JTC 1 Information Technology
    ISO/IEC JTC 1 Information technology Big data Preliminary Report 2014 Our vision Our process To be the world’s leading provider of high Our standards are developed by experts quality, globally relevant International all over the world who work on a Standards through its members and volunteer or part-time basis. We sell stakeholders. International Standards to recover the costs of organizing this process and Our mission making standards widely available. ISO develops high quality voluntary Please respect our licensing terms and International Standards that facilitate copyright to ensure this system remains international exchange of goods and independent. services, support sustainable and equitable economic growth, promote If you would like to contribute to the innovation and protect health, safety development of ISO standards, please and the environment. contact the ISO Member Body in your country: www.iso.org/iso/home/about/iso_ members.htm This document has been prepared by: Copyright protected document ISO/IEC JTC 1, Information technology All rights reserved. Unless otherwise Cover photo credit: ISO/CS, 2015 be reproduced or utilized otherwise in specified,any form noor partby anyof this means, publication electronic may or mechanical, including photocopy, or posting on the internet or intranet, without prior permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester: © ISO 2015, Published in Switzerland Case postale 56 • CH-1211 Geneva 20 Tel.ISO copyright+41 22
    [Show full text]
  • Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, Proposes
    Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, proposes ○ Geodata on the web in raw form. ○ Raw geodata must be searchable How do you find raw geospatial data ? Data Catalogs Wouldn’t it be nice if… And see.. Searchable Raw Geospatial Data www.georest.org Open Data Protocol “The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today.” www.odata.org ODATA HTTP Atom AtomPUB JSON HTTP://.../vancouver/libraries <feed xmlns=http://www.w3.org/2005/Atom … > <title type="text">libraries</title> <id>http://…/vancouver/libraries(10)</id> <title type="text"></title> <entry> <content type="application/xml"> <m:properties> <d:library_name>Britannia</d:library_name> <d:latitude m:type="Edm.Double">49.2756486</d:latitude> <d:longitude m:type="Edm.Double">-123.0737717</d:longitude> <d:address>1661 Napier St</d:address> </m:properties> …..</entry> <entry>…</entry></feed> HTTP://.../vancouver/libraries ?$format=JSON {"d":[{"library_name":"Britannia","latitude":" 49.2756486","longitude":"- 123.0737717","address":"1661 Napier St"} , {..}] } HTTP Header accept: application/json OData Example Live OData Service from Vancouver OData Producers SharePoint 2010, SQL Azure, IBM WebSphere, … GeoREST OData Live Services Netflix, Open Goverment Data Initiative (OGDI), Stack Overflow, Vancouver, Edmonton, … City of Nanaimo OData Consumers Browsers, Odata Explorer, Excel 2010,…
    [Show full text]
  • SAP Analytics Cloud, Analytics Designer Developer Handbook
    SAP Analytics Cloud, analytics designer Developer Handbook Document Version: 5.1 – 2020-04-06 Table of Contents 1 Table of Contents Table of Contents ......................................................................................................................... 1 Figures .......................................................................................................................................... 7 1 About Analytics Designer .............................................................................................10 1.1 What Is an Analytic Application? .....................................................................................10 1.2 What Is Analytics Designer? ............................................................................................10 1.3 What Can You Do with Analytic Applications That You Can’t Do with Stories? ..............10 1.4 How Are Stories and Analytic Applications Related to Each Other? ...............................10 1.5 Why Do We Need Both Stories and Analytic Applications? ............................................11 1.6 What Is the Typical Workflow in Creating an Analytic Application? .................................11 1.7 What Are Typical Analytic Applications? .........................................................................12 1.8 How Does Scripting Work in Analytic Applications? ........................................................12 1.9 What’s the Scripting Language for Analytic Applications? ..............................................13 2 Getting
    [Show full text]
  • Catalogue Open Data Protocol (Odata API) User Guide
    Catalogue Open Data Protocol (OData API) User Guide Content 1. Introduction .......................................................................................................................................... 3 1.1. Purpose......................................................................................................................... 3 1.2. Change register ............................................................................................................. 3 1.3. Structure of the document ............................................................................................. 3 1.4. Acronyms ...................................................................................................................... 4 1.5. Reference Documents ................................................................................................... 4 2. Open Data Protocol overview ............................................................................................................. 6 2.1. Entity Data Model concept ............................................................................................ 6 Entity Type ..................................................................................................................... 7 Entity Set ....................................................................................................................... 7 3. ONDA OData Entity Data Model ......................................................................................................... 8 3.1. ONDA Entity
    [Show full text]
  • Etir Code Lists
    eTIR Code Lists Code lists CL01 Equipment size and type description code (UN/EDIFACT 8155) Code specifying the size and type of equipment. 1 Dime coated tank A tank coated with dime. 2 Epoxy coated tank A tank coated with epoxy. 6 Pressurized tank A tank capable of holding pressurized goods. 7 Refrigerated tank A tank capable of keeping goods refrigerated. 9 Stainless steel tank A tank made of stainless steel. 10 Nonworking reefer container 40 ft A 40 foot refrigerated container that is not actively controlling temperature of the product. 12 Europallet 80 x 120 cm. 13 Scandinavian pallet 100 x 120 cm. 14 Trailer Non self-propelled vehicle designed for the carriage of cargo so that it can be towed by a motor vehicle. 15 Nonworking reefer container 20 ft A 20 foot refrigerated container that is not actively controlling temperature of the product. 16 Exchangeable pallet Standard pallet exchangeable following international convention. 17 Semi-trailer Non self propelled vehicle without front wheels designed for the carriage of cargo and provided with a kingpin. 18 Tank container 20 feet A tank container with a length of 20 feet. 19 Tank container 30 feet A tank container with a length of 30 feet. 20 Tank container 40 feet A tank container with a length of 40 feet. 21 Container IC 20 feet A container owned by InterContainer, a European railway subsidiary, with a length of 20 feet. 22 Container IC 30 feet A container owned by InterContainer, a European railway subsidiary, with a length of 30 feet. 23 Container IC 40 feet A container owned by InterContainer, a European railway subsidiary, with a length of 40 feet.
    [Show full text]
  • Z/OS, Language Environment, and UNIX How They Work Together
    The Trainer’s Friend, Inc. 256-B S. Monaco Parkway Telephone: (800) 993-8716 Denver, Colorado 80224 (303) 393-8716 U.S.A. Fax: (303) 393-8718 E-mail: [email protected] Internet: www.trainersfriend.com z/OS, Language Environment, and UNIX How They Work Together The following terms that may appear in these materials are trademarks or registered trademarks: Trademarks of the International Business Machines Corporation: AD/Cycle, AIX, AIX/ESA, Application System/400, AS/400, BookManager, CICS, CICS/ESA, COBOL/370, COBOL for MVS and VM, COBOL for OS/390 & VM, Common User Access, CORBA, CUA, DATABASE 2, DB2, DB2 Universal Database, DFSMS, DFSMSds, DFSORT, DOS/VSE, Enterprise System/3090, ES/3090, 3090, ESA/370, ESA/390, Hiperbatch, Hiperspace, IBM, IBMLink, IMS, IMS/ESA, Language Environment, MQSeries, MVS, MVS/ESA, MVS/XA, MVS/DFP, NetView, NetView/PC, Object Management Group, Operating System/400, OS/400, PR/SM, OpenEdition MVS, Operating System/2, OS/2, OS/390, OS/390 UNIX, OS/400, QMF, RACF, RS/6000, SOMobjects, SOMobjects Application Class Library, System/370, System/390, Systems Application Architecture, SAA, System Object Model, TSO, VisualAge, VisualLift, VTAM, VM/XA, VM/XA SP, WebSphere, z/OS, z/VM, z/Architecture, zSeries Trademarks of Microsoft Corp.: Microsoft, Windows, Windows NT, Windows ’95, Windows ’98, Windows 2000, Windows SE, Windows XP Trademark of Chicago-Soft, Ltd: MVS/QuickRef Trademark of Phoenix Software International: (E)JES Registered Trademarks of Institute of Electrical and Electronic Engineers: IEEE, POSIX Registered Trademark of The Open Group: UNIX Trademark of Sun Microsystems, Inc.: Java Registered Trademark of Linus Torvalds: LINUX Registered Trademark of Unicode, Inc.: Unicode Preface This document came about as a result of writing my first course for UNIX on the IBM mainframe.
    [Show full text]
  • Deliverable D7.5: Standards and Methodologies Big Data Guidance
    Project acronym: BYTE Project title: Big data roadmap and cross-disciplinarY community for addressing socieTal Externalities Grant number: 619551 Programme: Seventh Framework Programme for ICT Objective: ICT-2013.4.2 Scalable data analytics Contract type: Co-ordination and Support Action Start date of project: 01 March 2014 Duration: 36 months Website: www.byte-project.eu Deliverable D7.5: Standards and methodologies big data guidance Author(s): Jarl Magnusson, DNV GL AS Erik Stensrud, DNV GL AS Tore Hartvigsen, DNV GL AS Lorenzo Bigagli, National Research Council of Italy Dissemination level: Public Deliverable type: Final Version: 1.1 Submission date: 26 July 2017 Table of Contents Preface ......................................................................................................................................... 3 Task 7.5 Description ............................................................................................................... 3 Executive summary ..................................................................................................................... 4 1 Introduction ......................................................................................................................... 5 2 Big Data Standards Organizations ...................................................................................... 6 3 Big Data Standards ............................................................................................................. 8 4 Big Data Quality Standards .............................................................................................
    [Show full text]
  • File Organization and Management Com 214 Pdf
    File organization and management com 214 pdf Continue 1 1 UNESCO-NIGERIA TECHNICAL - VOCATIONAL EDUCATION REVITALISATION PROJECT-PHASE II NATIONAL DIPLOMA IN COMPUTER TECHNOLOGY FILE Organization AND MANAGEMENT YEAR II- SE MESTER I THEORY Version 1: December 2 2 Content Table WEEK 1 File Concepts... 6 Bit:... 7 Binary figure... 8 Representation... 9 Transmission... 9 Storage... 9 Storage unit... 9 Abbreviation and symbol More than one bit, trit, dontcare, what? RfC on trivial bits Alternative Words WEEK 2 WEEK 3 Identification and File File System Aspects of File Systems File Names Metadata Hierarchical File Systems Means Secure Access WEEK 6 Types of File Systems Disk File Systems File Systems File Systems Transactional Systems File Systems Network File Systems Special Purpose File Systems 3 3 File Systems and Operating Systems Flat File Systems File Systems according to Unix-like Operating Systems File Systems according to Plan 9 from Bell Files under Microsoft Windows WEEK 7 File Storage Backup Files Purpose Storage Primary Storage Secondary Storage Third Storage Out Storage Features Storage Volatility Volatility UncertaintyAbility Availability Availability Performance Key Storage Technology Semiconductor Magnetic Paper Unusual Related Technology Connecting Network Connection Robotic Processing Robotic Processing File Processing Activity 4 4 Technology Execution Program interrupts secure mode and memory control mode Virtual Memory Operating Systems Linux and UNIX Microsoft Windows Mac OS X Special File Systems Journalized File Systems Graphic User Interfaces History Mainframes Microcomputers Microsoft Windows Plan Unix and Unix-like operating systems Mac OS X Real-time Operating Systems Built-in Core Development Hobby Systems Pre-Emptification 5 5 WEEK 1 THIS WEEK SPECIFIC LEARNING OUTCOMES To understand: The concept of the file in the computing concept, field, character, byte and bits in relation to File 5 6 6 Concept Files In this section, we will deal with the concepts of the file and their relationship.
    [Show full text]
  • The 2016 SNIA Dictionary
    A glossary of storage networking data, and information management terminology SNIA acknowledges and thanks its Voting Member Companies: Cisco Cryptsoft DDN Dell EMC Evaluator Group Fujitsu Hitachi HP Huawei IBM Intel Lenovo Macrosan Micron Microsoft NetApp Oracle Pure Storage Qlogic Samsung Toshiba Voting members as of 5.23.16 Storage Networking Industry Association Your Connection Is Here Welcome to the Storage Networking Industry Association (SNIA). Our mission is to lead the storage industry worldwide in developing and promoting standards, technologies, and educational services to empower organizations in the management of information. Made up of member companies spanning the global storage market, the SNIA connects the IT industry with end-to-end storage and information management solutions. From vendors, to channel partners, to end users, SNIA members are dedicated to providing the industry with a high level of knowledge exchange and thought leadership. An important part of our work is to deliver vendor-neutral and technology-agnostic information to the storage and data management industry to drive the advancement of IT technologies, standards, and education programs for all IT professionals. For more information visit: www.snia.org The Storage Networking Industry Association 4360 ArrowsWest Drive Colorado Springs, Colorado 80907, U.S.A. +1 719-694-1380 The 2016 SNIA Dictionary A glossary of storage networking, data, and information management terminology by the Storage Networking Industry Association The SNIA Dictionary contains terms and definitions related to storage and other information technologies, and is the storage networking industry's most comprehensive attempt to date to arrive at a common body of terminology for the technologies it represents.
    [Show full text]
  • Units of Measure Used in International Trade Page 1/57 Annex II (Informative) Units of Measure: Code Elements Listed by Name
    Annex II (Informative) Units of Measure: Code elements listed by name The table column titled “Level/Category” identifies the normative or informative relevance of the unit: level 1 – normative = SI normative units, standard and commonly used multiples level 2 – normative equivalent = SI normative equivalent units (UK, US, etc.) and commonly used multiples level 3 – informative = Units of count and other units of measure (invariably with no comprehensive conversion factor to SI) The code elements for units of packaging are specified in UN/ECE Recommendation No. 21 (Codes for types of cargo, packages and packaging materials). See note at the end of this Annex). ST Name Level/ Representation symbol Conversion factor to SI Common Description Category Code D 15 °C calorie 2 cal₁₅ 4,185 5 J A1 + 8-part cloud cover 3.9 A59 A unit of count defining the number of eighth-parts as a measure of the celestial dome cloud coverage. | access line 3.5 AL A unit of count defining the number of telephone access lines. acre 2 acre 4 046,856 m² ACR + active unit 3.9 E25 A unit of count defining the number of active units within a substance. + activity 3.2 ACT A unit of count defining the number of activities (activity: a unit of work or action). X actual ton 3.1 26 | additional minute 3.5 AH A unit of time defining the number of minutes in addition to the referenced minutes. | air dry metric ton 3.1 MD A unit of count defining the number of metric tons of a product, disregarding the water content of the product.
    [Show full text]