Mathml 2.0 WD

Total Page:16

File Type:pdf, Size:1020Kb

Mathml 2.0 WD Mathematical Markup Language (MathML) Version 3.0 W3C Working Draft 17 November 2008 This version: http://www.w3.org/TR/2008/WD-MathML3-20081117/ Latest MathML 3 version: http://www.w3.org/TR/MathML3/ Latest MathML Recommendation: http://www.w3.org/TR/MathML/ Previous version: http://www.w3.org/TR/2008/WD-MathML3-20080409/ Editors: David Carlisle(NAG) Patrick Ion(Mathematical Reviews, American Mathematical Society) Robert Miner(Design Science, Inc.) Principal Authors: Ron Ausbrooks, Bert Bos, Olga Caprotti, David Carlisle, Giorgi Chavchanidze, Ananth Coorg, St\’ephane Dalmas, Stan Devitt, Sam Dooley, Margaret Hinchcliffe, Patrick Ion, Michael Kohlhase, Azzeddine Lazrek, Dennis Leas, Paul Libbrecht, Manolis Mavrikis, Bruce Miller, Robert Miner, Mur- ray Sargent, Kyle Siegrist, Neil Soiffer, Stephen Watt, Mohamed Zergaoui In addition to the HTML version, this document is also available in these non-normative formats: XHTML+MathML version and PDF version. Copyright c 1998-2008 W3C R (MIT, ERCIM, Keio), All Rights Reserved.W3C liability, trademark, document use and software licensing rules apply. Abstract This specification defines the Mathematical Markup Language, or MathML. MathML is an XML application for describing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathematics to be served, received, and processed on the World Wide Web, just as HTML has enabled this func- tionality for text. This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User’s Guide but rather a reference document. MathML can be used to encode both mathematical notation and mathematical content. About thirty-five of the MathML tags describe abstract notational structures, while another about one hundred and seventy provide a way of unambiguously specifying the intended meaning of an expression. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of special characters used for mathematics, their handling in MathML, their presence in Unicode, and their relation to fonts. While MathML is human-readable, in all but the simplest cases, authors use equation editors, conversion programs, and other specialized software tools to generate MathML. Several versions of such MathML tools exist, and more, both freely available software and commercial products, are under development. Status of this document This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/. This document is a W3C Public Working Draft produced by the W3C Math Working Group as part of the W3C Math Activity. The goals of the W3C Math Working Group are discussed in the W3C Math WG Charter (revised July 2006). A list of participants in the W3C Math Working Group is available. 2 Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. This fourth Public Working Draft specifies a new version of the the Mathematical Markup Language, MathML 3.0 which is at present under active development. The Math WG hopes this draft will permit informed feedback. There is a description of some considerations underlying this work in the W3C Math WG’s public Roadmap [roadmap]. Feedback should be sent to the Public W3C Math mailing list . The MathML 2.0 (Second Edition) specification has been a W3C Recommendation since 2001. After its recom- mendation, a W3C Math Interest Group collected reports of experience with the deployment of MathML and identified issues with MathML that might be ameliorated. The rechartering of a Math Working Group allows the revision to MathML 3.0 in the light of that experience, of other comments on the markup language, and of recent changes in specifications of the W3C and in the technological context. MathML 3.0 does not signal any change in the overall design of MathML. The major additions in MathML 3 are support for bidirectional layout, better line- breaking and explicit positioning, elementary math notations, and a new strict content MathML vocabulary with well-defined semantics generated from formal content dictionaries. The MathML 3 Specification has also been restructured. Public discussion of MathML and issues of support through the W3C for mathematics on the Web takes place on the public mailing list of the Math Working Group (list archives). To subscribe send an email to www-math- [email protected] with the word subscribe in the subject line. Please report errors in this document to [email protected]. This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. The basic chapter structure of this document is based on the earlier MathML 2.0 Recommendation [MathML2]. That MathML 2.0 itself was a revision of the earlier W3C Recommendation MathML 1.01 [MathML1]; MathML 3.0 is a revision of the W3C Recommendation MathML 2.0. It differs from it in that all previous chapters have been updated, some new elements and attributes added and some deprecated. This Public Working Draft differs in structure from the initial Public Working Draft as renewed efforts to separate the formal from the explanatory have resulted in eight chapters not seven. Much has been moved to separate documents containing Primer material, material on Characters and Entities and on the MathML DOM. First Working Drafts of these documents will be published soon. A current list of open issues, pointing into the relevant places in the draft, follows the Table of Contents. The present draft is an incremental one making public some of the results of Math Working Group work in recent months. The biggest difference this time is in Chapter 4, although there have been smaller ameliorations throughout the specification. A more detailed description of changes from the previous Recommendation follows. • With the second Working Draft, much of the non-normative explication that formerly was found in Chapters 1 and 2, and many examples from elsewhere in the previous MathML specifications, were removed from the MathML3 specification and incorporated into a MathML Primer being prepared as a separate document. It is expected this will help the use of this formal MathML3 specification as a reference document in implementations, and offer the new user better help in understanding MathML’s deployment. The remaining content of Chapters 1 and 2 is being edited to reflect the changes elsewhere in the document, and in the rapidly evolving Web environment. Some of their text used to go back to early days of the Web and XML, and its explanations are now commonplace. • Chapter 3, on presentation-oriented markup, in this draft adds new material on linebreaking and on markup for elementary math notations. Material introduced in the last draft revising the mpadded and 3 maction elements has been further revised as a result of active discussion. It is possible it may undergo further modification. In addition, the layout of schemata such as that for long division and its associated mcolumn element have been carefully revised. Earlier work, as recorded in the W3C Note Arabic math- ematical notation, has allowed clarification of the relationship with bidirectional text and examples with RTL text have been added. • Chapter 4, on content-oriented markup, contains major changes and additions in this Working Draft. The meaning of the actual content remains as before in principle, but a lot of work has been done on express- ing it better. The text of this chapter is generated by filtered extraction from XML Content Dictionaries written in accordance with OpenMath. The details of the Content Dictionary format have been further specified and the generation procedure improved. It is expected that the Content Dictionaries will be- come a separate joint publication of the W3C and OpenMath referenced by the MathML3 specification. The Content Dictionaries are now publicly available in draft and much work has already been done on refining them. Their format is given in Chapter 8. • Chapter 5 is being refined as its purpose has been further clarified. This chapter deals with interrelations of parts of the MathML specification, especially with presentation and content markup. • Chapter 6 has been rewritten and reorganized to reflect the new situation in regard to Unicode, and the changed W3C context with regard to named character entities. The new W3C specification of Entity Definitions for Characters in XML, which incorporates those used for mathematics is becoming a pub- lic working draft [Entities]. It is expected that some new ancillary tables will be provided that reflect requests the Math WG has received. • Chapter 7 has been restored with a new and clearer purpose. This chapter looks outward to the larger world in which MathML must function. • Chapter 8 will specify the format of MathML3 Content Dictionaries, as previously handled more briefly in sections 4.5 and 4.6. The DOM for MathML, previously in a chapter at this point, is being prepared as a separate specification.
Recommended publications
  • Bibliography of Erik Wilde
    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
    [Show full text]
  • Putting DDI in the Driver's Seat
    Putting DDI in the driver’s seat Using Metadata to control data capture Samuel Spencer Australian Bureau of Statistics 2010: XForms and DDI January: XForms transform demonstrated within ABS June: XForms live-demo at IASSIST 2010 July: XForms research put on hold October: Commercial Census web-form tool investigated ABS DDI Data Collection Projects Internet Activity Survey Agricultural Census Questionnaire Design Tool (QDT) Internet Activity Survey Then: Survey used in DDI/XForms research eForms solution using ABS developed technology Custom tool creates XForms, rendered using Orbeon Internet Activity Survey Then: Survey used in DDI/XForms research eForms solution using ABS developed technology Custom tool creates XForms, rendered using Orbeon Now: Candidate for migration to custom IBM web-form solution Agricultural Census Now: Currently running on IBM web-form solution Forms displayed using AJAX which interprets proprietary hand-crafted XML Agricultural Census Now: Currently running on IBM web-form solution Forms displayed using AJAX which interprets proprietary hand-crafted XML Future: Research into DDI to XML transforms Questionnaire Design Tool Then: Online app for questionnaire metadata management Manages creation of Blaise and paper forms Uses ABS-built proprietary XML (QDT-ML) Now: Investigations into replacing QDT-ML with DDI Research into using QDT to create web-forms How can it made simpler? The XForms standard describes a structured format for capturing form questions, control structures and complex data structures needed for accurate information capture. However, to be useful it needs to be transformed, as its not able to be displayed natively in current generation browsers. The DDI 3.0 standard describes a structured format for capturing form questions, control structures and complex data structures needed for accurate information capture.
    [Show full text]
  • Jørn Klungsøyr & Remi Andre Valvik (University of Bergen)
    DESIGN www.openXdata.org COLLECT www.openxdata.org MANAGE DESIGN Video tutorials available at: doc.openXdata.org www.openXdata.org [email protected] Usable data for informed decision making Jørn Klungsøyr ([email protected]) Remi Andre Valvik ([email protected]) Usable data for informed decision making Security Ease of Use Costs Scalability Integration Topics of this presentation • Functionalities • Ease of use • Change management • Security • Integration • Costs • Scalability • Open source community • Demonstrations Functionalities Design – Collect - Manage Design • Design complex forms in graphical interface • Supported question types include e.g.: Text, Numbers, Date, Time, Single / Multi-select, Multimedia, Geo tagging • Define skip logic & answer validation criteria Collect – Mobile phones <30$ Structured SMS – manually coded forms – for any phone eCollect – Android/iPhone/Pads/Laptops eCollect is a mini version openXdata web interface. • Stores data locally for offline functionality. • Users use regular browsers. • Android packag for native features like camera. Collect – Android with ODK-collect / JR Users can use ODK-collect due to a OpenROSA / JavaROSA standards API plugin. Collect - Web • Web-based forms can be accessed through desktop computer, laptop, netbook, pads/tabs and smartphones with access to the internet and JavaScript support Manage • Own your data - host on your own servers • Define roles for different types of users (e.g. administrator, study manager, mobile data collector) • Export data to CSV or direct to a relational database • Manage data and forms using a standard web-browser Ease of use Case reports from MoTeCH implementations MoTeCH – summary from interviews • Initial assumption to use structured SMS by health workers to create and update medical records using their own phones using "free" SMS.
    [Show full text]
  • Interactive Topographic Web Mapping Using Scalable Vector Graphics
    University of Nebraska at Omaha DigitalCommons@UNO Student Work 12-1-2003 Interactive topographic web mapping using scalable vector graphics Peter Pavlicko University of Nebraska at Omaha Follow this and additional works at: https://digitalcommons.unomaha.edu/studentwork Recommended Citation Pavlicko, Peter, "Interactive topographic web mapping using scalable vector graphics" (2003). Student Work. 589. https://digitalcommons.unomaha.edu/studentwork/589 This Thesis is brought to you for free and open access by DigitalCommons@UNO. It has been accepted for inclusion in Student Work by an authorized administrator of DigitalCommons@UNO. For more information, please contact [email protected]. INTERACTIVE TOPOGRAPHIC WEB MAPPING USING SCALABLE VECTOR GRAPHICS A Thesis Presented to the Department of Geography-Geology and the Faculty of the Graduate College University of Nebraska in Partial Fulfillment of the Requirements for the Degree Master of Arts University of Nebraska at Omaha by Peter Pavlicko December, 2003 UMI Number: EP73227 All rights reserved INFORMATION TO ALL USERS The quality of this reproduction is dependent upon the quality of the copy submitted. In the unlikely event that the author did not send a complete manuscript and there are missing pages, these will be noted. Also, if material had to be removed, a note will indicate the deletion. Dissertation WWisMng UMI EP73227 Published by ProQuest LLC (2015). Copyright in the Dissertation held by the Author. Microform Edition © ProQuest LLC. All rights reserved. This work is protected against unauthorized copying under Title 17, United States Code ProQuest LLC. 789 East Eisenhower Parkway P.O. Box 1346 Ann Arbor, Ml 48106-1346 THESIS ACCEPTANCE Acceptance for the faculty of the Graduate College, University of Nebraska, in Partial fulfillment of the requirements for the degree Master of Arts University of Nebraska Omaha Committee ----------- Uf.A [JL___ Chairperson.
    [Show full text]
  • Microsoft, Adobe & W3C to Shake up Electronic Forms Market
    Vol. 11, No, 8 October 2003 www.gilbane.com Published by: Bluebill Advisors, Inc. 763 Massachusetts Ave. Cambridge, MA 02139 USA (617) 497.9443 Fax (617) 497.5256 www.bluebilladvisors.com Editor: Frank Gilbane [email protected] (617) 497.9443 Content Technology Works! Editors Emeriti: Tim Bray [email protected] (604) 708.9592 MICROSOFT, ADOBE & XFORMS TO David Weinberger [email protected] (617) 738.8323 SHAKE UP ELECTRONIC FORMS MARKET Senior Editors: Sebastian Holst [email protected] Our title this month reads like a news headline on purpose. There are a number Bill Trippe [email protected] of new, and upcoming, developments in electronic forms (eForms) technology (617) 497.9443 that should be grabbing your attention. Some of these are of major importance Recent Contributors: on their own, but taken together, they signal the start of a major improvement Kathleen Reidy in businesses’ ability to easily collect, integrate, and process information. [email protected] Bob Doyle [email protected] “Electronic forms” have been around for years, but the term refers to a wide variety of technologies – from scanned image applications to HTML forms – Production Assistant: Sarah G. Dionne that are not at all similar and far from equal in their ability to accelerate and [email protected] smooth business processes. What eForm technology has shared is: a level of (617) 497.9443 difficulty that kept it out of the reach of office professionals who were com- Subscriptions: fortable enough with documents and spreadsheets, but scared-off by forms, [email protected] (617) 497.9443 and proprietary data formats that made information integration costly and complex.
    [Show full text]
  • Proposal to Represent the Slashed Zero Variant of Empty
    L2/15-268 Title: Proposal to Represent the Slashed Zero Variant of Empty Set Source: Barbara Beeton (American Mathematical Society), Asmus Freytag (ASMUS, Inc.), Laurențiu Iancu and Murray Sargent III (Microsoft Corporation) Status: Individual contribution Action: For consideration by the Unicode Technical Committee Date: 2015-10-30 Abstract As of Unicode Version 8.0, the symbol for empty set is encoded as the character U+2205 EMPTY SET, with no standardized variation sequences. In scientific publications, the symbol is typeset in one of three var- iant forms, chosen by notational style: a slashed circle, ∅, a slashed wide oval in the shape a letter, ∅, or a slashed narrow oval in the shape of a digit zero, . The slashed circle and the slashed zero forms are the most widely used, and correspond to the LaTeX commands \varnothing and \emptyset, respectively. Having one Unicode representation to map to, fonts that provide glyphs for more than one form of the symbol typically implement a stylistic variant or a mapping to a PUA code point. However, the wide- spread use of the slashed zero variant and its mapping to the main LaTeX command for the symbol, \emptyset, make it a candidate for a dedicated means to distinctly represent it in Unicode. This document evaluates three approaches for representing in Unicode the slashed zero variant of the empty set symbol and proposes a solution based on a variation sequence. Additional related characters resulting from the investigation and needed to complete the solution are also proposed for encoding. 1. The empty set symbol 1.1. Historical references The introduction of the modern symbol for the empty set is attributed to André Weil of the Nicholas Bourbaki group.
    [Show full text]
  • Jump Start Html5 by Tiffany B
    Summary of Contents Preface . xix 1. Basics: What is HTML5? . 1 2. Basics: The Anatomy of HTML5 . 7 3. Basics: Structuring Documents . 17 4. Basics: HTML5 Forms . 33 5. Basics: Multimedia, Audio and Video . 51 6. Multimedia: Preparing Your Media . 59 7. Multimedia: Using Native HTML5 Audio . 69 8. Multimedia: Using Native HTML5 Video . 77 9. Multimedia: The source Element . 87 10. Mutimedia: The track Element . 93 11. Multimedia: Scripting Media Players . 111 12. Canvas & SVG: An Introduction to Canvas . 123 13. Canvas & SVG: Canvas Basics . 127 14. Canvas & SVG: Handling Non-supporting Browsers . 137 15. Canvas & SVG: Canvas Gradients . 139 16. Canvas & SVG: Canvas Images and Videos . 145 17. Canvas & SVG: An Introduction to SVG . 149 18. Canvas & SVG: Using SVG . 159 19. Canvas & SVG: SVG Bézier Curves . 163 20. Canvas & SVG: SVG Filter Effects . 169 21. Canvas & SVG: Canvas or SVG? . 175 22. Offline Apps: Detecting When the User Is Connected . 179 23. Offline Apps: Application Cache . 185 24. Offline Apps: Web Storage . 197 25. Offline Apps: Storing Data With Client-side Databases . 215 26. APIs: Overview . 233 27. APIs: Web Workers . 239 28. APIs: The Geolocation API . 249 29. APIs: Server Sent Events . 255 30. APIs: The WebSocket API . 263 31. APIs: The Cross-document Messaging API . 269 JUMP START HTML5 BY TIFFANY B. BROWN KERRY BUTTERS SANDEEP PANDA iv Jump Start HTML5 by Tiffany B. Brown, Kerry Butters, and Sandeep Panda Copyright © 2014 SitePoint Pty. Ltd. Product Manager: Simon Mackie English Editor: Paul Fitzpatrick Technical Editor: Craig Buckler Cover Designer: Alex Walker Notice of Rights All rights reserved.
    [Show full text]
  • A Declarative Approach Based on Xforms
    Helsinki University of Technology Publications in Telecommunications Software and Multimedia Teknillisen korkeakoulun tietoliikenneohjelmistojen ja multimedian julkaisuja Espoo 2006 TML-A16 WEB USER INTERACTION - A DECLARATIVE APPROACH BASED ON XFORMS Mikko Honkala Dissertation for the degree of Doctor of Science in Technology to be presented with due permission of the Department of Computer Science and Engineering, for pub- lic examination and debate in Auditorium T2 at Helsinki University of Technology (Espoo, Finland) on the 12th of January, 2007, at 12 noon. Helsinki University of Technology Department of Computer Science and Engineering Telecommunications Software and Multimedia Laboratory Teknillinen korkeakoulu Tietotekniikan osasto Tietoliikenneohjelmistojen ja multimedian laboratorio Distribution: Helsinki University of Technology Telecommunications Software and Multimedia Laboratory P.O.Box 5400 FIN-02015 HUT Tel. +358-9-451 2870 Fax. +358-9-451 5014 c Mikko Honkala ISBN-13 978-951-22-8565-5 ISBN-10 951-22-8565-7 ISSN 1456-7911 ISBN-13 978-951-22-8566-2 (PDF) ISBN-10 951-22-8566-5 (PDF) ISSN 1455 9722 (PDF) URL: http://lib.tkk.fi/Diss/ Otamedia Oy Espoo 2006 ABSTRACT Author Mikko Honkala Title Web User Interaction - a Declarative Approach Based on XForms Published Doctoral thesis, Helsinki University of Technology, 2006 Keywords XML, User Interfaces, User Interaction, XForms, UIDL, XHTML This thesis studies next-generation web user interaction definition languages, as well as browser software architectures. The motivation comes from new end-user requirements for web applications: demand for higher interaction, adaptation for mobile and multimodal usage, and rich multimedia content. At the same time, there is a requirement for non- programmers to be able to author, customize, and maintain web user interfaces.
    [Show full text]
  • SMIL and SVG in Teaching
    SMIL and SVG in teaching Horst Eidenberger* Vienna University of Technology, Institute of Software Technology and Interactive Systems, Favoritenstrasse 9-11, 1040 Vienna, Austria ABSTRACT This paper describes how the web standards Synchronized Multimedia Integration Language (SMIL) and Scalable Vector Graphics (SVG) are used in teaching at the Vienna University of Technology. SMIL and SVG are used in courses on multimedia authoring. Didactically, the goal is to teach students how to use media objects and timing concepts to build interactive media applications. Additionally, SMIL is applied to generate multimedia content from a database using a content management system. The paper gives background information on the SMIL and SVG standards and sketches how teaching multimedia is organised at the Vienna University of Technology. Courses from the summer term 2003 are described and illustrated in two case studies. General design problems of SMIL-based presentations are modelled as patterns. Additionally, suggestions for improvement in the standards are given and shortcomings of existing user agents are summarised. Our conclusion is that SMIL and SVG are very well suited for teaching multimedia. Currently, the main problem is that all existing SMIL players lack some properties desired for teaching applications (stability, correctness, etc.). Keywords: Multimedia authoring, Synchronized Multimedia Integration Language, SMIL, Scalable Vector Graphics, SVG, content management, CMS, education, case study, personalisation, CC/PP 1. INTRODUCTION In recent years universities all over the world and, especially, in the German-speaking countries, that offer computer engineering studies have established courses on multimedia and temporal media processing. So at the Vienna University of Technology. Since the year 2000 it offers a very popular media informatics curriculum (about 350 beginners per year).
    [Show full text]
  • Leveraging Declarative Languages in Web Application Development
    World Wide Web DOI 10.1007/s11280-015-0339-z Leveraging declarative languages in web application development Petri Vuorimaa & Markku Laine & Evgenia Litvinova & Denis Shestakov Received: 7 February 2014 /Revised: 24 February 2015 /Accepted: 4 March 2015 # The Author(s) 2015. This article is published with open access at Springerlink.com Abstract Web Applications have become an omnipresent part of our daily lives. They are easy to use, but hard to develop. WYSIWYG editors, form builders, mashup editors, and markup authoring tools ease the development of Web Applications. However, more advanced Web Applications require servers-side programming, which is beyond the skills of end-user developers. In this paper, we discuss how declarative languages can simplify Web Application development and empower end-users as Web developers. We first identify nine end-user Web Application development levels ranging from simple visual customization to advanced three- tier programming. Then, we propose expanding the presentation tier to support all aspects of Web Application development. We introduce a unified XForms-based framework—called XFormsDB—that supports both client-side and server-side Web Application development. Furthermore, we make a language extension proposal—called XFormsRTC—for adding true real-time communication capabilities to XForms. We also present XFormsDB Integrated Development Environment (XIDE), which assists end-users in authoring highly interactive data-driven Web Applications. XIDE supports all Web Application development levels and, especially, promotes the transition from markup authoring and snippet programming to single and unified language programming. Keywords Web framework . Web application . Web development . End-user development . Declarative language . Real-time communication P. Vuorimaa (*) : M.
    [Show full text]
  • UBIWISE, a Simulator for Ubiquitous Computing Systems Design
    UBIWISE, A Simulator for Ubiquitous Computing Systems Design John J. Barton, Vikram Vijayaraghavan Mobile and Media Systems Laboratory HP Laboratories Palo Alto HPL-2003-93 April 29th , 2003* E-mail: {John_Barton, [email protected]} simulation, We describe UbiWise, a simulator for ubiquitous computing. The mobile, simulator concentrates on computation and communications devices ubiquitous, situated within their physical environments. It presents two views, handheld each in a separate window on the desktop of the users’ PC. One of the views provides a three dimensional world, built on the Quake III Arena graphics engine and serves to simulate a first-person view of the physical environment of a user. The other view, built using Java, shows a close-up view of devices and objects the user may manipulate. These views act as one unified whole by maintaining a client-server model with a central server. Multiple users can attach to the same server to create interactive ubiquitous computing scenarios. We describe how UbiWise looks to researchers and examples of its use as tool for ubiquitous computing research. * Internal Accession Date Only Approved for External Publication ã Copyright Hewlett-Packard Company 2003 UBIWISE, A Simulator for Ubiquitous Computing Systems Design John J. Barton, and Vikram Vijayaraghavan Hewlett-Packard Labs, 1501 Page Mill Road Palo Alto, CA 94304 {John_Barton, vikramv @hpl.hp.com} Abstract. We describe UbiWise, a simulator for ubiquitous computing. The simulator concentrates on computation and communications devices situated within their physical environments. It presents two views, each in a separate window on the desktop of the users' PC. One of the views provides a three dimensional world, built on the Quake III Arena graphics engine and serves to simulate a first-person view of the physical environment of a user.
    [Show full text]
  • Future of Text Book 2020 PDF.Indd
    THE FUTURE OF TEXT Edited by Frode Alexander Hegland First Published 2020. All articles are © Copyright of their respective authors. This collected work is © Copyright ‘Future Text Publishing’ and Frode Alexander Hegland. The PDF edition of this work is made available at no cost and the printed book is available from ‘Future Text Publishing’ (futuretextpublishing.com) a trading name of ‘The Liquid Information Company’. This work is freely available digitally, permitting any users to read, download, copy, distribute, print, search, or link to the full texts of these articles, crawl them for indexing, pass them as data to software, or use them for any other lawful purpose, without financial, legal, or technical barriers other than those inseparable from gaining access to the internet itself. The only constraint on reproduction and distribution, and the only role for copyright in this domain, should be to give authors control over the integrity of their work and the right to be properly acknowledged and cited. Typeset in Adobe Caslon Pro and Shinglewoode by Timothy Donaldson except for the Kindle version. ISBN: 9798556866782 DOI: future text publishing HOW TO READ THIS BOOK IN READER If you are reading this book in the Augmented Text Tool ‘Reader’ on macOS, which was developed to demonstrate some of the editor’s ideas about interactive text, you can interact with the text in experimental ways: • Copy As Citation: Copy and paste text into a visual-meta aware word processor, such as Author (see the ‘Visual-Meta’ section in this book) and it will paste as a full citation. This includes fields for both author and editor.
    [Show full text]