Clojure Cookbook

Total Page:16

File Type:pdf, Size:1020Kb

Clojure Cookbook Clojure Cookbook Luke VanderHart and Ryan Neufeld Clojure Cookbook by Luke VanderHart and Ryan Neufeld Copyright © 2014 Cognitect, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/ institutional sales department: 800-998-9938 or [email protected]. Editor: Meghan Blanchette Indexer: Judith McConville Production Editor: Kristen Brown Cover Designer: Karen Montgomery Copyeditor: Amanda Kersey Interior Designer: David Futato Proofreader: Rachel Head Illustrator: Rebecca Demarest March 2014: First Edition Revision History for the First Edition: 2014-03-04: First release See http://oreilly.com/catalog/errata.csp?isbn=9781449366179 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Clojure Cookbook, the image of an aardwolf, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. ISBN: 978-1-449-36617-9 [LSI] Table of Contents Preface. ix 1. Primitive Data. 1 1.1. Changing the Capitalization of a String 3 1.2. Cleaning Up Whitespace in a String 4 1.3. Building a String from Parts 5 1.4. Treating a String as a Sequence of Characters 7 1.5. Converting Between Characters and Integers 8 1.6. Formatting Strings 10 1.7. Searching a String by Pattern 12 1.8. Pulling Values Out of a String Using Regular Expressions 13 1.9. Performing Find and Replace on Strings 15 1.10. Splitting a String into Parts 17 1.11. Pluralizing Strings Based on a Quantity 18 1.12. Converting Between Strings, Symbols, and Keywords 20 1.13. Maintaining Accuracy with Extremely Large/Small Numbers 22 1.14. Working with Rational Numbers 24 1.15. Parsing Numbers 25 1.16. Truncating and Rounding Numbers 26 1.17. Performing Fuzzy Comparison 28 1.18. Performing Trigonometry 30 1.19. Inputting and Outputting Integers with Different Bases 31 1.20. Calculating Statistics on Collections of Numbers 32 1.21. Performing Bitwise Operations 36 1.22. Generating Random Numbers 37 1.23. Working with Currency 39 1.24. Generating Unique IDs 41 1.25. Obtaining the Current Date and Time 43 1.26. Representing Dates as Literals 44 iii 1.27. Parsing Dates and Times Using clj-time 46 1.28. Formatting Dates Using clj-time 47 1.29. Comparing Dates 49 1.30. Calculating the Length of a Time Interval 50 1.31. Generating Ranges of Dates and Times 52 1.32. Generating Ranges of Dates and Times Using Native Java Types 53 1.33. Retrieving Dates Relative to One Another 56 1.34. Working with Time Zones 58 1.35. Converting a Unix Timestamp to a Date 59 1.36. Converting a Date to a Unix Timestamp 61 2. Composite Data. 63 2.1. Creating a List 65 2.2. Creating a List from an Existing Data Structure 66 2.3. “Adding” an Item to a List 68 2.4. “Removing” an Item from a List 69 2.5. Testing for a List 70 2.6. Creating a Vector 71 2.7. “Adding” an Item to a Vector 72 2.8. “Removing” an Item from a Vector 73 2.9. Getting the Value at an Index 74 2.10. Setting the Value at an Index 76 2.11. Creating a Set 77 2.12. Adding and Removing Items from Sets 79 2.13. Testing Set Membership 80 2.14. Using Set Operations 82 2.15. Creating a Map 84 2.16. Retrieving Values from a Map 86 2.17. Retrieving Multiple Keys from a Map Simultaneously 89 2.18. Setting Keys in a Map 90 2.19. Using Composite Values as Map Keys 94 2.20. Treating Maps as Sequences (and Vice Versa) 96 2.21. Applying Functions to Maps 98 2.22. Keeping Multiple Values for a Key 100 2.23. Combining Maps 103 2.24. Comparing and Sorting Values 105 2.25. Removing Duplicate Elements from a Collection 109 2.26. Determining if a Collection Holds One of Several Values 111 2.27. Implementing Custom Data Structures: Red-Black Trees—Part I 112 2.28. Implementing Custom Data Structures: Red-Black Trees—Part II 115 3. General Computing. 121 iv | Table of Contents 3.1. Running a Minimal Clojure REPL 121 3.2. Interactive Documentation 123 3.3. Exploring Namespaces 125 3.4. Trying a Library Without Explicit Dependencies 126 3.5. Running Clojure Programs 127 3.6. Running Programs from the Command Line 130 3.7. Parsing Command-Line Arguments 132 3.8. Creating Custom Project Templates 135 3.9. Building Functions with Polymorphic Behavior 139 3.10. Extending a Built-In Type 145 3.11. Decoupling Consumers and Producers with core.async 146 3.12. Making a Parser for Clojure Expressions Using core.match 150 3.13. Querying Hierarchical Graphs with core.logic 153 3.14. Playing a Nursery Rhyme 159 4. Local I/O. 165 4.1. Writing to STDOUT and STDERR 165 4.2. Reading a Single Keystroke from the Console 167 4.3. Executing System Commands 168 4.4. Accessing Resource Files 171 4.5. Copying Files 173 4.6. Deleting Files or Directories 175 4.7. Listing Files in a Directory 176 4.8. Memory Mapping a File 178 4.9. Reading and Writing Text Files 179 4.10. Using Temporary Files 181 4.11. Reading and Writing Files at Arbitrary Positions 182 4.12. Parallelizing File Processing 183 4.13. Parallelizing File Processing with Reducers 185 4.14. Reading and Writing Clojure Data 188 4.15. Using edn for Configuration Files 190 4.16. Emitting Records as edn Values 194 4.17. Handling Unknown Tagged Literals When Reading Clojure Data 196 4.18. Reading Properties from a File 199 4.19. Reading and Writing Binary Files 201 4.20. Reading and Writing CSV Data 203 4.21. Reading and Writing Compressed Files 204 4.22. Working with XML Data 206 4.23. Reading and Writing JSON Data 207 4.24. Generating PDF Files 209 Table of Contents | v 4.25. Making a GUI Window with Scrollable Text 213 5. Network I/O and Web Services. 219 5.1. Making HTTP Requests 219 5.2. Performing Asynchronous HTTP Requests 221 5.3. Sending a Ping Request 223 5.4. Retrieving and Parsing RSS Data 224 5.5. Sending Email 226 5.6. Communicating over Queues Using RabbitMQ 229 5.7. Communicating with Embedded Devices via MQTT 236 5.8. Using ZeroMQ Concurrently 240 5.9. Creating a TCP Client 243 5.10. Creating a TCP Server 245 5.11. Sending and Receiving UDP Packets 248 6. Databases. 253 6.1. Connecting to an SQL Database 254 6.2. Connecting to an SQL Database with a Connection Pool 257 6.3. Manipulating an SQL Database 260 6.4. Simplifying SQL with Korma 266 6.5. Performing Full-Text Search with Lucene 270 6.6. Indexing Data with ElasticSearch 272 6.7. Working with Cassandra 277 6.8. Working with MongoDB 280 6.9. Working with Redis 284 6.10. Connecting to a Datomic Database 286 6.11. Defining a Schema for a Datomic Database 289 6.12. Writing Data to Datomic 293 6.13. Removing Data from a Datomic Database 296 6.14. Trying Datomic Transactions Without Committing Them 298 6.15. Traversing Datomic Indexes 300 7. Web Applications. 305 7.1. Introduction to Ring 305 7.2. Using Ring Middleware 307 7.3. Serving Static Files with Ring 309 7.4. Handling Form Data with Ring 311 7.5. Handling Cookies with Ring 312 7.6. Storing Sessions with Ring 314 7.7. Reading and Writing Request and Response Headers in Ring 316 7.8. Routing Requests with Compojure 318 7.9. Performing HTTP Redirects with Ring 320 vi | Table of Contents 7.10. Building a RESTful Application with Liberator 321 7.11. Templating HTML with Enlive 323 7.12. Templating with Selmer 330 7.13. Templating with Hiccup 334 7.14. Rendering Markdown Documents 337 7.15. Building Applications with Luminus 339 8. Performance and Production. 343 8.1. AOT Compilation 343 8.2. Packaging a Project into a JAR File 345 8.3. Creating a WAR File 348 8.4. Running an Application as a Daemon 352 8.5. Alleviating Performance Problems with Type Hinting 358 8.6. Fast Math with Primitive Java Arrays 360 8.7. Simple Profiling with Timbre 363 8.8. Logging with Timbre 365 8.9. Releasing a Library to Clojars 367 8.10. Using Macros to Simplify API Deprecations 369 9. Distributed Computation. 375 9.1. Building an Activity Feed System with Storm 376 9.2. Processing Data with an Extract Transform Load (ETL) Pipeline 385 9.3. Aggregating Large Files 389 9.4. Testing Cascalog Workflows 394 9.5. Checkpointing Cascalog Jobs 396 9.6. Explaining a Cascalog Query 398 9.7. Running a Cascalog Job on Elastic MapReduce 400 10. Testing. 403 10.1. Unit Testing 404 10.2.
Recommended publications
  • Specification for JSON Abstract Data Notation Version
    Standards Track Work Product Specification for JSON Abstract Data Notation (JADN) Version 1.0 Committee Specification 01 17 August 2021 This stage: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.html https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.pdf Previous stage: https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.html https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.pdf Latest stage: https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.html https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.pdf Technical Committee: OASIS Open Command and Control (OpenC2) TC Chair: Duncan Sparrell ([email protected]), sFractal Consulting LLC Editor: David Kemp ([email protected]), National Security Agency Additional artifacts: This prose specification is one component of a Work Product that also includes: JSON schema for JADN documents: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/schemas/jadn-v1.0.json JADN schema for JADN documents: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/schemas/jadn-v1.0.jadn Abstract: JSON Abstract Data Notation (JADN) is a UML-based information modeling language that defines data structure independently of data format.
    [Show full text]
  • Performance Comparison of Data Serialization Schemes for ETSI ITS Car-To-X Communication Systems
    International Journal on Advances in Telecommunications, vol 8 no 1 & 2, year 2015, http://www.iariajournals.org/telecommunications/ 48 Performance Comparison of Data Serialization Schemes for ETSI ITS Car-to-X Communication Systems Sebastian Bittl, Arturo A. Gonzalez, Michael Spahn,¨ and Wolf A. Heidrich Fraunhofer ESK Munich, Germany Email: fsebastian.bittl, arturo.gonzalez, michael.spaehn, [email protected] Abstract—Wireless Car-to-X communication is about to enter sense collision avoidance mechanism (CSMA-CA) for multi- the mass market in upcoming years. The non-licensed, but user channel access, longer packets imply longer transmission reserved bandwidth for such communications is relatively narrow times and hence a higher channel busy ratio. This means that in terms of the few usable channels and the expected number nodes near a transmitter, which are willing to transmit as well, of communicating entities. Among other communication aspects, must wait longer until the channel is free to use. Moreover, data serialization schemes that allow compact encoding as well as the wireless channel has a limited capacity allowing only a fast encoding and decoding are required. Compact representation of data helps in keeping a minimal bandwidth overhead in limited number of transmitted bits per unit of time. The lower the wireless channel. Moreover, since delay is an important the number of transmitted messages, the higher the number of performance parameter in Car-to-X communication, the pro- users that could use the given frequency spectrum in parallel. cessing time of the serialization/deserialization schemes shall be kept to a minimum. So far, no detailed analysis of different The data serialization schemes also influence processing data serialization schemes for Car-to-X communication regarding power requirements in both ETSI Intelligent Transport Sys- important properties such as runtime, memory consumption tems (ITS) in Europe [2] and Wireless Access in Vehicular and encoded output length has been published.
    [Show full text]
  • Reactively Querying an Immutable Log of Relational Facts. Design And
    Reactively Querying an Immutable Log of Relational Facts Design and Implementation of a Bitemporal EAV Database with a Subscription Query Language Master Thesis Submitted in partial fulfillment of the requirements for the degree of Master of Science in Engineering to the University of Applied Sciences FH Campus Wien Master Degree Program Software Design and Engineering Author: Albert Zak Student identification number: 1810838004 Supervisor: Priv.-Doz. Mag.rer.soc.oec. Dipl.-Ing. Dipl.-Ing. Dr.techn. Karl Michael Göschka Date: 2020-05-31 Declaration of authorship: I declare that this Master Thesis has been written by myself. I have not used any other than the listed sources, nor have I received any unauthorized help. I hereby certify that I have not submitted this Master Thesis in any form (to a reviewer for assessment) either in Austria or abroad. Furthermore, I assure that the (printed and electronic) copies I have submitted are identical. Date: Signature: Abstract Growing customer demands lead to increased incidental complexity of data-intensive distributed applications. Relational Database Management Systems (RDBMS), es- pecially those implementing Structured Query Language (SQL) possess performant but destructive-by-default write semantics. Modeling domains such as healthcare in classic RDBMS leads to an explosion in the number of columns and tables. Their structure has to be known in advance, discouraging an explorative development process. Requirements of real time collaboration and auditability of changes push the limit of established paradigms. The core of the data layer presented in this thesis is a simple relational model based on facts in the form of Entity-Attribute-Value (EAV) triples.
    [Show full text]
  • Concise Binary Object Representation See Also: IETF94 CBOR Lightning Tutorial Carsten Bormann, 2015-11-01
    CBOR (RFC 7049) Concise Binary Object Representation See also: IETF94 CBOR lightning tutorial Carsten Bormann, 2015-11-01 http://www.tzi.de/~cabo/CBOR-2015-11-01.pdf 1 Slide stolen from Douglas Crockford History of Data Formats • Ad Hoc • Database Model • Document Model • Programming Language Model 2 Box notation TLV 3 XML XSD 4 JSON data model Primitive: Container: • null • “object” (map, with text • false, true string keys only) • numbers (decimal float) • array • text string (UTF-8) 5 CBOR data model Primitive: Container: • null (+ other “simple”) • map (any key) • false, true • array • numbers: • Integer • Tag (extension point) • Float16, 32, 64 • text string (UTF-8) • byte string 6 JSON limitations • No binary data (byte strings) • Numbers are in decimal, some parsing required • Format requires copying: • Escaping for strings • Base64 for binary • No extensibility (e.g., date format?) • Interoperability issues • I-JSON further reduces functionality (RFC 7493) 7 Data Formats Character- Concise based Binary Document- Oriented XML EXI Data- Oriented JSON ??? 8 Prof. Carsten Bormann, [email protected] BSON and friends • Lots of “binary JSON” proposals • Often optimized for data at rest, not protocol use (BSON ➔ MongoDB) • Most are more complex than JSON 9 Why a new binary object format? • Different design goals from current formats – stated up front in the document • Extremely small code size – for work on constrained node networks • Reasonably compact data size – but no compression or even bit-fiddling • Useful to any protocol or application that likes the design goals 10 Concise Binary Object Representation (CBOR) 11 “Sea Boar” “Sea Boar” 12 Graphics: Stefanie Gerdes Data Formats Character- Concise based Binary Document- Oriented XML EXI Data- Oriented JSON CBOR 13 Prof.
    [Show full text]
  • CBOR (RFC 7049) Concise Binary Object Representation IETF94 CBOR Lightning Tutorial Carsten Bormann, 2015-11-01
    CBOR (RFC 7049) Concise Binary Object Representation IETF94 CBOR lightning tutorial Carsten Bormann, 2015-11-01 1 CBOR: Agenda • What is it, and when might I want it? • How does it work? • How do I work with it? 2 CBOR: Agenda • What is it, and when might I want it? • How does it work? • How do I work with it? 3 Slide stolen from Douglas Crockford History of Data Formats • Ad Hoc • Database Model • Document Model • Programming Language Model Box notation TLV 5 XML XSD 6 Slide stolen from Douglas Crockford JSON • JavaScript Object Notation • Minimal • Textual • Subset of JavaScript Values • Strings • Numbers • Booleans • Objects • Arrays • null Array ["Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"] [ [0, -1, 0], [1, 0, 0], [0, 0, 1] ] Object { "name": "Jack B. Nimble", "at large": true, "grade": "A", "format": { "type": "rect", "width": 1920, "height": 1080, "interlace": false, "framerate": 24 } } Object Map { "name": "Jack B. Nimble", "at large": true, "grade": "A", "format": { "type": "rect", "width": 1920, "height": 1080, "interlace": false, "framerate": 24 } } Application usage of JSON • No schema needed for parsing • Representation types: bool, number, string, null; map, array • Semantics: • struct: key names in map (vs. table use of maps) • record: position in array (vs. vector use of arrays) • Extensibility: new keys in a key/value struct • Ignore what you don’t understand 12 JSON limitations • No binary data (byte strings) • Numbers are in decimal, some parsing required • Format requires copying: • Escaping for strings • Base64 for binary • No extensibility (e.g., date format?) • Interoperability issues • I-JSON further reduces functionality (RFC 7493) 13 Data Formats Character- Concise based Binary Document- Oriented XML EXI Data- Oriented JSON ??? 14 Prof.
    [Show full text]
  • FRED: Um Formato Para Representação E Troca De Dados
    Universidade de Brasília – UnB Faculdade UnB Gama – FGA Engenharia de Software FRED: Um formato para representação e troca de dados Autor: Matheus de Sousa Bernardo Orientador: Prof. Dr. Fábio Macêdo Mendes Brasília, DF 2019 Matheus de Sousa Bernardo FRED: Um formato para representação e troca de dados Monografia submetida ao curso de graduação em Engenharia de Software da Universidade de Brasília, como requisito parcial para ob- tenção do Título de Bacharel em Engenharia de Software. Universidade de Brasília – UnB Faculdade UnB Gama – FGA Orientador: Prof. Dr. Fábio Macêdo Mendes Brasília, DF 2019 Matheus de Sousa Bernardo FRED: Um formato para representação e troca de dados/ Matheus de Sousa Bernardo. – Brasília, DF, 2019- 79 p. : il. (algumas color.) ; 30 cm. Orientador: Prof. Dr. Fábio Macêdo Mendes Trabalho de Conclusão de Curso – Universidade de Brasília – UnB Faculdade UnB Gama – FGA , 2019. 1. representação de dados. 2. troca de dados. I. Prof. Dr. Fábio Macêdo Mendes. II. Universidade de Brasília. III. Faculdade UnB Gama. IV. FRED: Um formato para representação e troca de dados CDU 02:141:005.6 Matheus de Sousa Bernardo FRED: Um formato para representação e troca de dados Monografia submetida ao curso de graduação em Engenharia de Software da Universidade de Brasília, como requisito parcial para ob- tenção do Título de Bacharel em Engenharia de Software. Trabalho aprovado. Brasília, DF, 12 de Julho de 2019 – Data da aprovação do trabalho: Prof. Dr. Fábio Macêdo Mendes Orientador Prof. Dr. Renato Coral Sampaio Convidado 1 Prof. Dr. Bruno César Ribas Convidado 2 Brasília, DF 2019 Resumo Este projeto propõe a especificação e a implementação de um formato para troca ere- presentação de dados chamado FRED.
    [Show full text]
  • Clojure Applied: from Practice to Practitioner
    www.allitebooks.com www.allitebooks.com Early praise for Clojure Applied Starting your first Clojure job? Kicking off your first big open source Clojure project? This is the book you need to get started building Clojure projects. You may worry, “I don’t know what I don’t know.” This book points you to the things you need to know. ➤ Bridget Hillyer Software developer, LivingSocial While other Clojure books enumerate the beautiful, pristine qualities derived from immutability and functional programming, this book is about getting your hands very dirty. Clojure Applied takes you step by step through the process of designing, writing, and shipping robust, high-performance production systems. ➤ David Nolen Software developer, Cognitect It’s refreshing to see experts such as Ben and Alex distill their knowledge into a tome for the masses. Clojure Applied covers a myriad of subjects that perplexed me about Clojure on my own journey. I’m hopeful the book will short-circuit the journey for many. ➤ Ryan Neufeld Software consultant, founder, Homegrown Labs www.allitebooks.com Clojure Applied is the book I wish I had when I started writing Clojure. This book is packed with advice and tips based on years of real-world experience. I learned something new on what seemed like every page. Buy this book and take your Clojure code to the next level. ➤ Larry Staton, Jr. Senior software engineer, Hendrick Automotive Group I had a solid foundation and collection of recipes. When I was ready for the next level, Clojure Applied gave me application patterns and instructed me on how to apply them in an idiomatic way, quickly.
    [Show full text]
  • Les Fichiers De Texte Et Leurs Applications
    EPAI, Jérôme Frossard (2017) LES FICHIERS DE TEXTE ET LEURS APPLICATIONS Caractériser, mettre en forme et analyser des données Texte et informatique 1 En informatique on utilise beaucoup de texte, mais pas seulement du texte dans le langage ordinaire. On utilise du texte également pour : Communiquer avec une machine à travers un terminal avec un interpréteur de commandes (Bash, Cmd, PowerShell, etc.). Écrire le code source d’un programme (Java, JavaScript, etc.). Stocker des données structurées (XML, JSON, etc.). Représenter l’apparence, la structure et la mise en page du texte dans un document de texte (HTML, Open XML, ODF, TeX, etc.). Échanger des données entre des programmes à travers le réseau ou le système de fichiers (HTTP, CSV, XML, JSON, etc.). EPAI, Jérôme Frossard (2017) Fichier de texte 2 Contient une suite de caractères codés sous forme numérique selon une certaine norme (ASCII, ANSI, UTF-8, etc.). Ne contient pas d’information sur la norme utilisée pour coder les caractères. L’émetteur et le récepteur du fichier doivent s’accorder d’une manière ou d’une autre sur la norme à utiliser. Certains éditeurs de texte peuvent détecter la norme d’encodage, mais des erreurs de détection sont possibles. EPAI, Jérôme Frossard (2017) Éditeur de texte 3 Un éditeur de texte est un programme permettant de créer et de modifier des fichiers de textes. Ne doit pas être confondu avec un logiciel de traitement de texte (pas de structuration ou de mise en page du texte). Peut avoir des fonctions avancées comme l’autocomplétion ou la coloration syntaxique pour faciliter l’écriture de code (Java, HTML, TeX, Bash, etc.).
    [Show full text]
  • ICBO2015 International Conference on Biomedical Ontology 2005
    ICBO2015 International Conference on Biomedical Ontology 2005 Proceedings of the Main Conference July, 27-30 Lisbon, Portugal Preface ICBO2015 is the 6th International Conference on Biomedical Ontology held on July 26-30, 2015 in Lisboa. It is a forum for presentation and discussion of current work and new advances in Biomedical Ontologies. This conference explores directions of future research and facilitates collaboration between researchers, developers, practitioners and students. After a careful revision, the program committee has selected 16 regular papers, 5 early career papers, 14 posters and 9 demos for presentation and discussion in the main confer- ence. This volume contains all these papers. The main conference includes also two invited presentations, one by Helen Parkinson, entitled Using Ontologies in the Wild, and another by Egon Willighagen, entitled The role of ontologies in chem- and bioinformatics. The main conference was preceded by 2 workshops, 1 hackathon and 4 tutorials: • 4th International Workshop on Vaccine and Drug Ontology Studies (VDOS) • Third International Workshop on Definitions in Ontologies (IWOOD) • Genomics data standards - hackathon • Tawny-OWL: re-purposing software engineering for ontology building • Basic Formal Ontology (BFO) • OBO Tutorial: Best Practices for Ontology Use • Tutorial on the Biological Pathway Exchange (BioPAX) Ontology and Pathway Com- mons Database We would like to acknowledge all the organizing committee, the program committee, the additional reviewers, the volunteers, authors
    [Show full text]