DOCSLIB.ORG

Abstraction Data, 81 Standards For, 4, 6–7, 10 Acceleration, 117, 188 ACID

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

MEGGINSON_Index.ps 11/11/04 10:31 AM Page 215 Index Abstraction Auditing data, 80 data, 81 Authors, in-line markup for, 154 standards for, 4, 6–7, 10 Automated conversions with legacy Acceleration, 117, 188 information, 181 ACID (atomicity, consistency, isolation, Automation, 77 durability) tests, 103–105 Addressable data, 98 B2B (business-to-business) Adobe PostScript language automation for, 77 as de facto standard, 26 types of, 134–135 for printing, 73 Backward compatibility, 44 Advanced searches, 148–149 Base64 encoding, 96 Aircraft manuals, 56, 74 Batch requests, 116 American Iron and Steel Institute, 17 Batch searching, 37 American National Standards Institute Berners-Lee, Tim, 13, 162 (ANSI), 11 Binary data Analysis of legacy information, 173–174 external references, 96 ANSI (American National Standards internal, 96–97 Institute), 11 representations of, 189 APIs, 22 space efficiency in, 186 Application specifications, 24–25 Binary Large Objects (BLOBs), 34, 36 Archiving data Binding benefits of, 80 data, 94, 109–110 in XML projects, 34, 36 programming languages, 22 Artificial intelligence in search process, 162 in WSDL, 128–129 Associating Style Sheets with XML BIS (Bureau of Indian Standards), 11 Documents, 20 Bloat in legacy information, 175–176 Asynchronous networking, 119, 126–127 BLOBs (Binary Large Objects), 34, 36 Atomicity in ACID test, 103 Bloomberg service, 38 Attributes Boolean searches, 148 in markup, 64 Bourret, Ronald, 110 in relationships, 87 Bray, Tim, 147–148 repetition of, 188 Broadcast networking, 119 215 MEGGINSON_Index.ps 11/11/04 10:31 AM Page 216 216 Index Budgets in XML projects, 46–47 CompuServe, 33 Bureau of Indian Standards (BIS), 11 Computer games, external metadata for, 158 Business documents, 134 Concurrent version system (CVS), 36, 74 Business-to-business (B2B) Consistency automation for, 77 in ACID test, 103 types of, 134–135 in standards, 27–29 bzip2 program, 199 Content management of, 74–75 CALS Table Model, 21 non-XML, 95–97 Canonical XML, 19 vs. protocols, 136–137 Capitalization, 58–59 Context in searches, 143–145 Cascading style sheets (CSS), 12 Converting as filters, 23 currency, 147 XML support in, 69 legacy information, 177–182 CDATA sections, 52 XML to HTML, 38 Change markup, 62–63 CORBA (Common Object Request Broker custom publishing issues in, Architecture), 121 65–66 Core specifications, 18 problems from, 63–65 Correlation in searches, 145–147 Character large objects (CLOBs), 36 Country identification codes, 11, Character size, 197–198 100 Client-side rendering, 38 Cover, Robin, 8, 17, 25 Client-side XML, 69 Cover Pages, 8, 17, 25 CLOBs (character large objects), 36 Creation stage in XML projects, 34–35 Cluster computing vs. grid computing, 131 Cross-conversions with legacy information, Code reduction in legacy information, 172 177 Collaboration protocol profiles, 135 Currency Collections, 98 codes for, 11, 100 Common data styles, 81–82 converting, 147 graph, 85–90 Custom coding, transformation for, 37 hierarchical, 90–92 Custom libraries, reading XML with, 110 tabular, 82–85 Custom programming for queries, 192 Common Object Request Broker Custom publishing, 56, 65–66 Architecture (CORBA), 121 CVS (concurrent version system), 36, 74 Compatibility networking for, 115–116 Data, 77 in standards, 27–29 abstraction, 81 in XML projects, 44–46 advantages of, 78 Compressed XML, 107 archiving and auditing, 80 Compression, 199 binding, 94, 109–110 MEGGINSON_Index.ps 11/11/04 10:31 AM Page 217 Index 217 common styles, 81–82 Disruptive technologies, 33, 40 graph, 85–90 Distributed Component Object Model hierarchical, 90–92 (DCOM), 121 tabular, 82–85 Distributed computing, 131 data typing, 105–108 DocBook specification, 13 identification of, 98–99 interoperability with, 151 existing schemes for, 100 for Linux, 25 future possibilities, 101–103 for master documents, 54 in searches, 146 words in, 145 interoperability of, 80–81 Document Object Model (DOM) markup issues in, 93 for parsing, 190–191 non-XML content, 95–97 programming bindings for, 22 whitespace handling, 93–95 tree-based, 180, 185, 192 platform and storage independence, W3C working group for, 13 78–79 Document type definitions (DTDs), 23 resources for, 81 costs of, 46 reusability of, 79 external, referencing, 189–190 self-documentation, 79 for searching, 159–161 summary, 111 top-levels of, 75 transactions, 103–105 validation, 27–28 verification, 79–80 Documents, XML, 51–53 Data interchange format (DIF), 78–79 change markup in, 62–66 Data-oriented XML, 93 client-side XML, 69 Database metadata in searches, 37 content management in, 74–75 DataPower, 188 custom publishing, 56 DCMI (Dublin Core Metadata Initiative), 15, hybrid data publishing, 55–56 149–150 idioms, 72–74 DCOM (Distributed Component Object knowledge preservation in, 58–59 Model), 121 layout control for, 61–62 De facto vs. de jure standards, looseleaf publishing, 66–67 26–27 multiple text flows in, 67–69 Denormalized documents, 71 people limitations in, 60–61 Department of Defense (DoD) networking reusability of, 57, 70–72 model, 136 single-source publishing, 53–54 Diagrams, UML, 25 summary, 76 Dictionaries, 74–75 DoD (Department of Defense) networking DIF (data interchange format), model, 136 78–79 DOM (Document Object Model) Direct mapping to programming interfaces, for parsing, 190–191 110 programming bindings for, 22 MEGGINSON_Index.ps 11/11/04 10:31 AM Page 218 218 Index DOM (Document Object Model) (cont.) Event-based interfaces, 190–191 tree-based, 180, 185, 192 Everything-is-a-string philosophy, 98 W3C working group for, 13 Excel spreadsheet DOM-like interfaces, 190–191 as standard, 78 pipelines in, 197 tabular style for, 82 for XSLT, 194 XML format for, 24 Domain names, 102–103 Expressions, XPath, 193 Down conversions with legacy information, Extensibility 177 in networking, 114–115 DTDs. See Document type definitions in XML projects, 44–46 (DTDs) Extensible Business Reporting Language Dublin Core (XBRL) format, 80 for consistency and compatibility, 29 Extensible Hypertext Markup Language for RDF data, 156 (XHTML), 25 with Semantic Web, 164 consistency in, 29 Dublin Core Metadata Initiative (DCMI), 15, interoperability with, 151 149–150 External metadata in searches, 154–159 Duplicated parsing, 196–197 External references, 189–190 Durability in ACID test, 104 Facades for legacy interfaces, 168–170 ebXML Fatal errors, 115 as B2B initiative, 135 Fear, uncertainty, and doubt (FUD) development of, 14 standards, 7–8 EDI (electronic data interchange), 14, Feed readers and aggregators in RSS, 134 134–135 Fielding, Roy, 119 8-bit ASCII encoding, 197 Financial-planning software, 133 Element content, 95 Firewalls, 117 Element names, repetition of, 188 Flexibility in switching, 139 Emacs LISP language, 70 Footnotes, text flow in, 68 Embeddable specifications, 19–21 Format level, interoperability in, 5 Emergency phone service, 5 Formats vs. protocols, 113 Empty tags, 63 Formatting Encoding, 189, 197–198 change markup, 62–66 End users in search process, 161 as information, 58–59 Enterprise resource planning (ERP), 176 vs. meaning, 54 Entities in relationships, 87 Forward compatibility, 44–46 Enumerated values, 106 FoxPro, 78 ERP (enterprise resource planning), Frustration problem, 41 176 FTP, plaintext with, 185, 187 MEGGINSON_Index.ps 11/11/04 10:31 AM Page 219 Index 219 FUD (fear, uncertainty, and doubt) standards, for online documentation, 53 7–8 SGML inspiration for, 52 Full-text searches, 37, 143 vs. XML, 78 Fully normalized data, 86–90 HTTP (Hypertext Transfer Protocol) extensibility of, 115 Generalized Markup Language (GML), 51 GET headers in, 137–138 GET headers and requests library problems with, 10 in HTTP, 137–138 plaintext with, 185, 188 in SOAP, 123 specifications for, 12 Global identifiers, 100–102 support for, 113 Globus Toolkit, 132 for transport, 34 GML (Generalized Markup Language), 51 Human intelligence in search process, 161 Gnumeric spreadsheet, XML format for, 24 Human-readable format, 170–172 Goldfarb, Charles, 51 Hybrid data publishing, 55–56 Google search engine, 143–144 Hypertext Markup Language. See HTML Granularity (Hypertext Markup Language) in in-line markup, 153 Hypertext Transfer Protocol. See HTTP in legacy information mismatches, (Hypertext Transfer Protocol) 174–175 HyTime specification, 157 Graph style, 85–90 Graphic Communications Association, 14 IANA (Internet Assigned Numbers Grid computing, 131–132 Authority), 101 Growth in legacy information, 176 IBM databases, XML support for, 36 Hardware acceleration, 117, 188 ICANN (International Corporation for Hardware support in performance, 187–188 Assigned Names and Numbers), 101 Headers in HTTP, 137–138 ICAO (International Civil Aviation Health Level Seven (HL7), 17 Organization) airport identifiers, 101 Heuristics in legacy information ICE (Information and Content Exchange), conversions, 177 15, 38, 134 Hierarchical style, 90–92 IDEAlliance, 14–15 Holman, Ken, 23, 195 Identification of data, 98–99 Homographs in searches, 144 existing schemes for, 100 HTML (Hypertext Markup Language) future possibilities, 101–103 converting XML to, 38 in searches, 146 development of, 12 Idioms, 72–74 extensibility of, 115 IETF (Internet Engineering Task Force), 12 forms and scripts with, 9 Ignorable whitespace, 95 meta elements in, 149–150 In-line markup, 151–154 MEGGINSON_Index.ps 11/11/04 10:31 AM Page 220 220 Index Independence, platform and storage, 78–79 Invited experts, 13 Indexes IP (Internet Protocol), 115 in in-line markup, 152 IPC (interprocess communications), 121 in structural searches, 37 IPTC (International
Recommended publications
  • Getting Started with Libreoffice 3.4 Copyright

    Getting Started with Libreoffice 3.4 Copyright

    Getting Started with LibreOffice 3.4 Copyright This document is Copyright © 2010–2012 by its contributors as listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/3.0/), version 3.0 or later. Contributors Jean Hollis Weber Jeremy Cartwright Ron Faile Jr. Martin Fox Dan Lewis David Michel Andrew Pitonyak Hazel Russman Peter Schofield John A Smith Laurent Balland-Poirier Cover art: Drew Jensen Christoph Noack Klaus-Jürgen Weghorn Jean Hollis Weber Acknowledgements This book is adapted and updated from Getting Started with OpenOffice.org 3.3. The contributors to that book are listed on page 13. Feedback Please direct any comments or suggestions about this document to: [email protected] Publication date and software version Published 10 September 2012. Based on LibreOffice 3.5.6. Documentation for LibreOffice is available at http://www.libreoffice.org/get-help/documentation Contents Copyright..................................................................................................................................... 2 Note for Mac users...................................................................................................................... 8 Preface.................................................................................................................................. 9 Who is this book for?................................................................................................................
  • On the Integrity and Trustworthiness of Web Produced Data

    On the Integrity and Trustworthiness of Web Produced Data

    CORE Metadata, citation and similar papers at core.ac.uk Provided by Open Repository of the University of Porto On the Integrity and Trustworthiness of web produced data Luís A. Maia Mestrado Integrado em Engenharia de Redes e Sistemas Informáticos Departamento de Ciência de Computadores 2013 Orientador Professor Doutor Manuel Eduardo Carvalho Duarte Correia, Professor Auxiliar do Departamento de Computadores, Faculdade de Ciências da Universidade do Porto Todas as correções determinadas pelo júri, e só essas, foram efetuadas. O Presidente do Júri, Porto, ______/______/_________ Acknowledgments I would like to express my appreciation for the help of my supervisor in researching and bringing different perspectives and to thank my family, for their support and dedication. 3 Abstract Information Systems have been a key tool for the overall performance improvement of administrative tasks in academic institutions. While most systems intend to deliver a paperless environment to each institution it is recurrent that document integrity and accountability is still relying on traditional methods such as producing physical documents for signing and archiving. While this method delivers a non-efficient work- flow and has an effective monetary cost, it is still the common method to provide a degree of integrity and accountability on the data contained in the databases of the information systems. The evaluation of a document signature is not a straight forward process, it requires the recipient to have a copy of the signers signature for comparison and training beyond the scope of any office employee training, this leads to a serious compromise on the trustability of each document integrity and makes the verification based entirely on the trust of information origin which is not enough to provide non-repudiation to the institutions.
  • XML Signature/Encryption — the Basis of Web Services Security

    XML Signature/Encryption — the Basis of Web Services Security

    Special Issue on Security for Network Society Falsification Prevention and Protection Technologies and Products XML Signature/Encryption — the Basis of Web Services Security By Koji MIYAUCHI* XML is spreading quickly as a format for electronic documents and messages. As a consequence, ABSTRACT greater importance is being placed on the XML security technology. Against this background research and development efforts into XML security are being energetically pursued. This paper discusses the W3C XML Signature and XML Encryption specifications, which represent the fundamental technology of XML security, as well as other related technologies originally developed by NEC. KEYWORDS XML security, XML signature, XML encryption, Distributed signature, Web services security 1. INTRODUCTION 2. XML SIGNATURE XML is an extendible markup language, the speci- 2.1 Overview fication of which has been established by the W3C XML Signature is an electronic signature technol- (WWW Consortium). It is spreading quickly because ogy that is optimized for XML data. The practical of its flexibility and its platform-independent technol- benefits of this technology include Partial Signature, ogy, which freely allows authors to decide on docu- which allows an electronic signature to be written on ment structures. Various XML-based standard for- specific tags contained in XML data, and Multiple mats have been developed including: ebXML and Signature, which enables multiple electronic signa- RosettaNet, which are standard specifications for e- tures to be written. The use of XML Signature can commerce transactions, TravelXML, which is an EDI solve security problems, including falsification, spoof- (Electronic Data Interchange) standard for travel ing, and repudiation. agencies, and NewsML, which is a standard specifica- tion for new distribution formats.
  • Sams Teach Yourself XML in 21 Days

    Sams Teach Yourself XML in 21 Days

    Steven Holzner Teach Yourself XML in 21 Days THIRD EDITION 800 East 96th Street, Indianapolis, Indiana, 46240 USA Sams Teach Yourself XML in 21 Days, ASSOCIATE PUBLISHER Michael Stephens Third Edition ACQUISITIONS EDITOR Copyright © 2004 by Sams Publishing Todd Green All rights reserved. No part of this book shall be reproduced, stored in a retrieval DEVELOPMENT EDITOR system, or transmitted by any means, electronic, mechanical, photocopying, record- Songlin Qiu ing, or otherwise, without written permission from the publisher. No patent liability MANAGING EDITOR is assumed with respect to the use of the information contained herein. Although every precaution has been taken in the preparation of this book, the publisher and Charlotte Clapp author assume no responsibility for errors or omissions. Nor is any liability assumed PROJECT EDITOR for damages resulting from the use of the information contained herein. Matthew Purcell International Standard Book Number: 0-672-32576-4 INDEXER Library of Congress Catalog Card Number: 2003110401 Mandie Frank PROOFREADER Printed in the United States of America Paula Lowell First Printing: October 2003 TECHNICAL EDITOR 06050403 4321 Chris Kenyeres Trademarks TEAM COORDINATOR Cindy Teeters All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. Sams Publishing cannot attest to the accuracy INTERIOR DESIGNER of this information. Use of a term in this book should not be regarded as affecting Gary Adair the validity of any trademark or service mark. COVER DESIGNER Warning and Disclaimer Gary Adair PAGE LAYOUT Every effort has been made to make this book as complete and as accurate as possi- ble, but no warranty or fitness is implied.
  • Bibliography of Erik Wilde

    Bibliography of Erik Wilde

    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
  • Feasibility and Performance Evaluation of Canonical XML

    Feasibility and Performance Evaluation of Canonical XML

    Feasibility and Performance Evaluation of Canonical XML Student Research Project Manuel Binna Student: E-mail: [email protected] Matriculation Number: 108004202162 Supervisor: Dipl.-Inf. Meiko Jensen Period: 20.07.2010 - 19.10.2010 Chair for Network and Data Security Prof. Dr. Jörg Schwenk Faculty of Electrical Engineering and Information Technology Ruhr University Bochum Feasibility and Performance Evaluation of Canonical XML Manuel Binna Abstract Within the boundaries of the XML specification, XML documents can be formatted in various ways without losing the logical equivalence of its content within the scope of the application. However, some applications like XML Signature cannot deal with this flexibility, thus needing a definite textual representation in order to distinguish changes which do or do not alter the logical equivalence of XML content. Canonical XML provides a method to transform textually different yet logically equivalent XML content into a single definite textual representation. This work evaluates the upcoming new major version Canonical XML Version 2.0 with respect to feasibility and performance. Chair for Network and Data Security, Ruhr University Bochum 2 Feasibility and Performance Evaluation of Canonical XML Manuel Binna Declaration I hereby declare that the content of this thesis is a work of my own and that it is original to the best of my knowledge, except where indicated by references to other sources. ____________________________ ______________________________________ Location, Date Signature Chair for Network and Data Security, Ruhr University Bochum 3 Feasibility and Performance Evaluation of Canonical XML Manuel Binna Table of Contents 1. Introduction! 5 1.1.XML 5 1.2.Canonicalization 6 1.3.History 7 1.4.Canonicalization and XML Signature 16 2.
  • Microsoft Exchange 2007 Journaling Guide

    Microsoft Exchange 2007 Journaling Guide

    Microsoft Exchange 2007 Journaling Guide Digital Archives Updated on 12/9/2010 Document Information Microsoft Exchange 2007 Journaling Guide Published August, 2008 Iron Mountain Support Information U.S. 1.800.888.2774 [email protected] Copyright © 2008 Iron Mountain Incorporated. All Rights Reserved. Trademarks Iron Mountain and the design of the mountain are registered trademarks of Iron Mountain Incorporated. All other trademarks and registered trademarks are the property of their respective owners. Entities under license agreement: Please consult the Iron Mountain & Affiliates Copyright Notices by Country. Confidentiality CONFIDENTIAL AND PROPRIETARY INFORMATION OF IRON MOUNTAIN. The information set forth herein represents the confidential and proprietary information of Iron Mountain. Such information shall only be used for the express purpose authorized by Iron Mountain and shall not be published, communicated, disclosed or divulged to any person, firm, corporation or legal entity, directly or indirectly, or to any third person without the prior written consent of Iron Mountain. Disclaimer While Iron Mountain has made every effort to ensure the accuracy and completeness of this document, it assumes no responsibility for the consequences to users of any errors that may be contained herein. The information in this document is subject to change without notice and should not be considered a commitment by Iron Mountain. Iron Mountain Incorporated 745 Atlantic Avenue Boston, MA 02111 +1.800.934.0956 www.ironmountain.com/digital
  • A Layered Approach to XML Canonicalization

    A Layered Approach to XML Canonicalization

    A Layered Approach to XML Canonicalization A Position Paper for the W3C Workshop on Next Steps for XML Signature and XML Encryption Ed Simon, XMLsec Inc. [email protected] 1 Background ● XML Canonicalization enables reliable textual and binary comparison of XML documents through the removal of irrelevant differences in structure and content ● Current approach is to write a single specification that details how all parts of XML instances are to be canonicalized ● Proposed alternative approach is to layer canonicalization rules according to the XML stack: core, schema-specific, namespace-specific ● Potential advantages include flexibility and significant optimization of processing 2 Canonicalization Layers ● Core – Normalizes the elements, attributes, and whitespace of an XML instance ● Schema-Aware – Normalization of schema- aware aspects including default attributes, schema-defined data types, etc ● Namespace-Aware – Normalization of XML information set nodes that belong to, or are contained by nodes that belong to, an XML node declared with a particular namespace. Includes the normalization of namespace declarations themselves. 3 Core Canonicalization ● Defined much as per W3C XML Canonicalization version 1.1 ● Only canonicalizes what can be derived from the text of the XML instance ● Includes formatting of XML elements and attributes, whitespace, line breaks, CDATA, entities, etc... ● No namespace normalization (but don't worry, it's coming!) 4 Core Canonicalization Example <xsl:stylesheet version='2.0' xmlns="http://www.w3.org/1999/xhtml" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns1="http://www.xmlsec.com/namespaces/a" > <xsl:template match="/"> <p>Total Amount: <xsl:value-of ... ...select="ns1:expense-report/ns1:total"/></p> </xsl:template> </xsl:stylesheet> ...will be, after core canonicalization, found to be identical to..
  • Package 'Gnumeric'

    Package 'Gnumeric'

    Package ‘gnumeric’ March 9, 2017 Version 0.7-8 Date 2017-03-09 Title Read Data from Files Readable by 'gnumeric' Author Karoly Antal <[email protected]>. Maintainer Karoly Antal <[email protected]> Depends R (>= 2.8.1), XML Imports utils Description Read data files readable by 'gnumeric' into 'R'. Can read whole sheet or a range, from several file formats, including the native format of 'gnumeric'. Reading is done by using 'ssconvert' (a file converter utility included in the 'gnumeric' distribution <http://projects.gnome.org/gnumeric/>) to convert the requested part to CSV. From 'gnumeric' files (but not other formats) can list sheet names and sheet sizes or read all sheets. License GPL (>= 2) Repository CRAN Date/Publication 2017-03-09 13:20:28 NeedsCompilation no R topics documented: read.gnumeric.sheet . .2 read.gnumeric.sheet.info . .6 read.gnumeric.sheets . .7 Index 9 1 2 read.gnumeric.sheet read.gnumeric.sheet Read data from a gnumeric (or MS Excel, Openoffice Calc, Xbase, Quatro Pro, Paradox, HTML, etc) spreadsheet or database file using ssconvert from the gnumeric distribution Description Read data from a sheet of a gnumeric (or other common spreadsheet or database) file to a data.frame. Requires an external program, ‘ssconvert’ (normally installed with gnumeric in ‘PATH’. (Gnumeric home page is http://projects.gnome.org/gnumeric/) (Note: last gnumeric release for windows is 1.12.17 from 2014) Calls ‘ssconvert’ to convert the input to CSV. ‘ssconvert’ can read several file formats (see Details below). Note: During conversion to CSV ‘ssconvert’ also evaluates formulas (e.g. ‘=sum(A1:A3)’) in cells, and emits the result instead of the formula.
  • Forcepoint DLP Supported File Formats and Size Limits

    Forcepoint DLP Supported File Formats and Size Limits

    Forcepoint DLP Supported File Formats and Size Limits Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 This article provides a list of the file formats that can be analyzed by Forcepoint DLP, file formats from which content and meta data can be extracted, and the file size limits for network, endpoint, and discovery functions. See: ● Supported File Formats ● File Size Limits © 2021 Forcepoint LLC Supported File Formats Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 The following tables lists the file formats supported by Forcepoint DLP. File formats are in alphabetical order by format group. ● Archive For mats, page 3 ● Backup Formats, page 7 ● Business Intelligence (BI) and Analysis Formats, page 8 ● Computer-Aided Design Formats, page 9 ● Cryptography Formats, page 12 ● Database Formats, page 14 ● Desktop publishing formats, page 16 ● eBook/Audio book formats, page 17 ● Executable formats, page 18 ● Font formats, page 20 ● Graphics formats - general, page 21 ● Graphics formats - vector graphics, page 26 ● Library formats, page 29 ● Log formats, page 30 ● Mail formats, page 31 ● Multimedia formats, page 32 ● Object formats, page 37 ● Presentation formats, page 38 ● Project management formats, page 40 ● Spreadsheet formats, page 41 ● Text and markup formats, page 43 ● Word processing formats, page 45 ● Miscellaneous formats, page 53 Supported file formats are added and updated frequently. Key to support tables Symbol Description Y The format is supported N The format is not supported P Partial metadata
  • Exploring the XML World

    Exploring the XML World

    Lars Strandén SP Swedish National Testing and Research Institute develops and transfers Exploring the XML World technology for improving competitiveness and quality in industry, and for safety, conservation of resources and good environment in society as a whole. With - A survey for dependable systems Swedens widest and most sophisticated range of equipment and expertise for technical investigation, measurement, testing and certfi cation, we perform research and development in close liaison with universities, institutes of technology and international partners. SP is a EU-notifi ed body and accredited test laboratory. Our headquarters are in Borås, in the west part of Sweden. SP Swedish National Testing and Research Institute SP Swedish National Testing SP Electronics SP REPORT 2004:04 ISBN 91-7848-976-8 ISSN 0284-5172 SP Swedish National Testing and Research Institute Box 857 SE-501 15 BORÅS, SWEDEN Telephone: + 46 33 16 50 00, Telefax: +46 33 13 55 02 SP Electronics E-mail: [email protected], Internet: www.sp.se SP REPORT 2004:04 Lars Strandén Exploring the XML World - A survey for dependable systems 2 Abstract Exploring the XML World - A survey for dependable systems The report gives an overview of and an introduction to the XML world i.e. the definition of XML and how it can be applied. The content shall not be considered a development tutorial since this is better covered by books and information available on the Internet. Instead this report takes a top-down perspective and focuses on the possibilities when using XML e.g. concerning functionality, tools and supporting standards. Getting started with XML is very easy and the threshold is low.
  • Information Integration with XML

    Information Integration with XML

    Information Integration with XML Chaitan Baru Richard Marciano {baru,marciano}@sdsc.edu Data Intensive Computing Environments (DICE) Group San Diego Supercomputer Center National Partnership for Advanced Computational Infrastructure San Diego Supercomputer Center Members of the DICE Group • Staff • Students • Chaitan Baru • Pratik Mukhopadhyay • Amarnath Gupta • Azra Mulic • Bertram Ludäscher • Kevin Munroe • Richard Marciano • Paul Nguyen • Reagan Moore • Michail Petropolis • Yannis Papakonstantinou • Nicholas Puz • Arcot Rajasekar • Pavel Velikhov • Wayne Schroeder • Michael Wan • Ilya Zaslavsky Tutorial Outline • PART I • Introduction to XML • The MIX Project • PART II • Storing/retrieving XML documents • XML and GIS • Open Issues Information Integration with XML PART I • Introduction to XML • HTML vs. XML • XML Industry Initiatives • DTD, Schema, Namespaces • DOM, SAX • XSL, XSLT • Tools • The MIX Project Introduction to XML • SGML (Standard Generalized Markup Language) • ISO Standard, 1986, for data storage & exchange • Used in U.S. gvt. & contractors, large manufacturing companies, technical info. Publishers. • HTML, a simple application of SGML, 1992 - 1999 • SGML reference is 600 pages long • XML (eXtensible Markup Language) • W3C (World Wide Web Consortium) -- http://www.w3.org/XML/) recommendation in 1998 • Simple subset of SGML: “The ASCII of the Web”. • XML specification is 26 pages long • Canonical XML • equivalence testing of XML documents • SML (Simple Markup Language) • No Attributes / No Processing Instructions (PI) /