DOCSLIB.ORG

A Key for Document Interoperability?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Key for Document Interoperability? ELAN Electronic Government and Applications Feature Based Document Profiling - A Key for Document Interoperability? Bibliografische Information der Deutschen Nationalbibliothek: Die Deutsche Nationalbibliothek verzeichnet diese Publikation in der Deutschen Nationalbibliografie; detaillierte bibliografische Daten sind im Internet über http://dnb.d-nb.deabrufbar. 1.Auflage Juni 2012 Alle Rechte vorbehalten © Fraunhofer-Institut für Offene Kommunikationssysteme FOKUS, Juni 2012 Fraunhofer-Institut für Offene Kommunikationssysteme FOKUS Kaiserin-Augusta-Allee31 10589 Berlin Telefon: +49-30-3436-7115 Telefax: +49-30-3436-8000 [email protected] www.fokus.fraunhofer.de Dieses Werk ist einschließlich aller seiner Teile urheberrechtlich geschützt. Jede Ver- wertung, die über die engen Grenzen des Urheberrechtsgesetzes hinausgeht, ist ohne schriftliche Zustimmung des Instituts unzulässig und strafbar. Dies gilt insbesondere für Vervielfältigungen, Übersetzungen, Mikroverfilmungen sowie die Speicherung in elektronischen Systemen. Die Wiedergabe von Warenbezeichnungen und Handels- namen in diesem Buch berechtigt nicht zu der Annahme, dass solche Bezeichnungen im Sinne der Warenzeichen-und Markenschutz-Gesetzgebung als frei zu betrachten wären und deshalb von jedermann benutzt werden dürften. Soweit in diesem Werk direkt oder indirekt auf Gesetze, Vorschriften oder Richt-linien (z.B. DIN, VDI) Bezug genommen oder aus ihnen zitiert worden ist, kann das Institut keine Gewähr für Richtigkeit, Vollständigkeit oder Aktualität übernehmen. ISBN 978-3-00-038675-6 Feature Based Document Profiling ‐ a Key For Document Interoperability? Authors Dr. Klaus‐Peter Eckert Fraunhofer Institut FOKUS eMail: klaus‐[email protected] Kerstin Goluchowicz Technische Universität Berlin, Fachgebiet Innovationsökonomie eMail: kerstin.goluchowicz@tu‐berlin.de Dr. Stephan Gauch Technische Universität Berlin, Fachgebiet Innovationsökonomie eMail: stephan.gauch@tu‐berlin.de Björn Kirchhoff eGov Consulting and Development GmbH eMail: [email protected] i ii Feature Based Document Profiling ‐ a Key For Document Interoperability? ii iii Feature Based Document Profiling ‐ a Key For Document Interoperability? Management Summary The working group WG5 of the ISO/IEC subcommittee SC34 “Document Description and Processing Languages” performs research about “Document Interoperability” considering open document standards such as “Open Document Format ‐ ODF” and “Office Open XML ‐ OOXML”. The TransDok project (validation and transformation of selected profiles of the document standards ISO/IEC 26300 and ISO/IEC 29500), sponsored by the German Federal Ministry of Economics and Technology contributes to this research. It examines, if and how feature based document profiles can be defined and used as a means to identify interoperable subsets of both document standards, especially for typical documents used in the German public sector. Utilizing the document features identified in ISO/IEC TR 29166 (1), XML schema for the definition of document features and feature based profiles have been defined. A feature list generator has been implemented that creates a list of all features used within a document and in addition a list of all features including their relative and absolute occurrence in all documents contained in a given folder. The list can be used to identify those properties that are characteristic for the documents within the folder and to define an associated document profile. The feasibility of feature based profiles to describe common properties of document types has been analysed using mathematical classification methods. These methods show that at least typical features for certain document types exist. These features can be used to define an interoperable profile or template for a document type. In case the set of features is restricted to those that are characteristic and necessary and that allow a unique translation between both document standards an important step towards document interoperability and translation has been done. The average accuracy of our classification algorithms reaches levels above 70%, making these approaches a viable complementary option to improve classification of documents. If the ideas developed in the project are applied to typical document types in the German public sector, their interoperability and portability can be enhanced significantly. The integration of the feature list generator in archiving systems will enhance the likelihood of sustainable storage of documents and reduce interoperability problems significantly. The ideas developed in the project have been presented to ISO/IEC SC34 WG5 as well as to ODF plug fests. The results of the project are included in the current WG5 study period report and will probably influence the next work items in WG5. The project underlying this report was funded by the German Federal Ministry of Economics and Technology under grant number 01FS10017. The responsibility for the content of this publication lies with the authors. iii v Feature Based Document Profiling ‐ a Key For Document Interoperability? Contents Management Summary ......................................................................................................iii Contents ............................................................................................................................. v 1 Introduction ............................................................................................................ 1 1.1 Practical Relevance ............................................................................................. 2 2 State of the Art ........................................................................................................ 3 2.1 Open Document Formats ................................................................................... 3 2.1.1 Introduction to OOXML .................................................................................................. 4 2.1.2 Introduction to ODF ........................................................................................................ 6 2.2 Conformity and Interoperability Definitions ...................................................... 8 2.2.1 Office Open XML ............................................................................................................. 8 2.2.2 OpenDocument Format ................................................................................................ 10 2.2.3 Summary ....................................................................................................................... 12 2.3 Document Features .......................................................................................... 14 2.3.1 ISO/IEC TR 29166 .......................................................................................................... 15 2.4 Profiling and Document Interoperability .......................................................... 20 2.5 Tools and Languages ......................................................................................... 21 2.5.1 Document Packages ..................................................................................................... 21 3 Methodology ......................................................................................................... 22 3.1 Definition of Document Features ..................................................................... 22 3.2 Feature Based Profile Definition ....................................................................... 22 3.3 Profile Inspection .............................................................................................. 24 3.3.1 Binary Membership ...................................................................................................... 24 3.3.2 Statistical Membership ................................................................................................. 25 4 Technical Details .................................................................................................... 26 4.1 Feature List Generator ...................................................................................... 26 4.1.1 Using the Feature List Generator ................................................................................. 28 4.2 Profile Definition and Checking ........................................................................ 31 4.2.1 Definition and Testing of a Profile ................................................................................ 32 5 Profile Evaluation .................................................................................................. 33 5.1 Dataset and Pre‐processing .............................................................................. 34 5.2 Testbed Specifications ...................................................................................... 37 5.3 Classification Approaches ................................................................................. 38 5.3.1 Fisher Exact Tests ......................................................................................................... 38 5.3.2 Cluster Analysis and Heatmaps .................................................................................... 39 5.3.3 Logistic Regression ....................................................................................................... 41 v vi Feature Based Document Profiling ‐ a Key For Document Interoperability? 5.3.4 Recursive Partitioning Trees ........................................................................................
Load more

