DOCSLIB.ORG

XML to RDF Transformation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Diploma Thesis August 3, 2006 XML to RDF Transformation Markus Fehlmann of Aadorf TG, Switzerland (00-912-857) supervised by Prof. Dr. Harald Gall Dr. Gerald Reif Department of Informatics software evolution & architecture lab Diploma Thesis XML to RDF Transformation Markus Fehlmann Department of Informatics software evolution & architecture lab Diploma Thesis Author: Markus Fehlmann, [email protected] Project period: February 3, 2006 - August 3, 2006 Software Evolution & Architecture Lab Department of Informatics, University of Zurich Acknowledgements I am grateful to Gerald Reif whose PhD thesis was an excellent foundation for this work. Many of the now implemented features and ideas originated from fruitful discussions during the last six months. Gerald proved that the sentence used to advertise the thesis ”be best supervised by your advisers” was more than just empty words. I also express my gratitude to professor Harald Gall for giving me the opportunity to write my diploma thesis in the field of the Semantic Web, that I believe will strongly influence the way people access and process information, the main resource of today’s information society. I thank my parents for making my education possible and for all their encouragement through the years. Needless to say I could not have done this without them. My thanks also go to my fellow students and friends who provided me with useful inputs and critical suggestions. Abstract XML continues to be the primary format for data exchange in distributed systems. However, since several serializations of domain specific knowledge are possible, XML documents have no imma- nent semantic. The Semantic Web provides a common framework that allows data to be shared and reused across application, enterprise, and community boundaries. The Resource Description Framework (RDF), which is part of the Semantic Web, formalizes the meaning of information. While many documents are encoded in XML, only few documents are represented in RDF. In his PhD thesis, Reif proposed an algorithm and did a prototype implementation, called WEESA, that generates RDF graphs out of arbitrary XML documents by applying processing instructions defined in a mapping. In this thesis we propose an object-oriented architecture of the mapping algorithm in order to improve its maintainability, efficiency, and extensibility. In addition to that, we introduce new mapping directives that simplify the mapping definition process. The result of this thesis is a new implementation of the mapping algorithm that incorpo- rates the suggested object-oriented architecture and the additional mapping constructs. Thus, the transformation from XML data to RDF could be simplified to a reasonable extent. A prominent example that benefits from our results is the semantic annotation of Web sites. Zusammenfassung XML ist das tragende Format um Daten in verteilten Systemen auszutauschen. Allerdings haben XML Dokumente keine immanente Semantik, da in XML unterschiedliche Serialisierungen des- selben domänenspezifischen Wissens möglich sind. Das semantische Web bietet ein Rahmen- werk, das es erlaubt, Daten über Anwendungs- und Unternehmensgrenzen hinaus zu teilen und wiederzuverwenden. Das Resource Description Framework (RDF), ein Bestandteil des seman- tischen Webs, formalisiert hierzu die Bedeutung von Informationen. Während viele Dokumente in XML vorliegen, existieren erst wenige, die eine RDF Repräsentation haben. Reif schlug in seiner Dissertation einen Algorithmus vor, der RDF Repräsentationen aus beliebigen XML Doku- menten erstellt, indem Verarbeitungsanweisungen aus einem Mappingdokument auf das XML Dokument angewendet werden. Ebenso hat er den Algorithmus prototypisch implementiert. In dieser Arbeit stellen wir eine objektorientierte Architektur des Mapping Algorithmus vor, um dessen Wartbarkeit, Effizienz und Erweiterbarkeit zu verbessern. Zusätzlich erweitern wir das Mappingvokabular um Anweisungen, welche die Erstellung von Mappings vereinfachen. Das Ergebnis dieser Arbeit ist eine neue Implementierung des genannten Algorithmus, der die objektorientierte Architektur und die neuen Mappinganweisungen vereinigt. Auf diese Weise konnte die Transformation von XML Dokumenten in das RDF Format erheblich vereinfacht wer- den. Ein bedeutendes Anwendungsgebiet, das von unseren Ergebnissen profitieren kann, ist die semantische Annotation von Webseiten. Contents 1 Introduction 1 1.1 Semantic Web Overview . 1 1.1.1 Origins and Vision . 1 1.1.2 Architecture . 3 1.2 XML based Web Engineering . 12 1.2.1 Apache Cocoon . 12 1.3 Problem Statement . 13 1.4 Structure of the Thesis, Objectives of this Work . 15 2 Semantic Annotation of XML-based Web Applications 17 2.1 Tools for Manual Annotation . 17 2.2 Embedding and Retrieving Metadata . 18 2.2.1 GRDDL . 18 2.2.2 RDFa . 19 2.3 XML to Metadata Translation . 21 2.3.1 Bridging the Gap between RDF and XML . 21 2.3.2 Mapping XML to OWL Ontologies . 21 2.3.3 Lifting XML Schema to OWL . 22 2.3.4 Round-tripping between XML and RDF . 23 2.3.5 XR . 24 2.4 Conversion of arbitrary document types to RDF . 25 2.4.1 Data Conversion, Extraction and Record Linkage using XML and RDF Tools in Project SIMILE . 25 3 Introduction to WEESA 27 3.1 WEESA - Web Engineering for Semantic Web Applications . 27 3.2 Semantic Web Applications with WEESA and Apache Cocoon . 28 3.2.1 Integration of WEESA in the Apache Cocoon Framework . 29 3.2.2 WEESA Cocoon Transformer to generate HTML+RDF . 30 3.2.3 WEESA Cocoon Transformer to generate RDF/XML . 30 3.3 Building the Knowledge Base of the Semantic Web Application . 31 3.3.1 Architecture and Maintenance of the WEESA Knowledge Base . 31 4 Design of the Object-Oriented Architecture 33 4.1 General Object-Oriented Design Principles . 33 4.2 Application of Design Principles to Mapping Algorithm . 34 4.3 Description of the WEESA Mapping Algorithm . 39 4.3.1 Resource Dependencies . 41 viii CONTENTS 4.3.2 Circular References in Resource Definitions . 42 4.3.3 Mapping Procedure . 43 4.3.4 Sample Mapping Procedure . 44 5 WEESA Mapping Features 47 5.1 Target Ontology and Source XML File . 47 5.2 WEESA Mapping Structure . 49 5.2.1 Method Parameter Attributes . 50 5.3 Relative Paths . 51 5.4 Variables . 52 5.5 If Statement . 53 5.6 Switch Statement . 55 5.7 Dictionary . 57 5.8 Datatype Attribute for Typed Literals . 58 5.9 Language Section, Language Attributes . 59 5.9.1 Language Tag Syntax . 59 5.9.2 Definition of a Default Language . 60 5.9.3 Language Definition in Triples Section . 60 5.9.4 Language Precedence and Typed Literals . 61 6 Conclusions and Future Work 63 6.1 Conclusions . 63 6.2 Summary of Contributions . 64 6.3 Future Research . 64 A XML Schemas 67 A.1 Mapping Definition . 67 A.2 WEESA Dictionary Schema . 77 A.3 Sample Shop Schema . 77 B XML Files 81 B.1 Sample Shop . 81 B.2 Sample Dictionary . 82 B.3 Shop Mapping . 82 B.4 Shop Ontology . 85 C Java Code of Methods used in Mapping Examples 87 C.1 weesa.util.MappingLib.addPrefix . 87 C.2 weesa.util.MappingLib.avg . 87 D Content of the CD 89 CONTENTS ix List of Figures 1.1 Semantic Web Architecture [AvH04] . 3 1.2 A simple RDF Graph . 5 1.3 A Blank Node that represents a Shop Item . 6 1.4 A Cocoon Pipeline using several XML Technologies [Rei05] . 13 2.1 Recursive Application of the GRDDL Mechanism [Haz05] . 19 2.2 Operating Sequence of an XML to OWL Transformation as suggested in [BA05] . 22 2.3 Operating Sequence of an XML to OWL Transformation as suggested in [FZT04] . 23 3.1 WEESA Design and Instance Levels [Rei05] . 28 3.2 a) Cocoon Pipeline to integrate RDF into HTML, b) Pipeline to create a separate RDF/XML File [Rei05] . 31 4.1 Interface Hierarchy of Jena’s RDF Nodes . 34 4.2 Interface Hierarchy of Mapping Elements that generate RDF Nodes and Arcs . 35 4.3 Triple Class that makes use of Interfaces described in Figure 4.2 . 36 4.4 Const Class Hierarchy that is used similarly for the Const, Method, and XPath Classes . 36 4.5 ExpressionFactory Class used for Resource, Literal, and Property Creation . 37 4.6 Integration of new Mapping Directives in Class Hierarchy . 38 4.7 Extract of the Operator Class Hierarchy . 39 4.8 Circular Dependencies that are not directly supported by the recursive Mapping Algorithm . 43 4.9 Simple RDF Graph for the Description of the Mapping Algorithm . 45 5.1 The Sample Shop Ontology . 48 5.2 Triple expressing that TrekKing belongs to the Outdoor Sector . 49 5.3 Triple created using Variables for ID/IDREF Relationship . 52 6.1 Target RDF Graph that needs careful Consideration with Respect to Variable and XPath Dependencies . 65 6.2 RDF Graph for Resources with several incoming Edges . 65 List of Tables 6.1 Table describing Variable and Relative Path Dependencies of Figure 6.2 . 66 List of Listings 1.1 Three different XML Representations of the same Fact . 4 1.2 RDF/XML Serialization Example . 7 1.3 TriX Serialization Example . 9 1.4 TriG Serialization.
Recommended publications
  • V a Lida T in G R D F Da

    V a Lida T in G R D F Da

    Series ISSN: 2160-4711 LABRA GAYO • ET AL GAYO LABRA Series Editors: Ying Ding, Indiana University Paul Groth, Elsevier Labs Validating RDF Data Jose Emilio Labra Gayo, University of Oviedo Eric Prud’hommeaux, W3C/MIT and Micelio Iovka Boneva, University of Lille Dimitris Kontokostas, University of Leipzig VALIDATING RDF DATA This book describes two technologies for RDF validation: Shape Expressions (ShEx) and Shapes Constraint Language (SHACL), the rationales for their designs, a comparison of the two, and some example applications. RDF and Linked Data have broad applicability across many fields, from aircraft manufacturing to zoology. Requirements for detecting bad data differ across communities, fields, and tasks, but nearly all involve some form of data validation. This book introduces data validation and describes its practical use in day-to-day data exchange. The Semantic Web offers a bold, new take on how to organize, distribute, index, and share data. Using Web addresses (URIs) as identifiers for data elements enables the construction of distributed databases on a global scale. Like the Web, the Semantic Web is heralded as an information revolution, and also like the Web, it is encumbered by data quality issues. The quality of Semantic Web data is compromised by the lack of resources for data curation, for maintenance, and for developing globally applicable data models. At the enterprise scale, these problems have conventional solutions. Master data management provides an enterprise-wide vocabulary, while constraint languages capture and enforce data structures. Filling a need long recognized by Semantic Web users, shapes languages provide models and vocabularies for expressing such structural constraints.
  • Semantics Developer's Guide

    Semantics Developer's Guide

    MarkLogic Server Semantic Graph Developer’s Guide 2 MarkLogic 10 May, 2019 Last Revised: 10.0-8, October, 2021 Copyright © 2021 MarkLogic Corporation. All rights reserved. MarkLogic Server MarkLogic 10—May, 2019 Semantic Graph Developer’s Guide—Page 2 MarkLogic Server Table of Contents Table of Contents Semantic Graph Developer’s Guide 1.0 Introduction to Semantic Graphs in MarkLogic ..........................................11 1.1 Terminology ..........................................................................................................12 1.2 Linked Open Data .................................................................................................13 1.3 RDF Implementation in MarkLogic .....................................................................14 1.3.1 Using RDF in MarkLogic .........................................................................15 1.3.1.1 Storing RDF Triples in MarkLogic ...........................................17 1.3.1.2 Querying Triples .......................................................................18 1.3.2 RDF Data Model .......................................................................................20 1.3.3 Blank Node Identifiers ..............................................................................21 1.3.4 RDF Datatypes ..........................................................................................21 1.3.5 IRIs and Prefixes .......................................................................................22 1.3.5.1 IRIs ............................................................................................22
  • Binary RDF for Scalable Publishing, Exchanging and Consumption in the Web of Data

    Binary RDF for Scalable Publishing, Exchanging and Consumption in the Web of Data

    WWW 2012 – PhD Symposium April 16–20, 2012, Lyon, France Binary RDF for Scalable Publishing, Exchanging and Consumption in the Web of Data Javier D. Fernández 1;2 Supervised by: Miguel A. Martínez Prieto 1 and Claudio Gutierrez 2 1 Department of Computer Science, University of Valladolid (Spain) 2 Department of Computer Science, University of Chile (Chile) [email protected] ABSTRACT era and hence they share a document-centric view, providing The Web of Data is increasingly producing large RDF data- human-focused syntaxes, disregarding large data. sets from diverse fields of knowledge, pushing the Web to In a typical scenario within the current state-of-the-art, a data-to-data cloud. However, traditional RDF represen- efficient interchange of RDF data is limited, at most, to com- tations were inspired by a document-centric view, which pressing the verbose plain data with universal compression results in verbose/redundant data, costly to exchange and algorithms. The resultant file has no logical structure and post-process. This article discusses an ongoing doctoral the- there is no agreed way to efficiently publish such data, i.e., sis addressing efficient formats for publication, exchange and to make them (publicly) available for diverse purposes and consumption of RDF on a large scale. First, a binary serial- users. In addition, the data are hardly usable at the time of ization format for RDF, called HDT, is proposed. Then, we consumption; the consumer has to decompress the file and, focus on compressed rich-functional structures which take then, to use an appropriate external tool (e.g.
  • Rdfa in XHTML: Syntax and Processing Rdfa in XHTML: Syntax and Processing

    Rdfa in XHTML: Syntax and Processing Rdfa in XHTML: Syntax and Processing

    RDFa in XHTML: Syntax and Processing RDFa in XHTML: Syntax and Processing RDFa in XHTML: Syntax and Processing A collection of attributes and processing rules for extending XHTML to support RDF W3C Recommendation 14 October 2008 This version: http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014 Latest version: http://www.w3.org/TR/rdfa-syntax Previous version: http://www.w3.org/TR/2008/PR-rdfa-syntax-20080904 Diff from previous version: rdfa-syntax-diff.html Editors: Ben Adida, Creative Commons [email protected] Mark Birbeck, webBackplane [email protected] Shane McCarron, Applied Testing and Technology, Inc. [email protected] Steven Pemberton, CWI Please refer to the errata for this document, which may include some normative corrections. This document is also available in these non-normative formats: PostScript version, PDF version, ZIP archive, and Gzip’d TAR archive. The English version of this specification is the only normative version. Non-normative translations may also be available. Copyright © 2007-2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract The current Web is primarily made up of an enormous number of documents that have been created using HTML. These documents contain significant amounts of structured data, which is largely unavailable to tools and applications. When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites, and allowing browsing applications to improve the user experience: an event on a web page can be directly imported - 1 - How to Read this Document RDFa in XHTML: Syntax and Processing into a user’s desktop calendar; a license on a document can be detected so that users can be informed of their rights automatically; a photo’s creator, camera setting information, resolution, location and topic can be published as easily as the original photo itself, enabling structured search and sharing.
  • 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.
  • RDF/XML: RDF Data on the Web

    RDF/XML: RDF Data on the Web

    Developing Ontologies • have an idea of the required concepts and relationships (ER, UML, ...), • generate a (draft) n3 or RDF/XML instance, • write a separate file for the metadata, • load it into Jena with activating a reasoner. • If the reasoner complains about an inconsistent ontology, check the metadata file alone. If this is consistent, and it complains only when also data is loaded: – it may be due to populating a class whose definition is inconsistent and that thus must be empty. – often it is due to wrong datatypes. Recall that datatype specification is not interpreted as a constraint (that is violated for a given value), but as additional knowledge. 220 Chapter 6 RDF/XML: RDF Data on the Web • An XML representation of RDF data for providing RDF data on the Web could be done straightforwardly as a “holds” relation mapped according to SQLX (see ⇒ next slide). • would be highly redundant and very different from an XML representation of the same data • search for a more similar way: leads to “striped XML/RDF” – data feels like XML: can be queried by XPath/Query and transformed by XSLT – can be parsed into an RDF graph. • usually: provide RDF/XML data to an agreed RDFS/OWL ontology. 221 A STRAIGHTFORWARD XML REPRESENTATION OF RDF DATA Note: this is not RDF/XML, but just some possible representation. • RDF data are triples, • their components are either URIs or literals (of XML Schema datatypes), • straightforward XML markup in SQLX style, • since N3 has a term structure, it is easy to find an XML markup. <my-n3:rdf-graph xmlns:my-n3="http://simple-silly-rdf-xml.de#"> <my-n3:triple> <my-n3:subject type="uri">foo://bar/persons/john</my-n3:subject> <my-n3:predicate type="uri">foo://bar/meta#name</my-n3:predicate> <my-n3:object type="http://www.w3.org/2001/XMLSchema#string">John</my-n3:object> </my-n3 triple> <my-n3:triple> ..
  • Exercise Sheet 1

    Exercise Sheet 1

    Semantic Web, SS 2017 1 Exercise Sheet 1 RDF, RDFS and Linked Data Submit your solutions until Friday, 12.5.2017, 23h00 by uploading them to ILIAS. Later submissions won't be considered. Every solution should contain the name(s), email adress(es) and registration number(s) of its (co-)editor(s). Read the slides for more submission guidelines. 1 Knowledge Representation (4pts) 1.1 Knowledge Representation Humans usually express their knowledge in natural language. Why aren't we using, e.g., English for knowledge representation and the semantic web? 1.2 Terminological vs Concrete Knowledge What is the role of terminological knowledge (e.g. Every company is an organization.), and what is the role of facts (e.g. Microsoft is an organization. Microsoft is headquartered in Redmond.) in a semantic web system? Hint: Imagine an RDF ontology that contains either only facts (describing factual knowledge: states of aairs) or constraints (describing terminological knowledge: relations between con- cepts). What could a semantic web system do with it? Semantic Web, SS 2017 2 2 RDF (10pts) RDF graphs consist of triples having a subject, a predicate and an object. Dierent syntactic notations can be used in order to serialize RDF graphs. By now you have seen the XML and the Turtle syntax of RDF. In this task we will use the Notation3 (N3) format described at http://www.w3.org/2000/10/swap/Primer. Look at the following N3 le: @prefix model: <http://example.com/model1/> . @prefix cdk: <http://example.com/chemistrydevelopmentkit/> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
  • XML for Java Developers G22.3033-002 Course Roadmap

    XML for Java Developers G22.3033-002 Course Roadmap

    XML for Java Developers G22.3033-002 Session 1 - Main Theme Markup Language Technologies (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Course Roadmap Consider the Spectrum of Applications Architectures Distributed vs. Decentralized Apps + Thick vs. Thin Clients J2EE for eCommerce vs. J2EE/Web Services, JXTA, etc. Learn Specific XML/Java “Patterns” Used for Data/Content Presentation, Data Exchange, and Application Configuration Cover XML/Java Technologies According to their Use in the Various Phases of the Application Development Lifecycle (i.e., Discovery, Design, Development, Deployment, Administration) e.g., Modeling, Configuration Management, Processing, Rendering, Querying, Secure Messaging, etc. Develop XML Applications as Assemblies of Reusable XML- Based Services (Applications of XML + Java Applications) 2 1 Agenda XML Generics Course Logistics, Structure and Objectives History of Meta-Markup Languages XML Applications: Markup Languages XML Information Modeling Applications XML-Based Architectures XML and Java XML Development Tools Summary Class Project Readings Assignment #1a 3 Part I Introduction 4 2 XML Generics XML means eXtensible Markup Language XML expresses the structure of information (i.e., document content) separately from its presentation XSL style sheets are used to convert documents to a presentation format that can be processed by a target presentation device (e.g., HTML in the case of legacy browsers) Need a
  • Odata-Csdl-Xml-V4.01-Os.Pdf

    Odata-Csdl-Xml-V4.01-Os.Pdf

    OData Common Schema Definition Language (CSDL) XML Representation Version 4.01 OASIS Standard 11 May 2020 This stage: https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/os/odata-csdl-xml-v4.01-os.docx (Authoritative) https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/os/odata-csdl-xml-v4.01-os.html https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/os/odata-csdl-xml-v4.01-os.pdf Previous stage: https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/cos01/odata-csdl-xml-v4.01-cos01.docx (Authoritative) https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/cos01/odata-csdl-xml-v4.01-cos01.html https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/cos01/odata-csdl-xml-v4.01-cos01.pdf Latest stage: https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.docx (Authoritative) https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.pdf Technical Committee: OASIS Open Data Protocol (OData) TC Chairs: Ralf Handl ([email protected]), SAP SE Michael Pizzo ([email protected]), Microsoft Editors: Michael Pizzo ([email protected]), Microsoft Ralf Handl ([email protected]), SAP SE Martin Zurmuehl ([email protected]), SAP SE Additional artifacts: This prose specification is one component of a Work Product that also includes: • XML schemas: OData EDMX XML Schema and OData EDM XML Schema.
  • 15 Years of Semantic Web: an Incomplete Survey

    15 Years of Semantic Web: an Incomplete Survey

    Ku¨nstl Intell (2016) 30:117–130 DOI 10.1007/s13218-016-0424-1 TECHNICAL CONTRIBUTION 15 Years of Semantic Web: An Incomplete Survey 1 2 Birte Glimm • Heiner Stuckenschmidt Received: 7 November 2015 / Accepted: 5 January 2016 / Published online: 23 January 2016 Ó Springer-Verlag Berlin Heidelberg 2016 Abstract It has been 15 years since the first publications today’s Web: Uniform Resource Identifiers (URIs) for proposed the use of ontologies as a basis for defining assigning unique identifiers to resources, the HyperText information semantics on the Web starting what today is Markup Language (HTML) for specifying the formatting known as the Semantic Web Research Community. This of Web pages, and the Hypertext Transfer Protocol (HTTP) work undoubtedly had a significant influence on AI as a that allows for the retrieval of linked resources from across field and in particular the knowledge representation and the Web. Typically, the markup of standard Web pages Reasoning Community that quickly identified new chal- describes only the formatting and, hence, Web pages and lenges and opportunities in using Description Logics in a the navigation between them using hyperlinks is targeted practical setting. In this survey article, we will try to give towards human users (cf. Fig. 1). an overview of the developments the field has gone through In 2001, Tim Berners-Lee, James Hendler, and Ora in these 15 years. We will look at three different aspects: Lassila describe their vision for a Semantic Web [5]: the evolution of Semantic Web Language Standards, the The Semantic Web is not a separate Web but an evolution of central topics in the Semantic Web Commu- extension of the current one, in which information is nity and the evolution of the research methodology.
  • XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département D©Informatique Et De Recherche Opérationnelle Université De Montréal

    XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département D©Informatique Et De Recherche Opérationnelle Université De Montréal

    XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département d©informatique et de recherche opérationnelle Université de Montréal C.P. 6128, Succ. Centre-Ville Montréal, Québec Canada H3C 3J7 [email protected] http://www.iro.umontreal.ca/~lapalme/ForestInsteadOfTheTrees/ Publication date April 14, 2019 XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/ XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département d©informatique et de recherche opérationnelle Université de Montréal C.P. 6128, Succ. Centre-Ville Montréal, Québec Canada H3C 3J7 [email protected] http://www.iro.umontreal.ca/~lapalme/ForestInsteadOfTheTrees/ Publication date April 14, 2019 Abstract This tutorial gives a high-level overview of the main principles underlying some XML technologies: DTD, XML Schema, RELAX NG, Schematron, XPath, XSL stylesheets, Formatting Objects, DOM, SAX and StAX models of processing. They are presented from the point of view of the computer scientist, without the hype too often associated with them. We do not give a detailed description but we focus on the relations between the main ideas of XML and other computer language technologies. A single compact pretty-print example is used throughout the text to illustrate the processing of an XML structure with XML technologies or with Java programs. We also show how to create an XML document by programming in Java, in Ruby, in Python, in PHP, in E4X (Ecmascript for XML) and in Swift. The source code of the example XML ®les and the programs are available either at the companion web site of this document or by clicking on the ®le name within brackets at the start of the caption of each example.
  • Integración De XML En Páginas Web Dinámicas DOM

    Integración De XML En Páginas Web Dinámicas DOM

    Integración de XML en páginas Web dinámicas DOM Jose Emilio Labra Gayo Departamento de Informática Universidad de Oviedo Motivación: Computación Dinámica Páginas Web estáticas vs. Dinámicas Computación Dinámica = Contenido se genera en el momento en que se hace la petición 2 Posibilidades: Cliente vs Servidor Internet Cliente Servidor GET http://servidor.com/hola.html http:/1.0 200 OK <html> <body> Enlace a <a href =“otro.html”>Otro</a> </body> </html> Computación Dinámica en Servidor Al solicitar ciertas páginas, el servidor genera el contenido Ejemplos: CGI's, Servlets, JSP, ASP, PHP, etc. El proceso es trasparente para el cliente El cliente recibe únicamente código HTML No tiene porqué haber problemas de usabilidad Desventajas La interactividad requiere comunicación entre cliente/servidor Mayor carga de la red y del servidor Desperdicio de las capacidades del cliente Computación dinámica en Cliente Se pueden incluir objetos computacionales que son interpretados por el cliente Varias posibilidades: Applets, Javascript, ... Se ejecutan en el entorno que ofrece el navegador DOM ofrece una API que permite acceder/manipular los elementos del documento También se puede acceder a otros elementos (eventos, barra de estado, etc.) Por seguridad no se permite escribir/leer ficheros JavaScript Un poco de historia Netscape 2 (Dic. 1995) incorporó Javascript (diseñado por Brendan Eich) Permite modificar contenido de páginas Web interactivamente JavaScript no tiene nada que ver con Java Se llamaba LiveScript (cambio de nombre por marketing) Microsoft