DOCSLIB.ORG

The State of the Art: Ontology Web- Based Languages: XML Based

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The State of the Art: Ontology Web- Based Languages: XML Based Journal of Computing, Volume 2, Issue 6, June 2010, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG 166 The State of the Art: Ontology Web- Based Languages: XML Based Mohammad Mustafa Taye Department of Software Engineering Faculty of Information Technology Philadelphia University, Amman, Jordan Abstract — Many formal languages have been proposed to express or represent Ontologies, including RDF, RDFS, DAML+OIL and OWL. Most of these languages are based on XML syntax, but with various terminologies and expressiveness. Therefore, choosing a language for building an Ontology is the main step. The main point of choosing language to represent Ontology is based mainly on what the Ontology will represent or be used for. That language should have a range of quality support features such as ease of use, expressive power, compatibility, sharing and versioning, internationalisation. This is because different kinds of knowledge-based applications need different language features. The main objective of these languages is to add semantics to the existing information on the web. The aims of this paper is to provide a good knowledge of existing language and understanding of these languages and how could be used. Index Terms — Ontology, Ontology language, RDF, RDFS, DAML+OIL , OWL 1 INTRODUCTION Ontologies become a critical part in many languages provide richer constructors for areas, especially in Web Semantics. forming complex class expressions and axioms. Consequently, a number of representational In fact, recently most Ontology developers formats have been proposed to support and have used Ontology Editors, which are express them completely. environments or tools used directly for editing, Current languages used to express developing or modifying Ontologies. These tools Ontologies fall generally into three categories [1]: are used for providing support for the vocabularies of Ontology defined using natural Ontological development process, as well as for language, frame-based languages used to build conceptualising the Ontology; they transform the the structure of Ontologies based on explicit conceptualisation into executable code using statements of class and slot, and those languages translators. So the output Ontology of these tools based on logic, such as Description Logics. will be in one of the Web Ontology languages The main object of semantic web languages supported by editors Such as Protégé [18], OWL- is to add semantics to the existing information on P [21] and OilEd [22]. Alternatively Ontology the Web. RDF/RDFS [7], OIL [14], DAML+OIL reasoners are used to check the conflicts with a [9], and OWL [2] are modelling web languages high degree of automation. Many such systems, that have already been developed to represent or including RACER [19] and FaCT [20], have been express Ontologies. In general, most of these developed recently. languages are based on XML [16] syntax, but Returning to the main concern of this section, they have different terminologies and modelling web languages, there are in general expressions. Indeed, some of these languages two different types of language: Presentation have the ability to represent some logical relation languages such as HTML, designed to represent but others do not. Because some languages have text and images to users or requesters without greater expressive power than others, languages reference to the content, and Data Languages, chosen for representing Ontologies are based intended to be processed by machines. The mainly on what the Ontology represents or what present research relates to the latter. it will be used for. In other words, different kinds Before OWL, much research has been of Ontological knowledge-based applications conducted into creating a powerful Ontology need different language facilitators for enabling modelling language. This research stream began reasoning on Ontology data. These description with the XML-based RDF and RDF/S, Journal of Computing, Volume 2, Issue 6, June 2010, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG 167 progressed to the Ontology Inference Layer metadata about the resources on the web, is (OIL), and continued with the creation of capable of representing data on and exchanging DAML+OIL, the result of joining the American knowledge over the Web. It was developed to be proposal DAML-ONT5 with the European understood by computers, facilitating language OIL. All these languages are XML or interoperability between applications. In other RDF syntax based, and are consequently words, it is a framework for using and compatible with web standards. Indeed, RDF representing metadata and describing the and OWL make searching for and reusing semantics of information about web resources in information both more reliable and easier, a way accessible to machines. because they are considered as standards that RDF is recommended by the World Wide Web enable the Web to be a global infrastructure for Consortium (W3C). Uniform Resource Identifiers sharing documents and data equally. (URIs) are the method used by RDF to identify As mentioned in [2], some important resources or thing. In fact, it is based built upon requirements for quality support should be taken XML, but while that is designed for syntax, RDF into account when developing languages for is intended for semantics. encoding Ontologies. These include giving the As has been mentioned, RDF is a framework user explicit written format, ease of use, for describing web resources, which is why it has expressive power, compatibility, sharing and become a common method of describing the versioning, internationalisation, formal properties, time, information and content of web conceptualisations of domains models, well resources, so that it can be read and understood defined syntax and semantics, efficient reasoning by computer applications. support, sufficient expressive power, and RDF can be used in several applications, one convenience of expression. of the most important being resource discovery, Syntax is one of the most important features used to enhance search engine capabilities. It is in any language, so it should be well-defined, it also used to facilitate knowledge sharing and is also the most significant condition required for exchange in intelligent software agents so-called the processing of information by machine. Ontology, and, previously mentioned, to The semantics of knowledge should be well describe the content and content relationships defined because it represents the meaning of that available with any resource such as a page. knowledge. Formal semantics should be The RDF model has three elements: a resource established in the domain of mathematical logic (the subject), the object and the predicate. We can in, clearly defined way that will lead to say that <subject> has a property <predicate> unambiguous meaning. Well-defined semantics valued by <object>. will lead to correct reasoning. Semantics can be For example, a triplet could be "H.ZEDAN is considered as pre- requisites that help to support the Head of the STRL Group". In an RDF graph, reasoning. On the other hand, reasoning will all triplets "nodes and arcs" should be labelled help to check and discover consistent Ontology, with qualified URIs. In this example, it could be to verify unintended relationships between said that the Subject (Resource) is the STRL classes, and to classify individuals into classes. Group, the predicate (property) is Head of, and This paper has detailed the most common and the Object (literally) is H.ZEDAN. important languages such as RDF, RDF/S, DAML+OIL, OWL, all of which are based on 2.1 RESOURCE DESCRIPTION FRAMEWORK CHEMA XML. (RDF) S Extensible Markup Language (XML) [16] is The Resource Description Framework / widely known in the WWW community because Schema (RDFS) [6, 7] has been built upon the it is a flexible text format and was designed to XML and RDF models and upon syntax. RDFS describe data and to meet the challenges of large- provides additional facilities to support scale e-business and electronic publishing, and it evolution in both of the individual RDF plays an important role in exchanging different vocabularies, and the core RDF Schema type of data on the Web. In fact, it is the basis for vocabulary. a rapidly growing number of software The RDF Schema provides a machine- development activities. understandable system for defining the The present research, for the sake of vocabularies needed for such applications or simplicity, deals with RDF and RDFS as one descriptive vocabularies. In other words, the description language. RDF Schema is a collection of RDF resources that can be used to define or describe properties of 2 RESOURCE DESCRIPTION FRAMEWORK other RDF resources which define application- (RDF) specific RDF vocabularies. At the same time, Resource Description Framework (RDF) [3, 4, RDF(S) helps developers to describe classes and and 5] a language used to provide a standard for properties in a specific way and to specify Journal of Computing, Volume 2, Issue 6, June 2010, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG 168 relationships between those properties and resource, a property, and property value forms, classes, and it allows combinations between as in the statement: "The University of classes, properties, or values. In other words, Http://www.dmu.ac.uk/RDF is De Montfort". RDFS is used to define RDF vocabularies. The subject of the statement above is http:// In general, RDFS is defined in a namespace www.dmu.ac.uk /RDF. informally called 'rdfs', and identified by the URI The predicate is university. reference http://www.w3.org/2000/01/rdf- The object is De Montfort. schema#. On the other hand, RDF is defined in a Statement: "The location of namespace informally called ‘rdf’, and identified http://www.dmu.ac.uk/RDF is UK-Leicester". by the URI reference The subject of the statement above is: http://www.w3.org/1999/02/22-rdf-syntax- http://www.dmu.ac.uk/RDF. ns#. The predicate is: location. The object is: UK-Leicester.
Load more

