DOCSLIB.ORG

Esa Study Contract Report

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Esa Study Contract Report ESA STUDY CONTRACT REPORT ESA Contract No: Subject: Contractor: ESA ITT Number Current and Future Tech- Distributed Systems Group, AO/3-12280/07/NL/CB nologies for Collaborative Vienna University of Tech- Working Environments nology ESA CR() No: No of volumes: 1 Contractor’s Reference: This Volume No: 1 TEUN Abstract: This document reports the final, detailed result of the study on current and future technologies for collaborative working environments (CWEs). The goal of this study is to analyze current CWEs and whether they and their future trends are suitable for large- scale multinational organizations. To this end, we have analyzed the structure of large-scale organizations in general, and of ESA in particular, with respect to organization, geographical distribution, and IT environments. Requirements for CWEs used in collaborative work are presented. Based on an initial list of criteria given by ESA, we have revised and extended the list to introduce a comprehensive set of criteria for evaluating CWEs. The state-of-the- art CWEs are discussed and classified. We have selected 15 representative CWE products and evaluated and compared them in detail. From the evaluation and comparison of CWE products, we have presented our findings of current issues and future trends of CWEs. In particular, existing products provide many features required by large-scale and multinational organizations but those features are not well-integrated into a single system. Due to the complexity of collaborative work within those organizations, often many CWEs are used in parallel and it is not easy to integrate those CWEs together. The work described in this report was done under ESA Contract. Responsibility for the contents resides in the author or organisation that prepared it. Name of authors: Florian Skopik, Hong-Linh Truong, Schahram Dustdar Name of ESA study manager: ESA Budget Heading: Tamas Vinko, Ian Carnelli General Studies Programme This page is intentionally left blank. Current and Future Technologies for Collaborative Working Environments1 Florian Skopik, Hong-Linh Truong and Schahram Dustdar Distributed Systems Group Vienna University of Technology, Austria {skopik,truong,dustdar}@infosys.tuwien.ac.at May 21, 2008 1This study is funded by ESA under the contract ESA ITT Number AO/3-12280/07/NL/CB. We thank ESA Advanced Concepts Team, in particular Tamas Vinko, Ian Carnelli and Andres Galvez, for their help on providing information related to ESA’s organizational structure and CWE requirements and for providing useful comments and suggestions for this study. This page is intentionally left blank. Abstract This document reports the final, detailed result of the study on current and future technologies for collaborative working environments (CWEs). The goal of this study is to analyze current CWEs and whether they and their future trends are suitable for large-scale multinational organi- zations. To this end, we have analyzed the structure of large-scale organizations in general, and of ESA in particular, with respect to organization, geographical distribution, and IT environments. Requirements for CWEs used in collaborative work are presented. Based on an initial list of criteria given by ESA, we have revised and extended the list to introduce a comprehensive set of criteria for evaluating CWEs. The state-of-the-art CWEs are discussed and classified. We have selected 15 representative CWE products and evaluated and compared them in detail. From the evaluation and comparison of CWEs products, we have presented our findings of current issues and future trends of CWEs. In particular, existing products provide many features required by large-scale and multinational organizations but those features are not well-integrated into a single system. Due to the complexity of collaborative work within those organizations, often many CWEs are used in parallel and it is not easy to integrate those CWEs together. This page is intentionally left blank. Contents 1 Introduction 4 1.1Purpose......................................... 4 1.2ObjectivesandApproach............................... 4 1.3StructureofthisReport................................ 5 2 Structure of Large-scale Organizations and CWE Requirements 7 2.1OverviewofLarge-ScaleEnterprises/Organizations................. 7 2.1.1 ITInfrastructure................................ 7 2.1.2 Accessibility . 9 2.1.3 InformationSecurityConcerns........................ 10 2.2StructureofESA.................................... 10 2.2.1 Overview.................................... 10 2.2.2 ESA’sRequirementsforCWEs........................ 11 2.3RequirementsforCWESoftware........................... 13 2.3.1 Security..................................... 14 2.3.2 Availability, Reliability and Serviceability (RAS) . 15 2.3.3 Scalability . 15 2.3.4 Usability/Acceptance . 15 2.3.5 Extensibility . 15 2.3.6 System Integration and Supported Platforms . 15 2.3.7 ComplianceandLegalIssues......................... 16 2.3.8 Mobility..................................... 16 2.3.9 Technical Support and Updates . 16 3 Evaluation Criteria 17 3.1CriteriaDescription.................................. 17 3.2CatalogofCriteria................................... 17 3.2.1 GeneralInformation.............................. 18 3.2.2 Software Development and Organizational Criteria . 18 3.2.3 SystemPrerequisitesandInstallation.................... 19 3.2.4 OverallSystemProperties........................... 19 3.2.5 Application and Task Support Criteria . 20 3.2.6 UsageCriteria................................. 20 4 Classification and Selection of CWEs 21 4.1Classification...................................... 21 4.2BriefSurveys...................................... 22 4.2.1 FileManagementSystems........................... 22 4.2.2 GroupwareSystems.............................. 23 4.2.3 Real-timeOfficeApplications......................... 25 4.2.4 Real-time Audio, Video and Data Collaboration Systems . 26 4.2.5 Wiki-basedSystems.............................. 27 4.3SelectionLimitations.................................. 27 4.4SelectionSummary................................... 28 1 5 Evaluation 29 5.1EvaluationProceduresandScope........................... 29 5.2Finallistofproductstobesurveyed......................... 30 5.3FileManagementSystems............................... 31 5.3.1 AlfrescoEnterpriseContentManagement.................. 31 5.3.2 BSCW - Basic Support for Cooperative Work . 34 5.3.3 PloneCMS................................... 37 5.3.4 MicrosoftSharepoint.............................. 40 5.3.5 Subversion................................... 43 5.4GroupwareSystems.................................. 46 5.4.1 CollanosWorkplace.............................. 46 5.4.2 eGroupware................................... 49 5.4.3 OracleCollaborationSuite.......................... 52 5.4.4 SimpleGroupware............................... 55 5.5Real-timeOffices.................................... 59 5.5.1 CoOffice..................................... 59 5.5.2 GoogleDocs.................................. 62 5.6 Real-time Audio, Video and Data Collaboration Systems . 64 5.6.1 Coccinella.................................... 64 5.6.2 Skype...................................... 67 5.7WikibasedSystems.................................. 70 5.7.1 MediaWiki................................... 70 5.7.2 MindtouchDekiWiki.............................. 73 5.8ComparisonofEvaluationResults.......................... 75 6 Findings and Future Trends 77 7Conclusion 79 Acronyms and Abbreviations ACT Advanced Concepts Team ACL Access Control List AES Advanced Encryption Standard API Application Programming Interface AS Application Server CRM Customer Relationship Management CMS Content Management System CWE Collaborative Working Environment DMS Document Management System ECM Enterprise Content Management ERP Enterprise Resource Management ESA European Space Agency EU European Union FTP File Transfer Protocol GPL General Public License ICT Information and Communication Technology IIS (Microsoft) Internet Information Server IM Instant Messenger / Instant Messaging IMAP Internet Message Access Protocol IT Information Technology JAAS Java Authentication and Authorization Service JSR Java Specification Request LDAP Lightweight Directory Access Protocol MS Microsoft MSI Microsoft Installer NTLM NT LAN Manager ORM Object Relational Mapping P2P Peer-to-Peer PIM Personal Information Manager PBX Private Branch Exchange REST Representational State Transfer SIP Session Initiation Protocol SMTP Simple Mail Transfer Protocol SoW Statement of Work TUV Vienna University of Technology VoIP Voice over IP WCM Web Content Management WebDAV Web-based Distributed Authoring and Versioning XMPP Extensible Messaging and Presence Protocol 3 Chapter 1 Introduction 1.1 Purpose Recent advances in hardware and software technologies have fostered the collaborative work across administrative/organizational boundaries. Various tools are available for users to conduct joint projects, regardless of the location and the organization of the users. For example, wikis1, SVN2, and document management systems3 allow different users to share and coedit documents, instant messaging4 and voice chat5 allow multiple users to converse online, just to name a few. With the support of existing Collaborative Working Environments (CWEs), many new con- cepts, such as virtual teams and communities, are introduced and realized today. Furthermore, the concept of user participation, such as collaborative blogs6 and collaborative tagging [13], sub-
Load more

