Graphdb Free Documentation Release 7.2

Total Page:16

File Type:pdf, Size:1020Kb

Graphdb Free Documentation Release 7.2 GraphDB Free Documentation Release 7.2 Ontotext Oct 28, 2016 CONTENTS 1 General 1 1.1 About GraphDB...........................................2 1.2 Architecture & components.....................................2 1.2.1 Architecture.........................................2 Sesame............................................3 The SAIL API........................................4 1.2.2 Components.........................................4 Engine............................................4 Connectors..........................................5 Workbench..........................................5 1.3 GraphDB Free............................................5 1.3.1 Comparison of GraphDB Free and GraphDB SE......................6 1.4 Connectors..............................................6 1.5 Workbench..............................................6 1.5.1 How to use it........................................7 2 Quick start guide 9 2.1 Start the database...........................................9 2.1.1 Run GraphDB as a desktop installation...........................9 On Windows.........................................9 On Mac OS..........................................9 On Linux...........................................9 Configuring GraphDB....................................9 Stopping GraphDB...................................... 10 2.1.2 Run GraphDB as a stand-alone server........................... 10 Running GraphDB...................................... 10 Configuring GraphDB.................................... 11 Stopping the database.................................... 12 2.2 Set up your license.......................................... 12 2.3 Create a repository.......................................... 12 2.4 Load your data............................................ 13 2.4.1 Load data through the GraphDB Workbench........................ 13 2.4.2 Load data through SPARQL or Sesame API........................ 14 2.4.3 Load data through the GraphDB LoadRDF tool...................... 15 2.5 Explore your data and class relationships.............................. 15 2.5.1 Class hierarchy....................................... 15 2.5.2 Domain-Range graph.................................... 18 2.5.3 Class relationships..................................... 20 2.6 Query your data........................................... 22 2.6.1 Query data through the GraphDB Workbench....................... 22 2.6.2 Query data programmatically................................ 26 2.7 Additional resources......................................... 26 3 Installation 29 3.1 Requirements............................................. 29 i 3.1.1 Minimum.......................................... 29 3.1.2 Recommended....................................... 29 3.1.3 Licensing.......................................... 29 3.2 Deployment scenarios........................................ 29 3.3 Running GraphDB.......................................... 30 3.3.1 Run GraphDB as a desktop installation........................... 30 On Windows......................................... 30 On Mac OS.......................................... 30 On Linux........................................... 30 Configuring GraphDB.................................... 31 Stopping GraphDB...................................... 31 3.3.2 Run GraphDB as a stand-alone server........................... 31 Running GraphDB...................................... 31 Configuring GraphDB.................................... 32 Stopping the database.................................... 33 3.3.3 Run GraphDB as a WAR file deployed in a servlet container............... 33 Configuring GraphDB.................................... 33 Stopping the database.................................... 33 3.4 Configuring GraphDB........................................ 33 3.4.1 Directories......................................... 34 GraphDB Home....................................... 34 Checking the configured directories............................. 35 3.4.2 Configuration........................................ 35 Config properties....................................... 35 Configuring logging..................................... 36 3.4.3 Best practices........................................ 36 Step by step guide...................................... 36 3.5 Distribution package......................................... 37 3.6 Using Maven artifacts........................................ 37 3.6.1 Public Maven repository.................................. 37 3.6.2 Distribution......................................... 38 3.6.3 GraphDB JAR file for embedding the database or plugin development.......... 38 4 Administration 39 4.1 Administration tasks......................................... 39 4.2 Administration tools......................................... 39 4.2.1 Through the Workbench.................................. 39 4.2.2 Through the JMX interface................................. 40 4.3 Creating locations and repositories................................. 40 4.4 Configuring a repository....................................... 41 4.4.1 Planning a repository configuration............................. 41 4.4.2 Configuring a repository through the GraphDB Workbench................ 41 4.4.3 Configuring a repository programmatically........................ 42 4.4.4 Configuration parameters.................................. 43 4.4.5 Configuring GraphDB memory............................... 47 Configuring Java heap memory............................... 47 Single global page cache................................... 48 Configuring Entity pool memory............................... 48 Sample memory configuration................................ 48 4.5 Sizing guidelines........................................... 49 4.5.1 Entry-level deployment................................... 49 4.5.2 Mid-range deployment................................... 49 4.5.3 Enterprise deployment................................... 49 4.6 Disk space requirements....................................... 50 4.6.1 GraphDB disk space requirements for loading a dataset.................. 50 4.6.2 GraphDB disk space requirements per statement...................... 50 4.7 Configuring the Entity Pool..................................... 51 4.8 Managing repositories........................................ 51 ii 4.8.1 Changing repository parameters.............................. 51 Using the Workbench..................................... 52 In the SYSTEM repository................................... 52 Global overrides....................................... 52 4.8.2 Renaming a repository................................... 52 4.9 Access rights and security...................................... 53 4.9.1 Using the GraphDB Workbench.............................. 53 4.10 Backing up and recovering a repository............................... 54 4.10.1 Backing up a repository................................... 54 4.10.2 Restoring a repository.................................... 56 4.11 Query monitoring and termination.................................. 56 4.11.1 Query monitoring...................................... 57 4.11.2 Terminating a query..................................... 57 Stopping queries using JMX................................. 58 Stopping queries with GraphDB Workbench........................ 58 Automatically prevent long running queries......................... 58 4.11.3 Terminating a transaction.................................. 58 4.12 Database health checks........................................ 59 4.12.1 Possible values for health checks and their meaning.................... 59 4.12.2 Default health checks for the different GraphDB editions................. 59 4.12.3 Running the health checks................................. 59 4.13 System metrics monitoring...................................... 60 4.13.1 Page cache metrics..................................... 60 cache.flush.......................................... 60 cache.hit........................................... 60 cache.load........................................... 60 cache.miss.......................................... 61 4.13.2 Entity pool metrics..................................... 61 epool.read........................................... 61 epool.write.......................................... 61 4.14 Diagnosing and reporting critical errors............................... 61 4.14.1 Logs............................................. 61 Setting up the root logger................................... 61 Logs location......................................... 62 Log files........................................... 62 4.14.2 Report script........................................ 62 Requirements......................................... 63 Example........................................... 63 5 Usage 65 5.1 Workbench user guide........................................ 65 5.1.1 Admin (Administering the Workbench).......................... 66 Managing locations...................................... 66 Managing repositories.................................... 67 Managing users and access.................................. 69 Query monitoring and interruption.............................. 70 Resource monitoring..................................... 71 System information...................................... 71 REST API.......................................... 72 5.1.2 Data (Working with data).................................. 73 Importing data........................................ 73 Exporting data.......................................
Recommended publications
  • Empirical Study on the Usage of Graph Query Languages in Open Source Java Projects
    Empirical Study on the Usage of Graph Query Languages in Open Source Java Projects Philipp Seifer Johannes Härtel Martin Leinberger University of Koblenz-Landau University of Koblenz-Landau University of Koblenz-Landau Software Languages Team Software Languages Team Institute WeST Koblenz, Germany Koblenz, Germany Koblenz, Germany [email protected] [email protected] [email protected] Ralf Lämmel Steffen Staab University of Koblenz-Landau University of Koblenz-Landau Software Languages Team Koblenz, Germany Koblenz, Germany University of Southampton [email protected] Southampton, United Kingdom [email protected] Abstract including project and domain specific ones. Common applica- Graph data models are interesting in various domains, in tion domains are management systems and data visualization part because of the intuitiveness and flexibility they offer tools. compared to relational models. Specialized query languages, CCS Concepts • General and reference → Empirical such as Cypher for property graphs or SPARQL for RDF, studies; • Information systems → Query languages; • facilitate their use. In this paper, we present an empirical Software and its engineering → Software libraries and study on the usage of graph-based query languages in open- repositories. source Java projects on GitHub. We investigate the usage of SPARQL, Cypher, Gremlin and GraphQL in terms of popular- Keywords Empirical Study, GitHub, Graphs, Query Lan- ity and their development over time. We select repositories guages, SPARQL, Cypher, Gremlin, GraphQL based on dependencies related to these technologies and ACM Reference Format: employ various popularity and source-code based filters and Philipp Seifer, Johannes Härtel, Martin Leinberger, Ralf Lämmel, ranking features for a targeted selection of projects.
    [Show full text]
  • YHWH's Absence Or Hostility As Two Main Motifs of Suffering and Protest
    YHWH’s absence or hostility as two main motifs of suffering and protest in lament psalms A Theo-dramatic approach By Bujorel Lucaci A thesis submitted in partial fulfillment Of the requirement for the degree of Master of Arts Melbourne College of Divinity Date 25. 03. 2011 Acknowledgement Declaration This thesis submitted for assessment is the result of my own work, and no unacknowledged assistance has been received in its planning, drafting, execution or writing. All sources on which it is based have been acknowledged in writing, as has the supervision which I received in the process of its preparation. Name: Bujorel Lucaci Signature: Date: 25 March 2011 i ABSTRACT This thesis seeks to develop a new method of interpretation for lament psalms and to apply it to Psalms 13, 22, 44, 88. The new method is called Theo-dramatic approach. This method recognizes lament psalms as dialogical prayers, (multi- voicing) which describe the drama of suffering experienced by the psalmists. The Theo-dramatic approach is an imaginative method of interpretation. The most important elements are: the script, the theatre and the performance. The actors are: God, the supplicant, the enemy, the community. Script : lament Psalms: 13, 22, 44, and 88, were chosen because they demonstrate much of the vocabulary of the absence or hostility of God. Theatre : the public space provided by the covenant relationship between God and pray-er. Performance : the dramatized grief and pain of the psalmist, caused by the hostility or absence of God. This method of interpretation emphasizes the drama presented in the script: protest, argument, accusation of God for being unfaithful to the covenantal responsibilities.
    [Show full text]
  • Towards an Integrated Graph Algebra for Graph Pattern Matching with Gremlin
    Towards an Integrated Graph Algebra for Graph Pattern Matching with Gremlin Harsh Thakkar1, S¨orenAuer1;2, Maria-Esther Vidal2 1 Smart Data Analytics Lab (SDA), University of Bonn, Germany 2 TIB & Leibniz University of Hannover, Germany [email protected], [email protected] Abstract. Graph data management (also called NoSQL) has revealed beneficial characteristics in terms of flexibility and scalability by differ- ently balancing between query expressivity and schema flexibility. This peculiar advantage has resulted into an unforeseen race of developing new task-specific graph systems, query languages and data models, such as property graphs, key-value, wide column, resource description framework (RDF), etc. Present-day graph query languages are focused towards flex- ible graph pattern matching (aka sub-graph matching), whereas graph computing frameworks aim towards providing fast parallel (distributed) execution of instructions. The consequence of this rapid growth in the variety of graph-based data management systems has resulted in a lack of standardization. Gremlin, a graph traversal language, and machine provide a common platform for supporting any graph computing sys- tem (such as an OLTP graph database or OLAP graph processors). In this extended report, we present a formalization of graph pattern match- ing for Gremlin queries. We also study, discuss and consolidate various existing graph algebra operators into an integrated graph algebra. Keywords: Graph Pattern Matching, Graph Traversal, Gremlin, Graph Alge- bra 1 Introduction Upon observing the evolution of information technology, we can observe a trend arXiv:1908.06265v2 [cs.DB] 7 Sep 2019 from data models and knowledge representation techniques being tightly bound to the capabilities of the underlying hardware towards more intuitive and natural methods resembling human-style information processing.
    [Show full text]
  • Licensing Information User Manual
    Oracle® Database Express Edition Licensing Information User Manual 18c E89902-02 February 2020 Oracle Database Express Edition Licensing Information User Manual, 18c E89902-02 Copyright © 2005, 2020, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or “commercial computer software documentation” pursuant to the applicable Federal
    [Show full text]
  • Large Scale Querying and Processing for Property Graphs Phd Symposium∗
    Large Scale Querying and Processing for Property Graphs PhD Symposium∗ Mohamed Ragab Data Systems Group, University of Tartu Tartu, Estonia [email protected] ABSTRACT Recently, large scale graph data management, querying and pro- cessing have experienced a renaissance in several timely applica- tion domains (e.g., social networks, bibliographical networks and knowledge graphs). However, these applications still introduce new challenges with large-scale graph processing. Therefore, recently, we have witnessed a remarkable growth in the preva- lence of work on graph processing in both academia and industry. Querying and processing large graphs is an interesting and chal- lenging task. Recently, several centralized/distributed large-scale graph processing frameworks have been developed. However, they mainly focus on batch graph analytics. On the other hand, the state-of-the-art graph databases can’t sustain for distributed Figure 1: A simple example of a Property Graph efficient querying for large graphs with complex queries. Inpar- ticular, online large scale graph querying engines are still limited. In this paper, we present a research plan shipped with the state- graph data following the core principles of relational database systems [10]. Popular Graph databases include Neo4j1, Titan2, of-the-art techniques for large-scale property graph querying and 3 4 processing. We present our goals and initial results for querying ArangoDB and HyperGraphDB among many others. and processing large property graphs based on the emerging and In general, graphs can be represented in different data mod- promising Apache Spark framework, a defacto standard platform els [1]. In practice, the two most commonly-used graph data models are: Edge-Directed/Labelled graph (e.g.
    [Show full text]
  • Introduction to Graph Database with Cypher & Neo4j
    Introduction to Graph Database with Cypher & Neo4j Zeyuan Hu April. 19th 2021 Austin, TX History • Lots of logical data models have been proposed in the history of DBMS • Hierarchical (IMS), Network (CODASYL), Relational, etc • What Goes Around Comes Around • Graph database uses data models that are “spiritual successors” of Network data model that is popular in 1970’s. • CODASYL = Committee on Data Systems Languages Supplier (sno, sname, scity) Supply (qty, price) Part (pno, pname, psize, pcolor) supplies supplied_by Edge-labelled Graph • We assign labels to edges that indicate the different types of relationships between nodes • Nodes = {Steve Carell, The Office, B.J. Novak} • Edges = {(Steve Carell, acts_in, The Office), (B.J. Novak, produces, The Office), (B.J. Novak, acts_in, The Office)} • Basis of Resource Description Framework (RDF) aka. “Triplestore” The Property Graph Model • Extends Edge-labelled Graph with labels • Both edges and nodes can be labelled with a set of property-value pairs attributes directly to each edge or node. • The Office crew graph • Node �" has node label Person with attributes: <name, Steve Carell>, <gender, male> • Edge �" has edge label acts_in with attributes: <role, Michael G. Scott>, <ref, WiKipedia> Property Graph v.s. Edge-labelled Graph • Having node labels as part of the model can offer a more direct abstraction that is easier for users to query and understand • Steve Carell and B.J. Novak can be labelled as Person • Suitable for scenarios where various new types of meta-information may regularly
    [Show full text]
  • Scripting for the Java Platform
    Scripting for the Java Platform Christopher M. Judd President/Consultant Judd Solutions, LLC Christopher M. Judd • President/Consultant of Judd Solutions • Central Ohio Java User Group (COJUG) coordinator Agenda • Java Scripting Overview •Examples –API – Script Shell – Java EE Debugging • Alternative Java Scripting Engines – Configuring –Creating • Closing Thoughts • Resources •Q&A Java is the greatest language ever invented Developer’s tools Every developer’s toolbox should contain a static typed language like Java or C# and a dynamically typed scripting language like JavaScript, Ruby or Groovy. Java Scripting • Java Scripting support added in Java SE 6 • JSR 223: Scripting for the Java Platform • Java Virtual Machine – Executes “language-neutral” bytecode – Rich class library Java JavaScript Groovy – Multi-platform JVM •Features JavaScript Groovy – API to evaluate scripts – Embedded JavaScript engine (Rhino 1.6R2) – Scripting engine discovery mechanism – Java Scripting command-line interpreter (jrunscript) Reasons for Scripting •Flexibility • Simplicity (Domain Specific Language) • Interpreted • Development productivity •Dynamic typing • Expressive syntax •FUN Scripting Uses • Configuration •Customization • Automation • Debugging • Templating •Unit Testing •Prototyping • Web Scripting • Data transport Scripting Options •JavaScript – Rhino – www.mozilla.org/rhino/ •Groovy (JSR-241) – groovy.codehaus.org •Python –Jython –www.jython.org •Ruby –JRuby–jruby.codehaus.org •TCL –Jacl–tcljava.sourceforge.net • Java (JSR-274) – BeanShell www.beanshell.org
    [Show full text]
  • The Query Translation Landscape: a Survey
    The Query Translation Landscape: a Survey Mohamed Nadjib Mami1, Damien Graux2,1, Harsh Thakkar3, Simon Scerri1, Sren Auer4,5, and Jens Lehmann1,3 1Enterprise Information Systems, Fraunhofer IAIS, St. Augustin & Dresden, Germany 2ADAPT Centre, Trinity College of Dublin, Ireland 3Smart Data Analytics group, University of Bonn, Germany 4TIB Leibniz Information Centre for Science and Technology, Germany 5L3S Research Center, Leibniz University of Hannover, Germany October 2019 Abstract Whereas the availability of data has seen a manyfold increase in past years, its value can be only shown if the data variety is effectively tackled —one of the prominent Big Data challenges. The lack of data interoperability limits the potential of its collective use for novel applications. Achieving interoperability through the full transformation and integration of diverse data structures remains an ideal that is hard, if not impossible, to achieve. Instead, methods that can simultaneously interpret different types of data available in different data structures and formats have been explored. On the other hand, many query languages have been designed to enable users to interact with the data, from relational, to object-oriented, to hierarchical, to the multitude emerging NoSQL languages. Therefore, the interoperability issue could be solved not by enforcing physical data transformation, but by looking at techniques that are able to query heterogeneous sources using one uniform language. Both industry and research communities have been keen to develop such techniques, which require the translation of a chosen ’universal’ query language to the various data model specific query languages that make the underlying data accessible. In this article, we survey more than forty query translation methods and tools for popular query languages, and classify them according to eight criteria.
    [Show full text]
  • Mr. Tompkins in Wonderland
    MR TOMPKINS IN WONDERLAND MR TOMPKINS EXPLORES THE ATOM GEORGE GAMOW This paperback volume combines and brings up to date two of Professor Gamow’s well known books, Mr Tompkins in Wonderland and Mr Tompkins Explores the Atom . New stories and illustrations have been added on fission and fusion, the steady state universe, and elementary particles. Professor Gamow has made many notable contributions to physics. Here he provides a delightful explanation of the concepts of modern physics by introducing Mr Tompkins, a bank clerk whose fantastic dreams and adventures lead him into the world inside the atom. Some reviewers’ opinions of the two books: Enthusiastically recommended to both scientific and general readers. - MANCHESTER GUARDIAN Not only entertaining; the ordinary reader can learn from it a great deal about sub-atomic particles—electrons, neutrons and the rest—and the strange rules which govern their behaviour. THE OBSERVER Will vastly fascinate the whimsical, and is also entirely scientific. SCIENTIFIC AMERICAN Physicists will appreciate the deft exposition of physical theories and facts and will chuckle over the many apt analogies. Science students will find it worth while for it is definitely a good supplement to a modern physics textbook. Non-physicist readers will find the book interesting and stimulating.. SCRIPTA MATHEMATICA Preface In the winter of 1938 I wrote a short, scientifically fantastic story (not a science fiction story) in which I tried to explain to the layman the basic ideas of the theory of curvature of space and the expanding universe. I decided to do this by exaggerating the actually existing relativistic phenomena to such an extent that they could easily be observed by the hero of the story, C.
    [Show full text]
  • Full-Graph-Limited-Mvn-Deps.Pdf
    org.jboss.cl.jboss-cl-2.0.9.GA org.jboss.cl.jboss-cl-parent-2.2.1.GA org.jboss.cl.jboss-classloader-N/A org.jboss.cl.jboss-classloading-vfs-N/A org.jboss.cl.jboss-classloading-N/A org.primefaces.extensions.master-pom-1.0.0 org.sonatype.mercury.mercury-mp3-1.0-alpha-1 org.primefaces.themes.overcast-${primefaces.theme.version} org.primefaces.themes.dark-hive-${primefaces.theme.version}org.primefaces.themes.humanity-${primefaces.theme.version}org.primefaces.themes.le-frog-${primefaces.theme.version} org.primefaces.themes.south-street-${primefaces.theme.version}org.primefaces.themes.sunny-${primefaces.theme.version}org.primefaces.themes.hot-sneaks-${primefaces.theme.version}org.primefaces.themes.cupertino-${primefaces.theme.version} org.primefaces.themes.trontastic-${primefaces.theme.version}org.primefaces.themes.excite-bike-${primefaces.theme.version} org.apache.maven.mercury.mercury-external-N/A org.primefaces.themes.redmond-${primefaces.theme.version}org.primefaces.themes.afterwork-${primefaces.theme.version}org.primefaces.themes.glass-x-${primefaces.theme.version}org.primefaces.themes.home-${primefaces.theme.version} org.primefaces.themes.black-tie-${primefaces.theme.version}org.primefaces.themes.eggplant-${primefaces.theme.version} org.apache.maven.mercury.mercury-repo-remote-m2-N/Aorg.apache.maven.mercury.mercury-md-sat-N/A org.primefaces.themes.ui-lightness-${primefaces.theme.version}org.primefaces.themes.midnight-${primefaces.theme.version}org.primefaces.themes.mint-choc-${primefaces.theme.version}org.primefaces.themes.afternoon-${primefaces.theme.version}org.primefaces.themes.dot-luv-${primefaces.theme.version}org.primefaces.themes.smoothness-${primefaces.theme.version}org.primefaces.themes.swanky-purse-${primefaces.theme.version}
    [Show full text]
  • Session 6 - Main Theme J2EE Component-Based Computing Environments
    Application Servers G22.3033-011 Session 6 - Main Theme J2EE Component-Based Computing Environments Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda Component Technologies Database Technology Review EJB Component Model J2EE Services JNDI, JMS, JTS, CMP/BMP/JDBC, JavaMail, etc. J2EE Web Architectures Security in J2EE Application Servers Structured Applications Design Tips Summary Readings Assignment #5 2 1 Summary of Previous Session COM and COM+ Introduction to .Net Component Technologies Object Management Architectures Java-Based Application Servers Windows Services Summary Readings Assignment #5 3 Additional References Intranet Architectures and Performance Report http://www.techmetrix.com/lab/benchcenter/archiperf/archiper ftoc.shtml#TopOfPage RMI FAQ http://java.sun.com/products/javaspaces/faqs/rmifaq.html CORBA beyond the firewall http://www.bejug.org/new/pages/articles/corbaevent/orbix/ Web Object Integration (vision document) http://www.objs.com/survey/web-object-integration.htm 4 2 Application Servers Architectures Application Servers for Enhanced HTML (traditional) a.k.a., Page-Based Application Servers Mostly Used to Support Standalone Web Applications New Generation Page-Based Script-Oriented App. Servers First Generation Extensions (e.g., Microsoft IIS with COM+/ASP) Servlet/JSP Environments XSP Environment Can now be used as front-end to enterprise applications Hybrid development environments Distributed Object
    [Show full text]
  • Abkürzungs-Liste ABKLEX
    Abkürzungs-Liste ABKLEX (Informatik, Telekommunikation) W. Alex 1. Juli 2021 Karlsruhe Copyright W. Alex, Karlsruhe, 1994 – 2018. Die Liste darf unentgeltlich benutzt und weitergegeben werden. The list may be used or copied free of any charge. Original Point of Distribution: http://www.abklex.de/abklex/ An authorized Czechian version is published on: http://www.sochorek.cz/archiv/slovniky/abklex.htm Author’s Email address: [email protected] 2 Kapitel 1 Abkürzungen Gehen wir von 30 Zeichen aus, aus denen Abkürzungen gebildet werden, und nehmen wir eine größte Länge von 5 Zeichen an, so lassen sich 25.137.930 verschiedene Abkür- zungen bilden (Kombinationen mit Wiederholung und Berücksichtigung der Reihenfol- ge). Es folgt eine Auswahl von rund 16000 Abkürzungen aus den Bereichen Informatik und Telekommunikation. Die Abkürzungen werden hier durchgehend groß geschrieben, Akzente, Bindestriche und dergleichen wurden weggelassen. Einige Abkürzungen sind geschützte Namen; diese sind nicht gekennzeichnet. Die Liste beschreibt nur den Ge- brauch, sie legt nicht eine Definition fest. 100GE 100 GBit/s Ethernet 16CIF 16 times Common Intermediate Format (Picture Format) 16QAM 16-state Quadrature Amplitude Modulation 1GFC 1 Gigabaud Fiber Channel (2, 4, 8, 10, 20GFC) 1GL 1st Generation Language (Maschinencode) 1TBS One True Brace Style (C) 1TR6 (ISDN-Protokoll D-Kanal, national) 247 24/7: 24 hours per day, 7 days per week 2D 2-dimensional 2FA Zwei-Faktor-Authentifizierung 2GL 2nd Generation Language (Assembler) 2L8 Too Late (Slang) 2MS Strukturierte
    [Show full text]