DOCSLIB.ORG

Xquery Update

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Xquery Update V. Christophides, I. Fundulaki, CS561 Spring 2010 XQuery Update 1 V. Christophides, I. Fundulaki, CS561 Spring 2010 Why XQuery Update XQuery is a read-only language it can return (compute) an instance of the XQuery Data Model, but it cannot modify an existing instance Applications require reading and updating XML data XQuery Update Facility a candidate recommendation, not yet a standard http://www.w3.org/TR/xquery-update-10/ (June 2009) 2 V. Christophides, I. Fundulaki, CS561 Spring 2010 Requirements for the XQuery Update language Expressive power: 1. Insert 2. Delete 3. Update 4. Copy with new identity Extension of XQuery itself: Simplifies understanding and learning the language Well-defined semantics (kind of) Amenable to efficient implementation 3 V. Christophides, I. Fundulaki, CS561 Spring 2010 XQuery Update Concepts XQuery expressions can be classified into: Updating expressions Non-updating expressions XQuery Update proposal introduces five new kind of expressions: insert, delete, replace, rename: updating expressions transform: non-updating expression 4 V. Christophides, I. Fundulaki, CS561 Spring 2010 XQuery Update Document XQuery Update specifies: how the XQuery syntax is extended to accommodate updates syntax, semantics and processing model for each new updating expression 5 V. Christophides, I. Fundulaki, CS561 Spring 2010 Extending XQuery with Updates 6 V. Christophides, I. Fundulaki, CS561 Spring 2010 Insert Expression Updating expression Syntax SourceExpr evaluates to 0 or more source nodes TargetExpr evaluates to a single target node SourceExpr and TargetExpr are non-updating expressions keyword node and nodes used interchangeably (independently of the actual number of nodes to be inserted) 7 V. Christophides, I. Fundulaki, CS561 Spring 2010 Insert Expression: Semantics (1) An insert expression inserts copies of 0 or more source nodes into a designated position w.r.t target node if before or after is specified, then the source nodes are inserted as preceding or following siblings of the target node if as first or as last is specified, then the source nodes are inserted as first or as last children elements resp. of the target node if into as specified, the source nodes are inserted as children of the target node (the position where the nodes are inserted depends on the implementation) If multiple nodes are inserted by a single insert expression, the nodes remain adjacent and their order preserves the node ordering of SourceExpr. 8 V. Christophides, I. Fundulaki, CS561 Spring 2010 Insert Expressions: Processing Model Execution Semantics: 1. evaluate TargetExpr to get the target nodes to which the update operation will be applied ⇒$target 1. evaluate SourceExpr to get the node(s) that will be inserted ⇒$clist 2. populate the pending update list op:insertInto($target, $clist) (into) op:insertBefore($target, $clist) (before) … 9 V. Christophides, I. Fundulaki, CS561 Spring 2010 Insert Expressions: Examples insert node <movie title=“Before Night Falls”/> as first into $doc/movies <movies> <movies> <movie title="The Big Lebowski"> <director>E. Cohen</director> <movie title=“Before Night Falls”/> <director>J. Cohen</director> </movie> <movie title="The Big Lebowski"> <movie title="All President's Men"> <director>E. Cohen</director> <director>A. J. Pakula</director> <director>J. Cohen</director> </movie> </movie> </movies> <movie title="All President's Men"> <director>A. J. Pakula</director> </movie> </movies> 10 V. Christophides, I. Fundulaki, CS561 Spring 2010 Insert Expressions: Examples insert node <movie title=“Before Night Falls”/> before $doc//movie[director=“A.J. Pakula”] <movies> <movie title="The Big Lebowski"> <movies> <director>E. Cohen</director> <movie title="The Big Lebowski"> <director>J. Cohen</director> <director>E. Cohen</director> </movie> <director>J. Cohen</director> <movie title="All President's Men"> </movie> <director>A. J. Pakula</director> </movie> <movie title=“Before Night Falls”/> <movie title=“The Parallax View”> <producer>A. J. Pakula</producer> <movie title="All President's Men"> </movie> <director>A. J. Pakula</director> </movies> </movie> <movie title=“The Parallax View”> <producer>A. J. Pakula</producer> </movie> </movies> $doc/descendant::*[value(self())=“A.J. Pakula”] 11 V. Christophides, I. Fundulaki, CS561 Spring 2010 Insert Expressions: Examples insert nodes $doc1//movie[director=“E.Cohen”] into $doc//movies[movie[director=“A.J. Pakula”]] doc <movies> <movie title="All President's Men"> <movies> <director>A. J. Pakula</director> <movie title="All President's Men"> </movie> <director>A. J. Pakula</director> <movie title=“A night on Earth”> </movie> <director>J. Jarmush</director> </movie> <movie title="The Big Lebowski"> </movies> <director>E. Cohen</director> <director>J. Cohen</director> </movie> doc1 <movie title=“A night on Earth”> <director>J. Jarmush</director> <comedies> <movie title="The Big Lebowski"> </movie> <director>E. Cohen</director> </movies> <director>J. Cohen</director> </movie> <comedies> 12 V. Christophides, I. Fundulaki, CS561 Spring 2010 Delete Updating expression Syntax TargetExpr evaluates to a a sequence of 0 or more nodes TargetExpr is a non-updating expression Semantics: deletes the nodes obtained from evaluating TargetExpr 13 V. Christophides, I. Fundulaki, CS561 Spring 2010 Delete Expression: Processing Model 1. evaluate TargetExpr to get the target nodes to which the update operation will be applied ⇒$tlist 2. for each $tnode in $tlist, populate the pending update list op:delete($tnode) 14 V. Christophides, I. Fundulaki, CS561 Spring 2010 Delete Expression: Examples delete node $doc//movie[director=“E.Cohen”] <movies> <movies> <movie title="The Big Lebowski"> <director>E. Cohen</director> <movie title="The Big Lebowski"> <director>J. Cohen</director> <director>E. Cohen</director> </movie> <director>J. Cohen</director> <movie title="All President's Men"> </movie> <director>A. J. Pakula</director> </movie> <movie title="All President's Men"> </movies> <director>A. J. Pakula</director> </movie> </movies> <movies> <movie title="All President's Men"> <director>A. J. Pakula</director> </movie> </movies> 15 V. Christophides, I. Fundulaki, CS561 Spring 2010 Replace Expressions Updating expression Syntax TargetExpr evaluates to a single target node TargetExpr is a non-updating expression 16 V. Christophides, I. Fundulaki, CS561 Spring 2010 Replace Expression: Semantics If value of is not specified: 1. replaces the node obtained from TargetExpr with a sequence of zero or more nodes returned from ExprSingle 2. The replacement nodes occupy the position in the document tree that was formerly occupied by the node that is replaced if value of is specified, a replace expression modifies the value of the node while preserving its node identity 17 V. Christophides, I. Fundulaki, CS561 Spring 2010 Replace Expression: Examples replace node $doc(“m”)//movie[1] with $doc(“s”)//documentary[2] <movies> <documentaries> <movie title="The Big Lebowski"> <documentary <director>E. Cohen</director> title=“The Corporation”/> <director>J. Cohen</director> <documentary </movie> title=“Enron, the smartest guys <movie title="All President's Men"> in the room”/> <director>A. J. Pakula</director> </documentaries> </movie> </movies> <movies> <documentary title=“Enron, the smartest guys in the room”/> <movie title="All President's Men"> <director>A. J. Pakula</director> </movie> </movies> 18 V. Christophides, I. Fundulaki, CS561 Spring 2010 Replace Expression: Examples replace value of node $doc(“m”)//movie[1]/director[2] with $doc(“m”)//movie[2]/director[1] <movies> <movies> <movie title="The Big Lebowski"> <movie title="The Big Lebowski"> <director>E. Cohen</director> <director>E. Cohen</director> <director>J. Cohen</director> </movie> <director>Alan J. Pakula</director> <movie title="All President's Men"> <director>A. J. Pakula</director> </movie> </movie> <movie title="All President's Men"> </movies> <director>A. J. Pakula</director> </movie> </movies> The identity of the node director is not modified! 19 V. Christophides, I. Fundulaki, CS561 Spring 2010 Replace Expression: Processing Model 1. evaluate TargetExpr to get the node to be replaced ⇒ $target 2. evaluate ExprSingle to get the nodes to replace $target with ⇒ $rlist 3. populate the pending update list with op:replaceNode($target, $rlist) 20 V. Christophides, I. Fundulaki, CS561 Spring 2010 Rename Expression Updating expression Syntax TargetExpr evaluates to a single target node (target node) NewNameExpr evaluates to an atomic value (string) TargetExpr, NewNameExpr are non-updating expressions Semantics: change the name of the target node with NewNameExpr 21 V. Christophides, I. Fundulaki, CS561 Spring 2010 Rename Expression: Examples rename $doc(“m”)//movie[2]/director[1] with main-director <movies> <movies> <movie title="The Big Lebowski"> <movie title="The Big Lebowski"> <director>E. Cohen</director> <director>E. Cohen</director> <director>J. Cohen</director> <director>J. Cohen</director> </movie> </movie> <movie title="All President's Men"> <movie title="All President's Men"> <director>A. J. Pakula</director> </movie> <main-director>A. J. Pakula </movies> </main-director> </movie> </movies> 22 V. Christophides, I. Fundulaki, CS561 Spring 2010 Transform Expressions Non-updating expression Syntax A transform expression can be used to create modified copies of existing nodes in a XML document tree and see the results in the same query It does not modify the original tree
Load more

