Open Source Disclosures

Total Page:16

File Type:pdf, Size:1020Kb

Open Source Disclosures SIMPLISAFE OPEN SOURCE DISCLOSURES ------------------------------------------------------------------------------------------------------------------------------------------ EULA OPEN SOURCE SOFTWARE DISCLOSURE FOR THE ANDROID APP ------------------------------------------------------------------------------------------------------------------------------------------ Horizon Wimba JSpeex Description: Android audio de/encoder https://github.com/SourceUtils/jspeex Copyright © 1999-2003 Wimba S.A., All Rights Reserved Copyright © 2002 Jean-March Valin License: This software is the property of Wimba S.A. This software is redistributed under the Xiph.org variant of the BSD license. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: − Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. − Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. − Neither the name of Wimba, the Xiph.org Foundation nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. WARRANTIES: This software is made available by the authors in the hope that it will be useful, but without any warranty. Wimba S.A. is not liable for any consequence related to the use of the provided software. Date: 22nd April 2003 *** Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: − Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. − Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. − Neither the name of the Xiph.org Foundation nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ------------------------------------------------------------------------------------------------------------------------------------------ Polidea RxAndroidBle Description: Android bluetooth helper https://github.com/Polidea/RxAndroidBle Copyright © 2016 Polidea Sp. z o.o License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Android Support Libraries v7 Description: Android support libraries https://developer.android.com/topic/libraries/support-library/packages#v7 Copyright (C) 2012 The Android Open Source Project License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Android Support Libraries v7 CardView Description: Android card view UI https://developer.android.com/guide/topics/ui/layout/cardview Copyright (C) 2015 The Android Open Source Project License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Android Support Libraries v7 Design Support Library Description: Android design tools https://developer.android.com/topic/libraries/support-library/features Copyright (C) 2015 The Android Open Source Project License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ EventBus Description: Android event bus https://github.com/greenrobot/EventBus Copyright (C) 2012-2017 Markus Junginger, greenrobot (http://greenrobot.org) License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Retrofit Description: Android HTTP communicator https://github.com/square/retrofit Copyright 2013 Square, Inc. License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Gson Converter Description: Android HTTP communicator https://github.com/square/retrofit/tree/master/retrofit-converters/gson Copyright 2013 Square, Inc. License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ RxAndroidble Description: Android HTTP communicator https://github.com/Polidea/RxAndroidBle Copyright 2016 Polidea Sp. z o.o License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ RxRelay Description: Android HTTP helper https://github.com/JakeWharton/RxRelay Copyright 2014 Netflix, Inc. Copyright 2015 Jake Wharton License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ google-gson Description: Android JSON (de) serializer https://github.com/google/gson Copyright 2008 Google Inc. License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Ultimately minimal (yet very convenient) logger for Android and Java Description: Log is a super-simple drop-in replacement for android.util.Log that can also be used in normal Java projects. https://github.com/zserge/log Copyright (c) 2015 zserge License: MIT (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Logging Interceptor Description: Android logging helper https://github.com/square/okhttp/tree/master/okhttp-logging-interceptor Copyright 2016 Square, Inc. License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ PinEntryView Description: Android pin entry https://github.com/Philio/PinEntryView Copyright 2014-2015 Phil Bayfield License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ QRGen Description: Android QR code generator https://github.com/kenglxn/QRGen License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Android Support Libraries v7 recyclerview library Description: Android recycler view UI https://developer.android.com/topic/libraries/support-library/features Copyright (C) 2015 The Android Open Source Project License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Android Support Libraries v7 appcompat library Description: Android support compatibility https://developer.android.com/topic/libraries/support-library/features Copyright (C) 2015 The Android Open Source Project License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Butter Knife Compiler Description: Android UI Help https://github.com/JakeWharton/butterknife/tree/master/butterknife-compiler Copyright 2013 Jake Wharton License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Butter Knife Description: Android UI Help https://github.com/JakeWharton/butterknife Copyright 2013 Jake Wharton License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ Android flow layout Description: Android UI Help https://github.com/ApmeM/android-flowlayout Copyright 2011, Artem Votincev (apmem.org) License: Apache License 2.0 (see below) ------------------------------------------------------------------------------------------------------------------------------------------ MaterialProgressBar Description: Android UI Help https://github.com/DreaminginCodeZH/MaterialProgressBar Copyright 2015
Recommended publications
  • Ardour Export Redesign
    Ardour Export Redesign Thorsten Wilms [email protected] Revision 2 2007-07-17 Table of Contents 1 Introduction 4 4.5 Endianness 8 2 Insights From a Survey 4 4.6 Channel Count 8 2.1 Export When? 4 4.7 Mapping Channels 8 2.2 Channel Count 4 4.8 CD Marker Files 9 2.3 Requested File Types 5 4.9 Trimming 9 2.4 Sample Formats and Rates in Use 5 4.10 Filename Conflicts 9 2.5 Wish List 5 4.11 Peaks 10 2.5.1 More than one format at once 5 4.12 Blocking JACK 10 2.5.2 Files per Track / Bus 5 4.13 Does it have to be a dialog? 10 2.5.3 Optionally store timestamps 5 5 Track Export 11 2.6 General Problems 6 6 MIDI 12 3 Feature Requests 6 7 Steps After Exporting 12 3.1 Multichannel 6 7.1 Normalize 12 3.2 Individual Files 6 7.2 Trim silence 13 3.3 Realtime Export 6 7.3 Encode 13 3.4 Range ad File Export History 7 7.4 Tag 13 3.5 Running a Script 7 7.5 Upload 13 3.6 Export Markers as Text 7 7.6 Burn CD / DVD 13 4 The Current Dialog 7 7.7 Backup / Archiving 14 4.1 Time Span Selection 7 7.8 Authoring 14 4.2 Ranges 7 8 Container Formats 14 4.3 File vs Directory Selection 8 8.1 libsndfile, currently offered for Export 14 4.4 Container Types 8 8.2 libsndfile, also interesting 14 8.3 libsndfile, rather exotic 15 12 Specification 18 8.4 Interesting 15 12.1 Core 18 8.4.1 BWF – Broadcast Wave Format 15 12.2 Layout 18 8.4.2 Matroska 15 12.3 Presets 18 8.5 Problematic 15 12.4 Speed 18 8.6 Not of further interest 15 12.5 Time span 19 8.7 Check (Todo) 15 12.6 CD Marker Files 19 9 Encodings 16 12.7 Mapping 19 9.1 Libsndfile supported 16 12.8 Processing 19 9.2 Interesting 16 12.9 Container and Encodings 19 9.3 Problematic 16 12.10 Target Folder 20 9.4 Not of further interest 16 12.11 Filenames 20 10 Container / Encoding Combinations 17 12.12 Multiplication 20 11 Elements 17 12.13 Left out 21 11.1 Input 17 13 Credits 21 11.2 Output 17 14 Todo 22 1 Introduction 4 1 Introduction 2 Insights From a Survey The basic purpose of Ardour's export functionality is I conducted a quick survey on the Linux Audio Users to create mixdowns of multitrack arrangements.
    [Show full text]
  • (A/V Codecs) REDCODE RAW (.R3D) ARRIRAW
    What is a Codec? Codec is a portmanteau of either "Compressor-Decompressor" or "Coder-Decoder," which describes a device or program capable of performing transformations on a data stream or signal. Codecs encode a stream or signal for transmission, storage or encryption and decode it for viewing or editing. Codecs are often used in videoconferencing and streaming media solutions. A video codec converts analog video signals from a video camera into digital signals for transmission. It then converts the digital signals back to analog for display. An audio codec converts analog audio signals from a microphone into digital signals for transmission. It then converts the digital signals back to analog for playing. The raw encoded form of audio and video data is often called essence, to distinguish it from the metadata information that together make up the information content of the stream and any "wrapper" data that is then added to aid access to or improve the robustness of the stream. Most codecs are lossy, in order to get a reasonably small file size. There are lossless codecs as well, but for most purposes the almost imperceptible increase in quality is not worth the considerable increase in data size. The main exception is if the data will undergo more processing in the future, in which case the repeated lossy encoding would damage the eventual quality too much. Many multimedia data streams need to contain both audio and video data, and often some form of metadata that permits synchronization of the audio and video. Each of these three streams may be handled by different programs, processes, or hardware; but for the multimedia data stream to be useful in stored or transmitted form, they must be encapsulated together in a container format.
    [Show full text]
  • Neufuzz: Efficient Fuzzing with Deep Neural Network
    Received January 15, 2019, accepted February 6, 2019, date of current version April 2, 2019. Digital Object Identifier 10.1109/ACCESS.2019.2903291 NeuFuzz: Efficient Fuzzing With Deep Neural Network YUNCHAO WANG , ZEHUI WU, QIANG WEI, AND QINGXIAN WANG China National Digital Switching System Engineering and Technological Research Center, Zhengzhou 450000, China Corresponding author: Qiang Wei ([email protected]) This work was supported by National Key R&D Program of China under Grant 2017YFB0802901. ABSTRACT Coverage-guided graybox fuzzing is one of the most popular and effective techniques for discovering vulnerabilities due to its nature of high speed and scalability. However, the existing techniques generally focus on code coverage but not on vulnerable code. These techniques aim to cover as many paths as possible rather than to explore paths that are more likely to be vulnerable. When selecting the seeds to test, the existing fuzzers usually treat all seed inputs equally, ignoring the fact that paths exercised by different seed inputs are not equally vulnerable. This results in wasting time testing uninteresting paths rather than vulnerable paths, thus reducing the efficiency of vulnerability detection. In this paper, we present a solution, NeuFuzz, using the deep neural network to guide intelligent seed selection during graybox fuzzing to alleviate the aforementioned limitation. In particular, the deep neural network is used to learn the hidden vulnerability pattern from a large number of vulnerable and clean program paths to train a prediction model to classify whether paths are vulnerable. The fuzzer then prioritizes seed inputs that are capable of covering the likely to be vulnerable paths and assigns more mutation energy (i.e., the number of inputs to be generated) to these seeds.
    [Show full text]
  • John Athayde and Bruce Williams — «The Rails View
    What readers are saying about The Rails View This is a must-read for Rails developers looking to juice up their skills for a world of web apps that increasingly includes mobile browsers and a lot more JavaScript. ➤ Yehuda Katz Driving force behind Rails 3.0 and Co-founder, Tilde In the past several years, I’ve been privileged to work with some of the world’s leading Rails developers. If asked to name the best view-layer Rails developer I’ve met, I’d have a hard time picking between two names: Bruce Williams and John Athayde. This book is a rare opportunity to look into the minds of two of the leading experts on an area that receives far too little attention. Read, apply, and reread. ➤ Chad Fowler VP Engineering, LivingSocial Finally! An authoritative and up-to-date guide to everything view-related in Rails 3. If you’re stabbing in the dark when putting together your Rails apps’ views, The Rails View provides a big confidence boost and shows how to get things done the right way. ➤ Peter Cooper Editor, Ruby Inside and Ruby Weekly The Rails view layer has always been a morass, but this book reins it in with details of how to build views as software, not just as markup. This book represents the wisdom gained from years’ worth of building maintainable interfaces by two of the best and brightest minds in our business. I have been writing Ruby code for over a decade and Rails code since its inception, and out of all the Ruby books I’ve read, I value this one the most.
    [Show full text]
  • Design of a Handset for the IP Multimedia Subsystem a Case Study
    Design of a Handset for the IP Multimedia Subsystem A Case Study James Sunil Selvam ITTIAM Systems [email protected] IMS Architecture OSA AS GSM SCF Application Layer OSA-SCS SIP AS IM-SSF Session Control CSCF Layer HSS GPRS, CDMA MGCF 802.11, DSL SIP Media Transport Layer Gateway EndPoint PSTN PTT, IM, VVoIP VoIP PTT, IM, VVoIP Hardware Block Diagram MIC LCD / Audio TOUCH Codec Speaker/ SCREEN Headphone GSM/ Keypad GPRS JTAG PROCESSOR WLAN Serial Board Control Flash/ Power SDRAM USB Reg TI Innovator Kit based on OMAP1510 Customised Hardware Based on OMAP™ Innovator Kit WLAN NOISE SUPRESSOR R O USB1 USB DWL-G122 T C TRANSCEIVER WLAN E 3.3V N N 5V O C GSM/ SIM E C GPRS CARD A F R E UART2 GM47 T LEVEL GSM/ N I SHIFTER GPRS R O T A MIC V O SPEAKER N N I POWER 2.75V (LEVEL SHIFTER) 5V POWER CONVERTERS 3.6V (GM47) Implementation Hardware Software Block Level SIP : oSIP Linux 2.6.16 RTP/RTCP : oRTP Circuit Design Audio Codec : Kernel Dep. G711, SPEEX, GSM Artwork Driver Management of SIM Test Programs Air Interface : GM47 TI Innovator Device + Custom Hardware Kernel Related Application Services VoIP : Linphone UA GUI Ergonomics Packaging ID Test Setup SIP Proxy & Registrar Ethernet Linphone UA Linphone UA IMS Handset Test Setup Integrated Product IMS Handset Design of a Handset for the IP Multimedia Subsystem - A Case Study James Selvam ITTIAM Systems (Pvt) Ltd Part 1: IMS Why IMS? • Internet – Ease of service creation & provision – Open protocols & large professional talent – Wealth of information • Cellular World – Service on the move
    [Show full text]
  • Codec Is a Portmanteau of Either
    What is a Codec? Codec is a portmanteau of either "Compressor-Decompressor" or "Coder-Decoder," which describes a device or program capable of performing transformations on a data stream or signal. Codecs encode a stream or signal for transmission, storage or encryption and decode it for viewing or editing. Codecs are often used in videoconferencing and streaming media solutions. A video codec converts analog video signals from a video camera into digital signals for transmission. It then converts the digital signals back to analog for display. An audio codec converts analog audio signals from a microphone into digital signals for transmission. It then converts the digital signals back to analog for playing. The raw encoded form of audio and video data is often called essence, to distinguish it from the metadata information that together make up the information content of the stream and any "wrapper" data that is then added to aid access to or improve the robustness of the stream. Most codecs are lossy, in order to get a reasonably small file size. There are lossless codecs as well, but for most purposes the almost imperceptible increase in quality is not worth the considerable increase in data size. The main exception is if the data will undergo more processing in the future, in which case the repeated lossy encoding would damage the eventual quality too much. Many multimedia data streams need to contain both audio and video data, and often some form of metadata that permits synchronization of the audio and video. Each of these three streams may be handled by different programs, processes, or hardware; but for the multimedia data stream to be useful in stored or transmitted form, they must be encapsulated together in a container format.
    [Show full text]
  • Html Cheat Sheet
    BEGINNER’S_ ​ HTML CHEAT SHEET Main root 2 Document metadata 2 Sectioning root 3 Content sectioning 3 Text content 4 Inline text semantics 6 Image and multimedia 8 Scripting 9 Demarcating edits 9 Table content 9 Forms 11 Interactive elements 12 WebsiteSetup.org - Beginner’s HTML Cheat Sheet ​ 1 Main root <html> … </html> The HTML <html> element represents the root (top-level element) of an HTML document, so it is also referred to as the root element. All other elements must be descendants of this element. Example: <!DOCTYPE html> <html lang="en"> <head>...</head> <body>...</body> </html> Document metadata <head> … </head> The HTML <head> element contains machine-readable information (metadata) about the document, like its title, scripts, and style sheets. <link> The HTML External Resource Link element (<link>) specifies relationships between the current document and an external resource. This element is most commonly used to link to stylesheets, but is also used to establish site icons (both "favicon" style icons and icons for the home screen and apps on mobile devices) among other things. <meta> The HTML <meta> element represents metadata that cannot be represented by other HTML meta-related elements, like <base>, <link>, <script>, <style> or <title> <style> … </style> The HTML <style> element contains style information for a document, or part of a document. <title> … </title> The HTML Title element (<title>) defines the document's title that is shown in a browser's title bar or a page's tab. Example: WebsiteSetup.org - Beginner’s HTML Cheat Sheet ​ 2 <!DOCTYPE html> <html lang="en"> <head>...</head> <body>...</body> </html> Sectioning root <body> … </body> The HTML <body> Element represents the content of an HTML document.
    [Show full text]
  • Release 0.23~Git Max Kellermann
    Music Player Daemon Release 0.23~git Max Kellermann Sep 24, 2021 CONTENTS: 1 User’s Manual 1 1.1 Introduction...............................................1 1.2 Installation................................................1 1.3 Configuration...............................................4 1.4 Advanced configuration......................................... 12 1.5 Using MPD................................................ 14 1.6 Advanced usage............................................. 16 1.7 Client Hacks............................................... 18 1.8 Troubleshooting............................................. 18 2 Plugin reference 23 2.1 Database plugins............................................. 23 2.2 Storage plugins.............................................. 24 2.3 Neighbor plugins............................................. 25 2.4 Input plugins............................................... 25 2.5 Decoder plugins............................................. 27 2.6 Encoder plugins............................................. 32 2.7 Resampler plugins............................................ 33 2.8 Output plugins.............................................. 35 2.9 Filter plugins............................................... 42 2.10 Playlist plugins.............................................. 43 2.11 Archive plugins.............................................. 44 3 Developer’s Manual 45 3.1 Introduction............................................... 45 3.2 Code Style...............................................
    [Show full text]
  • Microdata 184 Cross-Document Messaging 187 Accessible Rich Internet Applications (ARIA) 188 Accessibility 188 in Conclusion 191
    Mobile HTML5 Estelle Weyl Mobile HTML5 by Estelle Weyl Copyright © 2014 Estelle Weyl. 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]. Editors: Simon St. Laurent and Meghan Blanchette Indexer: Lucie Haskins Production Editor: Kristen Brown Cover Designer: Randy Comer Copyeditor: Kiel Van Horn Interior Designer: David Futato Proofreaders: Troy Mott and Jasmine Kwityn Illustrator: Rebecca Demarest November 2013: First Edition Revision History for the First Edition: 2013-11-12: First release See http://oreilly.com/catalog/errata.csp?isbn=9781449311414 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Mobile HTML5, the image of a Racket-tailed Drongo, 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 trade‐ mark 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 author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. ISBN: 978-1-449-31141-4 [LSI] Table of Contents Introduction.
    [Show full text]
  • HTML5 Cheatsheet 2019
    CHEAT SHEET HTML5 WEB DEVELOPMENT Created by @Manz ( https://twitter.com/Manz ) https://lenguajehtml.com/ S HTML Syntax Tag structure C Comment Syntax Dev annotations S Social metadata For social networks HTML TAG/ATTRIBUTE SYNTAX HTML COMMENT SYNTAX FACEBOOK OPEN GRAPH <tag attribute="value"> content </tag> <!-- text without effects on webpage --> <meta> metadata tag for open graph property metadata type open graph D Document tags HTML main structure H Head tags Header & document metadata content metadata value open graph MAIN TAGS RELATIONS REQUIRED METADATA PROPERTIES <!DOCTYPE html> HTML5 document <link> document relation og:title title of your object <html> document content root tag href link to related document og:type type of your object <head> metadata header related docs hreflang code doc language en, es... music video article book <body> page content visible content type mime hint type for browser profile website title set title to stylesheet set og:image image url for preview G Global Attributes for all elements sizes hint size for favicon 64x64, 96x96 og:url canonical & absolute url DOM / STYLE ATTRIBUTES rel relation type with other document OPTIONAL METADATA PROPERTIES id element identifier unique per page BASIC RELATION og:audio complementary audio url class element class multiple per page alternate link to alternate version og:description 1-2 sentence descr. slot element slot reference to <slot> author link to author URL og:determiner word auto, the, a, an, ... style inline CSS styles css properties help link to help URL
    [Show full text]
  • What Is Open Source?
    Putting OPen SOurce tO WOrk in the enterPriSe: A guide tO riSkS And OPPOrtunitieS © Copyright 2007 SAP AG. All rights reserved. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, No part of this publication may be reproduced or transmitted in Massachusetts Institute of Technology. any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed Java is a registered trademark of Sun Microsystems, Inc. without prior notice. JavaScript is a registered trademark of Sun Microsystems, Inc., Some software products marketed by SAP AG and its distributors used under license for technology invented and implemented contain proprietary software components of other software by Netscape. vendors. MaxDB is a trademark of MySQL AB, Sweden. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP products and services IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, mentioned herein as well as their respective logos are trademarks MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, or registered trademarks of SAP AG in Germany and in several xSeries, zSeries, System i, System i5, System p, System p5, System x, other countries all over the world. All other product and service System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, names mentioned are the trademarks of their respective compa- Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, nies. Data contained in this document serves informational OpenPower and PowerPC are trademarks or registered purposes only.
    [Show full text]
  • Modeling and Analysis of Next Generation 9-1-1 Emergency Medical Dispatch Protocols
    MODELING AND ANALYSIS OF NEXT GENERATION 9-1-1 EMERGENCY MEDICAL DISPATCH PROTOCOLS Neeraj Kant Gupta, BE(EE), MBA, MS(CS) Dissertation Prepared for the Degree of DOCTOR OF PHILOSOPHY UNIVERSITY OF NORTH TEXAS August 2013 APPROVED: Ram Dantu, Major Professor Kathleen Swigger, Committe Member Paul Tarau, Committee Member Sam G Pitroda Committee Member Barrett Bryant, Chair of the Department of Computer Science and Engineering Costas Tsatsoulis, Dean of the College of Engineering Mark Wardell, Dean of the Toulouse Graduate School Gupta, Neeraj Kant. Modeling and Analysis of Next Generation 9-1-1 Emergency Medical Dispatch Protocols. Doctor of Philosophy (Computer Science), August 2013, 192 pp., 12 tables, 72 figures, bibliography, 196 titles. In this thesis I analyze and model the emergency medical dispatch protocols for Next Generation 9-1-1 (NG9-1-1) architecture. I have identified various technical aspects to improve the NG9-1-1 dispatch protocols. The specific contributions in this thesis include developing applications that use smartphone sensors. The CPR application uses the smartphone to help administer effective CPR even if the person is not trained. The application makes the CPR process closed loop, i.e., the person who administers the CPR as well as the 9-1-1 operator receive feedback and prompt from the application about the correctness of the CPR. The breathing application analyzes the quality of breathing of the affected person and automatically sends the information to the 9-1-1 operator. In order to improve the human computer interface at the caller and the operator end, I have analyzed Fitts law and extended it so that it can be used to improve the instructions given to a caller.
    [Show full text]