Recommended publications
  • XXX Format Assessment
    Digital Preservation Assessment: Date: 20/09/2016 Preservation Open Document Text (ODT) Format Team Preservation Assessment Version: 1.0 Open Document Text (ODT) Format Preservation Assessment Document History Date Version Author(s) Circulation 20/09/2016 1.0 Michael Day, Paul Wheatley External British Library Digital Preservation Team [email protected] This work is licensed under the Creative Commons Attribution 4.0 International License. Page 1 of 12 Digital Preservation Assessment: Date: 20/09/2016 Preservation Open Document Text (ODT) Format Team Preservation Assessment Version: 1.0 1. Introduction This document provides a high-level, non-collection specific assessment of the OpenDocument Text (ODT) file format with regard to preservation risks and the practicalities of preserving data in this format. The OpenDocument Format is based on the Extensible Markup Language (XML), so this assessment should be read in conjunction with the British Library’s generic format assessment of XML [1]. This assessment is one of a series of format reviews carried out by the British Library’s Digital Preservation Team. Some parts of this review have been based on format assessments undertaken by Paul Wheatley for Harvard University Library. An explanation of the criteria used in this assessment is provided in italics below each heading. [Text in italic font is taken (or adapted) from the Harvard University Library assessment] 1.1 Scope This document will primarily focus on the version of OpenDocument Text defined in OpenDocument Format (ODF) version 1.2, which was approved as ISO/IEC 26300-1:2015 by ISO/IEC JTC1/SC34 in June 2015 [2]. Note that this assessment considers format issues only, and does not explore other factors essential to a preservation planning exercise, such as collection specific characteristics, that should always be considered before implementing preservation actions.
    [Show full text]
  • Schematron Overview Excerpted from Leigh Dodds’ 2001 XSLT UK Paper, “Schematron: Validating XML Using XSLT”
    Schematron: validating XML using XSLT Schematron Overview excerpted from Leigh Dodds’ 2001 XSLT UK paper, “Schematron: validating XML using XSLT” Leigh Dodds, ingenta ltd, xmlhack.com April 2001 Abstract Schematron [Schematron] is a structural based validation language, defined by Rick Jelliffe, as an alternative to existing grammar based approaches. Tree patterns, defined as XPath expressions, are used to make assertions, and provide user-centred reports about XML documents. Expressing validation rules using patterns is often easier than defining the same rule using a content model. Tree patterns are collected together to form a Schematron schema. Schematron is a useful and accessible supplement to other schema languages. The open-source XSLT implementation is based around a core framework which is open for extension and customisation. Overview This paper provides an introduction to Schematron; an innovative XML validation language developed by Rick Jelliffe. This innovation stems from selecting an alternative approach to validation than existing schema languages: Schematron uses a tree pattern based paradigm, rather than the regular grammars used in DTDs and XML schemas. As an extensible, easy to use, open source tool Schematron is an extremely useful addition to the XML developers toolkit. The initial section of this paper conducts a brief overview of tree pattern validation, and some of the advantages it has in comparison to a regular grammar approach. This is followed by an outline of Schematron and the intended uses which have guided its design. The Schematron language is then discussed, covering all major elements in the language with examples of their 1 of 14 Schematron: validating XML using XSLT usage.
    [Show full text]
  • Markup UK 2021 Proceedings
    2021 Proceedings A Conference about XML and Other Markup Technologies Markup UK 2021 Proceedings 2 Markup UK 2021 Proceedings 3 Markup UK 2021 Proceedings Markup UK Sister Conferences A Conference about XML and Other Markup Technologies https://markupuk.org/ Markup UK Conferences Limited is a limited company registered in England and Wales. Company registration number: 11623628 Registered address: 24 Trimworth Road, Folkestone, CT19 4EL, UK VAT Registration Number: 316 5241 25 Organisation Committee Geert Bormans Tomos Hillman Ari Nordström Andrew Sales Rebecca Shoob Markup UK 2021 Proceedings Programme Committee by B. Tommie Usdin, David Maus, Syd Bauman – Northeastern University Alain Couthures, Michael Kay, Erik Digital Scholarship Group Siegel, Debbie Lapeyre, Karin Bredenberg, Achim Berndzen – <xml-project /> Jaime Kaminski, Robin La Fontaine, Abel Braaksma – Abrasoft Nigel Whitaker, Steven Pemberton, Tony Peter Flynn – University College Cork Graham and Liam Quin Tony Graham – Antenna House Michael Kay – Saxonica The organisers of Markup UK would like to Jirka Kosek – University of Economics, thank Antenna House for their expert and Prague unstinting help in preparing and formatting Deborah A. Lapeyre – Mulberry the conference proceedings, and their Technologies generosity in providing licences to do so. David Maus – State and University Library Hamburg Antenna House Formatter is based on the Adam Retter – Evolved Binary W3C Recommendations for XSL-FO and B. Tommie Usdin – Mulberry Technologies CSS and has long been recognized as Norman Walsh – MarkLogic the most powerful and proven standards Lauren Wood – XML.com based formatting software available. It is used worldwide in demanding applications Thank You where the need is to format HTML and XML into PDF and print.
    [Show full text]
  • Xml Schema Viewer Eclipse
    Xml Schema Viewer Eclipse Archy exchanging worshipfully. Angelico have her sabra causelessly, intoxicant and unarranged. Is Thebault rugose or nonchalant when precluded some mesa hurts contrary? Some problems where the next button to elements and stored as we help you speed up xml schema support for working group In xml to. For anyone interested, I can give up altove xmlspy, copy and paste this URL into your RSS reader. Dtd schema viewer and xml query systems that corresponds to modify or personal. The Dictionary panel allows you to customize the dictionary that the Spell tool uses to identify misspelled words. Our plugin communicate with the analyzer through an XML file. Mac os x in multiple namespaces may appear in doing so that are very heavy use plugin i deal with eclipse dali java classes available enable increased automation. It uses to define and editor can be defined using xml is a full unicode support for example will go inside this interview he discusses specifying xml? Xsd schemas face when each row to xml using xml production implementations to. Strive to be All Powerful? Distinction between wood type definition and lobby of ring type: unlike XDR, a token was implemented that maps XInterfaces to a class framework in Java, a full eclipse install guide be overkill. XML bean definition files. This schema viewer for eclipse ide or sets. Kerberos realm of schemas will remain interoperable by running the viewer. UML associations and myself use interleave properly. This sentence exists because of the design problem; lacking a concept for what a primitive data type is, documentation can be written to provide some information on that element.
    [Show full text]
  • International Standard Iso/Iec 26300-2
    This is a previewINTERNATIONAL - click here to buy the full publication ISO/IEC STANDARD 26300-2 First edition 2015-07-01 Information technology — Open Document Format for Office Applications (OpenDocument) v1.2 — Part 2: Recalculated Formula (OpenFormula) Format Technologies de l’information — Format de document ouvert pour applications de bureau (OpenDocument) v1.2 — Partie 2: Titre manque Reference number ISO/IEC 26300-2:2015(E) © ISO/IEC 2015 ISO/IEC 26300-2:2015(E) This is a preview - click here to buy the full publication COPYRIGHT PROTECTED DOCUMENT © ISO/IEC 2015 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form orthe by requester. any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of Case postale 56 • CH-1211 Geneva 20 ISOTel. copyright+ 41 22 749 office 01 11 Fax + 41 22 749 09 47 Web www.iso.org E-mail [email protected] Published in Switzerland ii © ISO/IEC 2015 – All rights reserved This is a preview - click here to buy the full publication ISO/IEC 26300-2:2015(E) Open Document Format for Office Applications (OpenDocument) Version 1.2 Part 2: Recalculated Formula (OpenFormula) Format OASIS Standard 29 September 2011 Specification URIs: This version: http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.odt (Authoritative) http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.pdf
    [Show full text]
  • Introduction to Schematron
    Introduction to Schematron Wendell Piez and Debbie Lapeyre Mulberry Technologies, Inc. 17 West Jefferson St. Suite 207 Rockville MD 20850 Phone: 301/315-9631 Fax: 301/315-8285 [email protected] http://www.mulberrytech.com Version 90-1.0 (November 2008) © 2008 Mulberry Technologies, Inc. Introduction to Schematron Administrivia...................................................................................................................... 1 Schematron is a ................................................................................................................. 1 Reasons to use Schematron............................................................................................... 1 What Schematron is used for............................................................................................ 2 Schematron is an XML vocabulary................................................................................... 2 Schematron specifies, it does not perform........................................................................ 2 Simple Schematron processing architecture...................................................................... 3 Schematron validation in action........................................................................................ 4 Basic Schematron building blocks................................................................................. 4 How Schematron works.................................................................................................. 4 Outline of a simple Schematron
    [Show full text]
  • ODF Workshop
    ODF Workshop ODF: The Past, Present and Future Michael Brauer, Sun, ODF TC Chair ODF Accessibility Pete Brunet, IBM, ODF Accessibility Subcommittee ODF Programmability Rob Weir, IBM, ODF TC Michael Brauer, Sun, ODF TC Chair ODF Interoperability Alan Clark, Novell, ODF Adoption TC Rob Weir, IBM, ODF TC ODF Adoption Don Harbison, IBM, ODF Adoption TC Co-Chair OASIS OpenDocument ISO/IEC 26300 The Past, the Present, and the Future Michael Brauer Technical Architect Software Engineering StarOffice/OpenOffice.org Sun Microsystems About the Speaker Technical Architect in Sun Microsystem's OpenOffice.org/StarOffice development OpenOffice.org/StarOffice developer since 1995 Main focus: Office application development/file formats and XML technologies OpenOffice.org XML project owner OASIS OpenDocument Technical Committee chair Agenda The Past - History of OASIS OpenDocument format The Present – Sub Committees, Work in Progress The Future – OpenDocument v1.2 The Past 1999 Development of “StarOffice XML” file format starts Primary goal: interoperability 2000 Sun contributes StarOffice to OpenOffice.org “StarOffice XML” becomes “OpenOffice.org XML” open source community project First OpenOffice.org XML working draft publicly available 2001 OpenOffice.org XML is used as default file format for OpenOffice.org 1.0/Sun StarOffice 6.0 software 2002 Foundation of OASIS OpenDocument Technical Committee (TC) Basis of TC's work: OpenOffice.org XML file format OpenDocument TC Charter (Extract) The purpose [...] is to create an open, XML-based file format specification for office applications. [it] must meet the following requirements: it must be suitable for office documents containing text, spreadsheets, charts, and graphical documents, it must retain high-level information suitable for editing the document, it must be friendly to transformations using XSLT or similar XML-based languages or tools, it should 'borrow' from similar, existing standards wherever possible and permitted.
    [Show full text]
  • Comparing Libreoffice and Apache Openoffice Libreoffice and Apache Openoffice Both Are Derived from the Former Openoffice.Org Project
    Comparing LibreOffice and Apache OpenOffice LibreOffice and Apache OpenOffice both are derived from the former OpenOffice.org project. Over the years, the differences have grown and these documents offer a list of all the changes. This document is the starting point for the information comparing the two office suites. Time line showing the various releases AOO 3.4 4.0 4.1 LO 3.3 3.4 3.5 3.6 4.0 4.1 4.2 4.3 4.4 … 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 2010 2011 2012 2103 2014 2015 Each ApacheOpenOffice release gets one update Each LibreOffice release typically gets 6 or 7 updates links to release information wiki.documentfoundation.org/ReleaseNotes/3.4 wiki.documentfoundation.org/ReleaseNotes/3.5 cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Release+Notes wiki.documentfoundation.org/ReleaseNotes/3. 6 wiki.documentfoundation.org/ReleaseNotes/ 4.0 cwiki.apache.org/confluence/display/OOOUSERS/AOO+ 4 . 0 +Release+Notes wiki.documentfoundation.org/ReleaseNotes/ 4.1 wiki.documentfoundation.org/ReleaseNotes/ 4.2 cwiki.apache.org/confluence/display/OOOUSERS/AOO+ 4 . 1 +Release+Notes wiki.documentfoundation.org/ReleaseNotes/ 4.3 wiki.documentfoundation.org/ReleaseNotes/ 4.4 Simply the office suites are composed of 3 'layers' 1.
    [Show full text]
  • XML in 10 Points
    The QAML FAQ file:///Users/trc/Desktop/QAML-playground/qaml-faq.html The QAML FAQ The QAML F.A.Q. Table of Contents The QAML F.A.Q. A. General A.1. What is a FAQ? A.2. What is a Markup Language? A.3. What is QAML? This FAQ is about QAML, a markup A.4. Who wrote QAML? A.5. Why not just use HTML? language for internet FAQs. B. About Writing QAML Documents QAML is the Question and Answer B.1. How can I write a QAML document? Markup Language. B.2 What is the smallest QAML document? B.3. How can I make a list in [Table of Contents] QAML? B.4. What stylesheets are available for QAML? B.5. How can I make a hypertext link? A. General B.6. What is the relationship between QAML metadata and Dublin Core? [ A.1. What is a FAQ? ] B.7. What is the gist attribute? B.8. Why is the email address of the author mandatory? B.9. How can I include graphics? Rick Jelliffe, [email protected] C. Processing QAML documents C.1. What can I use QAML documents for? A FAQ is the nickname for a "Frequently C.2. What are text processing languages? Asked Questions" document. There are D. QAML and Standards thousands of FAQs available on the D.1. Are Standards Useful? World Wide Web on many different D.2. What is XML? D.3. What is I18n? topics. The basic format of a FAQ is that D.4. What is Accessability? D.5.
    [Show full text]
  • Open Document Format for Office Applications (Opendocument) Version 1.2
    Open Document Format for Office Applications (OpenDocument) Version 1.2 Part 2: Recalculated Formula (OpenFormula) Format OASIS Standard 29 September 2011 Specification URIs: This version: http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.odt (Authoritative) http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.pdf http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.html Previous version: http://docs.oasis-open.org/office/v1.2/csd06/OpenDocument-v1.2-csd06-part2.odt (Authoritative) http://docs.oasis-open.org/office/v1.2/csd06/OpenDocument-v1.2-csd06-part2.pdf http://docs.oasis-open.org/office/v1.2/csd06/OpenDocument-v1.2-csd06-part2.html Latest version: http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2-part2.odt (Authoritative) http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2-part2.pdf http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2-part2.html Technical Committee: OASIS Open Document Format for Office Applications (OpenDocument) TC Chairs: Rob Weir, IBM Michael Brauer, Oracle Corporation Editors: OpenDocument-v1.2-os-part2 29 September 2011 Copyright © OASIS Open 2002 - 2011. All Rights Reserved. Standards Track Work Product Page 1 of 234 David A. Wheeler Patrick Durusau Eike Rathke, Oracle Corporation Rob Weir, IBM Related work: This document is part of the OASIS Open Document Format for Office Applications (OpenDocument) Version 1.2 specification. The OpenDocument v1.2 specification has these parts: OpenDocument v1.2 part 1: OpenDocument Schema OpenDocument v1.2 part 2: Recalculated Formula (OpenFormula) Format (this part) OpenDocument v1.2 part 3: Packages Declared XML namespaces: None.
    [Show full text]
  • XML – Grammatiken Und Xforms Von Astrid Sackel
    XML – Grammatiken und XForms von Astrid Sackel im Rahmen des Seminars XML und intelligente Systeme bei Sebastian Wrede und Ingo Lütkebohle Uni Bielefeld Wintersemester 2005|06 31. Oktober 2005 XML – GRAMMATIKEN UND XFORMS ASTRID SACKEL XML und intelligente Systeme Uni Bielefeld WS 2005 | 06 Wozu eigentlich Grammatiken? Einleitung DTD XML Schema RelaxNG XForms Fazit Quellen 2 | 45 XML – GRAMMATIKEN UND XFORMS ASTRID SACKEL XML und intelligente Systeme Uni Bielefeld WS 2005 | 06 Wozu eigentlich Grammatiken? Fallbeispiel: „Hans und Peter arbeiten an einer Adressbuch- Datenbank, sie haben die ähnliche Vorstellung von der Struktur, aber nicht exakt dieselbe“ Einleitung DTD XML Schema RelaxNG XForms Fazit Quellen 3 | 45 DTD XML DTD XML – GRAMMATIKEN UND XFORMS ASTRID SACKEL XML und intelligente Systeme Uni Bielefeld WS 2005 | 06 Wozu eigentlich Grammatiken? Fallbeispiel: „Hans und Peter arbeiten an einer Adressbuch- Datenbank, sie haben die ähnliche Vorstellung von der Struktur, aber nicht exakt dieselbe“ Einleitung DTD XML Schema RelaxNG XForms Fazit Quellen 4 | 45 XML – GRAMMATIKEN UND XFORMS ASTRID SACKEL XML und intelligente Systeme Uni Bielefeld WS 2005 | 06 Wozu eigentlich Grammatiken? Fallbeispiel: „Hans und Peter arbeiten an einer Adressbuch- Datenbank, sie haben die ähnliche Vorstellung von der Struktur, aber nicht exakt dieselbe“ „Peter muss seine Dateien bearbeiten, Hans muss die Eingaben seiner Freunde korrigieren / validieren“ Einleitung DTD XML Schema RelaxNG XForms Fazit Quellen 5 | 45 XML – GRAMMATIKEN UND XFORMS ASTRID SACKEL XML und intelligente Systeme Uni Bielefeld WS 2005 | 06 DTD <!ELEMENT addressbook (description,contact*)> Document Type Definition <!ELEMENT description ANY> <!ELEMENT contact (firstname,lastname,fon*,address,comment ?)> <?xml version=“1.0“ encoding=“UTF-8“?> <!DOCTYPE addressbook SYSTEM „addressbook.
    [Show full text]
  • Libreoffice 7.1 Calc Guide | 3 Chart Wizard
    Copyright This document is Copyright © 2021 by the LibreOffice Documentation Team. Contributors are 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/4.0/), version 4.0 or later. All trademarks within this guide belong to their legitimate owners. Contributors To this edition Steve Fanning Felipe Viggiano Kees Kriek Jean Hollis Weber Vasudev Narayanan To previous editions John A Smith Jean Hollis Weber Martin J Fox Andrew Pitonyak Simon Brydon Gabriel Godoy Barbara Duprey Gabriel Godoy Peter Schofield John A Smith Christian Chenal Laurent Balland-Poirier Philippe Clément Pierre-Yves Samyn Shelagh Manton Peter Kupfer Andy Brown Stephen Buck Iain Roberts Hazel Russman Barbara M. Tobias Jared Kobos Martin Saffron Dave Barton Olivier Hallot Cathy Crumbley Kees Kriek Claire Wood Steve Fanning Zachary Parliman Gordon Bates Leo Moons Randolph Gamo Drew Jensen Samantha Hamilton Annie Nguyen Felipe Viggiano Stefan Weigel Feedback Please direct any comments or suggestions about this document to the Documentation Team’s mailing list: [email protected]. Note Everything you send to a mailing list, including your email address and any other personal information that is written in the message, is publicly archived and cannot be deleted. Publication date and software version Published May 2021. Based on LibreOffice 7.1 Community. Other
    [Show full text]