DOCSLIB.ORG

Open Source Licenses Fabasoft Software Products

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Open Source Licenses Fabasoft Software Products Open Source Licenses Fabasoft Software Products Copyright © Fabasoft R&D GmbH, Linz, Austria, 2021. All rights reserved. All hardware and software names used are registered trade names and/or registered trademarks of the respective manufacturers. No rights to our software or our professional services, or results of our professional services, or other protected rights can be based on the handing over and presentation of these documents. Fabasoft Software Products 2 Contents 1 Introduction _____________________________________________________________________________________ 4 2 Open Source Licenses ___________________________________________________________________________ 4 Fabasoft Software Products 3 1 Introduction The open source software contained in the Fabasoft software products “Fabasoft Folio”, “Fabasoft Cloud” and “Fabasoft Private Cloud” is licensed under conditions that require to display the following notes. 2 Open Source Licenses The corresponding copyright annotations and terms of license can be found here: Open Source Licenses • AFNetworking (https://github.com/AFNetworking/AFNetworking) • Android Open Source Project (https://source.android.com) • AndroidPdfViewer (https://github.com/barteksc/AndroidPdfViewer) • ANTLR (https://www.antlr2.org/) • Apache Batik (https://github.com/apache/batik) • Apache FOP (https://github.com/apache/fop) • Apache Jena (https://github.com/apache/jena) • Apache POI (https://github.com/apache/poi) • Axis 1 (https://github.com/apache/axis1-java) • Axis 2 (https://github.com/apache/axis2-java) • bzip2 (http://www.bzip.org) • CKEditor (https://github.com/ckeditor/ckeditor-dev/) • CLTokenInputView (https://github.com/rsattar/CLTokenInputView) • CocoaLumberjack (https://github.com/CocoaLumberjack/CocoaLumberjack) • CodeMirror (https://github.com/codemirror/CodeMirror) • CryptoJS (http://code.google.com/p/crypto-js/) • CTAssetsPickerController (https://github.com/chiunam/CTAssetsPickerController) • daemontools (http://cr.yp.to/daemontools.html) • dcraw (http://www.cybercom.net/~dcoffin/dcraw/) • DefinitelyTyped React (https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react) • DefinitelyTyped React DOM (https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom) • DejaVu Fonts (http://dejavu-fonts.org/) • Eclipse (http://www.eclipse.org) • Eclipse BIRT (http://www.eclipse.org/birt) • Expat XML Parser (http://www.libexpat.org/) • FingerprintJS (https://github.com/fingerprintjs/fingerprintjs) • Firebase JavaScript SDK (https://github.com/firebase/firebase-js-sdk) • FireflySung Fonts (http://www.study-area.org/apt/firefly-font/) • Fluent UI React (https://github.com/microsoft/fluentui) Fabasoft Software Products 4 • FullCalendar (http://arshaw.com/fullcalendar/) • GCDWebServer (https://github.com/swisspol/GCDWebServer) • geckodriver (https://github.com/mozilla/geckodriver) • globalize (https://github.com/jquery/globalize) • Google Code Prettify (http://code.google.com/p/google-code-prettify/) • Guava (https://github.com/google/guava) • highlight (http://johannburkard.de/blog/programming/javascript/highlight-javascript-text- higlighting-jquery-plugin.html) • html-entities (https://github.com/mdevils/html-entities) • ICU4C (http://site.icu-project.org) • ImageMagick (http://www.imagemagick.org) • IzPack (http://izpack.org/) • Jakarta Mail (https://github.com/eclipse-ee4j/mail) • Java Servlet API (https://mvnrepository.com/artifact/javax.servlet/javax.servlet-api) • JAX-WS (https://jax-ws.dev.java.net) • Jcrop (https://github.com/tapmodo/Jcrop) • JPEG (http://www.ijg.org/) • jQuery (http://jquery.com/) • jQuery History (https://github.com/balupton/jquery-history) • jQuery scrollintoview (https://github.com/litera/jquery-scrollintoview) • jQuery UI (http://jqueryui.com/) • jquery.maskedinput (https://github.com/digitalBush/jquery.maskedinput) • jsTree (http://www.jstree.com/) • Justified Gallery (https://github.com/miromannino/Justified-Gallery) • KissXML (https://github.com/robbiehanson/KissXML) • kjs (http://www.kde.org) • KVOController (https://github.com/facebook/KVOController) • libcurl (http://curl.haxx.se) • libglib (http://library.gnome.org/devel/glib) • libgsf (http://ftp.gnome.org/pub/gnome/sources/libgsf/1.11/) • libMemcached (https://libmemcached.org/) • libmspack (http://www.cabextract.org.uk/libmspack) • libtar (http://www.feep.net/libtar/) • libtiff (https://gitlab.com/libtiff/libtiff) • libxml2 (http://www.xmlsoft.org) • libxslt (http://www.xmlsoft.org) • Liferay Portal (http://www.liferay.com/) • Lightbox (https://lokeshdhakar.com/projects/lightbox2/) • M13BadgeView (https://github.com/Marxon13/M13BadgeView) Fabasoft Software Products 5 • M13ProgressSuite (https://github.com/Marxon13/M13ProgressSuite) • MBProgressHUD (https://github.com/jdg/MBProgressHUD) • MMWormhole (https://github.com/mutualmobile/MMWormhole) • Modernizr (https://modernizr.com/) • Moment.js (https://github.com/moment/moment/) • Mozilla Gecko SDK (http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/) • MySpell (http://lingucomponent.openoffice.org/dictionary.html) • MyThes (http://lingucomponent.openoffice.org/thesaurus.html) • NET-SNMP (http://www.net-snmp.org) • OkHttp (http://square.github.io/okhttp) • Okio (https://github.com/square/okio) • OpenOffice.org SDK (http://www.openoffice.org/) • OpenSSL (http://www.openssl.org) • PCRE (http://www.pcre.org) • PDFBox (http://www.pdfbox.org) • PDFium (https://pdfium.googlesource.com/pdfium) • PureLayout (https://github.com/PureLayout/PureLayout) • Qt (http://qt-project.org/) • React (https://github.com/facebook/react) • React DOM (https://github.com/facebook/react) • ReactiveObjC (https://github.com/ReactiveCocoa/ReactiveObjC) • Realm (https://github.com/realm/realm-cocoa) • renderjson (https://github.com/caldwell/renderjson) • Respond.js (https://github.com/scottjehl/Respond) • SDWebImage (https://github.com/rs/SDWebImage) • Selenium WebDriver (http://www.seleniumhq.org/projects/webdriver/) • Signavio Core Components (http://code.google.com/p/signavio-core-components/) • SIMILE Widgets Timeline (http://simile-widgets.org/timeline/) • SparkMD5 (https://www.npmjs.com/package/spark-md5) • TagLib (http://taglib.github.io/) • Toast (https://github.com/scalessec/Toast) • ulidj (https://github.com/azam/ulidj) • wsdl4j (http://sourceforge.net/projects/wsdl4j) • url-polyfill (https://github.com/lifaon74/url-polyfill) • XMLSec (http://www.aleksey.com/) • XMP Toolkit SDK (http://www.adobe.com/devnet/xmp.html) • XULRunner (http://developer.mozilla.org/en/XULRunner) • Yahoo User Interface Library (http://developer.yahoo.com/yui/) • zlib (http://www.zlib.net) Fabasoft Software Products 6 • ZXing (http://code.google.com/p/zxing/) Fabasoft Software Products 7 .
Load more

Recommended publications
  • Red Hat Enterprise Linux 6 Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
    [Show full text]
  • Web Application Development Using TCL/Apache Rivet and Javascript Anne-Leslie Dean, Senior Software Developer, Flightaware Prese
    Web Application Development Using TCL/Apache Rivet and JavaScript Anne-Leslie Dean, Senior Software Developer, FlightAware Presented: 25th Annual TCL/Tk Conference, Oct 15-19, 2018 Introduction Modern Web applications rival native applications in user experience. This is accomplished by manipulating the Web document dynamically in the client browser environment. There are a many choices of scripting (language) environments a developer may choose to use on the web server: PHP, Python, Ruby, TCL etc. But on the client side, the JavaScript environment is the standard for programmatic control of the Web application. Apache Rivet provides a server environment to build Web applications using TCL. This case study will demonstrate the application of fundamental software design principles such as separation of concerns, abstraction, and encapsulation in a TCL/Apache Rivet environment with integrated JavaScript. The basic structure of the Rivet script will distinguish content management from presentation and will visibly identify a clear interface between the TCL/Apache Rivet and the JavaScript environments. Each step of the case study will conclude with an analysis of the software development principles being applied. Case Study Step 1: Framing Out The Rivet Script The distinguishing architectural feature of modern Web applications boils down to a simple model: a document template rendered against an abstracted data model. The code concerned with managing the abstracted data model is commonly referred to as content management. The code concerned with describing the document template is commonly referred to as presentation. The basic structure of an Apache Rivet script should always reinforce this Web application architectural distinction. This can be accomplished by applying the software principle of separation of concerns with respect to content management and presentation.
    [Show full text]
  • THE FUTURE of SCREENS from James Stanton a Little Bit About Me
    THE FUTURE OF SCREENS From james stanton A little bit about me. Hi I am James (Mckenzie) Stanton Thinker / Designer / Engineer / Director / Executive / Artist / Human / Practitioner / Gardner / Builder / and much more... Born in Essex, United Kingdom and survived a few hair raising moments and learnt digital from the ground up. Ok enough of the pleasantries I have been working in the design field since 1999 from the Falmouth School of Art and onwards to the RCA, and many companies. Ok. less about me and more about what I have seen… Today we are going to cover - SCREENS CONCEPTS - DIGITAL TRANSFORMATION - WHY ASSETS LIBRARIES - CODE LIBRARIES - COST EFFECTIVE SOLUTION FOR IMPLEMENTATION I know, I know, I know. That's all good and well, but what does this all mean to a company like mine? We are about to see a massive change in consumer behavior so let's get ready. DIGITAL TRANSFORMATION AS A USP Getting this correct will change your company forever. DIGITAL TRANSFORMATION USP-01 Digital transformation (DT) – the use of technology to radically improve performance or reach of enterprises – is becoming a hot topic for companies across the globe. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-02 Companies face common pressures from customers, employees and competitors to begin or speed up their digital transformation. However they are transforming at different paces with different results. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-03 Successful digital transformation comes not from implementing new technologies but from transforming your organisation to take advantage of the possibilities that new technologies provide.
    [Show full text]
  • Is a SPARQL Endpoint a Good Way to Manage Nursing Documentation
    Is a SPARQL Endpoint a Good way to Manage Nursing Documentation Is a SPARQL Endpoint a good way to Manage Nursing Documentation by Muhammad Aslam Supervisor: Associate Professor Jan Pettersen Nytun Project report for Master Thesis in Information & Communication Technology IKT 590 in Spring 2014 University of Agder Faculty of Engineering and Science Grimstad, 2 June 2014 Status: Final Keywords: Semantic Web, Ontology, Jena, SPARQL, Triple Store, Relational Database Page 1 of 86 Is a SPARQL Endpoint a Good way to Manage Nursing Documentation Abstract. In Semantic Web there are different technologies available, among these technologies ontologies are considered a basic technology to promote semantic management and activities. An ontology is capable to exhibits a common, shareable and reusable view of a specific application domain, and they give meaning to information structures that are exchanged by information systems [63]. In this project our main goal is to develop an application that helps to store and manage the patient related clinical data. For this reason first we made an ontology, in ontology we add some patient related records. After that we made a Java application in which we read this ontology by the help of Jena. Then we checked this application with some other database solutions such as Triple Store (Jena TDB) and Relational database (Jena SDB). After that we performed SPARQL Queries to get results that reads from databases we have used, on the basis of results that we received after performing SPARQL Queries, we made an analysis on the performance and efficiency of databases. In these results we found that Triple Stores (Jena TDB) have capabilities to response very fast among other databases.
    [Show full text]
  • Tripwire Ip360 9.0 License Agreements
    TRIPWIRE® IP360 TRIPWIRE IP360 9.0 LICENSE AGREEMENTS FOUNDATIONAL CONTROLS FOR SECURITY, COMPLIANCE & IT OPERATIONS © 2001-2018 Tripwire, Inc. All rights reserved. Tripwire is a registered trademark of Tripwire, Inc. Other brand or product names may be trademarks or registered trademarks of their respective companies or organizations. Contents of this document are subject to change without notice. Both this document and the software described in it are licensed subject to Tripwire’s End User License Agreement located at https://www.tripwire.com/terms, unless a valid license agreement has been signed by your organization and an authorized representative of Tripwire. This document contains Tripwire confidential information and may be used or copied only in accordance with the terms of such license. This product may be protected by one or more patents. For further information, please visit: https://www.tripwire.com/company/patents. Tripwire software may contain or be delivered with third-party software components. The license agreements and notices for the third-party components are available at: https://www.tripwire.com/terms. Tripwire, Inc. One Main Place 101 SW Main St., Suite 1500 Portland, OR 97204 US Toll-free: 1.800.TRIPWIRE main: 1.503.276.7500 fax: 1.503.223.0182 https://www.tripwire.com [email protected] TW 1190-04 Contents License Agreements 4 Academic Free License ("AFL") 5 Apache License V2.0 (ASL 2.0) 9 BSD 20 Boost 28 CDDLv1.1 29 EPLv1 30 FreeType License 31 GNU General Public License V2 34 GNU General Public License V3 45 IBM 57 ISC 62 JasPer 63 Lesser General Public License V2 65 LibTiff 76 MIT 77 MPLv1.1 83 MPLv2 92 OpenLDAP 98 OpenSSL 99 PostgreSQL 102 Public Domain 104 Python 108 TCL 110 Vim 111 wxWidgets 113 Zlib 114 Contact Information 115 Tripwire IP360 9.0 License Agreements 3 Contents License Agreements This document contains licensing information relating to Tripwire's use of free and open-source software with or within the Tripwire IP360 product (collectively, "FOSS").
    [Show full text]
  • Talend Open Studio for Big Data Release Notes
    Talend Open Studio for Big Data Release Notes 6.0.0 Talend Open Studio for Big Data Adapted for v6.0.0. Supersedes previous releases. Publication date July 2, 2015 Copyleft This documentation is provided under the terms of the Creative Commons Public License (CCPL). For more information about what you can and cannot do with this documentation in accordance with the CCPL, please read: http://creativecommons.org/licenses/by-nc-sa/2.0/ Notices Talend is a trademark of Talend, Inc. All brands, product names, company names, trademarks and service marks are the properties of their respective owners. License Agreement The software described in this documentation is licensed under the Apache License, Version 2.0 (the "License"); you may not use this software except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.html. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software developed at AOP Alliance (Java/J2EE AOP standards), ASM, Amazon, AntlR, Apache ActiveMQ, Apache Ant, Apache Avro, Apache Axiom, Apache Axis, Apache Axis 2, Apache Batik, Apache CXF, Apache Cassandra, Apache Chemistry, Apache Common Http Client, Apache Common Http Core, Apache Commons, Apache Commons Bcel, Apache Commons JxPath, Apache
    [Show full text]
  • Native Libraries Lecture 10
    Native Libraries Lecture 10 Operating Systems Practical 11 January 2017 This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/. OSP Native libraries, Lecture 10 1/35 Bionic SQLite SSL WebKit Surface Manager Audio Manager Media Framework OpenGL ES OSP Native libraries, Lecture 10 2/35 Outline Bionic SQLite SSL WebKit Surface Manager Audio Manager Media Framework OpenGL ES OSP Native libraries, Lecture 10 3/35 Bionic I Custom C library I Replacement for glibc I Not POSIX compliant I Goals I BSD license I Avoid GPL and LGPL in userspace I Small size I glibc is very large I High speed I Designed for low CPU frequencies OSP Native libraries, Lecture 10 4/35 Bionic vs. glibc I Bionic routines do not throw, pass and handle C++ exceptions I Support for exceptions adds a great overhead I Exceptions can be used internally in C++ code, if they do not cross the libc routine I No C++ Standard Template Library I Native code developers can use gnustl or stlport I New pthread implementation I No wchar_t and no support for LOCALE OSP Native libraries, Lecture 10 5/35 Bionic vs. glibc I A shared memory region is used for configuration I Also used by the applications through property_get() and property_set() I No openlog() or syslog() I __libc_android_log_print() used for logging I Specific malloc implementation I A hash table used for tracking allocations to discover leaks I No pty support OSP Native libraries, Lecture 10 6/35 Bionic vs.
    [Show full text]
  • A Survey of Geospatial Semantic Web for Cultural Heritage
    heritage Review A Survey of Geospatial Semantic Web for Cultural Heritage Ikrom Nishanbaev 1,* , Erik Champion 1 and David A. McMeekin 2 1 School of Media, Creative Arts, and Social Inquiry, Curtin University, Perth, WA 6845, Australia; [email protected] 2 School of Earth and Planetary Sciences, Curtin University, Perth, WA 6845, Australia; [email protected] * Correspondence: [email protected] Received: 23 April 2019; Accepted: 16 May 2019; Published: 20 May 2019 Abstract: The amount of digital cultural heritage data produced by cultural heritage institutions is growing rapidly. Digital cultural heritage repositories have therefore become an efficient and effective way to disseminate and exploit digital cultural heritage data. However, many digital cultural heritage repositories worldwide share technical challenges such as data integration and interoperability among national and regional digital cultural heritage repositories. The result is dispersed and poorly-linked cultured heritage data, backed by non-standardized search interfaces, which thwart users’ attempts to contextualize information from distributed repositories. A recently introduced geospatial semantic web is being adopted by a great many new and existing digital cultural heritage repositories to overcome these challenges. However, no one has yet conducted a conceptual survey of the geospatial semantic web concepts for a cultural heritage audience. A conceptual survey of these concepts pertinent to the cultural heritage field is, therefore, needed. Such a survey equips cultural heritage professionals and practitioners with an overview of all the necessary tools, and free and open source semantic web and geospatial semantic web platforms that can be used to implement geospatial semantic web-based cultural heritage repositories.
    [Show full text]
  • Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Last Updated: 2017-10-20 Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Robert Krátký Red Hat Customer Content Services [email protected] Don Domingo Red Hat Customer Content Services Jacquelynn East Red Hat Customer Content Services Legal Notice Copyright © 2016 Red Hat, Inc. and others. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent.
    [Show full text]
  • Diplomová Práce Přenos Dat Z Registru SITS Ve Formátu DASTA
    Západočeská univerzita v Plzni Fakulta aplikovaných věd Katedra informatiky a výpočetní techniky Diplomová práce Přenos dat z registru SITS (Safe Impementation of Treatments in Stroke) ve formátu DASTA Plzeň, 2012 Bc. Pavel Karlík 1 Originální zadání práce 2 Prohlášení: Prohlašuji, že jsem diplomovou práci vypracoval samostatně a výhradně s použitím citovaných pramenů, pokud není explicitně uvedeno jinak. V Plzni dne …………… Bc. Pavel Karlík ………………… 3 Abstract Data Transfer from the SITS Registry (Safe Implementation of Treatments in Stroke) in the Format of DASTA The goal of this master´s thesis is to analyze the data standards in the field of medical applications with focus on the format DASTA, work with them and developing a suitable web-based tool for doctors in the FN Plzeň hospital to simplify the forms filling in the SITS registry. Application will be user-friendly with the focus on one-click access, multi-lingual, adaptive to changes, and fill in the forms with the data from hospital database stored in the DASTA. In the background will send same data also to the Department of Computer Science and Engineering in the University of West Bohemia for future research. 4 Poděkování Tímto bych chtěl poděkovat paní Doc. Dr. Ing. Janě Klečkové za neutuchající optimismus a podporu, který mně byl motivací během celé doby mé práce. Dále si cením věnovaného času a pomoci, která mi byla velkou podporou při tvorbě. Poděkování patří také mé rodině a blízkým za jejich ohleduplnost a motivaci. 5 Obsah 1 ÚVOD ............................................................................................................ 9 2 DATOVÉ STANDARDY .................................................................................. 10 2.1 STANDARDY OBECNĚ ......................................................................................... 10 2.1 DASTA .......................................................................................................... 12 2.1.1 Historie ................................................................................................
    [Show full text]
  • SVG-Based Knowledge Visualization
    MASARYK UNIVERSITY FACULTY}w¡¢£¤¥¦§¨ OF I !"#$%&'()+,-./012345<yA|NFORMATICS SVG-based Knowledge Visualization DIPLOMA THESIS Miloš Kaláb Brno, spring 2012 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Advisor: RNDr. Tomáš Gregar Ph.D. ii Acknowledgement I would like to thank RNDr. Tomáš Gregar Ph.D. for supervising the thesis. His opinions, comments and advising helped me a lot with accomplishing this work. I would also like to thank to Dr. Daniel Sonntag from DFKI GmbH. Saarbrücken, Germany, for the opportunity to work for him on the Medico project and for his supervising of the thesis during my erasmus exchange in Germany. Big thanks also to Jochen Setz from Dr. Sonntag’s team who worked on the server background used by my visualization. Last but not least, I would like to thank to my family and friends for being extraordinary supportive. iii Abstract The aim of this thesis is to analyze the visualization of semantic data and sug- gest an approach to general visualization into the SVG format. Afterwards, the approach is to be implemented in a visualizer allowing user to customize the visualization according to the nature of the data. The visualizer was integrated as an extension of Fresnel Editor. iv Keywords Semantic knowledge, SVG, Visualization, JavaScript, Java, XML, Fresnel, XSLT v Contents Introduction . .3 1 Brief Introduction to the Related Technologies ..........5 1.1 XML – Extensible Markup Language ..............5 1.1.1 XSLT – Extensible Stylesheet Lang.
    [Show full text]
  • Multi Software Product Lines in the Wild
    AperTO - Archivio Istituzionale Open Access dell'Università di Torino Multi software product lines in the wild This is the author's manuscript Original Citation: Availability: This version is available http://hdl.handle.net/2318/1667454 since 2020-07-06T10:51:50Z Publisher: Association for Computing Machinery Published version: DOI:10.1145/3168365.3170425 Terms of use: Open Access Anyone can freely access the full text of works made available as "Open Access". Works made available under a Creative Commons license can be used according to the terms and conditions of said license. Use of all other works requires consent of the right holder (author or publisher) if not exempted from copyright protection by the applicable law. (Article begins on next page) 27 September 2021 Multi Software Product Lines in the Wild Michael Lienhardt Ferruccio Damiani [email protected] [email protected] Università di Torino Università di Torino Italy Italy Simone Donetti Luca Paolini [email protected] [email protected] Università di Torino Università di Torino Italy Italy ABSTRACT 1 INTRODUCTION Modern software systems are often built from customizable and A Software Product Line (SPL) is a set of similar programs, called inter-dependent components. Such customizations usually define variants, with a common code base and well documented variabil- which features are offered by the components, and may depend ity [1, 6, 19]. Modern software systems are often built as complex on backend components being configured in a specific way. As assemblages of customizable components that out-grow the expres- such system become very large, with a huge number of possible siveness of SPLs.
    [Show full text]