DOCSLIB.ORG

Interoperability Landscaping Report December 28, 2015

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Ref. Ares(2016)2259176 - 13/05/2016 Interoperability Landscaping Report December 28, 2015 Deliverable Code: D5.1 Version: 3 – Intermediary Dissemination level: PUBLIC H2020-EINFRA-2014-2015 / H2020-EINFRA-2014-2 Topic: EINFRA-1-2014 Managing, preserving and computing with big research data Research & Innovation action Grant Agreement 654021 Interoperability Landscaping Report Document Description D5.1 – Interoperability Landscaping Report WP5 – Interoperability Framework WP participating organizations: ARC, UNIMAN, UKP-TUDA, INRA, EMBL-EBI, AK, LIBER, UvA, OU, EPFL, CNIO, USFD, GESIS, GRNET, Frontiers, UoS Contractual Delivery Date: 12/2015 Actual Delivery Date: 12/2015 Nature: Report Version: 1.0 (Draft) Public Deliverable Preparation slip Name Organization Date Authors Listed in the document Edited by Piotr Przybyła UNIMAN 20/12/2015 Matthew Shardlow UNIMAN Reviewed by John McNaught UNIMAN 20/12/2015 Natalia Manola ARC 22/12/2015 Approved by Natalia Manola ARC 16/1/2016 For delivery Mike Hatzopoulos ARC Document change record Issue Item Reason for Change Author Organization V0.1 Draft version Initial document structure Piotr Przybyła, UNIMAN Matthew Shardlow V0.2 Draft version Included initial content Piotr Przybyła, UNIMAN Matthew Shardlow V1.0 First delivery Applied corrections and Piotr Przybyła, UNIMAN added discussion Matthew Shardlow Public Page 1 of 112 Interoperability Landscaping Report Table of Contents 1. INTRODUCTION 8 2. REPOSITORIES 11 2.1 DESCRIPTION OF RESOURCES 11 2.1.1 METADATA SCHEMAS & PROFILES 12 2.1.2 VOCABULARIES AND ONTOLOGIES FOR DESCRIBING SPECIFIC INFORMATION TYPES 19 2.1.3 MECHANISMS USED FOR THE IDENTIFICATION OF RESOURCES 20 2.1.4 SUMMARY 20 2.2 REGISTRIES/REPOSITORIES OF RESOURCES 21 3. TOOLS AND SERVICES 32 3.1 TEXT MINING COMPONENT COLLECTIONS AND WORKFLOW ENGINES 32 3.1 NON-TEXT MINING AND GENERAL-PURPOSE WORKFLOW ENGINES 40 3.2 ANNOTATION EDITORS 48 4. CONTENT 54 4.1 CHARACTER STANDARDS 54 4.1.1 MAJOR STANDARDS 55 4.1.2 STANDARDS FOR SPECIFIC LANGUAGES 55 4.1.3 INFORMING THE CHARACTER ENCODING 56 4.1.4 CHARACTER ENCODING APIS 57 4.1.5 SUMMARY 58 4.2 ANNOTATION FORMATS 58 4.2.1 DOMAIN-DEPENDENT 60 4.2.2 GENERIC 60 4.2.3 SUMMARY 63 4.3 ONTOLOGIES, DICTIONARIES AND LEXICONS 63 4.3.1 FORMATS FOR ENCODING LEXICA, ONTOLOGIES, DICTIONARIES 63 4.3.2 ONTOLOGIES, DICTIONARIES AND LEXICA 66 4.3.3 SUMMARY 70 5. COMPUTING INFRASTRUCTURES 71 5.1 CLOUD COMPUTING OVERVIEW 71 5.1.1 CLOUD DEPLOYMENT MODELS 72 5.1.2 CLOUD SERVICE MODELS 72 5.2 INTEROPERABILITY AND PORTABILITY 74 5.2.1 RESOURCE MANAGEMENT 75 Public Page 2 of 112 Interoperability Landscaping Report 5.2.2 DATA MANAGEMENT 76 5.2.3 IDENTITY MANAGEMENT 78 5.2.4 APPLICATION DEVELOPMENT AND DEPLOYMENT 80 5.2.5 APPLICATION PORTABILITY 83 5.2.6 CONTAINERS 86 5.2.7 CLOUD MARKETPLACES 87 5.3 CLOUD COMPUTING STANDARDS ORGANIZATIONS AND INITIATIVES 87 5.4 PRODUCTION AND COMMERCIAL CLOUD OFFERINGS 90 5.5 DISTRIBUTED PROCESSING 92 5.5.1 MAPREDUCE & APACHE HADOOP 92 5.5.2 DISTRIBUTED PROCESSING PROVIDERS 93 6. LEGAL ISSUES 96 6.1 CONTENT LICENSING 97 6.2 TOOL LICENSES 98 6.3 SERVICE TERMS OF USE 99 6.4 DATA PROTECTION 99 6.5 LICENSE INTEROPERABILITY 100 7. DISCUSSION 102 7.1 RELATED EFFORTS 102 7.2 LIMITATIONS OF THIS STUDY 102 7.3 OVERVIEW OF THE FIELD 103 7.4 GAP ANALYSIS 104 8. REFERENCES 105 Public Page 3 of 112 Interoperability Landscaping Report Table of tables TABLE 1. COMPARISON OF METADATA SCHEMATA AND PROFILES. 13 TABLE 2. COMPARISON OF VOCABULARIES AND ONTOLOGIES FOR INFORMATION TYPES. 19 TABLE 3. WEB SERVICE REGISTRIES. 22 TABLE 4. AGGREGATORS OF SCHOLARLY PUBLICATIONS. 22 TABLE 5. REPOSITORIES, REGISTRIES & CATALOGUES OF LANGUAGE RESOURCES. 23 TABLE 6. REPOSITORIES & REGISTRIES OF SERVICES AND RESOURCES. 24 TABLE 7. LANGUAGE SPECIFIC REPOSITORIES. 25 TABLE 8. PLATFORMS/INFRASTRUCTURES INTEGRATING LANGUAGE RESOURCES & SERVICES. 26 TABLE 9. COMPARISON OF COMPONENT COLLECTIONS AND WORKFLOW ENGINES. 33 TABLE 10. GENERAL COMPARISON OF WORKFLOW ENGINES. 42 TABLE 11. TECHNICAL ASPECTS OF WORKFLOW ENGINES. 43 TABLE 12. GENERAL COMPARISON OF ANNOTATION EDITORS. 50 TABLE 13. SUMMARY TABLE OF CHARACTER STANDARDS (NON-EXHAUSTIVE LIST). 54 TABLE 14. SUMMARY TABLE OF ANNOTATION FORMATS 59 TABLE 15. MAIN FORMATS FOR LEXICAL RESOURCES. 64 TABLE 16. A NON-EXHAUSTIVE LIST OF POPULAR KNOWLEDGE RESOURCES. 67 TABLE 17. COMPARISON TABLE FOR CLOUD API LIBRARIES 81 TABLE 18. FILE IMAGE FORMATS. 84 TABLE 19. CLOUD COMPUTING STANDARD ORGANIZATIONS AND INITIATIVES. 88 TABLE 20. INITIATIVES RELEVANT OF CLOUD COMPUTING INTEROPERABILITY ISSUES. 89 TABLE 21. COMPARISON BETWEEN HADOOP SOFTWARE AND PROVIDERS. 95 Public Page 4 of 112 Interoperability Landscaping Report Disclaimer This document contains description of the OpenMinTeD project findings, work and products. Certain parts of it might be under partner Intellectual Property Right (IPR) rules so, prior to using its content please contact the consortium head for approval. In case you believe that this document harms in any way IPR held by you as a person or as a representative of an entity, please do notify us immediately. The authors of this document have taken any available measure in order for its content to be accurate, consistent and lawful. However, neither the project consortium as a whole nor the individual partners that implicitly or explicitly participated in the creation and publication of this document hold any sort of responsibility that might occur as a result of using its content. This publication has been produced with the assistance of the European Union. The content of this publication is the sole responsibility of the OpenMinTeD consortium and can in no way be taken to reflect the views of the European Union. The European Union is established in accordance with the Treaty on European Union (Maastricht). There are currently 28 Member States of the Union. It is based on the European Communities and the member states cooperation in the fields of Common Foreign and Security Policy and Justice and Home Affairs. The five main institutions of the European Union are the European Parliament, the Council of Ministers, the European Commission, the Court of Justice and the Court of Auditors. (http://europa.eu.int/) OpenMinTeD is a project funded by the European Union (Grant Agreement No 654021). Public Page 5 of 112 Interoperability Landscaping Report Contribution Editors Piotr Przybyła (UNIMAN) Matthew Shardlow (UNIMAN) Authors Sophia Ananiadou (UNIMAN) Thomas Margoni (UoS) Sophie Aubin (INRA) Mandy Neumann (GESIS) Robert Bossy (INRA) Wim Peters (USFD) Louise Deléger (INRA) Stelios Piperidis (ARC) Richard Eckart de Castilho (UKP-TUDA) Prokopis Prokopidis (ARC) Vangelis Floros (GRNET) Piotr Przybyła (UNIMAN) Dimitris Galanis (ARC) Angus Roberts (USFD) Byron Georgantopoulos (GRNET) Ian Roberts (USFD) Mark Greenwood (USFD) Stavros Sachtouris (GRNET) Masoud Kiaeeha (UKP-TUDA) Jochen Schirrwagen (OpenAIRE) Penny Labropoulou (ARC) Matthew Shardlow (UNIMAN) Reviewers John McNaught (UNIMAN) Natalia Manola (ARC) Public Page 6 of 112 Interoperability Landscaping Report Publishable Summary The goal of this document is to present the current state of the field of text and data mining (TDM) with a focus on interoperability issues. This will serve as a starting point for subsequent OpenMinTeD efforts concentrating on developing interoperability specifications for the future platform. The report starts by introducing the concept of interoperability and its importance for TDM. Section 2 describes existing repositories of resources, services and components, allowing users to find a solution that best suits their needs. We also survey methods for describing resources, i.e., metadata schemata and vocabularies. The next part focusses on tools and services – active elements used to process textual data and produce annotations. We cover various component collections, annotation editors and workflow engines, both general-purpose and those focussed on text mining. In section 4 we concentrate on static resources, including text encoding standards, annotation formats and finally common representations used in developing ontologies, dictionaries and lexicons. Sections 5 and 6 describe additional aspects that have a strong influence on TDM, i.e., computing infrastructure and legal issues. Finally, we provide a discussion, in which we describe previous related efforts, explain the limitations of this study and analyse the current gaps that need to be addressed in order to realise the goals of OpenMinTeD. Public Page 7 of 112 Interoperability Landscaping Report 1. Introduction The Open Mining Infrastructure for Text and Data (OpenMinTeD) is a new European initiative which seeks to promote the cause of text and data mining (TDM). OpenMinTeD will work within the field of TDM to promote collaboration between the providers of TDM infrastructures as well as working outside of the field to encourage uptake in other areas which may benefit from TDM. Service providers will benefit from this project through the standardisation of formats for TDM as well as the creation of new interoperable TDM workflows, which will seek to standardise existing content and allow previously incompatible services to work together. Service users will benefit through the provision of training and support for TDM tailored to their fields of expertise. Interoperability is key to the goals of OpenMinTeD and to the content in this report. Interoperability is an ability of two or more information systems to integrate with
Recommended publications
  • Hieroglyphs for the Information Age: Images As a Replacement for Characters for Languages Not Written in the Latin-1 Alphabet Akira Hasegawa

    Hieroglyphs for the Information Age: Images As a Replacement for Characters for Languages Not Written in the Latin-1 Alphabet Akira Hasegawa

    Rochester Institute of Technology RIT Scholar Works Theses Thesis/Dissertation Collections 5-1-1999 Hieroglyphs for the information age: Images as a replacement for characters for languages not written in the Latin-1 alphabet Akira Hasegawa Follow this and additional works at: http://scholarworks.rit.edu/theses Recommended Citation Hasegawa, Akira, "Hieroglyphs for the information age: Images as a replacement for characters for languages not written in the Latin-1 alphabet" (1999). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by the Thesis/Dissertation Collections at RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Hieroglyphs for the Information Age: Images as a Replacement for Characters for Languages not Written in the Latin- 1 Alphabet by Akira Hasegawa A thesis project submitted in partial fulfillment of the requirements for the degree of Master of Science in the School of Printing Management and Sciences in the College of Imaging Arts and Sciences of the Rochester Institute ofTechnology May, 1999 Thesis Advisor: Professor Frank Romano School of Printing Management and Sciences Rochester Institute ofTechnology Rochester, New York Certificate ofApproval Master's Thesis This is to certify that the Master's Thesis of Akira Hasegawa With a major in Graphic Arts Publishing has been approved by the Thesis Committee as satisfactory for the thesis requirement for the Master ofScience degree at the convocation of May 1999 Thesis Committee: Frank Romano Thesis Advisor Marie Freckleton Gr:lduate Program Coordinator C.
  • SLP-5 Setup for Uni-3/5/7 & WM-Nano Chinese BIG5 Characters

    SLP-5 Setup for Uni-3/5/7 & WM-Nano Chinese BIG5 Characters

    SLP-5 Configuration for Uni-3, Uni-5, Uni-7 & WM-Nano Chinese BIG5 Characters The Uni-3, Uni-5, Uni-7 scales and WM-Nano wrapper can display and print PLU information in Chinese BIG5, also known as Traditional, characters but all menus, etc. remain in English. Chinese characters are entered in SLP-5 and sent to the scales. Chinese characters cannot be entered at the scales. Refer to the following procedure to configure the scales and wrapper and SLP-5. SCALE SETUP Update the firmware for the Uni-5, Uni-7 and WM-Nano to the following versions. Uni-5: C1830x Uni-7: C1828x (PK-260A CF CPU), C2072x (PK-260B SD CPU) WM-Nano: C1832x (PK-260A CF CPU), C2074x (PK-260B SD CPU) Uni-3: C1937U or later, C2271x The Language setting in the Uni-3 must be set to print and display Chinese characters. Note: Only the Uni-3L2 models display Chinese characters. KEY IN ITEM No. Enter 6000, press MODE 0.000 0.000 0.00 0.00 <B00 SETUP> Enter 495344, press PLU <B00 SETUP> <B00 SETUP> Enter 26, press Down Arrow <B00 SETUP> B26 COUNTRY Press ENTER B26 COUNTRY *LANGUAGE 1:ENGLISH Enter 15, press ENTER B26-01-02 LANGUAGE 1 *LANGUAGE 15:FORMOSAN After the long beep press MODE B26-01-02 LANGUAGE 15 REBOOT Shut off the scale for this setting change to 19004-0000 take effect. SLP-5 SETUP SLP-5 must be configured to use Chinese fonts. Refer to the instructions below. The following Chinese character sizes are available.
  • File Formats

    File Formats

    man pages section 4: File Formats Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 817–3945–10 September 2004 Copyright 2004 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
  • Enterprise Integration Patterns N About Apache Camel N Essential Patterns Enterprise Integration Patterns N Conclusions and More

    Enterprise Integration Patterns N About Apache Camel N Essential Patterns Enterprise Integration Patterns N Conclusions and More

    Brought to you by... #47 CONTENTS INCLUDE: n About Enterprise Integration Patterns n About Apache Camel n Essential Patterns Enterprise Integration Patterns n Conclusions and more... with Apache Camel Visit refcardz.com By Claus Ibsen ABOUT ENTERPRISE INTEGRATION PaTTERNS Problem A single event often triggers a sequence of processing steps Solution Use Pipes and Filters to divide a larger processing steps (filters) that are connected by channels (pipes) Integration is a hard problem. To help deal with the complexity Camel Camel supports Pipes and Filters using the pipeline node. of integration problems the Enterprise Integration Patterns Java DSL from(“jms:queue:order:in”).pipeline(“direct:transformOrd (EIP) have become the standard way to describe, document er”, “direct:validateOrder”, “jms:queue:order:process”); and implement complex integration problems. Hohpe & Where jms represents the JMS component used for consuming JMS messages Woolf’s book the Enterprise Integration Patterns has become on the JMS broker. Direct is used for combining endpoints in a synchronous fashion, allow you to divide routes into sub routes and/or reuse common routes. the bible in the integration space – essential reading for any Tip: Pipeline is the default mode of operation when you specify multiple integration professional. outputs, so it can be omitted and replaced with the more common node: from(“jms:queue:order:in”).to(“direct:transformOrder”, “direct:validateOrder”, “jms:queue:order:process”); Apache Camel is an open source project for implementing TIP: You can also separate each step as individual to nodes: the EIP easily in a few lines of Java code or Spring XML from(“jms:queue:order:in”) configuration.
  • SUPPORTING the CHINESE, JAPANESE, and KOREAN LANGUAGES in the OPENVMS OPERATING SYSTEM by Michael M. T. Yau ABSTRACT the Asian L

    SUPPORTING the CHINESE, JAPANESE, and KOREAN LANGUAGES in the OPENVMS OPERATING SYSTEM by Michael M. T. Yau ABSTRACT the Asian L

    SUPPORTING THE CHINESE, JAPANESE, AND KOREAN LANGUAGES IN THE OPENVMS OPERATING SYSTEM By Michael M. T. Yau ABSTRACT The Asian language versions of the OpenVMS operating system allow Asian-speaking users to interact with the OpenVMS system in their native languages and provide a platform for developing Asian applications. Since the OpenVMS variants must be able to handle multibyte character sets, the requirements for the internal representation, input, and output differ considerably from those for the standard English version. A review of the Japanese, Chinese, and Korean writing systems and character set standards provides the context for a discussion of the features of the Asian OpenVMS variants. The localization approach adopted in developing these Asian variants was shaped by business and engineering constraints; issues related to this approach are presented. INTRODUCTION The OpenVMS operating system was designed in an era when English was the only language supported in computer systems. The Digital Command Language (DCL) commands and utilities, system help and message texts, run-time libraries and system services, and names of system objects such as file names and user names all assume English text encoded in the 7-bit American Standard Code for Information Interchange (ASCII) character set. As Digital's business began to expand into markets where common end users are non-English speaking, the requirement for the OpenVMS system to support languages other than English became inevitable. In contrast to the migration to support single-byte, 8-bit European characters, OpenVMS localization efforts to support the Asian languages, namely Japanese, Chinese, and Korean, must deal with a more complex issue, i.e., the handling of multibyte character sets.
  • Orchestrating Big Data Analysis Workflows in the Cloud: Research Challenges, Survey, and Future Directions

    Orchestrating Big Data Analysis Workflows in the Cloud: Research Challenges, Survey, and Future Directions

    00 Orchestrating Big Data Analysis Workflows in the Cloud: Research Challenges, Survey, and Future Directions MUTAZ BARIKA, University of Tasmania SAURABH GARG, University of Tasmania ALBERT Y. ZOMAYA, University of Sydney LIZHE WANG, China University of Geoscience (Wuhan) AAD VAN MOORSEL, Newcastle University RAJIV RANJAN, Chinese University of Geoscienes and Newcastle University Interest in processing big data has increased rapidly to gain insights that can transform businesses, government policies and research outcomes. This has led to advancement in communication, programming and processing technologies, including Cloud computing services and technologies such as Hadoop, Spark and Storm. This trend also affects the needs of analytical applications, which are no longer monolithic but composed of several individual analytical steps running in the form of a workflow. These Big Data Workflows are vastly different in nature from traditional workflows. Researchers arecurrently facing the challenge of how to orchestrate and manage the execution of such workflows. In this paper, we discuss in detail orchestration requirements of these workflows as well as the challenges in achieving these requirements. We alsosurvey current trends and research that supports orchestration of big data workflows and identify open research challenges to guide future developments in this area. CCS Concepts: • General and reference → Surveys and overviews; • Information systems → Data analytics; • Computer systems organization → Cloud computing; Additional Key Words and Phrases: Big Data, Cloud Computing, Workflow Orchestration, Requirements, Approaches ACM Reference format: Mutaz Barika, Saurabh Garg, Albert Y. Zomaya, Lizhe Wang, Aad van Moorsel, and Rajiv Ranjan. 2018. Orchestrating Big Data Analysis Workflows in the Cloud: Research Challenges, Survey, and Future Directions.
  • Reference Guide

    Reference Guide

    Apache Syncope - Reference Guide Version 2.1.9 Table of Contents 1. Introduction. 2 1.1. Identity Technologies. 2 1.1.1. Identity Stores . 2 1.1.2. Provisioning Engines . 4 1.1.3. Access Managers . 5 1.1.4. The Complete Picture . 5 2. Architecture. 7 2.1. Core . 7 2.1.1. REST . 7 2.1.2. Logic . 8 2.1.3. Provisioning . 8 2.1.4. Workflow. 9 2.1.5. Persistence . 9 2.1.6. Security . 9 2.2. Admin UI. 10 2.2.1. Accessibility . 10 2.3. End-user UI. 12 2.3.1. Password Reset . 12 2.3.2. Accessibility . 13 2.4. CLI . 15 2.5. Third Party Applications. 15 2.5.1. Eclipse IDE Plugin . 15 2.5.2. Netbeans IDE Plugin. 15 3. Concepts . 16 3.1. Users, Groups and Any Objects . 16 3.2. Type Management . 17 3.2.1. Schema . 17 Plain . 17 Derived . 18 Virtual . 18 3.2.2. AnyTypeClass . 19 3.2.3. AnyType . 19 3.2.4. RelationshipType . 21 3.2.5. Type Extensions . 22 3.3. External Resources. 23 3.3.1. Connector Bundles . 24 3.3.2. Connector Instance details . 24 3.3.3. External Resource details . 25 3.3.4. Mapping . 26 3.3.5. Linked Accounts . 29 3.4. Realms . 29 3.4.1. Realm Provisioning . 30 3.4.2. LogicActions . 31 3.5. Entitlements. 31 3.6. Privileges . 31 3.7. Roles. 31 3.7.1. Delegated Administration . 32 3.8. Provisioning. 33 3.8.1. Overview. 33 3.8.2.
  • Apache Camel

    Apache Camel

    Apache Camel USER GUIDE Version 2.0.0 Copyright 2007-2009, Apache Software Foundation 1 Table of Contents Table of Contents......................................................................... ii Chapter 1 Introduction ...................................................................................1 Chapter 2 Quickstart.......................................................................................1 Chapter 3 Getting Started..............................................................................7 Chapter 4 Architecture................................................................................ 17 Chapter 5 Enterprise Integration Patterns.............................................. 27 Chapter 6 Cook Book ................................................................................... 32 Chapter 7 Tutorials....................................................................................... 85 Chapter 8 Language Appendix.................................................................. 190 Chapter 9 Pattern Appendix..................................................................... 231 Chapter 10 Component Appendix ............................................................. 299 Index ................................................................................................0 ii APACHE CAMEL CHAPTER 1 °°°° Introduction Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful Bean Integration. Camel lets you create the Enterprise Integration
  • An Enterprise Knowledge Network

    An Enterprise Knowledge Network

    Fogbeam Labs Cut Through The Information Fog http://www.fogbeam.com An Enterprise Knowledge Network Knowledge exists in many forms inside your organization – ranging from tacit knowledge which exists only in the minds of the users who possess it, to codified knowledge stored in databases and document repositories. Unfortunately while knowledge exists throughout the organization, it is often not easy (if even possible) to locate, use, share, and reuse existing knowledge. This results in a situation often described as “the left hand doesn't know what the right hand is doing” and damages morale as employees spend their days frustrated and complaining that “nobody knows what is going on around here”. The obstacles that hinder access to existing knowledge can be cultural, geographical, social, and/or technological. And while no technological solution can guarantee perfect knowledge-sharing, tools drawn from big data, data mining / machine learning, deep learning, and artificial intelligence techniques can improve an organization's power to generate, capture, use, share and reuse knowledge. Using technologies developed as part of the semantic web initiative, and applying the principles of linked data within the enterprise, the Fogbeam Labs Enterprise Knowledge Network approach can help your firm integrate and aggregate knowledge which is spread across your existing enterprise applications, content repositories and Intranet. An Enterprise Knowledge Network enables your firm's capabilities to: • engage in high levels of knowledge transfer and
  • Polycom Realpresence Cloudaxis Open Source Software OFFER

    Polycom Realpresence Cloudaxis Open Source Software OFFER

    Polycom® RealPresence® CloudAXIS™ Suite OFFER of Source for GPL and LGPL Software You may have received from Polycom®, certain products that contain—in part—some free software (software licensed in a way that allows you the freedom to run, copy, distribute, change, and improve the software). As a part of this product, Polycom may have distributed to you software, or made electronic downloads, that contain a version of several software packages, which are free software programs developed by the Free Software Foundation. With your purchase of the Polycom RealPresence® CloudAXIS™ Suite, Polycom has granted you a license to the above-mentioned software under the terms of the GNU General Public License (GPL), GNU Library General Public License (LGPLv2), GNU Lesser General Public License (LGPL), or BSD License. The text of these Licenses can be found at the internet address provided in Table A. For at least three years from the date of distribution of the applicable product or software, we will give to anyone who contacts us at the contact information provided below, for a charge of no more than our cost of physically distributing, the following items: • A copy of the complete corresponding machine-readable source code for programs listed below that are distributed under the GNU GPL • A copy of the corresponding machine-readable source code for the libraries listed below that are distributed under the GNU LGPL, as well as the executable object code of the Polycom work that the library links with The software included or distributed for the product, including any software that may be downloaded electronically via the internet or otherwise (the "Software") is licensed, not sold.
  • Legacy Character Sets & Encodings

    Legacy Character Sets & Encodings

    Legacy & Not-So-Legacy Character Sets & Encodings Ken Lunde CJKV Type Development Adobe Systems Incorporated bc ftp://ftp.oreilly.com/pub/examples/nutshell/cjkv/unicode/iuc15-tb1-slides.pdf Tutorial Overview dc • What is a character set? What is an encoding? • How are character sets and encodings different? • Legacy character sets. • Non-legacy character sets. • Legacy encodings. • How does Unicode fit it? • Code conversion issues. • Disclaimer: The focus of this tutorial is primarily on Asian (CJKV) issues, which tend to be complex from a character set and encoding standpoint. 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated Terminology & Abbreviations dc • GB (China) — Stands for “Guo Biao” (国标 guóbiâo ). — Short for “Guojia Biaozhun” (国家标准 guójiâ biâozhün). — Means “National Standard.” • GB/T (China) — “T” stands for “Tui” (推 tuî ). — Short for “Tuijian” (推荐 tuîjiàn ). — “T” means “Recommended.” • CNS (Taiwan) — 中國國家標準 ( zhôngguó guójiâ biâozhün) in Chinese. — Abbreviation for “Chinese National Standard.” 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated Terminology & Abbreviations (Cont’d) dc • GCCS (Hong Kong) — Abbreviation for “Government Chinese Character Set.” • JIS (Japan) — 日本工業規格 ( nihon kôgyô kikaku) in Japanese. — Abbreviation for “Japanese Industrial Standard.” — 〄 • KS (Korea) — 한국 공업 규격 (韓國工業規格 hangug gongeob gyugyeog) in Korean. — Abbreviation for “Korean Standard.” — ㉿ — Designation change from “C” to “X” on August 20, 1997. 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated Terminology & Abbreviations (Cont’d) dc • TCVN (Vietnam) — Tiu Chun Vit Nam in Vietnamese. — Means “Vietnamese Standard.” • CJKV — Chinese, Japanese, Korean, and Vietnamese. 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated What Is A Character Set? dc • A collection of characters that are intended to be used together to create meaningful text.
  • Basis Technology Unicode対応ライブラリ スペックシート 文字コード その他の名称 Adobe-Standard-Encoding A

    Basis Technology Unicode対応ライブラリ スペックシート 文字コード その他の名称 Adobe-Standard-Encoding A

    Basis Technology Unicode対応ライブラリ スペックシート 文字コード その他の名称 Adobe-Standard-Encoding Adobe-Symbol-Encoding csHPPSMath Adobe-Zapf-Dingbats-Encoding csZapfDingbats Arabic ISO-8859-6, csISOLatinArabic, iso-ir-127, ECMA-114, ASMO-708 ASCII US-ASCII, ANSI_X3.4-1968, iso-ir-6, ANSI_X3.4-1986, ISO646-US, us, IBM367, csASCI big-endian ISO-10646-UCS-2, BigEndian, 68k, PowerPC, Mac, Macintosh Big5 csBig5, cn-big5, x-x-big5 Big5Plus Big5+, csBig5Plus BMP ISO-10646-UCS-2, BMPstring CCSID-1027 csCCSID1027, IBM1027 CCSID-1047 csCCSID1047, IBM1047 CCSID-290 csCCSID290, CCSID290, IBM290 CCSID-300 csCCSID300, CCSID300, IBM300 CCSID-930 csCCSID930, CCSID930, IBM930 CCSID-935 csCCSID935, CCSID935, IBM935 CCSID-937 csCCSID937, CCSID937, IBM937 CCSID-939 csCCSID939, CCSID939, IBM939 CCSID-942 csCCSID942, CCSID942, IBM942 ChineseAutoDetect csChineseAutoDetect: Candidate encodings: GB2312, Big5, GB18030, UTF32:UTF8, UCS2, UTF32 EUC-H, csCNS11643EUC, EUC-TW, TW-EUC, H-EUC, CNS-11643-1992, EUC-H-1992, csCNS11643-1992-EUC, EUC-TW-1992, CNS-11643 TW-EUC-1992, H-EUC-1992 CNS-11643-1986 EUC-H-1986, csCNS11643_1986_EUC, EUC-TW-1986, TW-EUC-1986, H-EUC-1986 CP10000 csCP10000, windows-10000 CP10001 csCP10001, windows-10001 CP10002 csCP10002, windows-10002 CP10003 csCP10003, windows-10003 CP10004 csCP10004, windows-10004 CP10005 csCP10005, windows-10005 CP10006 csCP10006, windows-10006 CP10007 csCP10007, windows-10007 CP10008 csCP10008, windows-10008 CP10010 csCP10010, windows-10010 CP10017 csCP10017, windows-10017 CP10029 csCP10029, windows-10029 CP10079 csCP10079, windows-10079