DOCSLIB.ORG

Xml-Based Rdf Query Language (Xrql) and Its Implementation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

XML-BASED RDF QUERY LANGUAGE (XRQL) AND ITS IMPLEMENTATION Norihiro Ishikawa, Takeshi Kato, Hiromitsu Sumino NTT DoCoMo Inc, 3-5 Hikarino-oka, Yokosuka, Kanagawa, Japan Johan Hjelm Ericsson Research, Torshamnsgatan 23, Kista SE-16480, Stockholm, Sweden Kazuhiro Miyatsu Ericsson Research Japan,1-4-14 Koraku, Bunkyo-ku Tokyo, Japan Keywords: Mobile phone, RDF, XML, Query Language, Metadata, Semantic Web Abstract: Resource Description Framework (RDF) is a language which represents information about resources. In order to search RDF resource descriptions, several RDF query languages such as RQL and SquishQL have been proposed. However, these RDF query languages do not use XML syntax and they have limited functionality. xRQL is proposed to solve these issues by defining an XML-based RDF query language with enhanced manipulations of the RDF metadata. xRQL is a logic language relying on a functional approach. It consists of an operator declaration, a RDF data description and a result description. Based on RDF graph data model, xRQL defines a graphical path expression with variables, which is similar to GOQL for describing RDF data. It also adopts the object-oriented model for creation, modification and deletion operations of RDF data. Users can define their favorite XML- compliant result descriptions by themselves, which is similar to XQuery. In addition, a set of RDF operations for RDF schema is defined to manipulate the class and property hierarchies in RDF schema. xRQL has been implemented as an RDF query language over a native RDF database management system. This paper also briefly describes the implementation status. 1 INTRODUCTION RDF and logic language, there are some problems to be solved: The World Wide Web was originally built for human z Non-XML Syntax consumption. It contains such a large volume of Since the existing RDF query languages use SQL- information that it’s impossible to manage manually. like syntax to describe an RDF query, a special The use of metadata to describe the information can parser other than an XML parser is required. achieve automatic processing. RDF (Resource SQL-like syntax has limitations in expressing a Description Framework) (Ora, 1999, Dan, 2002) is a complicated RDF query, compared with XML- W3C recommendation for describing information based syntax. It is also difficult to describe the objects and processing metadata. hierarchical RDF data model with a plain text For querying RDF resource description, several syntax language. RDF query languages (G.Karvounarakis, 2002, Mike, z Limitation of RDF Metadata 2002, L.Miller,2001, Flavius,2002, Joachim,2002, Manipulations Edutella, 2002) have been developed. However, in The existing RDF query languages only support the context of processing within an XML-based RDF metadata search operations. Other functions, distributed database system, and with respect to an such as Creation, Modification and Deletion of 319 Ishikawa N., Kato T., Sumino H., Hjelm J. and Miyatsu K. (2005). XML-BASED RDF QUERY LANGUAGE (XRQL) AND ITS IMPLEMENTATION. In Proceedings of the First International Conference on Web Information Systems and Technologies, pages 319-326 DOI: 10.5220/0001229203190326 Copyright c SciTePress WEBIST 2005 - WEB INTERFACES AND APPLICATIONS RDF metadata should be considered to support z RDF Schema Query: Besides the metadata manipulation operations, as well as the manipulation functions of the distributed similar functions are supported by SQL in a heterogeneous metadata represented in RDF, relational database system. the retrieval function of schema definitions z Lack of Result Format Declaration for the vocabularies used in any given block The existing RDF query languages retrieve the of RDF data is needed. Since schema search result in an unordered and ambiguous way. definitions are defined by using the RDF It takes more time for machine to understand and Schema (RDFS) Specification, which process the retrieval results. It will be effective provide information about relationships and powerful if an expected result format is between classes and properties which might declared in the RDF query language. be used in queries, RDF query language should be able to query RDF schemas which As a solution to the above problems, we have are implicit in any RDF data model. proposed an XML-based RDF query language, z Inference: Because of the hierarchical named xRQL, to manipulate RDF resource vocabularies defined in RDFS specification, description and RDF schemas. It relies on the RDF such as subClassof and subPropertyof, an graph data model that captures the RDF modeling RDF query language should support the primitives and permits the interpretation of operations of inferring “implicit” superimposed resource description. xRQL adopts the relationships between classes and properties. functionality of an XML query language (D. z RDF Metadata Manipulation: In addition Chamberlin, 2001), several object-oriented query to basic search functions, RDF query languages (ODMG,1998, Serge, 1989, Zeki, 1996, language should support the operations of Flavius, 2002) and a graph query language creation, modification and deletion of RDF (Jeonghee, 1999, R.Fikes, 2001). So it’s expected to metadata. These operations, not yet be a standard query language for manipulation of supported by the current query languages, RDF resource description stored in the distributed will be attractive to the clients who want to RDF repositories. construct their own RDF metadata Section 2 summarizes the requirements that an repositories based on given RDF schemas. RDF query language should satisfy. In Section 3, we z Definition of Search Result Format: In depict xRQL design concepts and xRQL syntax in order to achieve the efficient processing of details, and give some typical examples. In Section search results, the capability of defining 4, a native RDF management system that supports search result format should be available in xRQL is briefly introduced. Finally, we summarize RDF query language. That will help the our contributions and show our considerations in the clients to retrieve the search results in their future research in Section 5. favorite formats. 2 REQUIREMENTS OF AN RDF 3 XML-BASED RDF QUERY QUERY LANGUAGE LANGUAGE: xRQL We summarize the general requirements of an RDF xRQL is a logic language relying on a functional query language as follows. approach. It consists of an operator declaration, a z Machine Readability: RDF query language RDF data description and a result description. Based syntax should be human readable and on RDF graph data model, xRQL defines a graphical machine understandable for processing RDF path expression with variables, in the same way as metadata easily and efficiently between the Graphical Object-Oriented Query Language (GOQL) distributed heterogeneous metadata (L.Sheng, 1999) for describing RDF data. It also repositories. adopts the object-oriented model (D.Chamberlin, z Support for RDF Data Model: RDF query 2001) for creation, modification and deletion language should support the RDF data operations of RDF data. Users can define their model (e.g. resources, properties, values), favorite XML-compliant result formats by which is similar to the object-oriented data themselves, in the same way as XQuery (ODMG, model. This means RDF query language 1998). In addition, a set of RDF schema operations should support concepts in the object- is defined to manipulate the class and property oriented data model, such as class hierarchies. hierarchies and inheritance. 320 XML-BASED RDF QUERY LANGUAGE (XRQL) AND ITS IMPLEMENTATION 3.1 Design Concept RDF Data Model We describe the design concepts of xRQL by using RDF Schema the following example of RDF resource for the web content. Figure 1 depicts the contents published on a certain web site. The lower part depicts the RDF Resource descriptions of two persons (r1 and r4) and two content of music and movie on the web (r2 and r5). Figure 2: The layered data model The middle part depicts a schema for contents Then the relations between these three levels are annotation. In this schema, property create is defined ensured by a standard type interpretation. In Figure with domain “person” and range “content”. The 1, the r1 in RDF Resource level has a directed type upper part shows the well-known RDF data model. label pointing to composer in RDF Schema level Properties (e.g. create, managed) serve to represent whose type is rdfs:class of RDF Data Model level. attributes (or characteristics) of resources as well as xRQL is designed based on this 3 layered data relationships between resources. Furthermore, both model. classes and properties include hierarchical semantics. For example, class music (or movie) is a subclass of 3.1.2 RDF Resource Manipulation content while property compose (or produce) is a subproperty of create. According to the data model in section 3.1.1, we rdfs:domain defined four basic operations to manipulate RDF rdfs:class r d rdfs:property resource under the constraint of RDF Schema level. rdfs:range RDF Data Model These operations include search, deletion, creation and modification. string address create managed name person content company The xRQL queries essentially provide the means of string tel compose manipulating RDF resource with the knowledge of string composer music produce technique the given RDF schema. For search operations, we producer movie string RDF Schema proposed a path expression based on RDF graph data washington address compose managed model. In compliance with RDF graph (i.e.
Recommended publications
  • SPARQL with Xquery-Based Filtering?

    SPARQL with Xquery-Based Filtering?

    SPARQL with XQuery-based Filtering? Takahiro Komamizu Nagoya University, Japan [email protected] Abstract. Linked Open Data (LOD) has been proliferated over vari- ous domains, however, there are still lots of open data in various format other than RDF, a standard data description framework in LOD. These open data can also be connected to entities in LOD when they are as- sociated with URIs. Document-centric XML data are such open data that are connected with entities in LOD as supplemental documents for these entities, and to convert these XML data into RDF requires various techniques such as information extraction, ontology design and ontology mapping with human prior knowledge. To utilize document-centric XML data linked from entities in LOD, in this paper, a SPARQL-based seam- less access method on RDF and XML data is proposed. In particular, an extension to SPARQL, XQueryFILTER, which enables XQuery as a filter in SPARQL is proposed. For efficient query processing of the combination of SPARQL and XQuery, a database theory-based query optimization is proposed. Real-world scenario-based experiments in this paper showcase that effectiveness of XQueryFILTER and efficiency of the optimization. 1 Introduction Open data movement is a worldwide movement that data are published online with FAIR principle1. Linked Open Data (LOD) [4] started by Sir Tim Berners- Lee is best aligned with this principle. In LOD, factual records are represented by a set of triples consisting of subject, predicate and object in the form of a stan- dardized representation framework, RDF (Resource Description Framework) [5]. Each element in RDF is represented by network-accessible identifier called URI (Uniform Resource Identifier).
  • 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
  • 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.
  • Rdfs:Frbr– Towards an Implementation Model for Library Catalogs Using Semantic Web Technology

    Rdfs:Frbr– Towards an Implementation Model for Library Catalogs Using Semantic Web Technology

    rdfs:frbr– Towards an Implementation Model for Library Catalogs Using Semantic Web Technology Stefan Gradmann SUMMARY. The paper sets out from a few basic observations (biblio- graphic information is still mostly part of the ‘hidden Web,’ library au- tomation methods still have a low WWW-transparency, and take-up of FRBR has been rather slow) and continues taking a closer look at Se- mantic Web technology components. This results in a proposal for im- plementing FRBR as RDF-Schema and of RDF-based library catalogues built on such an approach. The contribution concludes with a discussion of selected strategic benefits resulting from such an approach. [Article copies available for a fee from The Haworth Document Delivery Service: 1-800-HAWORTH. E-mail address: <[email protected]> Web- site: <http://www.HaworthPress.com> © 2005 by The Haworth Press, Inc. All rights reserved.] Stefan Gradmann, PhD, is Head, Hamburg University “Virtual Campus Library” Unit, which is part of the computing center and has a mission of providing information management services to the university as a whole, including e-publication services and open access to electronic scientific information resources. Address correspondence to: Stefan Gradmann, Virtuelle Campusbibliothek Regionales Rechenzentrum der Universität Hamburg, Schlüterstrasse 70, D-20146 Hamburg, Germany (E-mail: [email protected]). [Haworth co-indexing entry note]: “rdfs:frbr–Towards an Implementation Model for Library Cata- logs Using Semantic Web Technology.” Gradmann, Stefan. Co-published simultaneously in Cataloging & Classification Quarterly (The Haworth Information Press, an imprint of The Haworth Press, Inc.) Vol. 39, No. 3/4, 2005, pp. 63-75; and: Functional Requirements for Bibliographic Records (FRBR): Hype or Cure-All? (ed: Patrick Le Boeuf) The Haworth Information Press, an imprint of The Haworth Press, Inc., 2005, pp.
  • RDF Query Languages Need Support for Graph Properties

    RDF Query Languages Need Support for Graph Properties

    RDF Query Languages Need Support for Graph Properties Renzo Angles1, Claudio Gutierrez1, and Jonathan Hayes1,2 1 Dept. of Computer Science, Universidad de Chile 2 Dept. of Computer Science, Technische Universit¨at Darmstadt, Germany {rangles,cgutierr,jhayes}@dcc.uchile.cl Abstract. This short paper discusses the need to include into RDF query languages the ability to directly query graph properties from RDF data. We study the support that current RDF query languages give to these features, to conclude that they are currently not supported. We propose a set of basic graph properties that should be added to RDF query languages and provide evidence for this view. 1 Introduction One of the main features of the Resource Description Framework (RDF) is its ability to interconnect information resources, resulting in a graph-like structure for which connectivity is a central notion [GLMB98]. As we will argue, basic concepts of graph theory such as degree, path, and diameter play an important role for applications that involve RDF querying. Considering the fact that the data model influences the set of operations that should be provided by a query language [HBEV04], it follows the need for graph operations support in RDF query languages. For example, the query “all relatives of degree 1 of Alice”, submitted to a genealogy database, amounts to retrieving the nodes adjacent to a resource. The query “are suspects A and B related?”, submitted to a police database, asks for any path connecting these resources in the (RDF) graph that is stored in this database. The query “what is the Erd˝osnumber of Alberto Mendelzon”, submitted to (a RDF version of) DBLP, asks simply for the length of the shortest path between the nodes representing Erd˝osand Mendelzon.
  • Web and Semantic Web Query Languages: a Survey

    Web and Semantic Web Query Languages: a Survey

    Web and Semantic Web Query Languages: A Survey James Bailey1, Fran¸coisBry2, Tim Furche2, and Sebastian Schaffert2 1 NICTA Victoria Laboratory Department of Computer Science and Software Engineering The University of Melbourne, Victoria 3010, Australia http://www.cs.mu.oz.au/~jbailey/ 2 Institute for Informatics,University of Munich, Oettingenstraße 67, 80538 M¨unchen, Germany http://pms.ifi.lmu.de/ Abstract. A number of techniques have been developed to facilitate powerful data retrieval on the Web and Semantic Web. Three categories of Web query languages can be distinguished, according to the format of the data they can retrieve: XML, RDF and Topic Maps. This ar- ticle introduces the spectrum of languages falling into these categories and summarises their salient aspects. The languages are introduced us- ing common sample data and query types. Key aspects of the query languages considered are stressed in a conclusion. 1 Introduction The Semantic Web Vision A major endeavour in current Web research is the so-called Semantic Web, a term coined by W3C founder Tim Berners-Lee in a Scientific American article describing the future of the Web [37]. The Semantic Web aims at enriching Web data (that is usually represented in (X)HTML or other XML formats) by meta-data and (meta-)data processing specifying the “meaning” of such data and allowing Web based systems to take advantage of “intelligent” reasoning capabilities. To quote Berners-Lee et al. [37]: “The Semantic Web will bring structure to the meaningful content of Web pages, creating an environment where software agents roaming from page to page can readily carry out sophisticated tasks for users.” The Semantic Web meta-data added to today’s Web can be seen as advanced semantic indices, making the Web into something rather like an encyclopedia.
  • XML-Based RDF Data Management for Efficient Query Processing

    XML-Based RDF Data Management for Efficient Query Processing

    XML-Based RDF Data Management for Efficient Query Processing Mo Zhou Yuqing Wu Indiana University, USA Indiana University, USA [email protected] [email protected] Abstract SPARQL[17] is a W3C recommended RDF query language. A The Semantic Web, which represents a web of knowledge, offers SPARQL query contains a collection of triples with variables called new opportunities to search for knowledge and information. To simple access patterns which form graph patterns for describing harvest such search power requires robust and scalable data repos- query requirements. For SELECT ?t example, the SPARQL itories that can store RDF data and support efficient evaluation of WHERE {?p type Person. ?r ?x ?t. SPARQL queries. Most of the existing RDF storage techniques rely ?p name ?n. ?p write ?r} query on the left re- on relation model and relational database technologies for these trieves all properties of tasks. They either keep the RDF data as triples, or decompose it reviews written by a person whose name is known. into multiple relations. The mis-match between the graph model The needs to develop applications on the Semantic Web and sup- of the RDF data and the rigid 2D tables of relational model jeop- port search in RDF graphs call for RDF repositories to be reliable, ardizes the scalability of such repositories and frequently renders a robust and efficient in answering SPARQL queries. As in the con- repository inefficient for some types of data and queries. We pro- text of RDB and XML, the selection of storage models is critical to pose to decompose RDF graph into a forest of semantically cor- a data repository as it is the dominating factor to determine how to related XML trees, store them in an XML repository and rewrite evaluate queries and how the system behaves when it scales up.
  • Answering SPARQL Queries Modulo RDF Schema with Paths Faisal Alkhateeb, Jérôme Euzenat

    Answering SPARQL Queries Modulo RDF Schema with Paths Faisal Alkhateeb, Jérôme Euzenat

    Answering SPARQL queries modulo RDF Schema with paths Faisal Alkhateeb, Jérôme Euzenat To cite this version: Faisal Alkhateeb, Jérôme Euzenat. Answering SPARQL queries modulo RDF Schema with paths. [Research Report] RR-8394, INRIA. 2013, pp.46. hal-00904961 HAL Id: hal-00904961 https://hal.inria.fr/hal-00904961 Submitted on 15 Nov 2013 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Answering SPARQL queries modulo RDF Schema with paths Faisal Alkhateeb, Jérôme Euzenat RESEARCH REPORT N° 8394 November 2013 Project-Teams Exmo ISSN 0249-6399 ISRN INRIA/RR--8394--FR+ENG Answering SPARQL queries modulo RDF Schema with paths Faisal Alkhateeb∗, Jérôme Euzenat† Project-Teams Exmo Research Report n° 8394 — November 2013 — 46 pages Abstract: SPARQL is the standard query language for RDF graphs. In its strict instantiation, it only offers querying according to the RDF semantics and would thus ignore the semantics of data expressed with respect to (RDF) schemas or (OWL) ontologies. Several extensions to SPARQL have been proposed to query RDF data modulo RDFS, i.e., interpreting the query with RDFS semantics and/or considering external ontologies. We introduce a general framework which allows for expressing query answering modulo a particular semantics in an homogeneous way.
  • Powl – a Web Based Platform for Collaborative Semantic Web Development

    Powl – a Web Based Platform for Collaborative Semantic Web Development

    Powl – A Web Based Platform for Collaborative Semantic Web Development Sören Auer University of Leipzig [email protected] Abstract: We outline Powl, an opensource, web-based semantic web develop- ment platform for PHP. It may be used as a foundational framework for seman- tic web applications. Powl allows parsing, storing, querying, manipulating, ver- sioning, serving and serializing RDF-S and OWL knowledge bases in a collaborative web enabled environment. Detailed project information, a demon- stration and complete source code of Powl is available at http://powl.sf.net. 1 Introduction In this demonstration paper we give an overview on Powl, a web based ontology management tool. Its capabilities include parsing, storing, querying, manipulating, versioning, serving and serializing RDF and OWL knowledge bases for different target audiences. For the semantic web researcher it may provide a test bed for rapid implementations of new approaches. For the web application developer it offers an object-oriented application programming interface for semantic web software devel- opment. For knowledge engineers there is a sophisticated web interface for collabora- tive development of ontologies in a web enabled environment. Powl is implemented in the web scripting language PHP1. An implementation in a script language has serveral advantages. In addition to being platform independent, Powl is thus simple to modify and extend by researchers and semantic web develop- ers. The source code is compact and easy to grasp. This results in a short development time - Powl was developed in approximately 9 man-months so far. An advantage of PHP in particular is that it is by far the most widely used pro- gramming language for web applications.
  • Building Xquery Based Web Service Aggregation and Reporting Applications

    Building Xquery Based Web Service Aggregation and Reporting Applications

    TECHNICAL PAPER BUILDING XQUERY BASED WEB SERVICE AGGREGATION AND REPORTING APPLICATIONS TABLE OF CONTENTS Introduction ........................................................................................................................................ 1 Scenario ............................................................................................................................................ 1 Writing the solution in XQuery ........................................................................................................... 3 Achieving the result ........................................................................................................................... 6 Reporting to HTML using XSLT ......................................................................................................... 6 Sample Stock Report ......................................................................................................................... 8 Summary ........................................................................................................................................... 9 XQuery Resources ............................................................................................................................ 9 www.progress.com 1 INTRODUCTION The widespread adoption of XML has profoundly altered the way that information is exchanged within and between enterprises. XML, an extensible, text-based markup language, describes data in a way that is both hardware- and software-independent. As such,
  • Xquery Tutorial

    Xquery Tutorial

    XQuery Tutorial Agenda • Motivation&History • Basics • Literals • XPath • FLWOR • Constructors • Advanced • Type system • Functions • Modules 2 Motivation • XML Query language to query data stores • XSLT for translation, not for querying • Integration language • Connect data from different sources • Access relational data represented as XML • Use in messaging systems • Need expressive language for integration 3 Design Goals • Declarative & functional language • No side effects • No required order of execution etc. • Easier to optimize • Strongly typed language, can handle weak typing • Optional static typing • Easier language • Non-XML syntax • Not a cumbersome SQL extension 4 History • Started 1998 as “Quilt” • Influenced by database- and document-oriented community • First W3C working draft in Feb 2001 • Still not a recommendation in March 2006 • Lots of implementations already available • Criticism: much too late • Current work • Full text search • Updates within XQuery 5 A composed language • XQuery tries to fit into the XML world • Based on other specifications • XPath language • XML Schema data model • various RFCs (2396, 3986 (URI), 3987 (IRI)) • Unicode • XML Names, Base, ID • Think: XPath 1.0 + XML literals + loop constructs 6 Basics • Literals • Arithmetic • XPath • FLWOR • Constructors 7 Basics - Literals • Strings • "Hello ' World" • "Hello "" World" • 'Hello " World' • "Hello $foo World" – doesn't work! • Numbers • xs:integer - 42 • xs:decimal – 3.5 • xs:double - .35E1 • xs:integer* - 1 to 5 – (1, 2, 3, 4, 5) 8 Literals (ctd.)
  • Xpath and Xquery

    Xpath and Xquery

    XPath and XQuery Patryk Czarnik Institute of Informatics University of Warsaw XML and Modern Techniques of Content Management – 2012/13 . 1. Introduction Status XPath Data Model 2. XPath language Basic constructs XPath 2.0 extras Paths 3. XQuery XQuery query structure Constructors Functions . 1. Introduction Status XPath Data Model 2. XPath language Basic constructs XPath 2.0 extras Paths 3. XQuery XQuery query structure Constructors Functions . XPath XQuery . Used within other standards: Standalone standard. XSLT Main applications: XML Schema XML data access and XPointer processing XML databases . DOM . Introduction Status XPath and XQuery Querying XML documents . Common properties . Expression languages designed to query XML documents Convenient access to document nodes Intuitive syntax analogous to filesystem paths Comparison and arithmetic operators, functions, etc. Patryk Czarnik 06 – XPath XML 2012/13 4 / 42 Introduction Status XPath and XQuery Querying XML documents . Common properties . Expression languages designed to query XML documents Convenient access to document nodes Intuitive syntax analogous to filesystem paths Comparison and arithmetic operators, functions, etc. XPath XQuery . Used within other standards: Standalone standard. XSLT Main applications: XML Schema XML data access and XPointer processing XML databases . DOM . Patryk Czarnik 06 – XPath XML 2012/13 4 / 42 . XPath 2.0 . Several W3C Recommendations, I 2007: XML Path Language (XPath) 2.0 XQuery 1.0 and XPath 2.0 Data Model XQuery 1.0 and XPath 2.0 Functions and Operators XQuery 1.0 and XPath 2.0 Formal Semantics Used within XSLT 2.0 Related to XQuery 1.0 . Introduction Status XPath — status . XPath 1.0 . W3C Recommendation, XI 1999 used within XSLT 1.0, XML Schema, XPointer .