DOCSLIB.ORG

Animal Welfare Inspection Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Animal Welfare Inspection Guide United States Department of Animal Welfare Inspection Agriculture Guide Animal and Plant Health Inspection Service Animal Care The U.S. Department of Agriculture (USDA) prohibits discrimination in all its programs and activities on the basis of race, color, national origin, age, disability, and where applicable, sex, marital status, familial status, parental status, religion, sexual orientation, genetic information, political beliefs, reprisal, or because all or part of any individual’s income is derived from any public assistance program. (Not all prohibited bases apply to all programs). Persons with disabilities who require alternative means for communciation of program information (Braille, large print, audiotape, etc.) should contact USDA’s TARGET Center at (202) 720-2600 (voice and TDD). To file a complaint of discrimination, write to USDA, Director, Office of Civil Rights, 1400 Independence Avenue, SW., Washington, DC 20250-9410, or call (800) 795-3272 (voice) or (202) 720-6382 (TDD). USDA is an equal opportunity provider and employer. The opinions expressed by individuals in this report do not necessarily represent the policies of the U.S. Department of Agriculture. First Edition Issued 2013 Contents Animal Welfare Inspection Guide Contents Contents-1 Figures LOF-1 Tables LOT-1 Introduction 1-1 Required Inspection Procedures 2-1 General Inspection Procedures 3-1 Specific Types of Inspections 4-1 Record-keeping 5-1 Veterinary Care 6-1 Research Facility Inspection–IACUC Requirements and Protocols 7-1 Confiscation Information 8-1 Animal Care Policies 9-1 Appendix A—Forms and Worksheets A-1 Appendix B—Direct Noncompliance Item (NCI) Guidance B-1 Appendix C—Equipment and Supplies C-1 Appendix D—Body Condition Charts D-1 Glossary Glossary-1 Index Index-1 09/2013-01 Animal Welfare Inspection Guide Contents-1 Contents Contents-2 Animal Welfare Inspection Guide 09/2013-01 Figures Animal Welfare Inspection Guide List of Graphics and Pictures Figure 1-1 Adobe Maximize, Minimize, and Close Buttons 1-8 Figure 1-2 Adobe PDF Work Area 1-9 Figure 1-3 Adobe Menu Bar 1-9 Figure 1-4 Adobe Tool Bar 1-10 Figure 1-5 Navigation Bar Bookmarks 1-11 Figure 4-1 Maximum Volume for Single Sampling for Various Species (page 1 of 2) 4-20 Figure 4-2 Maximum Volume for Single Sampling for Various Species (page 2 of 2) 4-21 Figure 8-1 Emaciated Asian Elephant 8-4 Figure 8-2 Emaciated Lion 8-5 Figure 8-3 Thin Tiger with Chronic Poor Hair Coat 8-5 Figure 8-4 Emaciated Dog, Dorsal View 8-6 Figure 8-5 Chronic Untreated Eye Problems 8-6 Figure 8-6 Eye Problems 8-7 Figure 8-7 Serious Untreated Tail Injury of Cougar 8-7 Figure 8-8 Ruptured Abscess on Dog 8-7 Figure 8-9 Bloody Feces 8-8 Figure 8-10 Dead Dog in Enclosure 8-8 Figure 8-11 Overgrown Hooves 8-8 Figure 8-12 Mutilated Front Leg of Dog 8-9 Figure 8-13 Untreated Skin Problems 8-9 Figure 8-14 Chained With No Access to Shade 8-10 Figure 8-15 Inadequate Sized Shelter for Four Wolves 8-10 Figure 8-16 Shelter Not Structurally Sound 8-11 Figure 8-17 No Bedding, Rusted Enclosure 8-11 Figure 8-18 Dogs With No Shelter or Shade 8-11 Figure 8-19 Dogs With No Shade 8-12 Figure 8-20 Poor Quality Rotting Chicken 8-13 Figure 8-21 Rotting Carcass in Cougar Enclosure 8-13 Figure 8-22 Poor Quality Chicken and Meat 8-14 Figure 8-23 Self Feeder with Moldy Food 8-14 Figure 8-24 Mouse Feces in Feeder 8-14 Figure 8-25 Filthy Water Receptacle 8-15 Figure 8-26 Grossly Inadequate Space 8-15 Figure 8-27 Extremely Soiled, Overcrowded Hamster Enclosure 8-16 Figure 8-28 Extremely Soiled Rabbit Enclosure 8-16 Figure 8-29 Excessive Accumulation of Feces in Trays Under Dog Run 8- 16 Figure 8-30 Layers of Moist, Filthy Bedding 8-17 09/2013-01 Animal Welfare Inspection Guide LOF-1 Figures List of Forms and Worksheets Figure 8-31 View from Front of Cougar 8-18 Figure 8-32 Side View (Lateral) of Cougar 8-18 Figure 8-33 Dorsal View of Cougar 8-19 Figure 8-34 Sheep Suffering from Unshorn Coat in Hot Weather 8-21 Figure 8-35 Overgrown Hooves 8-21 Figure 8-36 Guinea Pigs in Filthy Enclosure 8-22 Figure 8-37 Filth in an Animal Enclosure 8-22 Figure 8-38 Milk and Cottage Cheese in Pig Trough that is Never Cleaned 8-23 Figure 8-39 Evidence of Inadequate Water (Dry Bucket) 8-23 Figure 8-40 Notice of Intent to Confiscate Animals 8-30 Figure 8-41 Notice of Confiscation of Animals 8-31 Figure D-1 Cat Body Assessment Chart D-3 Figure D-2 Cougar Body Assessment Chart D-4 Figure D-3 Dog Body Assessment Chart D-5 Figure D-4 Elephant Body Assessment Chart D-6 Figure D-5 Leopard Body Assessment Chart D-7 Figure D-6 Lion Body Assessment Chart D-8 Figure D-7 Tiger Body Assessment Chart D-9 List of Forms and Worksheets Figure A-1 Animal Care Forms—Ordering Information A-3 Figure A-2 APHIS Form 7002–Program of Veterinary Care for Research Facilities or Exhibitors/Dealers (1 of 4) A-5 Figure A-3 APHIS Form 7002–Program of Veterinary Care for Research Facilities or Exhibitors/Dealers (2 of 4) A-6 Figure A-4 APHIS Form 7002–Program of Veterinary Care for Research Facilities or Exhibitors/Dealers (3 of 4) A-7 Figure A-5 APHIS Form 7002–Program of Veterinary Care for Research Facilities or Exhibitors/Dealers (4 of 4) A-8 Figure A-6 Program of Veterinary Care Instructions A-9 Figure A-7 APHIS Form 7003A–Application for New License A-11 Figure A-8 APHIS Form 7003–Application for License Renewal A-13 Figure A-9 APHIS Form 7005–Record of Acquisition of Dogs and Cats on Hand (front) A-15 Figure A-10 APHIS Form 7005–Record of Acquisition of Dogs and Cats on Hand (reverse) A-16 Figure A-11 APHIS Form 7006–Record of Disposition of Dogs and Cats (front) A-17 Figure A-12 APHIS Form 7006–Record of Disposition of Dogs and Cats (reverse) A-18 Figure A-13 APHIS Form 7006A–Continuation Sheet for Record of Disposi- tion of Dogs and Cats A-19 Figure A-14 APHIS Form 7011–Application for Registration Update A-21 Figure A-15 APHIS Form 7011A–Application for New Registration A-23 Figure A-16 APHIS Form 7019–Record of Animals on Hand (Other than Dogs and Cats) A-25 Figure A-17 APHIS Form 7020A–Continuation Sheet for Record of Acquisi- LOF-2 Animal Welfare Inspection Guide 09/2013-01 Figures List of Forms and Worksheets tion, Disposition or Transport of Animals (Other than Dogs and Cats) A-27 Figure A-18 APHIS Form 7020–Record of Acquisition, Disposition or Trans- port of Animals (Other Than Dogs and Cats) A-29 Figure A-19 APHIS Form 7023-Annual Report of Research Facility A-31 Figure A-20 APHIS Form 7023-Instructions for Completion of APHIS Form 7023 (reverse) A-33 Figure A-21 APHIS Form 7023 Annual Report Guidelines for Reporting Ani- mals In Column B A-34 Figure A-22 APHIS Form 7023 Annual Report Column E Explanation A- 35 Figure A-23 Annual Reports Important Information A-37 Figure A-24 Assistance with Accurate Annual Reporting for Research Facil- ities, Sept 2012 (1 of 2) A-39 Figure A-25 Assistance with Accurate Annual Reporting for Research Facil- ities, Sept. 2012 (2 of 2) A-40 Figure A-26 Annual Report Checklist A-41 Figure A-27 USDA, APHIS, Animal Care Animal Welfare Complaint Sheet A-43 Figure A-28 USDA, APHIS, Animal Care Inspection Report and Narrative A-45 Figure A-29 USDA, APHIS, Animal Care Search for Unlicensed Activity Worksheet A-47 Figure A-30 Amended Report Letter A-51 Figure A-31 Animal Care Traceback Worksheet A-53 Figure A-32 Exercise Plan for Dogs A-55 Figure A-33 Handling of Dangerous Animals Letter (1 of 2) A-57 Figure A-34 Options for Identification of Dogs and Cats A-59 Figure A-35 Perimeter Fence Variance Request Letter (1 of 2) A-61 Figure A-36 Perimeter Fence Variance Request Letter (2 of 2) A-62 Figure A-37 Procedure for Obtaining a Tattoo Code A-63 Figure A-38 Handling of Dangerous Animals Letter (2 of 2) A-64 Figure A-39 Request to Cancel License/Registration A-65 Figure A-40 Request to Use Microchipping as a Method of Identification A-67 Figure A-41 Request for Federal Taxpayer Identification Number A-69 Figure A-42 State and Territory Identification Codes A-71 Figure A-43 Itinerary for Traveling Facilities (optional form) A-73 09/2013-01 Animal Welfare Inspection Guide LOF-3 Figures List of Forms and Worksheets LOF-4 Animal Welfare Inspection Guide 09/2013-01 Tables Animal Welfare Inspection Guide Table 1-1 How to Use Decision Tables 1-5 Table 1-2 Where to Report Questions or Concerns With the Inspection Guide 1-7 Table 3-1 Biosafety Measures When Conducting an Inspection 3-4 Table 4-1 Action to Take on a Complaint 4-16 Table 4-2 Traveling Petting Zoo Itinerary Guidance 4-34 Table 4-3 Holding Period for Dogs and Cats Held by Random Source Class B Dealers 4-37 Table 7-1 Species-Typical Signs of Pain 7-38 Table 9-1 Categories of Animals Needing Licenses 9-19 Table B-1 Direct Noncompliance Item Guidance B-2 Table C-1 Industry Standards Related Texts and Materials C-7 Table C-2 Optional Reference Texts C-8 Table D-1 Generic Bengal Tiger Cub Weights D-10 09/2013-01 Animal Welfare Inspection Guide LOT-1 Tables LOT-2 Animal Welfare Inspection Guide 09/2013-01 Chapter Introduction 1 Contents Purpose 1-2 Philosophy 1-2 Scope 1-2 Disclaimer 1-2 Meaning of Should, May, and Must 1-2 Conventions 1-3 Advisories 1-3 Boldface 1-4 Bullets 1-4 Chapters 1-4 Contents 1-5 Control Data 1-5 Decision Tables 1-5 Examples 1-5 Footnotes 1-5 Heading Levels 1-6 Hyperlinks to Tables, Figures, and Headings 1-6 Italics 1-6 Numbering Scheme 1-7 Transmittal Number 1-7 Using the Inspection Guide 1-7 Reporting Questions or Concerns With the Inspection Guide 1-7 Inspection Guide Updates 1-8 Ordering Additional Inspection Guides and Revisions 1-8 Navigating Adobe® PDF Documents 1-8 The Menu Bar 1-9 The Tool Bar 1-10 Navigation Bar with Bookmarks 1-11 Document Pane 1-12 Navigating the PDF Document 1-12 09/2013-01 Animal Welfare Inspection Guide 1-1 Introduction Purpose Purpose The purpose of the Animal Welfare Inspection Guide is to provide an aid for APHIS Animal Care personnel when inspecting USDA licensed and registered facilities.
Load more

