XML London 2013 Proceedings

Total Page:16

File Type:pdf, Size:1020Kb

XML London 2013 Proceedings XML LONDON 2013 CONFERENCE PROCEEDINGS UNIVERSITY COLLEGE LONDON, LONDON, UNITED KINGDOM JUNE 15–16, 2013 XML London 2013 – Conference Proceedings Published by XML London Copyright © 2013 Charles Foster ISBN 978-0-9926471-0-0 Table of Contents General Information. 6 Sponsors. 7 Preface. 8 Building Rich Web Applications using XForms 2.0 - Nick van den Bleeken. 9 When MVC becomes a burden for XForms - Eric van der Vlist. 15 XML on the Web: is it still relevant? - O'Neil Delpratt. 35 Practice what we Preach - Tomos Hillman and Richard Pineger. 49 Optimizing XML for Comparison and Change - Nigel Whitaker and Robin La Fontaine. 57 What you need to know about the Maths Stack - Ms. Autumn Cuellar and Mr. Paul Topping. 63 Small Data in the large with Oppidum - Stéphane Sire and Christine Vanoirbeek. 69 Extremes of XML - Philip Fennell. 80 The National Archives Digital Records Infrastructure Catalogue: First Steps to Creating a Semantic Digital Archive - Rob Walpole. 87 From trees to graphs: creating Linked Data from XML - Catherine Dolbear and Shaun McDonald. 106 xproc.xq - Architecture of an XProc processor - James Fuller. 113 Lazy processing of XML in XSLT for big data - Abel Braaksma. 135 Using Distributed Version Control Systems Enabling enterprise scale, XML based information development - Dr. Adrian R. Warman. 145 A complete schema definition language for the Text Encoding Initiative - Lou Burnard and Sebastian Rahtz. 152 General Information Date Saturday, June 15th, 2013 Sunday, June 16th, 2013 Location University College London, London – Roberts Engineering Building, Torrington Place, London, WC1E 7JE Organising Committee Kate Foster, Socionics Limited Dr. Stephen Foster, Socionics Limited Charles Foster, XQJ.net & Socionics Limited Programme Committee Abel Braaksma, AbraSoft Adam Retter, Freelance Charles Foster (chair), XQJ.net Dr. Christian Grün, BaseX Eric van der Vlist, Dyomedea Jim Fuller, MarkLogic John Snelson, MarkLogic Lars Windauer, BetterFORM Mohamed Zergaoui, Innovimax Philip Fennell, MarkLogic Produced By XML London (http://xmllondon.com) Sponsors Gold Sponsor • OverStory - http://www.overstory.co.uk Silver Sponsor • oXygen - http://www.oxygenxml.com Bronze Sponsor • Mercator IT Solutions - http://www.mercatorit.com Preface This publication contains the papers presented during the XML London 2013 conference. This was the first international XML conference held in London for XML Developers – Worldwide, Semantic Web & Linked Data enthusiasts, Managers / Decision Makers and Markup Enthusiasts. This 2 day conference covered everything XML, both academic as well as the applied use of XML in industries such as finance and publishing. The conference took place on the 15th and 16th June 2013 at the Faculty of Engineering Sciences (Roberts Building) which is part of University College London (UCL). The conference dinner and the XML London 2013 DemoJam were held in the Jeremy Bentham Room at UCL, London. The conference will be held annually using the same format in subsequent years with XML London 2014 taking place in June 2014. — Charles Foster Chairman, XML London Building Rich Web Applications using XForms 2.0 Nick van den Bleeken Inventive Designers <[email protected]> Abstract XForms is a cross device, host-language independent markup language for declaratively defining a data XForms is a cross device, host-language independent markup processing model of XML data and its User Interface. It language for declaratively defining a data processing model uses a model-view-controller approach. The model of XML data and its User Interface. It reduces the amount consists of one or more XForms models describing the of markup that has to be written for creating rich web- data, constraints and calculations based upon that data, applications dramatically. There is no need to write any and submissions. The view describes what controls code to keep the UI in sync with the model, this is completely appear in the UI, how they are grouped together, and to handled by the XForms processor. what data they are bound. XForms 2.0 is the next huge step forward for XForms, XForms reduces the amount of markup that has to be making it an easy to use framework for creating powerful written for creating rich web-applications dramatically. web applications. There is no need to write any code to keep the UI in This paper will highlight the power of these new sync with the model, this is completely handled by the features, and show how they can be used to create real life XForms processor. web-applications. It will also discuss a possible framework XForms 2.0 is the next huge step forward for for building custom components, which is currently still XForms, making it an easy to use framework for creating missing in XForms. powerful web applications. This paper will first discuss the most important improvements in this new version of the specification, followed by an analysis of possible 1. Introduction improvements. Over the last 2 years there is a trend of moving away 2. XForm 2.0 from browser plug-in frameworks (Adobe Flash, JavaFX, and Microsoft silverlight) in favor of HTML5/Javascript This section will discuss the most important for building rich web-applications. This shift is driven by improvements of XForms compared to its previous the recent advances in technology (HTML5 [HTML5], version. Those improvements make it easier to create CSS [CSS] and Javascript APIs) and the vibrant browser powerful web applications that integrate with data market on one hand, and the recent security problems in available on the web. those plug-in frameworks on the other hand. Javascript is a powerful dynamic language, but a 2.1. XPath 2.0 potential maintenance nightmare if one is not extremely diligent. Creating rich web-applications using javascript XPath 2.0 [XPATH-20] adds a much richer type system, requires a lot of code. There are a lot of frameworks (like greatly expands the set of functions and adds additional Dojo [DOJO] and jQuery [JQUERY]) that try to language constructs like 'for' and 'if'. These new minimize the effort of creating user interfaces. Dojo even language features make it much easier to specify goes one step further by allowing you to create model- constraints and calculations. At the same time it makes it view-controller applications, but you still have to write a easier to display the data the way you want in the UI. lot of javascript to glue everything together. doi:10.14337/XMLLondon13.Bleeken01 Page 9 of 162 Building Rich Web Applications using XForms 2.0 Example 1. XPath 2.0: Calculate order price Example 3. Variables The folowing XPath expression calculates the sum of the <xf:var name="paging" value="instance('paging')"/> multiplication of the price and quantity of each item in <xf:group> the order: <xf:var name="total" value="$paging/@total"/> sum( for $n in order/item <xf:var name="page-size" return $n/price * $n/quantity value="$paging/@page-size"/> ) <xf:var name="page-count" value="($total + $page-size - 1) 2.2. Attribute Value Templates idiv $page-size"/> Attribute Value Templates [AVT] allow you the use <xf:output value="$page-count"> dynamic expressions virtually everywhere in the markup. <xf:label>Number of pages</xf:label> They are not limited to the XForms elements, but are </xf:output> supported on most host language attributes. Attribute </xf:group> Value Templates enable even more powerful styling of your form based on the data. As an example, a form 2.4. Custom Functions author can now easily highlight rows in a table based on certain data conditions (overdue, negative values, or Custom functions [CUST_FUNC] like variables allow complex conditions). In HTML5, this feature enables form authors to simplify expressions and prevent code the form author to declaratively specify when certain css- duplication without using extensions. classes apply to an element. Example 4. Custom Functions: Fibonacci Example 2. AVT: Higlight overdue jobs <function signature=" <xf:repeat ref="job"> my:fibonacci($n as xs:integer) as xs:integer"> <tr class="{ <var name="sqrt5" value="math:sqrt(5)" if(current-dateTime() > xs:dateTime(@due)) <result value="( then 'over-due' else '' math:power(1+$sqrt5, $n) - }"> math:power(1-$sqrt5, $n)) div ... (math:power(2, $n) * $sqrt5)" /> </tr> </function> </xf:repeat> 2.5. Non-XML data 2.3. Variables Because XForms' data model is XML it can consume Variables [VAR] make it possible to break down complex data from a lot of sources with little effort (SOAP expressions into pieces and make it easier to understand services, XML data bases using XQuery, REST XML the relationship of those pieces, by using expressive services, ...). Starting from XForms 2.0, XForms can variable names and documenting those individual pieces natively consume JSON data [JSON]. As more and more and their relationships. services on the web are starting to deliver JSON today Variables also facilitate in de-duplication of XPath this is an important feature. XForms implementations expressions in your form. In typical forms the same may support other non-XML file formats like CSV, expression is used multiple times (e.g.: XPath expression vCard, ... that calculates the selected language in a multi-lingual The form author can use all normal XForms UI). constructs (binds, UI controls, actions,...) independant from the data format of the external source. The XForms processor will build an XPath data model from the recieved data. Page 10 of 162 Building Rich Web Applications using XForms 2.0 2.6. Miscellaneous improvements 4.1. Using Custom Components Other interesting new features are: This section will discuss the aspects of a custom • Model based switching/repeats allows form authors to component that are relevant to the user of the capture the state of the switch/repeat in the model, component and demonstrate how custom controls can which makes it possible to save and restore the actual be used by the form author in an XForms document.
Recommended publications
  • OMA Specification
    Scalable Vector Graphics (SVG) for the Mobile Domain Candidate Version 1.0 – 24 Oct 2008 Open Mobile Alliance OMA-TS-SVG_Mobile-V1_0-20081024-C 2008 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. [OMA-Template-Spec-20080101-I] OMA-TS-SVG_Mobile-V1_0-20081024-C Page 2 (30) Use of this document is subject to all of the terms and conditions of the Use Agreement located at http://www.openmobilealliance.org/UseAgreement.html. Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance™ specification, and is subject to revision or removal without notice. You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document.
    [Show full text]
  • Efficient XML Processing in Browsers
    Efficient XML Processing in Browsers R. Alexander Milowski ILCC, School of Informatics, University of Edinburgh [email protected] Motivation Partially, in response to the anti-XML crowd's complaints about XML in browser applications: XML slow, inefficient way to deliver data, JSON is simpler and more directly usable, and several other red herrings. Mostly because I want it! ...pretty shiny XML objects... The reality: XMLHttpRequest is insufficient for both XML and JSON delivery. Why and what do you do about processing large amounts of XML data efficiently in browsers? Inefficiencies with XMLHttpRequest Three general deficiencies: 1. If the response is not XML and not characters, there is little support for handling the entity body (e.g. images). 2. If the response is not XML but is characters, treating it as XML or as a sequence of characters may be wasteful. 3. If the response is XML, the "whole document" intermediary DOM may be wasteful. This talk is about concerned with #3. Strategy We want flexibility and choice in our processing model: whole document, subsetting, multiple DOMs, view porting, filtering, or just a stream of events. We'll replace XMLHttpRequest and: Keep the request formulation, Remove the "whole document" treatment of the response, Add event-oriented processing of the XML. The XMLReader Interface Shares a lot in common with XMLHttpRequest for making the request: send, open, overrideMimeType, setRequestHeader, etc. request model is the same, added a parse(in DOMString xml) method for completeness, added an onxml event listener attribute for receiving XML, added an "xml" event type for addEventListener() XML Events Events for: start/end document, start/end element, characters, processing instructions, comments Events are flattened - one interface for all of them.
    [Show full text]
  • Xml Parsing with Dom4j
    University at Buffalo Hanifi Gunes Spring 2011 PhD Candidate Computer Science & Engineering CSE 586 - Distributed Systems hanifigu{at}buffalo{dot}edu xml parsing with dom4j In this tutorial we will talk about XML parsing with dom4j, an easy to use, open source library working with XML, XPath and XSLT on the Java platform. So let’s get started. ➀ Download and install eclipse for Java developers: http://www.eclipse.org Download the dom4j jar package: http://dom4j.sourceforge.net Download the jaxen jar package: http://jaxen.codehaus.org ➁ Run eclipse and locate your workspace directory if you are running it for the first time. Now, create a new Java Project, MyXMLReader, from File ➝ New ➝ Java Project. Notice that the project is created under the workspace directory {workspace_dir}/MyXMLReader. ➂ Right click on your project and select Build Path ➝ Add External Archives. Locate and add the dom4j jar archive from step 1 and repeat the same procedure to add the jaxen package to your build path. At that point, you should see these packages listed under Referenced Libraries as it is on the left snapshot. ➃ Now that, the project setup is done we can work with Yahoo! Weather. Visit http:// developer.yahoo.com/weather/ to get familiar with the XML response schema. First thing to observe is that you can query Yahoo Weather for a particular zip code using the following pattern http://weather.yahooapis.com/forecastrss?p=ZIPCODE. Try substituting your own zip code into the address pattern and then navigate to that address from your browser in order to inspect the XML response.
    [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]
  • 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]
  • XML Pipeline Performance
    XML Pipeline Performance Nigel Whitaker DeltaXML Ltd <[email protected]> Tristan Mitchell DeltaXML Ltd <[email protected]> Abstract This paper considers XML pipeline performance of a case study constructed from real code and data. It extends our original small study into 'Filter Pipeline Performance' on the saxon-help email list. The system used in this case study is a comparison tool for OASIS OpenDocument Text or '.odt' files. We will not describe the code in detail, but rather concentrate on the mechanisms used to interlink the various pipeline components used. These components include XML parsers, XSLT filter stages, XML comparison, Java filters based on the SAX XMLFilter interface and serialization. In the previous study we compared two pipelining techniques; this paper will extend this to consider three mechanisms which can be used to construct pipelines; these are: • The Java API for XML Processing (JAXP) included in Java Standard Edition 1.4 and subsequent releases • The s9api package provided by the Saxon XSLT processor 9.0 and sub- sequent releases • The Calabash implementation of the XProc XML pipeline language Our primary focus is performance and we will look at run times and memory sizes using these technologies. The overall runtime of the complete system will be described, but we will then concentrate on the performance of running a chain of filters (XSLT and Java based) as this is likely to be of moregeneral interest. We will also discuss some optimization techniques we have implemen- ted during the development process and further ideas for future performance improvement work. 1. Introduction In this section we will introduce the system being studied, briefly describe the data and also some aspects of the experimental approach.
    [Show full text]
  • SALT: an XML Application for Web-Based Multimodal Dialog Management
    SALT: An XML Application for Web-based Multimodal Dialog Management Kuansan Wang Speech Technology Group, Microsoft Research One Microsoft Way, Microsoft Corporation Redmond, WA, 98006, USA http://research.microsoft.com/stg devices. GUI is an immensely successful concept, Abstract notably demonstrated by the World Wide Web. Although the relevant technologies for the This paper describes the Speech Internet had long existed, it was not until the Application Language Tags, or SALT, an adoption of GUI for the Web did we witness a XML based spoken dialog standard for surge on its usage and rapid improvements in multimodal or speech-only applications. A Web applications. key premise in SALT design is that speech-enabled user interface shares a lot GUI applications have to address the issues of the design principles and computational commonly encountered in a goal-oriented dialog requirements with the graphical user system. In other words, GUI applications can be interface (GUI). As a result, it is logical to viewed as conducting a dialog with its user in an introduce into speech the object-oriented, iconic language. For example, it is very common event-driven model that is known to be for an application and its human user to undergo flexible and powerful enough in meeting many exchanges before a task is completed. The the requirements for realizing application therefore must manage the interaction sophisticated GUIs. By reusing this rich history in order to properly infer user’s intention. infrastructure, dialog designers are The interaction style is mostly system initiative relieved from having to develop the because the user often has to follow the underlying computing infrastructure and prescribed interaction flow where allowable can focus more on the core user interface branches are visualized in graphical icons.
    [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]
  • Product Description for Saxon- HE (Home Edition) Version 9.7 Released Nov 2015 Page 1/4
    Product Description for Saxon- HE (Home Edition) Version 9.7 released Nov 2015 Page 1/4 This document lists the features provided by Saxon 9.7 open source Home Edition (Saxon-HE). This document does not form part of any contract unless expressly incorporated. Language Support 1. XSLT (Transformation Processing) 1.1 XSLT 2.0 Provides a basic XSLT 2.0 processor as defined in section 21 of the (Basic) XSLT 2.0 Recommendation: it is a conformance level that includes all features of the language other than those that involve schema processing. For more details see: XSLT 2.0 conformance. Relevant W3C Specification: XSLT 2.0 Recommendation (23 January 2007). 2. XPath 2.1 XPath 2.0 Provides all XPath 2.0 features other than schema-awareness. (Basic) For more details see: XPath 2.0 conformance. Relevant W3C Specification: XPath 2.0 Recommendation (14 December 2010). 2.2 XPath 3.0 Provides all XPath 3.0 features other than schema-awareness and (Basic) higher-order functions. For more details see: XPath 3.0 conformance. Relevant W3C Specification: XPath 3.0 Recommendation (08 April 2014). 2.3 XPath 3.1 Provides all XPath 3.1 features other than schema-awareness and (Basic) higher-order functions. This includes an implementation of maps and arrays, and support for JSON. For more details see: XPath 3.1 conformance. Relevant W3C Specification: XPath 3.1 Candidate Recommendation (18 December 2014). Product Description for Saxon-HE (Home Edition) © Saxonica Ltd. 2017 Product Description for Saxon- HE (Home Edition) Version 9.7 released Nov 2015 Page 2/4 3.
    [Show full text]
  • Developing XML Applications for Oracle Weblogic Server 12C (12.2.1.2.0) E78038-02
    Oracle® Fusion Middleware Developing XML Applications for Oracle WebLogic Server 12c (12.2.1.2.0) E78038-02 December 2016 This document is a resource for software developers who design and develop applications that include XML processing. Oracle Fusion Middleware Developing XML Applications for Oracle WebLogic Server, 12c (12.2.1.2.0) E78038-02 Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Architectural Specifications for the World Wide Web and Their Role for Language Resources
    Architectural Specifications for the World Wide Web and their Role for Language Resources L. Quin, F. Sasaki, C.M. Sperberg-McQueen, H.S. Thompson W3C/MIT, W3C/Keio, W3C/MIT, W3C/ERCIM [email protected], [email protected], [email protected], [email protected] Abstract This paper describes specifications which have been (or are being) developed within the Architecture Domain of the World Wide Web Consortium. This Domain is responsible for many of the core technologies for the World Wide Web, including XML. We will describe XML-related technologies in five areas: validation, full-text analysis, declarative descriptions of XML processing, layout, and Interna- tionalization, focusing on how they are particularly suited for the representation and processing of language resources. The paper also includes a broad overview of the standardization process which underlies the development of these and other W3C technologies. 1. Introduction: A Brief Overview of W3C disclosure requirements for the participation in W3C work and its Process and is an important factor for many organizations to decide W3C1 is an international consortium with the mission to de- about their engagement in W3C. velop Web standards, with contributions from W3C mem- Two key aspects of W3C Recommendation development ber organizations, the W3C staff, and the public. are that we aim to reach consensus, within the W3C and W3C is working on a technology stack informally the public, about the actual features of new technologies, described at <http://www.w3.org/Consortium/techstack- and it is required to demonstrate several interoperable im- desc.html>. The Work is organized in Activities like the plementations before publishing a Recommendation.
    [Show full text]