Recommended publications
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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> ..
    [Show full text]
  • EAN.UCC XML Architectural Guide Version 1.0 July 2001
    EAN·UCC System The Global Language of Business ® EAN.UCC XML Architectural Guide Version 1.0 July 2001 COPYRIGHT 2001, EAN INTERNATIONAL™ AND UNIFORM CODE COUNCIL, INC.Ô EAN.UCC Architectural Guide EAN·UCC System The Global Language of Business ® Table of Contents Document History........................................................................................................................ 4 1. Introduction............................................................................................................................ 5 1.1 Overview......................................................................................................................................................................... 5 1.1.1 Extensions in UML............................................................................................................................................... 5 1.1.1.1 Common Core Components ....................................................................................................................... 6 1.2 In A Nutshell: A Business Process Document......................................................................................................... 6 1.3 Other Related Documents ............................................................................................................................................ 7 2. Implementation Guidelines ..................................................................................................... 8 2.1 Schema Language ........................................................................................................................................................
    [Show full text]
  • 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
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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
    [Show full text]
  • Information Technology - Object Management Group XML Metadata Interchange (XMI)
    ISO/IEC 19509:2014(E) Date: April 2014 Information technology - Object Management Group XML Metadata Interchange (XMI) formal/2014-04-06 This version has been formally published by ISO as the 2014 edition standard: ISO/IEC 19509. ISO/IEC 19509:2014(E) Table of Contents 1 Scope ................................................................................................. 1 2 Conformance ...................................................................................... 1 2.1 General ....................................................................................................1 2.2 Required Compliance ...............................................................................1 2.2.1 XMI Schema Compliance ................................................................................. 1 2.2.2 XMI Document Compliance .............................................................................. 1 2.2.3 Software Compliance ....................................................................................... 2 2.3 Optional Compliance Points .....................................................................2 2.3.1 XMI Extension and Differences Compliance .................................................... 2 3 Normative References ........................................................................ 2 4 Terms and Definitions ......................................................................... 3 5 Symbols .............................................................................................. 3 6 Additional
    [Show full text]
  • OWL 2 Web Ontology Language XML Serialization W3C Proposed Recommendation 22 September 2009
    OWL 2 Web Ontology Language XML Serialization W3C Proposed Recommendation 22 September 2009 OWL 2 Web Ontology Language XML Serialization W3C Proposed Recommendation 22 September 2009 This version: http://www.w3.org/TR/2009/PR-owl2-xml-serialization-20090922/ Latest version: http://www.w3.org/TR/owl2-xml-serialization/ Previous version: http://www.w3.org/TR/2009/CR-owl2-xml-serialization-20090611/ (color-coded diff) Editors: Boris Motik, Oxford University Computing Laboratory Bijan Parsia, University of Manchester Peter F. Patel-Schneider, Bell Labs Research, Alcatel-Lucent Contributors: (in alphabetical order) Sean Bechhofer, University of Manchester Bernardo Cuenca Grau, Oxford University Computing Laboratory Achille Fokoue, IBM Corporation Rinke Hoekstra, University of Amsterdam This document is also available in these non-normative formats: PDF version. Copyright © 2009 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. Page 1 of 35 http://www.w3.org/TR/2009/PR-owl2-xml-serialization-20090922/ OWL 2 Web Ontology Language XML Serialization W3C Proposed Recommendation 22 September 2009 This document specifies an XML serialization for OWL 2 that mirrors its structural specification.
    [Show full text]
  • Xml Xpath, Xslt
    More XML XPATH, XSLT CS 431 – February 27, 2006 Carl Lagoze – Cornell University XPath • Language for addressing parts of an XML document –XSLT –Xpointer • Tree model similar to DOM • W3C Recommendation (1999) – http://www.w3.org/TR/xpath Remember to think in terms of DOM trees DOCUMENT type=Element <?xml version="1.0" name="book" encoding="UTF-8"?> <book> <title lang='"en"'>"XML Basics"</title> type=Element name="title" </book> type=Text type=Attribute data="XML name="lang" Basics" data="en" Xpath Concepts •Context Node – current node in XML document that is basis of path evaluation – Default to root (remember that root is “Document”) • Location Steps – selection from context node – Axis – sub-tree(s) selection from context node – Node Test – select specific elements or node type(s) – Predicates – predicate for filtering after axis and node tests Context, Axis, Node Test, Predicate Document Root Location Path Specification • /step/step/…. – absolute from document root • step/step …. – relative from context • //step/step – anywhere in document tree • where step is: axis::node-test[predicate] axis::node-test[predicate] • child:: all children of context • descendant:: all children, grandchildren, … • parent:: parent of context • ancestor:: all nodes on path to root from context axis::node-test[predicate] • Element name: e.g. “Book” – make sure to pay attention to namespaces!!!! •Wildcard: * • Type(): where type is “node”, “text”, etc. – Remember in DOM that everything is a node axis::node-test[predicate] • Boolean and comparative operators
    [Show full text]
  • Best Practices Managing XML Data
    ® IBM® DB2® for Linux®, UNIX®, and Windows® Best Practices Managing XML Data Matthias Nicola IBM Silicon Valley Lab Susanne Englert IBM Silicon Valley Lab Last updated: January 2011 Managing XML Data Page 2 Executive summary ............................................................................................. 4 Why XML .............................................................................................................. 5 Pros and cons of XML and relational data ................................................. 5 XML solutions to relational data model problems.................................... 6 Benefits of DB2 pureXML over alternative storage options .................... 8 Best practices for DB2 pureXML: Overview .................................................. 10 Sample scenario: derivative trades in FpML format............................... 11 Sample data and tables................................................................................ 11 Choosing the right storage options for XML data......................................... 16 Selecting table space type and page size for XML data.......................... 16 Different table spaces and page size for XML and relational data ....... 16 Inlining and compression of XML data .................................................... 17 Guidelines for adding XML data to a DB2 database .................................... 20 Inserting XML documents with high performance ................................ 20 Splitting large XML documents into smaller pieces ..............................
    [Show full text]