Recommended publications
  • Jenkins Declarative Pipeline Checkout Scm Example
    Jenkins Declarative Pipeline Checkout Scm Example Thor confab improbably. Permissible Augie usually damnify some corolla or name-drops unalike. Nicholas remains scenic: she depressurize her chessels doctors too straight? How they evaluate Git branch name itself a Jenkins pipeline using. 'checkout scm' is a great single line to add maybe your script that checks out the commute the Jenkinsfile is crisp from. Confirmed that were very similar to us to other useful by jenkins declarative pipeline checkout scm example, and seeing that. Jenkins Pipeline Checkout Scm Example abound on Jenkins comjavahometechmywebblobmasterJenkins-Declarative-GitFor OnlineClassroom trainings and. BRANCHNAME JENKINS-4565 Declarative Pipeline Example. Jenkins Stash Example. I've key a jenkins pipeline and bow is pulling the pipeline script from scm. If necessary files in the example pipeline code. Feature Request Parallel Stage name for Declarative. Pipeline Pipeline stage Pipeline Declarative Checkout SCM Pipeline checkout. Jenkins Beginner Tutorial 14 How to setup DELIVERY PIPELINE in Jenkins Step by. In turkey first step 1 we checkout project from GitHub and then build it with Maven 2. How to Use the Jenkins Scripted Pipeline BlazeMeter. In simple words Jenkins Pipeline is a combination of plugins that block the integration and implementation of continuous delivery pipelines using Jenkins A pipeline has an extensible automation server for creating simple less complex delivery pipelines as code via pipeline DSL Domain-specific Language. The Declarative Pipeline example above contains the minimum necessary. That is why science would awake to steam a border more with Jenkins Pipelines to present. How do I of environment variables in Jenkins pipeline? Nodelabel def myRepo checkout scm def gitCommit myRepo.
    [Show full text]
  • How to Select a Suitable Tool for a Software Development Project
    HowtoSelect aSuitable Tool foraSoftwareDevelopment Project: Three Case Studies and the Lessons Learned Mark Kibanov, Dominik J. Erdmann, Martin Atzmueller Knowledge and Data Engineering Group, University of Kassel, Germany {kibanov, erdmann, atzmueller}@cs.uni-kassel.de Abstract: This paper describes aframework for evaluating and selecting suitable soft- ware tools for asoftware project, which is easily extendable depending on needs of the project. Foranevaluation, we applied the presented framework in three different projects. These projects use different software development methods (from classical models to Scrum) in different environments (industry and academia). We discuss our experiences and the lessons learned. 1Introduction With the growth of the software industry the number of software products (programs, tools, frameworks) with similar functions has also increased. Therefore, the process of selection of the required software has also become more complex. In this paper,weintroduce a general three-step framework for selecting suitable software for the current project and environment. Furthermore, we describe the application of the framework to three different software projects: These use different software development methods and environments. All three case studies showpromising results and indicate the possibility to apply the suggested framework for awide range of different projects. In these contexts, we discuss our experiences and the lessons learned. The rest of the paper is structured as follows: Section 2discusses related work. After that, Section 3presents the framework, its advantages, disadvantages and the three distinct steps of selecting the software tools. Section 4describes three case studies where we applied the framework and the results we obtained during these case studies. 2Related Work Starting in 1980 with [Saa80], Thomas L.
    [Show full text]
  • Universidad Pol Facultad D Trabajo
    UNIVERSIDAD POLITÉCNICA DE MADRID FACULTAD DE INFORMÁTICA TRABAJO FINAL DE CARRERA ESTUDIO DEL PROTOCOLO XMPP DE MESAJERÍA ISTATÁEA, DE SUS ATECEDETES, Y DE SUS APLICACIOES CIVILES Y MILITARES Autor: José Carlos Díaz García Tutor: Rafael Martínez Olalla Madrid, Septiembre de 2008 2 A mis padres, Francisco y Pilar, que me empujaron siempre a terminar esta licenciatura y que tanto me han enseñado sobre la vida A mis abuelos (q.e.p.d.) A mi hijo icolás, que me ha dejado terminar este trabajo a pesar de robarle su tiempo de juego conmigo Y muy en especial, a Susana, mi fiel y leal compañera, y la luz que ilumina mi camino Agradecimientos En primer lugar, me gustaría agradecer a toda mi familia la comprensión y confianza que me han dado, una vez más, para poder concluir definitivamente esta etapa de mi vida. Sin su apoyo, no lo hubiera hecho. En segundo lugar, quiero agradecer a mis amigos Rafa y Carmen, su interés e insistencia para que llegara este momento. Por sus consejos y por su amistad, les debo mi gratitud. Por otra parte, quiero agradecer a mis compañeros asesores militares de Nextel Engineering sus explicaciones y sabios consejos, que sin duda han sido muy oportunos para escribir el capítulo cuarto de este trabajo. Del mismo modo, agradecer a Pepe Hevia, arquitecto de software de Alhambra Eidos, los buenos ratos compartidos alrrededor de nuestros viejos proyectos sobre XMPP y que encendieron prodigiosamente la mecha de este proyecto. A Jaime y a Bernardo, del Ministerio de Defensa, por haberme hecho descubrir las bondades de XMPP.
    [Show full text]
  • Groupwise Mobility Quick Start for Microsoft Outlook Users
    GroupWise Mobility Quick Start for Microsoft Outlook Users August 2016 GroupWise Mobility Service 2014 R2 allows the Microsoft Outlook client for Windows to run against a GroupWise backend via Microsoft ActiveSync 14.1 protocol. This document helps you set up your Outlook client to access your GroupWise account and provides known limitations you should be aware of while using Outlook against GroupWise. Supported Microsoft Outlook Clients CREATING THE GROUPWISE PROFILE MANUALLY Microsoft Outlook 2013 or 21016 for Windows 1 On the machine, open Control Panel > User Accounts and Family Safety. Microsoft Outlook Mobile App Adding a GroupWise Account to the Microsoft Outlook Client You must configure the Microsoft Outlook client in order to access your GroupWise account. The following instructions assume that the Outlook client is already installed on your machine. You can use the GroupWise Profile Setup utility to set the profile up automatically or you can manually create the GroupWise profile for Outlook. Using the GroupWise Profile Setup Utility Creating the GroupWise Profile Manually 2 Click Mail. 3 (Conditional) If a Mail Setup dialog box is displayed, USING THE GROUPWISE PROFILE SETUP UTILITY click Show Profiles to display the Mail dialog box. You must first obtain a copy of the GWProfileSetup.zip from If GroupWise is installed on the machine, the Profiles your system administrator before following the steps below list includes a GroupWise profile, as shown in the to create the profile on your workstation. following screenshot. You need to keep this profile and create a new profile. 1 Extract the GWProfileSetup.zip to a temporary location on your workstation.
    [Show full text]
  • Efficient Algorithms for Comparing, Storing, and Sharing
    EFFICIENT ALGORITHMS FOR COMPARING, STORING, AND SHARING LARGE COLLECTIONS OF EVOLUTIONARY TREES A Dissertation by SUZANNE JUDE MATTHEWS Submitted to the Office of Graduate Studies of Texas A&M University in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY May 2012 Major Subject: Computer Science EFFICIENT ALGORITHMS FOR COMPARING, STORING, AND SHARING LARGE COLLECTIONS OF EVOLUTIONARY TREES A Dissertation by SUZANNE JUDE MATTHEWS Submitted to the Office of Graduate Studies of Texas A&M University in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY Approved by: Chair of Committee, Tiffani L. Williams Committee Members, Nancy M. Amato Jennifer L. Welch James B. Woolley Head of Department, Hank W. Walker May 2012 Major Subject: Computer Science iii ABSTRACT Efficient Algorithms for Comparing, Storing, and Sharing Large Collections of Evolutionary Trees. (May 2012) Suzanne Jude Matthews, B.S.; M.S., Rensselaer Polytechnic Institute Chair of Advisory Committee: Dr. Tiffani L. Williams Evolutionary relationships between a group of organisms are commonly summarized in a phylogenetic (or evolutionary) tree. The goal of phylogenetic inference is to infer the best tree structure that represents the relationships between a group of organisms, given a set of observations (e.g. molecular sequences). However, popular heuristics for inferring phylogenies output tens to hundreds of thousands of equally weighted candidate trees. Biologists summarize these trees into a single structure called the consensus tree. The central assumption is that the information discarded has less value than the information retained. But, what if this assumption is not true? In this dissertation, we demonstrate the value of retaining and studying tree collections.
    [Show full text]
  • XEP-0113: Simple Whiteboarding
    XEP-0113: Simple Whiteboarding Huib-Jan Imbens mailto:jabber@imbens:nl xmpp:imbens@jabber:org 2003-09-07 Version 0.2 Status Type Short Name Deferred Informational Not yet assigned A proposal for an extremely simple whiteboarding protocol over Jabber. Legal Copyright This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF). Permissions Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the ”Specification”), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specifi- cation, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or sub- stantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or pub- lisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. Warranty ## NOTE WELL: This Specification is provided on an ”AS IS” BASIS, WITHOUT WARRANTIES OR CONDI- TIONS OF ANY KIND, express or implied, including, without limitation,
    [Show full text]
  • Diplomarbeit Kalenderstandards Im Internet
    Diplomarbeit Kalenderstandards im Internet Eingereicht von Reinhard Fischer Studienkennzahl J151 Matrikelnummer: 9852961 Diplomarbeit am Institut für Informationswirtschaft WIRTSCHAFTSUNIVERSITÄT WIEN Studienrichtung: Betriebswirtschaft Begutachter: Prof. DDr. Arno Scharl Betreuender Assistent: Dipl.-Ing. Mag. Dr. Albert Weichselbraun Wien, 20. August 2007 ii Inhaltsverzeichnis Abbildungsverzeichnis vi Abkürzungsverzeichnis vii 1 Einleitung 1 1.1 Problemstellung . 1 1.2 Inhalt und Vorgehensweise . 3 2 Standards für Kalender im Internet 5 2.1 iCalendar und darauf basierende Standards . 6 2.1.1 iCalendar und vCalendar . 6 2.1.2 Transport-Independent Interoperability Protocol (iTIP) . 8 2.1.3 iCalendar Message-Based Interoperability Protocol (iMIP) . 8 2.1.4 iCalendar über WebDAV (WebCAL) . 10 2.1.5 Storage of Groupware Objects in WebDAV (GroupDAV) . 11 2.1.6 Calendaring and Scheduling Extensions to WebDAV (CalDAV) . 12 2.1.7 IETF Calendar Access Protocol (CAP) . 13 2.2 XML-basierte Formate . 15 2.2.1 XML iCalendar (xCal) . 15 2.2.2 RDF Calendar (RDFiCal) . 16 2.2.3 RDFa (RDF/A) . 16 2.2.4 OWL-Time . 17 2.3 Mikroformate (hCalendar) . 18 2.4 SyncML . 20 2.5 Weitere Formate . 21 2.6 Zusammenfassung . 22 iii 3 Offene Kalenderanwendungen im Internet 24 3.1 Server . 24 3.1.1 Citadel/UX . 24 3.1.2 Open-Xchange . 26 3.1.3 OpenGroupware.org . 26 3.1.4 Kolab2 . 27 3.1.5 Weitere Server . 28 3.2 Clients . 29 3.2.1 Mozilla Calendar Project . 29 3.2.2 KDE Kontact . 30 3.2.3 Novell Evolution . 30 3.2.4 OSAF Chandler . 31 3.2.5 Weitere Open-Source- und Closed-Source-Clients .
    [Show full text]
  • Codice Plastic
    Francisco Monteverde “The Cadillac of the SCMs” - eWeek CEO Codice Software www.plasticscm.com [email protected] @plasticscm @plasticscm www.plasticscm.com © 2014 Codice Software Computers, Mobile Phones, Tablets, Internet Services, Video Games, Consoles, Financial Services, Telecommunications, Automobiles, Transportation, Healthcare, Commerce, Distribution, Industrial Manufacturing… … TODAY SOFTWARE IS ALMOST EVERYWHERE….AND INCREASING © 2014 Codice Software VERSION CONTROL IS AN ESSENTIAL FUNCTION WITHIN SOFTWARE DEVELOPMENT © 2014 Codice Software The Problem with Software Development: Limited Productivity, Low Quality Code 1. Development in serial mode (not parallel) creates many dependencies and continuous broken builds 2. Developers need to be connected to central server to use the Version Control tool Distributed Version Control Systems (DVCS) © 2014 Codice Software Introducing Plastic SCM Branching and Merging is GOOD! The Only Commercial Enterprise Distributed Version Control Systems (DVCS) for Teams of Any Size, Enabling Parallel and Distributed Development that works Integrated with Polarion ALM: Closing the GAP between Requirements & Code © 2014 Codice Software Polarion ALM & Plastic SCM Working Together • Plastic SCM integrates with Polarion using “branch per task” and “task per cset” • Branches can be created listing the assigned and open tasks • Alternatively, individual changesets can be linked to Polarion tasks • Quick access from Plastic SCM GUI to Polarion info © 2014 Codice Software Codice Software Company Background Some Global Customers: Funded 2005 Products Plastic SCM & Semantic Merge Investors Bullnet Capital (VC): Valladolid (Spain) & Silicon Valley HQ’s Office Distribution US/Canda, EU, Israel, South Korea © 2014 Codice Software Codice Software in US Developer’s Press Jeff Cogswell Adrian Bridgwater Eric Caoili Heavy Refactoring In Parallel? Plastic SCM 4.0 solution for Plastic SCM is the Cadillac No Problem.
    [Show full text]
  • March/April 2006
    The newsletter for IPFW computer users Information Technology Services March-April 2006 By Joseph McCormick Manager of Client Support his spring, most Indiana counties T will observe Daylight Savings Time Data Security and Your Workstation (DST) for the first time since 1970. In 2006, DST begins at 2 a.m. on the first Sunday in April (April 2) and ends at 2 option involves a reboot which With recent security incidents at a.m. on the last Sunday in October refreshes your workstation, and the (October 29). other campuses and businesses, it has next time you log in to the network, become imperative that we all take Because of modifications to the Trend OfficeScan antivirus steps to protect data accessed through GroupWise, to accommodate the software installed on your Windows our computers. Precautions should change to Daylight Savings Time, your workstation automatically updates. also be taken to protect data stored on calendar items scheduled between April Keep your workstation up-to- any portable devices such as laptops, 2 at 2:00 a.m. and October 29 at 2:00 date with vendor patches and virus disks or flash drives. Here are a few a.m. are now showing up an hour later protection by activating updates key steps that we can all do quickly to than originally scheduled. Unfortunately, promptly when you are signaled that increase security significantly. this problem was unavoidable as we they are ready. Windows XP/2000 adjusted the system to recognize Daylight users: when you see the “msg”. at the Savings time. bottom of your tool bar that says you Your cooperation is key to The only way to correct this have new updates, please click on the providing overall campus problem is to manually change your button and add your updates.
    [Show full text]
  • Higher Inductive Types (Hits) Are a New Type Former!
    Git as a HIT Dan Licata Wesleyan University 1 1 Darcs Git as a HIT Dan Licata Wesleyan University 1 1 HITs 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! They were originally invented[Lumsdaine,Shulman,…] to model basic spaces (circle, spheres, the torus, …) and constructions in homotopy theory 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! They were originally invented[Lumsdaine,Shulman,…] to model basic spaces (circle, spheres, the torus, …) and constructions in homotopy theory But they have many other applications, including some programming ones! 2 Generator for 2 equality of equality Patches Patch a a 2c2 diff b d = < b c c --- > d 3 3 id a a b b
    [Show full text]
  • Freebsd Opengroupware - English
    FreeBSD OpenGroupware - English FreeBSD As Basis For OpenGroupware.org PostgreSQL As Database FreeBSD can currently look back on a history of over 30 PostgreSQL, like BSD, originated at the University of Ca- years. It originated at the University of Berkeley and lifornia and is also distributed under the BSD license. It's FreeBSD evolved over a few intermediate steps into the project one of the oldest and most advanced object-relational founded in 1993 called FreeBSD. The supported architec- database management systems (ORDBMS) in the realm tures are the following: i386, amd64, Alpha, Itanium, of free software and looks back on a development of OpenGroupware.org SPARC, PPC (Mac) and others. over 15 years. PostgreSQL is largely conforming to the FreeBSD has very good support for multiprocessor sys- SQL92/SQL99 standards, that means that all functions in The ideal solution for professional the standards are available and behave as defined; that tems (SMP) and is distributed under the BSD license team communication on the Internet, which grants the user nearly every freedom and is free is not always the case with some commercial and non- commercial SQL database systems. of cost. Apart from having to name the origins of the with FreeBSD and PostgreSQL code, the user may use it in any which way he or she pleases. FreeBSD is a gift to humanity, we are pleased when you use it! FreeBSD has not only got many features, it also has a What is a groupware solution? huge amount of free and open software in its so-called Ports Collection.
    [Show full text]
  • Onapp Admin Guide
    2.0 Admin Guide 2.0 Admin Guide Contents 0. About This Guide ............................................................................................... 5 1. OnApp Overview ................................................................................................ 6 1.1 Servers ................................................................................................................... 6 1.2 Networks ................................................................................................................ 7 1.3 Templates .............................................................................................................. 8 1.4 Virtual Machines .................................................................................................... 8 1.5 Scalability .............................................................................................................. 8 1.6 Availability and Reliability .................................................................................... 8 1.7 Security .................................................................................................................. 9 1.8 API and Integration ............................................................................................... 9 2. OnApp Hardware & Software Requirements ................................................. 10 2.1 Hypervisor Servers ............................................................................................. 10 2.2 Control Panel Server ..........................................................................................
    [Show full text]