DOCSLIB.ORG

Appendix C: Technical Details (With Code)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Appendix C: Technical Details (With Code) Appendix C: Technical Details (with code) Note: This appendix provides technical details about the eXist system. In some cases the code used to create applications are referenced. As the length of some of the code files is over a few pages, there are two versions of this appendix; one that references the file name and displays the code while the other just lists the file name. Table of Contents 1. System Information 2. Template Files 3. File Structure 4. Creating New Collections 5. Search Functionality 6. Search 7. Search Performance 8. Modifying Indexing Parameters 9. Uploading Files 10. Moving Files 11. Checksum Application 12. Stress Test Tool 13. Dublin Core 14. Exporting Methods 15. Migration to XML Formats 16. Role-Based Access Controls 17. Scalability 1. System Information - eXist Database 1 Free download available on eXist’s home page o 2 Instructions for loading software o 3 o Play with code in the XQuery Sandbox using preloaded with sample data sets - oXygen XML Editor 4 Download free trial version or order licensed product o 5 o Database perspective communicates with eXist database file structure - Mozilla Firefox 6 o Download 1 eXist. Home Page. 2010. http://exist.sourceforge.net/ 2 Meier, Wolfgang M. Quick Start Guide. eXist. November 2009. http://exist.sourceforge.net/quickstart.html 3 eXist. XQuery Sandbox. http://demo.exist-db.org/exist/sandbox/sandbox.xql 4oXygen. oXygen: XML Editor Home Page. 2010. http://www.oxygenxml.com/ 5 oXygen. XML Database Perspective. http://www.oxygenxml.com/xml_and_relational_database_perspective.html 2. Template Files The following files were used as templates for creating new applications. For most new applications, only minor edits were needed for each file. Specific functionality of specialized applications required additional modifications or files. File Description index.xq Main landing page of the application. list-items.xq XQuery for listing items with one item per row. view-item.xq File that transforms XML document into XHTML for viewing. search-form.xq XHTML search form. search.xq Search service. edit.xq XForms application for saving new data and changing data. new-instance.xml Data for a new item (i.e. includes default values). next-id.xml XML file that contains the next ID number to be assigned to a document. save-new.xq Service that takes a HTTP POST (Save) from the edit form and saves it into the collection. It also assigns an ID to the document and increments the ID for the next save. update.xq Updates an existing document from an edit POST. delete-confirm.xq Confirms with the user that a delete should be performed. delete.xq Deletes a document. metrics.xq Counts the number of items in a collection. views collection Files that provide instructions for additional views of data in HTML format, including various reports. scripts collection XQuery Scripts that could be run to import or cleanup data sets or other functions. Sample Template Files 3. File Structure The folder/file structure of eXist is very repetitious which makes locating files simpler. The pilot project folder structure is shown below using oXygen’s Database Perspective. This clip shows the applications (apps) associated with the Minnesota Historical Society (mhs). The folder structure is as follows: - localhost (eXist) o db (eXist database) . cust (customers) • mhs (Minnesota Historical Society) o apps (the applications created for MHS) 6 Mozilla. Firefox 3.6. 2010. http://www.mozilla.com/firefox/ . the list of applications Each application folder contains the same set of folders used to organize the information. The applications ‘ca-bills’, ‘il-bills’, and ‘mn-bills’ are all expanded in this view and show that they all have the following: - A data folder (data) - An image folder (images) - A search folder (search) - A view folder (views) - A file for application information (app-info.xml) - A file for the home page for the application (index.xq) This view expands the folders found under each collection. The data folder holds the data (in this case one file); the images folder holds the images; the search folder holds the search forms required for the application; and the views folder holds the files and forms required for various views. By default, the folder structure also determines the web address in the browser being used to view the database. The following addresses show pathways to selected individual files: - Application Main Page: o http:// localhost:8080/exist/rest/cust/mhs/ap ps/index.xq - Glossary Main Page: o http:// localhost:8080/exist/rest/db/cust/mhs/ apps/glossary/index.xq - California Bill’s Search Page: o http://localhost:8080/exist/rest/db/cust/mhs/apps/ca-bills/search/search-form- html.xq - Minnesota Bill List View: o http://localhost:8080/exist/rest/db/cust/mhs/apps/mn-bills/views/list-items.xq - Checksum Data File: o http:// localhost:8080/exist/rest/db/cust/mhs/apps/check-sum/data/4.xml 4. Creating New Collections The following describes the general steps of creating a new collection within the pilot project system. After these steps are taken you should be able to view the new application home page, view a list of items, view individual records, and search the collection. 1. A set of template files was copied, renamed, and placed into the system structure. (localhost/db/cust/mhs/apps/collection name). The template files included the files contained in the data, images, search, and view folders as well as the main application files described below. a. index.xq: ‘home page’ for collection – shows icon, application title, and list of what you can do with the collection – generally list items, search item, and a count of items b. app-info.xml: provides an icon and application title on the application home page as well as give background information on who created it and with what versions 2. Icons and other necessary collection images were uploaded into the ‘images’ folder for the collection. 3. Data was uploaded into the ‘data’ folder for the collection. a. The XML tags found within the data will be used to determine what is displayed while viewing a record and what tags are searched. 4. The following template files were modified to be able to view the items in the collection. a. views/list.items.xq: view list of bills in the collection b. views/view-bill.xq: view individual bill i. Note that the individual bill views include transformation of XML strikeouts to HTML markup elements. This process uses ‘typeswitch’ XQuery transformations that are based on template rules. 5. The following template files were modified to search an individual collection. a. search/search-form-html.xq: provides a simple keyword search box for a collection b. search/search.xq: query instructions for keyword search displaying a list of results Note: Because of differences with XML tag names between the state collections, it was necessary to write separate transformations for each of the document viewers. For the applications Syntactica developed, each transformation was approximately two pages of XQuery that used the typeswitch function to translate each tag into the appropriate XHTML tag. If standard tags are used across collections, this action would not be necessary. Note: Some form operations on XML data sets are much easier than when using relational database. For example if a field has a one-to-many relationship it is easy to add this function to any form without making any changes to the database or the index configurations. Only a few lines of code were needed to add multiple categories to one item in selected collections. 5. Search Functionality To allow users to search, a simple search HTML form is used (file = search-form-html.xq). The search form displays a web page that contains a key word search box and a search button. The entire form for searching Illinois Bills is shown below: [File: search-form-html.xq for Illinois bills.] xquery version "1.0"; import module namespace style='http://www.mnhs.org/style' at '/db/cust/mhs/modules/style.xqm'; declare option exist:serialize "method=xhtml media-type=text/html indent=yes"; let $title := 'Search Illinois Bills' return <html> <head> <title>{$title}</title> {style:import-css()} </head> <body> {style:header()} {style:breadcrumb()} <h2>{$title}</h2> <div id="searchform"> <form method="GET" action="search.xq"> <p> <strong>Search:</strong> <input name="q" type="text" value="" size="60"/> <input type="submit" value="Search"/> </p> </form> </div> {style:footer()} </body> </html> 6. Search The keywords that are entered into the search box are passed to a REST search interface that actually performs the search. Using reverse keyword indexes created by the Lucene full-text indexing library, the search.xq file tells the REST service what documents match and gives instructions on how to display the search results. In general, the code for this service is a basic XQuery FLWOR7 statement in the form: for $hit in collection($my-collection)[ft:query(., $keywords)] order by ft:score($hit) return local:view-summary($hit) where: $my-collection was the name of the collection to be search $keywords is the string of keywords the users was searching $view-summary is an XQuery summary to view the document hit summary This service is invoked by simply adding the query parameter to the URL such as the following: SERVER/apps/mn-bills/search/search.xq?q=healthcare In addition, all of the search applications use two simple functions that are part of the Lucene function module: fq:query($context, $keywords): a function that returns a conditional (true, false) if a document contains a keyword ft:score($hit) : a relative numeric score that allows the hit results to be sorted from highest score to lowest score A small XQuery transformation was used to transform each XML document into a full HTML document for viewing on a web browser.
Load more