Recommended publications
  • 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]
  • Refactoring XSLT
    XSLT and XQuery September 19, 2019 Refactoring XSLT Priscilla Walmsley, Datypic, Inc. Class Outline Introduction ......................................................................................................................................2 Cleaning Up......................................................................................................................................9 Improving Code Quality..................................................................................................................14 Other Improvements.......................................................................................................................21 Introduction 2 Obligatory Wikipedia Quote 3 Code refactoring is the process of restructuring existing computer code - changing the factoring - without changing its external behavior. Refactoring improves nonfunctional attributes of the software. Advantages include improved code readability and reduced complexity; these can improve source code maintainability and create a more expressive internal architecture or object model to improve extensibility. Typically, refactoring applies a series of standardised basic micro-refactorings, each of which is (usually) a tiny change in a computer program's source code that either preserves the behaviour of the software, or at least does not modify its conformance to functional requirements. Many development environments provide automated support for performing the mechanical aspects of these basic refactorings. If done extremely well, code
    [Show full text]
  • Supporting SPARQL Update Queries in RDF-XML Integration *
    Supporting SPARQL Update Queries in RDF-XML Integration * Nikos Bikakis1 † Chrisa Tsinaraki2 Ioannis Stavrakantonakis3 4 Stavros Christodoulakis 1 NTU Athens & R.C. ATHENA, Greece 2 EU Joint Research Center, Italy 3 STI, University of Innsbruck, Austria 4 Technical University of Crete, Greece Abstract. The Web of Data encourages organizations and companies to publish their data according to the Linked Data practices and offer SPARQL endpoints. On the other hand, the dominant standard for information exchange is XML. The SPARQL2XQuery Framework focuses on the automatic translation of SPARQL queries in XQuery expressions in order to access XML data across the Web. In this paper, we outline our ongoing work on supporting update queries in the RDF–XML integration scenario. Keywords: SPARQL2XQuery, SPARQL to XQuery, XML Schema to OWL, SPARQL update, XQuery Update, SPARQL 1.1. 1 Introduction The SPARQL2XQuery Framework, that we have previously developed [6], aims to bridge the heterogeneity issues that arise in the consumption of XML-based sources within Semantic Web. In our working scenario, mappings between RDF/S–OWL and XML sources are automatically derived or manually specified. Using these mappings, the SPARQL queries are translated on the fly into XQuery expressions, which access the XML data. Therefore, the current version of SPARQL2XQuery provides read-only access to XML data. In this paper, we outline our ongoing work on extending the SPARQL2XQuery Framework towards supporting SPARQL update queries. Both SPARQL and XQuery have recently standardized their update operation seman- tics in the SPARQL 1.1 and XQuery Update Facility, respectively. We have studied the correspondences between the update operations of these query languages, and we de- scribe the extension of our mapping model and the SPARQL-to-XQuery translation algorithm towards supporting SPARQL update queries.
    [Show full text]
  • XML Transformations, Views and Updates Based on Xquery Fragments
    Faculteit Wetenschappen Informatica XML Transformations, Views and Updates based on XQuery Fragments Proefschrift voorgelegd tot het behalen van de graad van doctor in de wetenschappen aan de Universiteit Antwerpen, te verdedigen door Roel VERCAMMEN Promotor: Prof. Dr. Jan Paredaens Antwerpen, 2008 Co-promotor: Dr. Ir. Jan Hidders XML Transformations, Views and Updates based on XQuery Fragments Roel Vercammen Universiteit Antwerpen, 2008 http://www.universiteitantwerpen.be Permission to make digital or hard copies of portions of this work for personal or classroom use is granted, provided that the copies are not made or distributed for profit or commercial advantage and that copies bear this notice. Copyrights for components of this work owned by others than the author must be honored. Abstracting with credit is permitted. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission of the author. Research funded by a Ph.D. grant of the Institute for the Promotion of Innovation through Science and Technology in Flan- ders (IWT-Vlaanderen). { Onderzoek gefinancierd met een specialisatiebeurs van het Instituut voor de Aanmoediging van Innovatie door Wetenschap en Technologie in Vlaanderen (IWT-Vlaanderen). Grant number / Beurs nummer: 33581. http://www.iwt.be Typesetting by LATEX Acknowledgements This thesis is the result of the contributions of many friends and colleagues to whom I would like to say \thank you". First and foremost, I want to thank my advisor Jan Paredaens, who gave me the opportunity to become a researcher and teached me how good research should be performed. I had the honor to write several papers in collaboration with him and will always remember the discussions and his interesting views on research, politics and gastronomy.
    [Show full text]
  • Access Control Models for XML
    Access Control Models for XML Abdessamad Imine Lorraine University & INRIA-LORIA Grand-Est Nancy, France [email protected] Outline • Overview on XML • Why XML Security? • Querying Views-based XML Data • Updating Views-based XML Data 2 Outline • Overview on XML • Why XML Security? • Querying Views-based XML Data • Updating Views-based XML Data 3 What is XML? • eXtensible Markup Language [W3C 1998] <files> "<record>! ""<name>Robert</name>! ""<diagnosis>Pneumonia</diagnosis>! "</record>! "<record>! ""<name>Franck</name>! ""<diagnosis>Ulcer</diagnosis>! "</record>! </files>" 4 What is XML? • eXtensible Markup Language [W3C 1998] <files>! <record>! /files" <name>Robert</name>! <diagnosis>! /record" /record" Pneumonia! </diagnosis> ! </record>! /name" /diagnosis" <record …>! …! </record>! Robert" Pneumonia" </files>! 5 XML for Documents • SGML • HTML - hypertext markup language • TEI - Text markup, language technology • DocBook - documents -> html, pdf, ... • SMIL - Multimedia • SVG - Vector graphics • MathML - Mathematical formulas 6 XML for Semi-Structered Data • MusicXML • NewsML • iTunes • DBLP http://dblp.uni-trier.de • CIA World Factbook • IMDB http://www.imdb.com/ • XBEL - bookmark files (in your browser) • KML - geographical annotation (Google Maps) • XACML - XML Access Control Markup Language 7 XML as Description Language • Java servlet config (web.xml) • Apache Tomcat, Google App Engine, ... • Web Services - WSDL, SOAP, XML-RPC • XUL - XML User Interface Language (Mozilla/Firefox) • BPEL - Business process execution language
    [Show full text]
  • 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.
    [Show full text]
  • Towards Quality Analysis for Document Oriented Bases Paola Gómez, Claudia Roncancio, Rubby Casallas
    Towards quality analysis for document oriented bases Paola Gómez, Claudia Roncancio, Rubby Casallas To cite this version: Paola Gómez, Claudia Roncancio, Rubby Casallas. Towards quality analysis for document oriented bases. International Conference on Conceptual Modeling (ER), Oct 2018, Xi’an, China. hal-01908112 HAL Id: hal-01908112 https://hal.archives-ouvertes.fr/hal-01908112 Submitted on 29 Oct 2018 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. Towards quality analysis for document oriented bases Paola Gomez´ 1, Claudia Roncancio1, and Rubby Casallas2 1 Univ. Grenoble Alpes, CNRS, Grenoble INP* paola.gomez-barreto,[email protected] 2 TICSw, Universidad de los Andes,Bogota´ - Colombia, [email protected] Abstract. Document-oriented bases allow high flexibility in data representation which facilitates a rapid development of applications and enables many possi- bilities for data structuring. Nevertheless, the structural choices remain crucial because of their impact on several aspects of the document base and application quality, e.g, memory print, data redundancy, readability and maintainability. Our research is motivated by quality issues of document-oriented bases. We aim at facilitating the study of the possibilities of data structuring and providing objective metrics to better reveal the advantages and disadvantages of each solution with respect to user needs.
    [Show full text]
  • Declarative Access to Filesystem Data New Application Domains for XML Database Management Systems
    Declarative Access to Filesystem Data New application domains for XML database management systems Alexander Holupirek Dissertation zur Erlangung des akademischen Grades Doktor der Naturwissenschaften (Dr. rer. nat.) Fachbereich Informatik und Informationswissenschaft Mathematisch-Naturwissenschaftliche Sektion Universität Konstanz Referenten: Prof. Dr. Marc H. Scholl Prof. Dr. Marcel Waldvogel Tag der mündlichen Prüfung: 17. Juli 2012 Abstract XML and state-of-the-art XML database management systems (XML-DBMSs) can play a leading role in far more application domains as it is currently the case. Even in their basic configuration, they entail all components necessary to act as central systems for complex search and retrieval tasks. They provide language-specific index- ing of full-text documents and can store structured, semi-structured and binary data. Besides, they offer a great variety of standardized languages (XQuery, XSLT, XQuery Full Text, etc.) to develop applications inside a pure XML technology stack. Benefits are obvious: Data, logic, and presentation tiers can operate on a single data model, and no conversions have to be applied when switching in between. This thesis deals with the design and development of XML/XQuery driven informa- tion architectures that process formerly heterogeneous data sources in a standardized and uniform manner. Filesystems and their vast amounts of different file types are a prime example for such a heterogeneous dataspace. A new XML dialect, the Filesystem Markup Language (FSML), is introduced to construct a database view of the filesystem and its contents. FSML provides a uniform view on the filesystem’s contents and allows developers to leverage the complete XML technology stack on filesystem data.
    [Show full text]
  • XSL-FO by Dave Pawson Publisher
    XSL-FO By Dave Pawson Publisher : O'Reilly Pub Date : August 2002 ISBN : 0-596-00355-2 Pages : 282 Table of • Contents • Index • Reviews Reader • Reviews Extensible Style Language-Formatting Objects, or XSL-FO, is a set of tools developers and web designers use to describe page printouts of their XML (including XHTML) documents. XSL-FO teaches you how to think about the formatting of your documents and guides you through the questions you'll need to ask to ensure that your printed documents meet the same high standards as your computer-generated content. 777 Copyright Preface Who Should Read This Book? What Does This Book Cover? Motivation Organization of This Book What Else Do You Need? Conventions Used in This Book How to Contact Us Acknowledgments Chapter 1. Planning for XSL-FO Section 1.1. XML and Document Processing Section 1.2. Choosing Your Print Production Approach Section 1.3. Choosing Tools Section 1.4. The Future for XSL-FO Chapter 2. A First Look at XSL-FO Section 2.1. An XSL-FO Overview Section 2.2. Related Stylesheet Specifications Section 2.3. Using XSL-FO as Part of XSL Section 2.4. Shorthand, Short Form, and Inheritance Chapter 3. Pagination Section 3.1. Document Classes Section 3.2. The Main Parts of an XSL-FO Document Section 3.3. Simple Page Master Section 3.4. Complex Pagination Section 3.5. Page Sequences Chapter 4. Areas Section 4.1. Informal Definition of an Area Section 4.2. Area Types Section 4.3. Components of an Area Section 4.4.
    [Show full text]
  • How Can the DDI Community Take Advantage of the Native XML Database Exist-Db EDDI 2011, Gothenburg
    How can the DDI community take advantage of the native XML database eXist-db EDDI 2011, Gothenburg Olof Olsson, SND Leif-Jöran Olsson, Språkbanken Johan Fihn, SND New features in eXist since IASSIST ● 1.4.1 ○ Better Referential Integrity, revised Database Shutdown and Crash Protection, new WebDAV implementation based on the Milton WebDAV library. The Lucene Full-Text Indexing has been made more robust and performant. It now also includes configurable analyzers and parameters, better match highlighting and additional functions for working with Lucene document fields. The betterFORM server-side XForms 1.1 engine is integrated and enabled by default. New features in eXist since IASSIST ● 1.5 ○ Lucene indexing of binary files, e.g. pdf ○ eXide editing, app development, package management (xar archives) and repository installation (hot deploy) of these packages ○ svn extension, working copy in db etc ○ new authentication and access restriction model, allowing openid, oauth, ldap etc ○ Some XQuery 3 functions e.g. switch, try/catch, hof Will be reelased as new stable release 1.6 in beginning of 2012. OAI-PMH ● Provider ○ configuration per datatype available e.g. ddi, cmdi, meta-share etc ● Harvester Next steps ● Package as apps DDI Stylesheets News in the DDI 3.1 stylesheet ○ Translatable labels (re-use from icpsr stylesheet) ○ Support for more elements To do: ● Better navigation (javascript) ● More parameters for different types of views ● Separation of the stylesheet More info and download: https://code.google.com/p/ddixslt Call for stylesheets
    [Show full text]
  • Standardised Xquery 3.0 Annotations for REST
    RESTful XQuery Standardised XQuery 3.0 Annotations for REST Adam Retter Adam Retter Consulting <[email protected]> January, 2012 Abstract Whilst XQuery was originally envisaged and designed as a query language for XML, it has been adopted by many as a language for application development This, in turn, has encouraged additional and diverse extensions, many of which could not easily have been foreseen. This paper examines how XQuery has been used for Web Application development, current implementation approaches for executing XQuery in a Web context, and subsequently presents a proposal for a standard approach to RESTful XQuery through the use of XQuery 3.0 Annotations. Keywords: XQuery 3.0, Annotations, REST, HTTP, Standard 1. Introduction 1.1 Background XML Query Language (XQuery) was originally born from several competing query languages for XML[1]. All of these languages had in common the noble yet limited goal of querying XML. They focused on XML as a read-only store for data. In addition, whilst several of these predecessors recognised the Web as a critical factor, like their successor XQuery, none of them attempted to implement constructs in the language that supported use as a (Web) server-side processing language. With the adoption and use of XQuery, because of its functional nature and module system which permit the organisation of code units, people attempted to write complex processing applications in XQuery. As the limits of what was achievable in XQuery were tested, real world scenarios emerged which called for additional XQuery facilities, resulting in extension standards: XPath and XQuery Update[2] and XQuery Full-Text[3].
    [Show full text]
  • Xpath, Xquery and XSLT
    XPath, XQuery and XSLT Timo Lilja February 25, 2010 Timo Lilja () XPath, XQuery and XSLT February 25, 2010 1 / 24 Introduction When processing, XML documents are organized into a tree structure in the memory All XML Query and transformation languages operate on this tree XML Documents consists of tags and attributes which form logical constructs called nodes The basic operation unit of these query/processing languages is the node though access to substructures is provided Timo Lilja () XPath, XQuery and XSLT February 25, 2010 2 / 24 XPath XPath XPath 2.0 [4] is a W3C Recomendation released on January 2007 XPath provides a way to query the nodes and their attributes, tags and values XPath type both dynamic and static typing if the XML Scheme denition is present, it is used for static type checking before executing a query otherwise nodes are marked for untyped and they are coerced dynamically during run-time to suitable types Timo Lilja () XPath, XQuery and XSLT February 25, 2010 3 / 24 XPath Timo Lilja () XPath, XQuery and XSLT February 25, 2010 4 / 24 XPath Path expressions Path expressions provide a way to choose all matching branches of the tree representation of the XML Document Path expressions consist of one or more steps separated by the path operater/. A step can be an axis which is a way to reference a node in the path. a node-test which corresponds to a node in the actual XML document zero or more predicates Syntax for the path expressions: /step/step Syntaxc for a step: axisname::nodestest[predicate] Timo Lilja () XPath, XQuery and XSLT February 25, 2010 5 / 24 XPath Let's assume that we use the following XML Docuemnt <bookstore> <book category="COOKING"> <title lang="it">Everyday Italian</title> <author>Giada De Laurentiis</author> <year>2005</year> <price>30.00</price> </book> <book category="CHILDREN"> <title lang="en">Harry Potter</title> <author>J K.
    [Show full text]