Recommended publications
  • Flash Player and Linux
    Flash Player and Linux Ed Costello Engineering Manager Adobe Flash Player Tinic Uro Sr. Software Engineer Adobe Flash Player 2007 Adobe Systems Incorporated. All Rights Reserved. Overview . History and Evolution of Flash Player . Flash Player 9 and Linux . On the Horizon 2 2007 Adobe Systems Incorporated. All Rights Reserved. Flash on the Web: Yesterday 3 2006 Adobe Systems Incorporated. All Rights Reserved. Flash on the Web: Today 4 2006 Adobe Systems Incorporated. All Rights Reserved. A Brief History of Flash Player Flash Flash Flash Flash Linux Player 5 Player 6 Player 7 Player 9 Feb 2001 Dec 2002 May 2004 Jan 2007 Win/ Flash Flash Flash Flash Flash Flash Flash Mac Player 3 Player 4 Player 5 Player 6 Player 7 Player 8 Player 9 Sep 1998 Jun 1999 Aug 2000 Mar 2002 Sep 2003 Aug 2005 Jun 2006 … Vector Animation Interactivity “RIAs” Developers Expressive Performance & Video & Standards Simple Actions, ActionScript Components, ActionScript Filters, ActionScript 3.0, Movie Clips, 1.0 Video (H.263) 2.0 Blend Modes, New virtual Motion Tween, (ECMAScript High-!delity machine MP3 ed. 3), text, Streaming Video (ON2) video 5 2007 Adobe Systems Incorporated. All Rights Reserved. Widest Reach . Ubiquitous, cross-platform, rich media and rich internet application runtime . Installed on 98% of internet- connected desktops1 . Consistently reaches 80% penetration within 12 months of release2 . Flash Player 9 reached 80%+ penetration in <9 months . YUM-savvy updater to support rapid/consistent Linux penetration 1. Source: Millward-Brown September 2006. Mature Market data. 2. Source: NPD plug-in penetration study 6 2007 Adobe Systems Incorporated. All Rights Reserved.
    [Show full text]
  • Actionscript 3.0 from the Ground up Tour
    Adobe Presents Colin Moock’s ActionScript 3.0 From the Ground Up Tour Materials provided by O’Reilly Media, Inc. Welcome Key Learning Welcome to the ActionScript 3.0: From the Ground Up Tour! In collaboration with Colin Moock, FITC Design and Technology The following table lists some of today’s most important concepts. Events, O’Reilly, and participating academic institutions around the world, Adobe is thrilled to bring you this world-class day of training. Following the tradition of Flex Camp (http://flex.org/camp/) and the onAIR bus tour (http://onair.adobe.com/), this Concept Example lecture is an important part of Adobe’s ongoing initiative to bring knowledge to the development community. Classes are blueprints for objects. class VirtualPet { At Adobe, we understand that a tool is only useful when you know how to use it. And we’re committed to helping you gain that knowledge. So sit back, get ready for a high-paced day of learning, and most of all have fun! } Objects (or instances) are the things in a program, new VirtualPet() Links and Resources such as a number, a car, a button, a point in time The entire set of notes for today’s lecture are available at: Some classes are built into ActionScript, others are MovieClip, TextField, Sound, String custom-made. http://moock.org/lectures/groundUpAS3 A package contains a class so its name doesn’t package zoo { The code for the virtual zoo application can be obtained at: conflict with other names. class VirtualPet { http://moock.org/eas3/examples/moock_eas3_examples/virtualzoo_final } For a prose version of today’s lecture in book form, see Colin Moock’s Essential ActionScript 3.0 (O’Reilly, 2007).
    [Show full text]
  • Optimizing Actionscript Bytecode Using LLVM
    Optimizing ActionScript Bytecode using Replace with LLVM a graphic White Master 5.5” Tall & 4.3” Wide 10/2/2009 Scott Petersen Adobe Systems, Inc. Copyright 2009 Adobe Systems Incorporated. All rights reserved. Adobe confidential. 1 ActionScript 3 . Adobe Flash/AIR app development language . EcmaScript based – “JavaScript with classes and types” . var x; // implicitly a variant – JS style . var x:int; // x is an int! . var x:*; // explicitly a variant . ActionScript Bytecode (ABC) reminiscent of JVM bytecode . Verified . Stack oriented . Object oriented ® Copyright 2009 Adobe Systems Incorporated. All rights reserved. Adobe confidential. 2 ActionScript 3 . JIT compiler + interpreter + garbage collector + basic support library in around 1.5M uncompressed, 600k compressed for x86 . Open Source Tamarin Project http://www.mozilla.org/projects/tamarin . Straightforward AS3 compiler . Effectively non-optimizing ® Copyright 2009 Adobe Systems Incorporated. All rights reserved. Adobe confidential. 3 ActionScript 3 Performance . Performance for AS => AS3 compiler + Tamarin JIT . Roughly 1.2% of native optimized C (Scimark2 numeric benchmark) . Performance for C => C/LLVM based frontend (Alchemy) + Tamarin JIT . Roughly 30% of native optimized C (Scimark2 numeric benchmark) . Performance for Java => javac + JRE 6 . Roughly 60% of native optimized C (Scimark2 numeric benchmark) ® Copyright 2009 Adobe Systems Incorporated. All rights reserved. Adobe confidential. 4 ActionScript 3 Performance . C code running on the Tamarin JIT is >20x faster than AS3! . Why is C code so fast on Tamarin? . Why is AS3 code so slow on Tamarin? . Alchemy generated code . Avoids some known performance pitfalls in Tamarin . AS3 has a variant type – boxing and unboxing is expensive – Alchemy avoids this . AS3 often does many object allocations, taxing the GC – Alchemy uses a single “ram” object with fast access opcodes .
    [Show full text]
  • Tion Thomas EA Graphics Lunch Presentation
    Tion Thomas EA Graphics Lunch Presentation Software Engineering Intern Central Technology Group – Apt Purdue University – MS ‘09 Mentor: Anand Kelkar Manager: Fazeel Gareeboo EA Company Overview Founded in 1982 Largest 3rd party game publisher in the world Net revenue of $3.67 billion in FY 2008 #1 mobile game publisher (acquired JAMDAT) Multi-Platform philosophy Has/owns development studios all over the globe: Bioware/Pandemic (Bioshock, Mercenaries) Criterion (Burnout, Black) Digital Illusions (Battlefield series) Tiburon (Madden) Valve (Half-Life) Crytek (Crysis) EA Company Overview cont… 4 Major Brands/Divisions: EA Sports (FIFA, Madden, NBA, NFL, Tiger Woods, NASCAR) EA Sports Freestyle (NBA Street, NFL Street, FIFA Street, SSX) EA (Medal of Honor, C&C, Need For Speed, SIMS, Spore, Dead Space) POGO (Casual web based games) Currently has 4 entries on the top selling franchises of all time list: #3 - Sims (100 million) #5 - Need For Speed (80 million) #7 – Madden (70 million) #9 - FIFA (65 million) EA Is Unique Sheer size breaks the traditional game developer paradigm Bound by multi-platform technology Long history with titles on almost every console that ever existed Most studios have annual cycles that cannot be broken Both developer and publisher with ownership in many huge studios Origin Of Tiburon Founded by 3 programmers in Longwood, FL First title was MechWarrior for SNES First Madden title was Madden 96 for Genesis, SNES Acquired by EA in 1998 How Tiburon Got Madden Originally, EA contracted Visual
    [Show full text]
  • VULNERABLE by DESIGN: MITIGATING DESIGN FLAWS in HARDWARE and SOFTWARE Konoth, R.K
    VU Research Portal VULNERABLE BY DESIGN: MITIGATING DESIGN FLAWS IN HARDWARE AND SOFTWARE Konoth, R.K. 2020 document version Publisher's PDF, also known as Version of record Link to publication in VU Research Portal citation for published version (APA) Konoth, R. K. (2020). VULNERABLE BY DESIGN: MITIGATING DESIGN FLAWS IN HARDWARE AND SOFTWARE. General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal ? Take down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. E-mail address: [email protected] Download date: 07. Oct. 2021 VULNERABLE BY DESIGN: MITIGATING DESIGN FLAWS IN HARDWARE AND SOFTWARE PH.D. THESIS RADHESH KRISHNAN KONOTH VRIJE UNIVERSITEIT AMSTERDAM, 2020 Faculty of Science The research reported in this dissertation was conducted at the Faculty of Science — at the Department of Computer Science — of the Vrije Universiteit Amsterdam This work was supported by the MALPAY consortium, consisting of the Dutch national police, ING, ABN AMRO, Rabobank, Fox-IT, and TNO.
    [Show full text]
  • Virtual Machines for Dynamic Languages Ausgewählte Kapitel Der Systemsoftwaretechnik, WS2021
    Virtual Machines for Dynamic Languages Ausgewählte Kapitel der Systemsoftwaretechnik, WS2021 Mark Deutel Friedrich-Alexander-University Erlangen-Nürnberg (FAU) Erlangen, Germany [email protected] ABSTRACT threading model. It is common that once a dynamic language has A common approach to execute dynamic languages is inside a vir- grown popular enough the interpreter is extended by a just-in-time tual machine (VM), usually implemented in a low level system (JIT) compiler to more efficiently execute interpreted code. language like C. Such VMs have to support the often complex However this approach does not come without problems. The syntax and semantics of the dynamic languages they are hosting. effort required to write a complete virtual machine from scratch Additionally, some properties of dynamic language code can only is huge. It also forces the language implementer to deal with plat- be inferred at runtime making the optimization of code execution form or target architecture specific details. This makes implement- another challenging task. Therefore, it is hardly possible to provide ing a VM time consuming, error prone, and complicated to port general purpose implementations that support a large range of to other systems. Additionally, modern dynamic languages like different dynamic languages. Furthermore, many commonly used Python, Ruby or JavaScript evolve rapidly and have complex syn- dynamic languages such as Python or Javascript are still evolving tax and semantics. This not only makes it hard to represent the which means that their VMs have to adapt constantly. This implies language properly in low level code, but makes maintenance of that it is necessary to write and maintain a sufficiently elaborated existing VM implementations a complicated task as well.
    [Show full text]
  • Building on Nature: Area-Based Conservation As a Key Tool for Delivering Sdgs
    Area-based conservation as a key tool for delivering SDGs CITATION For the publication: Kettunen, M., Dudley, N., Gorricho, J., Hickey, V., Krueger, L., MacKinnon, K., Oglethorpe, J., Paxton, M., Robinson, J.G., and Sekhran, N. 2021. Building on Nature: Area-based conservation as a key tool for delivering SDGs. IEEP, IUCN WCPA, The Nature Conservancy, The World Bank, UNDP, Wildlife Conservation Society and WWF. For individual case studies: Case study authors. 2021. Case study name. In: Kettunen, M., Dudley, N., Gorricho, J., Hickey, V., Krueger, L., MacKinnon, K., Oglethorpe, J., Paxton, M., Robinson, J.G., and Sekhran, N. 2021. Building on Nature: Area-based conservation as a key tool for delivering SDGs. IEEP, IUCN WCPA, The Nature Conservancy, The World Bank, UNDP, Wildlife Conservation Society and WWF. CORRESPONDING AUTHORS Nigel Dudley ([email protected]) and Marianne Kettunen ([email protected]) PARTNERS Institute for European Environmental Policy (IEEP) IUCN World Commission on Protected Areas (WCPA) The Nature Conservancy (TNC) The World Bank Group UN Development Programme (UNDP) Wildlife Conservation Society (WCS) WWF DISCLAIMER The information and views set out in this publication are those of the authors and do not necessarily reflect official opinions of the institutions involved. ACKNOWLEDGEMENTS This report and the work underpinning it has benefitted from the support of the following people: Sophia Burke (AmbioTEK CIC), Andrea Egan (UNDP), Marie Fischborn (PANORAMA), Barney Long (Re-Wild), Melanie McField (Healthy Reefs), Mark Mulligan (King’s College, London), Caroline Snow (proofreading), Sue Stolton (Equilibrium Research), Lauren Wenzel (NOAA), and from the many case study authors named individually throughout the publication.
    [Show full text]
  • Javascript: the First 20 Years
    JavaScript: The First 20 Years ALLEN WIRFS-BROCK, Wirfs-Brock Associates, Inc., USA BRENDAN EICH, Brave Software, Inc., USA Shepherds: Sukyoung Ryu, KAIST, South Korea Richard P. Gabriel: poet, writer, computer scientist How a sidekick scripting language for Java, created at Netscape in a ten-day hack, ships first as a de facto Web standard and eventually becomes the world’s most widely used programming language. This paper tells the story of the creation, design, evolution, and standardization of the JavaScript language over the period of 1995–2015. But the story is not only about the technical details of the language. It is also the story of how people and organizations competed and collaborated to shape the JavaScript language which dominates the Web of 2020. CCS Concepts: • General and reference ! Computing standards, RFCs and guidelines; • Information systems ! World Wide Web; • Social and professional topics ! History of computing; History of programming languages; • Software and its engineering ! General programming languages; Scripting languages. Additional Key Words and Phrases: JavaScript, ECMAScript, Standards, Web browsers, Browser game theory, History of programming languages ACM Reference Format: Allen Wirfs-Brock and Brendan Eich. 2020. JavaScript: The First 20 Years. Proc. ACM Program. Lang. 4, HOPL (June 2020), 190 pages. https://doi.org/10.1145/3386327 1 INTRODUCTION In 2020, the World Wide Web is ubiquitous with over a billion websites accessible from billions of Web-connected devices. Each of those devices runs a Web browser or similar program which is able to process and display pages from those sites. The majority of those pages embed or load source code written in the JavaScript programming language.
    [Show full text]
  • Make JIT-Spray Great Again
    Make JIT-Spray Great Again Robert Gawlik and Thorsten Holz Ruhr-Universität Bochum August 13/14 2018 – Baltimore JIT Overview JIT Just-In-Time Compilation (JIT) • Generate native machine code from higher-level language JavaScript PHP Java x86_32, x86_64, ARM, AArch64 ActionScript ... • Performance gain compared to interpreted execution JIT Just-In-Time Compilation (JIT) • Several compilers and optimization layers Baseline, Baseline, JS: IonMonkey DFG, FTL Java: HotSpot JIT ChakraCore (2 Tier JIT) TurboFan PHP: HHVM JIT ActionScript: Linux Kernel: .Net: NanoJIT eBPF RyuJIT JIT Just-In-Time Compilation (JIT) • Several compilers and optimization layers Baseline, Baseline, JS: IonMonkey DFG, FTL Java: HotSpot JIT ChakraCoreMore than 13 compilation engines. (2 TierWhat JIT) could TurboFanpossibly go wrong? PHP: HHVM JIT ActionScript: Linux Kernel: .Net: NanoJIT eBPF RyuJIT JIT-Spray (x86) JIT-Spray 1. Hide native instructions in constants of high-level language c = 0xa8909090 x86 Disassembly @ offset 1 c += 0xa8909090 01: 90 nop 02: 90 nop 03: 90 nop 04: a805 test al, 5 06: 90 nop 07: 90 nop Emitted JIT Code 08: 90 nop 00: b8909090a8 mov eax, 0xa8909090 05: 05909090a8 add eax, 0xa8909090 JIT-Spray 1. Hide native instructions in constants of high-level language 2. Force allocations to predictable address regions function JIT(){ predictable?! c = 0xa8909090 0x20202021: 90 nop c += 0xa8909090 0x20202022: 90 nop } 0x20202023: 90 nop 0x20202024: a805 test al, 5 While (not address_hit){ 0x20202025: 90 nop createFuncAndJIT() 0x20202026: 90 nop 0x20202027:
    [Show full text]
  • Mozilla Project and Open
    오픈소스 컨퍼런스 2007 Mozilla Project & Open Web Seokchan Yun Mozilla Korean Community http://www.mozilla.or.kr Agenda • History of Mozilla and Firefox • Mozilla Community and Development • Effects of Firefox’s Success • Mozilla Manifesto • Focus on Open Web • Future of Firefox • How to do for Open Web 2 First Iteration • 1998- Open Sourcing the Browser ¾ Established Mozilla.org community • 1999- Communicator Transformed ¾ Gecko, XPCOM and XPConnect developed ¾ XPFE, XPAT XML, Netlib, XSLT, mathML, and more arrive in Mozilla code-base • 2000- A Breakdown : Netscape 6 ¾ Based on Mozilla 0.6 ¾ Suffered in performance, stability, heavy-weight advertising, and even standards compliance. 3 Second Iteration • 2001- Mozilla 1.0 Menifesto ¾ API compatibility, Library version identification, Enough modularity, ¾ Good performance and memory footprint, Better-than-any- competition standards compliance, Usability • 2002- Mozilla 1.0 ¾ “The Mozilla project has quietly become a key building block in the open source infrastructure.”–Tim O’Reilly • A Breakdown : Netscape 7 ¾ Based on Mozilla 1.0.1 ¾ “Don’t switch browsers” reads headline as reviewers learn that Netscape removed Mozilla’s popular pop-up blocker for Netscape 7. 4 Why Birth of Firefox During the same year that Mozilla 1.0 and Netscape 7 were released, development began on what would become the Firefox web browser. This splinter project was started by a small group of disgruntled Mozilla developers who were extremely disappointed in the Netscape browser and not satisfied with Mozilla's mediocre successes. We believed in the technology that Mozilla had built in the last 4 years, but we knew that commercial organizations like Netscape and Microsoft did not care about making a better browser because it was not in their financial interest to do so.
    [Show full text]
  • 2.2 Tamarin Prover
    Mitigating private key compromise A thesis submitted in fulfillment of the requirements for the award of the degree Doctor of Philosophy from UNIVERSITY OF BIRMINGHAM by Jiangshan Yu School of Computer Science University of Birmingham August 2016 University of Birmingham Research Archive e-theses repository This unpublished thesis/dissertation is copyright of the author and/or third parties. The intellectual property rights of the author or third parties in respect of this work are as defined by The Copyright Designs and Patents Act 1988 or as modified by any successor legislation. Any use made of information contained in this thesis/dissertation must be in accordance with that legislation and must be properly acknowledged. Further distribution or reproduction in any format is prohibited without the permission of the copyright holder. ⃝c Copyright 2016 by Jiangshan Yu All Rights Reserved ii Dedicated to My Parents & Grandparents iii Declaration This is to certify that the work reported in this thesis was done by the author, unless specified otherwise, and that no part of it has been submitted in a thesis to any other university or similar institution. Jiangshan Yu August 12, 2016 iv Abstract Cryptosystems rely on the assumption that the computer end-points can securely store and use cryptographic keys. Yet, this assumption is rather hard to justify in practice. New software vulnerabilities are discovered every day, and malware is pervasive on mobile devices and desktop PCs. This thesis provides research on how to mitigate private key compromise in three different cases. The first case considers compromised signing keys of certificate au- thorities in public key infrastructure.
    [Show full text]
  • Shaver Black Hat Edits 2.Key
    Building and Breaking the Browser Window Snyder Mike Shaver Overview Who the @#&^@#$ are we? A security process tested by millions Lies, damned lies, and statistics New security goodies in future Firefoxen Tools you can use About Mozilla Mozilla is... • a global efort to promote choice & innovation on the Internet • the foremost advocate for users on the Web • an open source project with thousands of code contributors and tens of thousands of non-code contributors • home of the Firefox Web browser • more than 100 million users worldwide Who runs Firefox? 18% of Internet users worldwide; 100 million people. http://www.xitimonitor.com April 2007 Who runs Firefox? Almost 25% of Europe! (Finland loves us: 41%!) Aliens run Firefox… (Market share numbers unavailable.) A security process tested by millions Opening up to lock it down Approach to Security - Transparency • Community supports security testing and review eforts • Code and developer documentation is available to anyone • Security researches can spend their time in analysis and not in reconnaissance • External parties can check our work, do not need to rely on what we tell them • Design online, open meetings (MSFT take great notes!) • Real time updates on vulnerabilities Security Process Self-organizing Security Group is about 85 people representing all aspects of the community Features are security reviewed to ensure compatibility with the overall security model Designed with security in mind Security testing is continuous throughout development process Security updates every 6-8 weeks Threat Modeling Identify entry points into the system Trace data flows through the application Focuses penetration testing efort on specific components Component Security Review Review new features to determine how they impact the security of the product.
    [Show full text]