Recommended publications
  • 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]
  • 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]
  • 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]
  • Document Store Database Example
    Document Store Database Example Roderich is Barmecide: she predefine originally and juicing her currants. Prototypal Eli still utilises: purgatorial and associate Ron dimes quite eerily but drift her equalisers abidingly. Very and tantalizing Rikki luminesces, but Davis leftwardly rightens her docks. Returns an idea of database document model needs with each also accepts parameters such as strings Break when out nor the JSON and have it light an explicit issue in a hybrid store. Running a document database on Sql Server. Documents are stored in Collections and glide their dedicated CRUD operation set. How they use SQL Server as a Document Store Octopus Deploy. Examples of RDBMS and NoSQL databases Rackspace. MySQL JSON Document Store dasininet Diary create a MySQL. Tinydb PyPI. A database document store represents a collection of documents imported into. As we knew also see play are four tables in the worldx database but db. 3Pillar blog post by Girish Kumar and Rahul Checker exploring the different types of NoSQL databases that you cancel consider for each enterprise needs. How will data here a document database also possess as an own database stored? Document databases make it easier for developers to display and hence data in most database. Why You mother Never Use MongoDB Sarah Mei. For utility if you now looking at video surveillance data sensor. NoSQL Tutorial Types of NoSQL Databases What is & Example. To connect an obedience of the DocumentStore you need to abduct a best of URL addresses that compassion to RavenDB server nodes new DocumentStoreurls database. Xml document store lists of document stores do the database store and console gamer, specially if available.
    [Show full text]
  • Introduction to XSL Max Froumentin - W3C
    Introduction to XSL Max Froumentin - W3C l Introduction to XSL l XSL and other W3C specs l XML Documents l Transformations: XSLT l Styling XML Documents l General-purpose XSLT l XSL l Templates l Example I: Hamlet l XSLT statements l Example II: Mixed Writing Modes l "Play" to HTML l Example III: database l XPath l Other Examples l Formatting Objects basics l How do they do that? l Pages l The XSL Process(es) l The area model l Server-Side/Client-Side XSL l Block/inline areas Introduction to XSL Max Froumentin - W3C l Formatting Objects: l Properties l Example: Play to FO l Top-level Template l I18N Formatting Objects and Properties l Other Formatting Objects l Example: mixed writing modes l If you are still interested... Introduction to XSL In a nutshell: XSL is a W3C specification that describes a method for visually presenting XML documents. This tutorial will cover: l An overview of the XSL spec (including XSLT and XPath) l Examples of various use cases l Relationship with other XML technologies l A detailed example These slides are available at http://www.w3.org/People/maxf/XSLideMaker/ Introduction to XSL Max Froumentin - W3C 1 of 30 XML Documents l XML (eXtensible Markup Language) adds information to text files, using tags and attributes [example1], [example2] l Tag names are defined for a specific document type. l Uses the Unicode character set l Designed to be easily processed by machine while remaining readable. Introduction to XSL Max Froumentin - W3C 2 of 30 Styling XML Documents l XML documents are ideally semantic.
    [Show 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
    [Show full text]
  • Advanced Techniques in XSLT Jean-Michel Hufflen
    Advanced Techniques in XSLT Jean-Michel Hufflen To cite this version: Jean-Michel Hufflen. Advanced Techniques in XSLT. Biuletyn , 2006, pp.69–75. hal-00663119 HAL Id: hal-00663119 https://hal.archives-ouvertes.fr/hal-00663119 Submitted on 26 Jan 2012 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. Advanced Techniques in xslt∗ Jean-Michel HUFFLEN LIFC (FRE CNRS 2661) University of Franche-Comté 16, route de Gray 25030 BESANÇON CEDEX FRANCE [email protected] http://lifc.univ-fcomte.fr/~hufflen Abstract This talk focus on some advanced techniques used within xslt, such as sort procedures, keys, interface with identifier management, and priority rules among templates matching an xml node. We recall how these features work and propose some examples, some being related to bibliography styles. A short comparison between xslt and nbst, the language used within MlBibTEX for bibliography styles, is given, too. Keywords xslt, sort, keys, invoking rules, nbst. Streszczenie W prezentacji skupimy się na zaawansowanych technikach używanych w xslt, ta- kich jak procedury sortowania, klucze, interfejs do zarządzania identyfikatorami i reguły pierwszeństwa szablonów dopasowanych do konkretnego węzła. Przypo- mnimy jak te własności działają i pokażemy kilka przykładów, w tym niektóre związane ze stylami bibliograficznymi.
    [Show full text]
  • Basex Documentation
    BaseX Documentation Version 9.1 BaseX Documentation: Version 9.1 Publication date 2018-10-31 Content is available under Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0). Table of Contents 1. Main Page ................................................................................................................................ 1 Getting Started .................................................................................................................... 1 XQuery Portal ..................................................................................................................... 1 Advanced User's Guide ......................................................................................................... 2 I. Getting Started .......................................................................................................................... 3 2. Getting Started .................................................................................................................. 4 Overview .................................................................................................................... 4 3. Startup ............................................................................................................................. 6 Getting Started ............................................................................................................ 6 Distributions ........................................................................................................ 6 Requirements ......................................................................................................
    [Show full text]