DOCSLIB.ORG

XML Prague 2020

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
XML Prague 2020 XML Prague 2020 Conference Proceedings University of Economics, Prague Prague, Czech Republic February 13–15, 2020 XML Prague 2020 – Conference Proceedings Copyright © 2020 Jiří Kosek ISBN 978-80-906259-8-3 (pdf) ISBN 978-80-906259-9-0 (ePub) Table of Contents General Information ..................................................................................................... vii Sponsors .......................................................................................................................... ix Preface .............................................................................................................................. xi A note on Editor performance – Stef Busking and Martin Middel .............................. 1 XSLWeb: XSLT- and XQuery-only pipelines for the web – Maarten Kroon and Pieter Masereeuw ............................................................................ 19 Things We Lost in the Fire – Geert Bormans and Ari Nordström .............................. 31 Sequence alignment in XSLT 3.0 – David J. Birnbaum .............................................. 45 Powerful patterns with XSLT 3.0 hidden improvements – Abel Braaksma ............ 67 A Proposal for XSLT 4.0 – Michael Kay ..................................................................... 109 (Re)presentation in XForms – Steven Pemberton and Alain Couthures ................... 139 Greenfox – a schema language for validating file systems – Hans-Juergen Rennau ................................................................................................... 151 Use cases and examination of XML to process MS Word documents – Colin Mackenzie ............................................................................................................ 185 XML-MutaTe – Renzo Kottmann and Fabian Büttner ................................................ 205 Analytical XSLT – Liam Quin ..................................................................................... 219 XSLT Earley: First Steps to a Declarative Parser Generator – Tomos Hillman ..... 231 v vi General Information Date February 13th, 14th and 15th, 2020 Location University of Economics, Prague (UEP) nám. W. Churchilla 4, 130 67 Prague 3, Czech Republic Organizing Committee Petr Cimprich, XML Prague, z.s. Vít Janota, XML Prague, z.s. Káťa Kabrhelová, XML Prague, z.s. Jirka Kosek, xmlguru.cz & XML Prague, z.s. & University of Economics, Prague Martin Svárovský, Memsource & XML Prague, z.s. Mohamed Zergaoui, ShareXML.com & Innovimax Program Committee Robin Berjon, The New York Times Petr Cimprich, Wunderman Jim Fuller, MarkLogic Michael Kay, Saxonica Jirka Kosek (chair), University of Economics, Prague Ari Nordström, Creative Words Uche Ogbuji, Zepheira LLC Adam Retter, Evolved Binary Andrew Sales, Bloomsbury Publishing plc Felix Sasaki, Cornelsen GmbH John Snelson, MarkLogic Jeni Tennison, Open Data Institute Eric van der Vlist, Dyomedea Priscilla Walmsley, Datypic Norman Tovey-Walsh, MarkLogic Mohamed Zergaoui, Innovimax Produced By XML Prague, z.s. (http://xmlprague.cz/about) Faculty of Informatics and Statistics, UEP (http://fis.vse.cz) vii viii Sponsors oXygen (https://www.oxygenxml.com) Antenna House (https://www.antennahouse.com/) le-tex publishing services (https://www.le-tex.de/en/) Saxonica (https://www.saxonica.com/) print-css.rock (https://print-css.rock/) Czech Association for Digital Humanities (https://www.czadh.cz) speedata (https://www.speedata.de/) schematronist.org (https://schematronist.org/) Mercator IT Solutions Ltd (http://www.mercatorit.com) ix x Preface This publication contains papers presented during the XML Prague 2020 confer- ence. In its 15th year, XML Prague is a conference on XML for developers, markup geeks, information managers, and students. XML Prague focuses on markup and semantic on the Web, publishing and digital books, XML technologies for Big Data and recent advances in XML technologies. The conference provides an over- view of successful technologies, with a focus on real world application versus theoretical exposition. The conference takes place 13–15 February 2020 at the campus of University of Economics in Prague. XML Prague 2020 is jointly organized by the non-profit organization XML Prague, z.s. and by the Faculty of Informatics and Statistics, University of Economics in Prague. The full program of the conference is broadcasted over the Internet (see https://xmlprague.cz)—allowing XML fans, from around the world, to participate on-line. The Thursday runs in an un-conference style which provides space for various XML community meetings in parallel tracks. Friday and Saturday are devoted to classical single-track format and papers from these days are published in the pro- ceeedings. This year we put special focus on CSS and publishing. On the un-conference day there will be introductory tutorial about producing print output using CSS followed by the workshop where future of CSS Print should be discussed. Friday opening keynote by Rachel Andrew Refactoring (the way we talk about) CSS will hopefully give you a new perspective about how to perceive CSS. We hope that you enjoy XML Prague 2020! — Petr Cimprich & Jirka Kosek & Mohamed Zergaoui XML Prague Organizing Committee xi xii A note on Editor performance A story on how the performance of Fonto came to be what it is, and how we will further improve it Stef Busking FontoXML <[email protected]> Martin Middel FontoXML <[email protected]> Abstract This paper will discuss a number of key performance optimizations made during the development of Fonto, a web-based WYSIWYM XML editor. It describes how the configuration layer of Fonto works and what we did to make it faster. It will also describe how the indexing layer of Fonto works and how we improve it in the future. 1. Introduction 1.1. How does Fonto work? Fonto is a browser-based WYSIWYM1 editor for XML documents. It can be con- figured for any schema, including many DITA specializations, JATS, the TEI, doc- book and more. Fonto configuration consists of three parts: 1. How do elements look and feel (the schema experience) 2. How can they be mutated (the operations) 3. The encompassing user interface of Fonto The schema experience is specified as a set of rules that assign specific properties to all nodes matching a corresponding selector. These selectors are expressed in XPath. Operations also make use of XPath in order to query the documents. Effects are defined either as JavaScript code, or using XQuery Update Facility 3.0. The user interface of Fonto has several areas (e.g., the toolbar, sidebar and cus- tom dialog boxes) in which custom UI can be composed from React components. These can observe XPath expressions to access the current state of the documents 1What You See Is What You Mean 1 A note on Editor performance and be updated when it changes. The documents themselves are rendered recur- sively by querying the schema experience for each node and generating HTML appropriate for the resulting configuration. 1.2. What is performance? When a single key is pressed, Fonto needs to update the XML and then update all related UI. This includes updating the HTML representation of the documents, recomputing the state of all toolbar buttons based on the applicability of their operation in the new state, and updating any other UI as necessary. Typically, such updates involve looking up the values of various configured properties for a number of nodes (by re-evaluating the associated XPath selectors against those nodes) and/or executing other types of XPath / XQuery queries. In order to keep the editor responsive, these updates need to be implemented in a way that scales well with respect to both the complexity of the configuration as well as the sizes of the documents being edited. In order to keep Fonto easy to configure, we should not place too many requirements on the shape of this con- figuration. This means Fonto has to deal with a wide range of possibilities regard- ing the number of selectors etc. When we started Fonto, we considered documents of around 100KB to be ‘pretty big’, and these could be pretty slow to work with. After heavy optimiza- tion, we now have workable editors that load documents of multiple megabytes2, using (automatically updating) cross references, (automatic) numbering of sec- tions and more. This paper details a few of the most significant optimizations we have applied in order to get to that point. 2. Accessing schema experience configuration As described in the introduction, Fonto uses XPath selectors to apply a set of properties to nodes. We call the combination of a selector and a value a declara- tion. Example of the look and feel configuration of the ‘p’ element: configureAsBlock(sxModule, 'self::p'); This configuration does the following internally: 2Using just-in-time loading to only load a small subset, this even scales to working in collections total- ing in the hundreds of megabytes, but that could be considered cheating. 2 A note on Editor performance Table 1. Summary of properties set for a paragraph Property Value Automergable false Closed false Detached false Ignored for navigation false Removable if empty true Splittable true Select before delete false Default Text Container none Layout type block Inner layout type inline … (a total of 23 properties, plus optionally up to 35 more that are not set ... automatically) There are about 23 properties being configured for a single paragraph, each speci- fying whether the paragraph may be split, how it should interact
Load more

Recommended publications
  • Generating Xml Documents from Xml Schemas C
    Generating Xml Documents From Xml Schemas C Sven unbuckling his fantasm untucks mindlessly, but ginger Dom never overlooks so meanly. Hypochondriac arrivedand surplus imbricately Emmet after evanishes: Udale cellulated which Roland although, is tabescent quite gnarlier. enough? Pomiferous Augusto upbuilds no recitalists The wrapper may have hold two values: the base excess value velocity a derived type value. Are you sure you want to convert this comment to answer? The generic collection. First I created an XML file that represents the object in the web service by serializing an instance to XML. Xml manner as xpaths are two instances of five data sets up a number of xml schemas reference. This formatter replaces the default Eclipse XML formatter, returns the terminal type, etc. There forty three occurrence indicators: the plus sign, or the order then which these appear in relation to one another, answer how hospitality can design a protocol correctly. XSLT processor handle than with its default behavior is now. Only care that generates go to make some of excel workbook, and validate xml representation of how to. Yes, by applying the occurrence indicator to publish group rate than not each element within it, XML Schema provides very fine with over the kinds of data contained in an element or attribute. Each schema is opened as a temporary miscellaneous file. With this spreadsheet, instead of using the special DTD language to waiting a schema, since generating the file. XSD File Options section. In the examples we navigate a namespace prefix for the XML and none read the Schema. Very flexible when schemas change.
    [Show full text]
  • V a Lida T in G R D F Da
    Series ISSN: 2160-4711 LABRA GAYO • ET AL GAYO LABRA Series Editors: Ying Ding, Indiana University Paul Groth, Elsevier Labs Validating RDF Data Jose Emilio Labra Gayo, University of Oviedo Eric Prud’hommeaux, W3C/MIT and Micelio Iovka Boneva, University of Lille Dimitris Kontokostas, University of Leipzig VALIDATING RDF DATA This book describes two technologies for RDF validation: Shape Expressions (ShEx) and Shapes Constraint Language (SHACL), the rationales for their designs, a comparison of the two, and some example applications. RDF and Linked Data have broad applicability across many fields, from aircraft manufacturing to zoology. Requirements for detecting bad data differ across communities, fields, and tasks, but nearly all involve some form of data validation. This book introduces data validation and describes its practical use in day-to-day data exchange. The Semantic Web offers a bold, new take on how to organize, distribute, index, and share data. Using Web addresses (URIs) as identifiers for data elements enables the construction of distributed databases on a global scale. Like the Web, the Semantic Web is heralded as an information revolution, and also like the Web, it is encumbered by data quality issues. The quality of Semantic Web data is compromised by the lack of resources for data curation, for maintenance, and for developing globally applicable data models. At the enterprise scale, these problems have conventional solutions. Master data management provides an enterprise-wide vocabulary, while constraint languages capture and enforce data structures. Filling a need long recognized by Semantic Web users, shapes languages provide models and vocabularies for expressing such structural constraints.
    [Show full text]
  • Bibliography of Erik Wilde
    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
    [Show full text]
  • A Practical Ontology for the Large-Scale Modeling of Scholarly Artifacts and Their Usage
    A Practical Ontology for the Large-Scale Modeling of Scholarly Artifacts and their Usage Marko A. Rodriguez Johan Bollen Herbert Van de Sompel Digital Library Research & Digital Library Research & Digital Library Research & Prototyping Team Prototyping Team Prototyping Team Los Alamos National Los Alamos National Los Alamos National Laboratory Laboratory Laboratory Los Alamos, NM 87545 Los Alamos, NM 87545 Los Alamos, NM 87545 [email protected] [email protected] [email protected] ABSTRACT evolution of the amount of publications indexed in Thom- The large-scale analysis of scholarly artifact usage is con- son Scientific’s citation database over the last fifteen years: strained primarily by current practices in usage data archiv- 875,310 in 1990; 1,067,292 in 1995; 1,164,015 in 2000, and ing, privacy issues concerned with the dissemination of usage 1,511,067 in 2005. However, the extent of the scholarly data, and the lack of a practical ontology for modeling the record reaches far beyond what is indexed by Thompson usage domain. As a remedy to the third constraint, this Scientific. While Thompson Scientific focuses primarily on article presents a scholarly ontology that was engineered to quality-driven journals (roughly 8,700 in 2005), they do not represent those classes for which large-scale bibliographic index more novel scholarly artifacts such as preprints de- and usage data exists, supports usage research, and whose posited in institutional or discipline-oriented repositories, instantiation is scalable to the order of 50 million articles datasets, software, and simulations that are increasingly be- along with their associated artifacts (e.g.
    [Show full text]
  • Pearls of XSLT/Xpath 3.0 Design
    PEARLS OF XSLT AND XPATH 3.0 DESIGN PREFACE XSLT 3.0 and XPath 3.0 contain a lot of powerful and exciting new capabilities. The purpose of this paper is to highlight the new capabilities. Have you got a pearl that you would like to share? Please send me an email and I will add it to this paper (and credit you). I ask three things: 1. The pearl highlights a capability that is new to XSLT 3.0 or XPath 3.0. 2. Provide a short, complete, working stylesheet with a sample input document. 3. Provide a brief description of the code. This is an evolving paper. As new pearls are found, they will be added. TABLE OF CONTENTS 1. XPath 3.0 is a composable language 2. Higher-order functions 3. Partial functions 4. Function composition 5. Recursion with anonymous functions 6. Closures 7. Binary search trees 8. -- next pearl is? -- CHAPTER 1: XPATH 3.0 IS A COMPOSABLE LANGUAGE The XPath 3.0 specification says this: XPath 3.0 is a composable language What does that mean? It means that every operator and language construct allows any XPath expression to appear as its operand (subject only to operator precedence and data typing constraints). For example, take this expression: 3 + ____ The plus (+) operator has a left-operand, 3. What can the right-operand be? Answer: any XPath expression! Let's use the max() function as the right-operand: 3 + max(___) Now, what can the argument to the max() function be? Answer: any XPath expression! Let's use a for- loop as its argument: 3 + max(for $i in 1 to 10 return ___) Now, what can the return value of the for-loop be? Answer: any XPath expression! Let's use an if- statement: 3 + max(for $i in 1 to 10 return (if ($i gt 5) then ___ else ___))) And so forth.
    [Show full text]
  • High Performance XML Data Retrieval
    High Performance XML Data Retrieval Mark V. Scardina Jinyu Wang Group Product Manager & XML Evangelist Senior Product Manager Oracle Corporation Oracle Corporation Agenda y Why XPath for Data Retrieval? y Current XML Data Retrieval Strategies and Issues y High Performance XPath Requirements y Design of Extractor for XPath y Extractor Use Cases Why XPath for Data Retrieval? y W3C Standard for XML Document Navigation since 2001 y Support for XML Schema Data Types in 2.0 y Support for Functions and Operators in 2.0 y Underlies XSLT, XQuery, DOM, XForms, XPointer Current Standards-based Data Retrieval Strategies y Document Object Model (DOM) Parsing y Simple API for XML Parsing (SAX) y Java API for XML Parsing (JAXP) y Streaming API for XML Parsing (StAX) Data Retrieval Using DOM Parsing y Advantages – Dynamic random access to entire document – Supports XPath 1.0 y Disadvantages – DOM In-memory footprint up to 10x doc size – No planned support for XPath 2.0 – Redundant node traversals for multiple XPaths DOM-based XPath Data Retrieval A 1 1 2 2 1 /A/B/C 2 /A/B/C/D B F B 1 2 E C C 2 F D Data Retrieval using SAX/StAX Parsing y Advantages – Stream-based processing for managed memory – Broadcast events for multicasting (SAX) – Pull parsing model for ease of programming and control (StAX) y Disadvantages – No maintenance of hierarchical structure – No XPath Support either 1.0 or 2.0 High Performance Requirements y Retrieve XML data with managed memory resources y Support for documents of all sizes y Handle multiple XPaths with minimum node traversals
    [Show full text]
  • Decentralized Identifier WG F2F Sessions
    Decentralized Identifier WG F2F Sessions Day 1: January 29, 2020 Chairs: Brent Zundel, Dan Burnett Location: Microsoft Schiphol 1 Welcome! ● Logistics ● W3C WG IPR Policy ● Agenda ● IRC and Scribes ● Introductions & Dinner 2 Logistics ● Location: “Spaces”, 6th floor of Microsoft Schiphol ● WiFi: SSID Publiek_theOutlook, pwd Hello2020 ● Dial-in information: +1-617-324-0000, Meeting ID ● Restrooms: End of the hall, turn right ● Meeting time: 8 am - 5 pm, Jan. 29-31 ● Breaks: 10:30-11 am, 12:30-1:30 pm, 2:30-3 pm ● DID WG Agenda: https://tinyurl.com/didwg-ams2020-agenda (HTML) ● Live slides: https://tinyurl.com/didwg-ams2020-slides (Google Slides) ● Dinner Details: See the “Dinner Tonight” slide at the end of each day 3 W3C WG IPR Policy ● This group abides by the W3C patent policy https://www.w3.org/Consortium/Patent-Policy-20040205 ● Only people and companies listed at https://www.w3.org/2004/01/pp-impl/117488/status are allowed to make substantive contributions to the specs ● Code of Conduct https://www.w3.org/Consortium/cepc/ 4 Today’s agenda 8:00 Breakfast 8:30 Welcome, Introductions, and Logistics Chairs 9:00 Level setting Chairs 9:30 Security issues Brent 10:15 DID and IoT Sam Smith 10:45 Break 11:00 Multiple Encodings/Different Syntaxes: what might we want to support Markus 11:30 Different encodings: model incompatibilities Manu 12:00 Abstract data modeling options Dan Burnett 12:30 Lunch (brief “Why Are We Here?” presentation) Christopher Allen 13:30 DID Doc Extensibility via Registries Mike 14:00 DID Doc Extensibility via JSON-LD Manu
    [Show full text]
  • Hermes Documentation Release 2.2
    Hermes Documentation Release 2.2 CECID Nov 21, 2017 Contents 1 Proven Solution to Automate B2B Transactions1 2 EDI over the Internet 3 3 Unified and Extensible B2B Messaging Framework5 i ii CHAPTER 1 Proven Solution to Automate B2B Transactions Hermes Business Messaging Gateway is a proven open-source solution for enterprises to automate business trans- actions with business partners through secure and reliable exchange of electronic documents (e.g., purchase orders). Hermes is secure; it allows you to encrypt and digitally sign the documents for transmission. Hermes is reliable; the sender can automatically retransmit a message when it is dropped in the network while the receiver can guarantee every message is delivered once and only once, and in the right order. 1 Hermes Documentation, Release 2.2 2 Chapter 1. Proven Solution to Automate B2B Transactions CHAPTER 2 EDI over the Internet Electronic Data Interchange (EDI) was developed as the de facto standard for organizations to exchange business data. EDI is running on private networks and based on a cryptic protocol, which makes implementation complicated, expensive, and flexible. These disadvantages have limited the EDI usage to very large organizations only. Hermes is designed to use the Internet, Public Key Infrastructure (PKI), and XML technologies to replace the EDI as a more affordable and extensible solution. Hermes supports mainstream business-to-business (B2B) transport protocols, such as ebXML Message Service 2.0 (ebMS 2.0) and Applicability Statement 2 (AS2). (The ebMS 3.0 / AS4 support is currently under development.). 3 Hermes Documentation, Release 2.2 4 Chapter 2. EDI over the Internet CHAPTER 3 Unified and Extensible B2B Messaging Framework Hermes unifies different transport protocols into a single B2B messaging framework.
    [Show full text]
  • Automatic Generic Web Information Extraction at Scale
    1 Automatic Generic Web Information Extraction at Scale Master Thesis Computer Science, Data Science and Technology University of Twente. Enschede, The Netherlands An attempt to bring some structure to the web data mess. Author Mahmoud Aljabary Supervisors Dr. Ir. Maurice van Keulen Dr. Ir. Marten van Sinderen March 2021 2 Abstract The internet is growing at a rapid speed, as well as the need for extracting valuable information from the web. Web data is messy and disconnected, which poses a challenge for information extraction research. Current extraction methods are limited to a specific website schema, require manual work, and hard to scale. In this thesis, we propose a novel component-based design method to solve these challenges in a generic and automatic way. The global design consists of 1. a relevancy filter (binary classifier) to clean out irrelevant websites. 2. a feature extraction component to extract useful features from the relevant websites, including XPath. 3. an XPath-based clustering component to group similar web page elements into clusters based on Levenshtein distance. 4. a knowledge-based entity recognition component to link clusters with their corresponding entities. The last component remains for future work. Our experiments show huge potential in this generic approach to structure and extract web data at scale without the need for pre-defined website schemas. More work is needed in future experiments to link entities with their attributes and explore untapped candidate features. Keywords: Web information extraction, Machine learning, Web data wrapping, Wrapper induction, Relevancy filter, Clustering, Entity recognition, XPath, DOM, HTML, JSON, Levenshtein distance, Design science.
    [Show full text]
  • STYX: Connecting the XML Web to the World of Semantics
    STYX: Connecting the XML Web to the World of Semantics Irini Fundulaki1, Bernd Amann1, Catriel Beeri2, Michel Scholl1, and Anne-Marie Vercoustre3 1 Cedric-CNAM Paris, INRIA Rocquencourt [email protected], [email protected], [email protected] 2 Hebrew University, Israel [email protected] 3 INRIA-Rocquencourt; currently on leave at CSIRO Mathematical and Information Sciences, Melbourne, Australia [email protected] 1 Introduction The STYX prototype illustrates a new way to publish and query XML resources on the Web. It has been developed as part of the C-Web (Community Web) project1 whose main objective is to support the sharing, integration and retrieval of information in Web communities concerning a specific domain of interest. STYX is based on a simple but nevertheless powerful model for publish- ing and querying XML resources [1]. It implements a set of Web-based tools for creating and exploiting semantic portals to XML Web resources. The main functions of such a portal can be summarized as follows: (i) XML resources can be published/unpublished on the fly; (ii) structured queries can be formulated by taking into consideration the conceptual representation of a specific domain in form of an ontology; (iii) query results can be customized for display and further exploitation. The backbone of a STYX portal is a domain specific ontology comprised of concepts and roles describing the basic notions in the domain. Our approach [1] takes advantage of the presence of XML Document Type Definitions (DTDs) that capture the structure of XML documents. An XML source is published in 2 a STYX portal by a set of mapping rules that map XML document fragments specified by XPath3 location paths to ontology paths.
    [Show full text]
  • Documentum Xplore Administration Guide
    EMC ® Documentum ® xPlore Version 1.0 Administration Guide EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.EMC.com Copyright© 2010 EMC Corporation. All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. Table of Contents Preface ................................................................................................................................ 11 Chapter 1 Overview of xPlore ...................................................................................... 13 Features and limitations.................................................................................... 13 Indexing features.......................................................................................... 13 Indexing limitations...................................................................................... 13 Search features ............................................................................................
    [Show full text]
  • Presentation Component XSL Reference Rev: 2013-10-04
    Sitecore CMS 6.2 or later Presentation Component XSL Reference Rev: 2013-10-04 Sitecore CMS 6.2 or later Presentation Component XSL Reference A Conceptual Overview for Developers Sitecore® is a registered trademark. All other brand and product names are the property of their respective holders. The contents of this document are the property of Sitecore. Copyright © 2001-2013 Sitecore. All rights reserved. Sitecore CMS 6.2 or later Presentation Component XSL Reference Table of Contents Chapter 1 Introduction .................................................................................................................... 4 Chapter 2 Basic XSL and XPath Constructs .................................................................................... 5 2.1 XSL Overview .................................................................................................................... 6 2.2 XML, XSL, and XPath Tokens ............................................................................................ 7 2.3 XSL Elements .................................................................................................................... 9 2.3.1 The <xsl:variable> XSL Element ..................................................................................... 9 2.3.2 The <xsl:value-of> XSL Element ..................................................................................... 9 2.3.3 The <xsl:if> XSL Element ............................................................................................. 10 2.3.4 The <xsl:choose, <xsl:when>,
    [Show full text]