DOCSLIB.ORG

Mathematical Markup Language (Mathml) 1.01 Specification

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mathematical Markup Language (Mathml) 1.01 Specification Mathematical Markup Language (MathML") 1.01 Specification W3C Recommendation, revision of 7 July 1999 REC-MathML-19980407; revised 19990707 This version: http://www.w3.org/1999/07/REC-MathML-19990707 Latest version: http://www.w3.org/TR/REC-MathML Previous version: http://www.w3.org/TR/1998/REC-MathML-19980407 Editors: Patrick Ion <[email protected]> (Mathematical Reviews / American Mathematical Society) Robert Miner <[email protected]> (Geometry Technologies, Inc.) Principal Writers: Stephen Buswell, Stan Devitt, Angel Diaz, Patrick Ion, Robert Miner, Nico Poppelier, Bruce Smith, Neil Soiffer, Robert Sutor, Stephen Watt Copyright © 1999 W3C (MIT, INRIA, 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 Web, just as HTML has enabled this functionality 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. This document begins with background information on mathematical notation, the problems it poses, and the philosophy underlying the solutions MathML proposes. MathML can be used to encode both mathematical notation and mathematical content. Twenty-eight of the MathML tags describe abstract notational structures, while another seventy-five 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 MathML entities (extended characters) and their relation to fonts. While MathML is human-readable it is anticipated that, in all but the simplest cases, authors will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several early versions of such MathML tools already exist, and a number of others, both freely available software and commercial products, are under development. Status of this document This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web. The fundamental eXtensible Markup Language (XML) 1.0 specification upon which MathML is based has been adopted as a W3C Recommendation. Should future changes in the XML specification necessitate changes in the MathML specification, it is the intention of the W3C Math Working Group to issue a revision of the MathML specification. However, any changes are very unlikely to be substantial. Most of this document represents technology tested by multiple implementations. A summary of MathML rendering and authoring software is described on the W3C Math Working Group home page. The www-math mailing list is a public forum for questions and comments about MathML and issues related to putting math on the Web. The W3C Math Working Group intends further development of recommendations for mathematics on the Web, as set out below. A list of current W3C Recommendations and other technical reports can be found at http://www.w3.org/TR. This document is a revised version of the document first released on 7 April 1998. Changes from the original version are only editorial in nature. The present W3C Math Working Group is working on further improvements of MathML. Available formats The MathML 1.01 W3C Recommendation is made available in different formats from the W3C Math WG's site. In case of a discrepancy between any of the derived forms and that found in the W3C's archive of Recommendations the definitive version is naturally the Recommendation. At first it is expected that zipped and gzipped bundles will be made available, but such easily printable formats as PostScript or PDF may be supplied. Available languages The English version of this specification is the only normative version. However, for translations of this document, see http://www.w3.org/MarkUp/mathml101-updates/translations.html. Errata The list of known errors in this specification is available at: http://www.w3.org/MarkUp/mathml101-updates/errata.html. Please report errors in this document to [email protected]. Table of contents Extended Table of Contents ● Chapter 1. Introduction ● Chapter 2. MathML Fundamentals ● Chapter 3. Presentation Markup ● Chapter 4. Content Markup ● Chapter 5. Mixing Presentation and Content ● Chapter 6. Entities, Characters and Fonts ● Chapter 7. Implementing MathML ● Appendix A. DTD for MathML ● Appendix B. Glossary ● Appendix C. Operator Dictionary ● Appendix D. Working Group Membership ● Appendix E. Informal EBNF Grammar for Content Elements ● Appendix F. Default Semantic Bindings for Content Elements ● Appendix G. MathML 1.0 Changes ● References REC-MathML-19980407; revised 19990707 Mathematical Markup Language 1.01 Specification Table of Contents ● Title page and Abstract ● 1. Introduction ❍ 1.1 Mathematics and its Notation ❍ 1.2 Origins and Goals ■ 1.2.1 The History of MathML ■ 1.2.2 Limitations of HTML ■ 1.2.3 Requirements for Mathematical Markup ■ 1.2.4 Goals of MathML ❍ 1.3 The Role of MathML on the Web ■ 1.3.1 Layered Design of Mathematical Web Services ■ 1.3.2 Relation to Other Web Technology ● 2. MathML Fundamentals ❍ 2.1 MathML Overview ■ 2.1.1 Taxonomy of MathML Elements ■ 2.1.2 Expression Trees and Token Elements ■ 2.1.3 Presentation Markup ■ 2.1.4 Content Markup ■ 2.1.5 Mixing Presentation and Content ❍ 2.2 Some MathML Examples ■ 2.2.1 Presentation Examples ■ 2.2.2 Content Examples ■ 2.2.3 Mixed Markup Examples ❍ 2.3 MathML Syntax and Grammar ■ 2.3.1 An XML Syntax Primer ■ 2.3.2 Children vs. Arguments ■ 2.3.3 MathML Attributes Values ■ 2.3.4 Attributes Shared by all MathML Elements ■ 2.3.5 Collapsing Whitespace in Input ● 3. Presentation Markup ❍ 3.1 Introduction ■ 3.1.1 What Presentation Elements Represent ■ 3.1.2 Terminology Used In This Chapter ■ 3.1.3 Required Arguments ■ 3.1.4 Elements with Special Behaviors ■ 3.1.5 Summary of Presentation Elements ❍ 3.2 Token elements ■ 3.2.1 Attributes common to token elements ■ 3.2.2 <mi> -- identifier ■ 3.2.3 <mn> -- number ■ 3.2.4 <mo> -- operator, fence, or separator ■ 3.2.5 <mtext> -- text ■ 3.2.6 <mspace/> -- space ■ 3.2.7 <ms> -- string literal ❍ 3.3 General Layout Schemata ■ 3.3.1 <mrow> -- horizontally group any number of subexpressions ■ 3.3.2 <mfrac> -- form a fraction from two subexpressions ■ 3.3.3 <msqrt> and <mroot> -- form a radical ■ 3.3.4 <mstyle> -- style change ■ 3.3.5 <merror> -- enclose a syntax error message from a preprocessor ■ 3.3.6 <mpadded> -- adjust space around content ■ 3.3.7 <mphantom> -- make content invisible but preserve its size ■ 3.3.8 <mfenced> -- surround content with a pair of fences ❍ 3.4 Script and Limit Schemata ■ 3.4.1 <msub> -- attach a subscript to a base ■ 3.4.2 <msup> -- attach a superscript to a base ■ 3.4.3 <msubsup> -- attach a subscript-superscript pair to a base ■ 3.4.4 <munder> -- attach an underscript to a base ■ 3.4.5 <mover> -- attach an overscript to a base ■ 3.4.6 <munderover> -- attach an underscript-overscript pair to a base ■ 3.4.7 <mmultiscripts> -- attach prescripts and tensor indices to a base ❍ 3.5 Tables and Matrices ■ 3.5.1 <mtable> -- table or matrix ■ 3.5.2 <mtr> -- row in a table or matrix ■ 3.5.3 <mtd> -- one entry in a table or matrix ■ 3.5.4 <maligngroup/> and <malignmark/> -- alignment markers ❍ 3.6 Enlivening Expressions ■ 3.6.1 <maction> -- bind actions to a subexpression ● 4. Content Markup -- Index of All Content Elements ❍ 4.1 Introduction ■ 4.1.1 The Intent of Content Markup ■ 4.1.2 The Scope of Content Markup ■ 4.1.3 Basic Concepts of Content Markup ❍ 4.2 Content Element Usage Guide ■ 4.2.1 Overview of Syntax and Usage ■ 4.2.2 Containers ■ 4.2.3 Functions, Operators and Qualifiers ■ 4.2.4 Relations ■ 4.2.5 Conditions ■ 4.2.6 Syntax and Semantics ■ 4.2.7 Semantic Mappings ■ 4.2.8 MathML element types ❍ 4.3 Content Element Attributes ■ 4.3.1 Content Element Attribute Values ■ 4.3.2 Attributes Modifying Content Markup Semantics ■ 4.3.3 Attributes Modifying Content Markup Rendering ❍ 4.4 The Content Markup Elements ■ 4.4.1 Token Elements ■ 4.4.2 Basic Content Elements ■ 4.4.3 Arithmetic, Algebra and Logic ■ 4.4.4 Relations ■ 4.4.5 Calculus ■ 4.4.6 Theory of Sets ■ 4.4.7 Sequences and Series ■ 4.4.8 Trigonometry ■ 4.4.9 Statistics ■ 4.4.10 Linear Algebra ■ 4.4.11 Semantic Mapping Elements ● 5. Mixing Presentation and Content ❍ 5.1 When to Use Mixed Markup ■ 5.1.1 Why Two Different Kinds of Markup? ■ 5.1.2 Reasons to Mix Markup ❍ 5.2 How to use Mixed Markup ■ 5.2.1 Presentation Markup Contained in Content Markup ■ 5.2.2 Content Markup Contained in Presentation Markup ❍ 5.3 Anticipating Macros for Combined Markup ● 6. Entities, Characters and Fonts ❍ 6.1 Introduction ■ 6.1.1 The Intent of Entity Names ■ 6.1.2 The STIX Project ❍ 6.2 Entity Listings ■ 6.2.1 Non-Marking Entities ■ 6.2.2 Printing Entity List ■ 6.2.3 Special Constants ■ 6.2.4 Full Alphabetical Lists ■ 6.2.5 ISO Entity Set Groupings ■ 6.2.5.1 ISO Symbol Entity Sets ■ 6.2.5.2 ISO Math Font Entity Sets ■ 6.2.5.3 Other ISO Font Entity Sets ■ 6.2.6 Additional Entity Set Grouping ● 7.
Load more

Recommended publications
  • Just Another Perl Hack Neil Bowers1 Canon Research Centre Europe
    Weblint: Just Another Perl Hack Neil Bowers1 Canon Research Centre Europe Abstract Weblint is a utility for checking the syntax and style of HTML pages. It was inspired by lint [15], which performs a similar function for C and C++ programmers. Weblint does not aspire to be a strict SGML validator, but to provide helpful comments for humans. The importance of quality assurance for web sites is introduced, and one particular area, validation of HTML, is described in more detail. The bulk of the paper is devoted to weblint: what it is, how it is used, and the design and implementation of the current development version. 1. Introduction The conclusion opens with a summary of the information and opinions given in this paper. A Web sites are becoming an increasingly critical part of selection of the lessons learned over the last four years how many companies do business. For many companies is given, followed by plans for the future, and related web sites are their business. It is therefore critical that ideas. owners of web sites perform regular testing and analysis, to ensure quality of service. 2. Web Site Quality Assurance There are many different checks and analyses which The following are some of the questions you should be you can run on a site. For example, how usable is your asking yourself if you have a web presence. I have site when accessed via a modem? An incomplete list of limited the list to those points which are relevant to similar analyses are given at the start of Section 2.
    [Show full text]
  • HTML5 and the Open Web Platform
    HTML5 and the Open Web Platform Stuttgart 28 May 2013 Dave Raggett <[email protected]> The Open Web Platform What is the W3C? ● International community where Members, a full-time staff and the public collaborate to develop Web standards ● Led by Web inventor Tim Berners-Lee and CEO Jeff Jaffe ● Hosted by MIT, ERCIM, Keio and Beihang ● Community Groups open to all at no fee ● Business Groups get more staff support ● Technical Working Groups ● Develop specs into W3C Recommendations ● Participants from W3C Members and invited experts ● W3C Patent process for royalty free specifications 3 Who's involved ● W3C has 377 Members as of 11 May 2013 ● To name just a few ● ACCESS, Adobe, Akamai, Apple, Baidu, BBC, Blackberry (RIM), BT, Canon, Deutsche Telekom, eBay, Facebook, France Telecom, Fujitsu, Google, Hitachi, HP, Huawei, IBM, Intel, LG, Microsoft, Mozilla, NASA, NEC, NTT DoCoMo, Nuance, Opera Software, Oracle, Panasonic, Samsung, Siemens, Sony, Telefonica, Tencent, Vodafone, Yandex, … ● Full list at ● http://www.w3.org/Consortium/Member/List 4 The Open Web Platform 5 Open Web Platform ● Communicate with HTTP, Web Sockets, XML and JSON ● Markup with HTML5 ● Style sheets with CSS ● Rich graphics ● JPEG, PNG, GIF ● Canvas and SVG ● Audio and Video ● Scripting with JavaScript ● Expanding range of APIs ● Designed for the World's languages ● Accessibility with support for assistive technology 6 Hosted and Packaged Apps ● Hosted Web apps can be directly loaded from a website ● Packaged Web apps can be locally installed on a device and run without the need for access to a web server ● Zipped file containing all the necessary resources ● Manifest file with app meta-data – Old work on XML based manifests (Web Widgets) – New work on JSON based manifests ● http://w3c.github.io/manifest/ ● Pointer to app's cache manifest ● List of required features and permissions needed to run correctly ● Runtime and security model for web apps ● Privileged apps must be signed by installation origin's private key 7 HTML5 Markup ● Extensive range of features ● Structural, e.g.
    [Show full text]
  • Downloaded (Just Like an EXE File) and Executed from Local File System
    HTML - Wikipedia, the free encyclopedia http://en.wikipedia.org/wiki/HTML HTML From Wikipedia, the free encyclopedia HyperText Markup Language ( HTML ) is the main HTML markup language for displaying web pages and other (HyperText Markup Language) information that can be displayed in a web browser. Filename .html, .htm HTML is written in the form of HTML elements extension consisting of tags enclosed in angle brackets (like <html> ), within the web page content. HTML tags most Internet text/html commonly come in pairs like <h1> and </h1> , although media type some tags, known as empty elements , are unpaired, for Type code TEXT example <img> . The first tag in a pair is the start tag , the second tag is the end tag (they are also called opening Uniform Type public.html tags and closing tags ). In between these tags web Identifier designers can add text, tags, comments and other types of Developed by World Wide Web Consortium & text-based content. WHATWG The purpose of a web browser is to read HTML Type of Markup language documents and compose them into visible or audible web format pages. The browser does not display the HTML tags, but Extended SGML uses the tags to interpret the content of the page. from HTML elements form the building blocks of all websites. Extended to XHTML HTML allows images and objects to be embedded and Standard(s) can be used to create interactive forms. It provides a ISO/IEC 15445 means to create structured documents by denoting W3C HTML 4.01 structural semantics for text such as headings, paragraphs, (http://www.w3.org/TR/1999 lists, links, quotes and other items.
    [Show full text]
  • HTML5 Favorite Twitter Searches App Browser-Based Mobile Apps with HTML5, CSS3, Javascript and Web Storage
    Androidfp_19.fm Page 1 Friday, May 18, 2012 10:32 AM 19 HTML5 Favorite Twitter Searches App Browser-Based Mobile Apps with HTML5, CSS3, JavaScript and Web Storage Objectives In this chapter you’ll: ■ Implement a web-based version of the Favorite Twitter Searches app from Chapter 5. ■ Use HTML5 and CSS3 to implement the interface of a web app. ■ Use JavaScript to implement the logic of a web app. ■ Use HTML5’s Web Storage APIs to store key-value pairs of data that persist between executions of a web app. ■ Use a CSS reset to remove all browser specific HTML- element formatting before styling an HTML document’s elements. ■ Save a shortcut for a web app to your device’s home screen so you can easily launch a web app. = DRAFT: © Copyright 1992–2012 by Deitel & Associates, Inc. All Rights Reserved. Androidfp_19.fm Page 2 Friday, May 18, 2012 10:32 AM 2 Chapter 19 HTML5 Favorite Twitter Searches App 19.1 Introduction 19.5 Building the App 19.2 Test-Driving the Favorite Twitter 19.5.1 HTML5 Document Searches App 19.5.2 CSS 19.5.3 JavaScript 19.3 Technologies Overview Outline 19.6 Wrap-Up 19.1 Introduction The Favorite Twitter Searches app from Chapter 5 allowed users to save their favorite Twit- ter search strings with easy-to-remember, user-chosen, short tag names. Users could then conveniently follow tweets on their favorite topics. In this chapter, we reimplement the Fa- vorite Twitter Searches app as a web app, using HTML5, CSS3 and JavaScript.
    [Show full text]
  • Copyrighted Material
    05_096970 ch01.qxp 4/20/07 11:27 PM Page 3 1 Introducing Cascading Style Sheets Cascading style sheets is a language intended to simplify website design and development. Put simply, CSS handles the look and feel of a web page. With CSS, you can control the color of text, the style of fonts, the spacing between paragraphs, how columns are sized and laid out, what back- ground images or colors are used, as well as a variety of other visual effects. CSS was created in language that is easy to learn and understand, but it provides powerful control over the presentation of a document. Most commonly, CSS is combined with the markup languages HTML or XHTML. These markup languages contain the actual text you see in a web page — the hyperlinks, paragraphs, headings, lists, and tables — and are the glue of a web docu- ment. They contain the web page’s data, as well as the CSS document that contains information about what the web page should look like, and JavaScript, which is another language that pro- vides dynamic and interactive functionality. HTML and XHTML are very similar languages. In fact, for the majority of documents today, they are pretty much identical, although XHTML has some strict requirements about the type of syntax used. I discuss the differences between these two languages in detail in Chapter 2, and I also pro- vide a few simple examples of what each language looks like and how CSS comes together with the language to create a web page. In this chapter, however, I discuss the following: ❑ The W3C, an organization that plans and makes recommendations for how the web should functionCOPYRIGHTED and evolve MATERIAL ❑ How Internet documents work, where they come from, and how the browser displays them ❑ An abridged history of the Internet ❑ Why CSS was a desperately needed solution ❑ The advantages of using CSS 05_096970 ch01.qxp 4/20/07 11:27 PM Page 4 Part I: The Basics The next section takes a look at the independent organization that makes recommendations about how CSS, as well as a variety of other web-specific languages, should be used and implemented.
    [Show full text]
  • Mathplayer: Web-Based Math Accessibility Neil Soiffer Design Science, Inc 140 Pine Avenue, 4Th Floor
    MathPlayer: Web-based Math Accessibility Neil Soiffer Design Science, Inc 140 Pine Avenue, 4th Floor. Long Beach, CA 90802 USA +1 562-432-2920 [email protected] ABSTRACT UMA[4] and Lambda[9]. Both projects have a strong focus on MathPlayer is a plug-in to Microsoft’s Internet Explorer (IE) that two-way translation between MathML and multiple braille math renders MathML[11] visually. It also contains a number of codes. They also include some standalone software for voicing features that make mathematical expressions accessible to people and navigating math. with print-disabilities. MathPlayer integrates with many screen Our work differs from previous work mainly in its focus – readers including JAWS and Window-Eyes. MathPlayer also MathPlayer is a mainstream application that is also designed to works with a number of TextHELP!’s learning disabilities work with popular assistive technology (AT) software. Our goal is products. to allow people to continue to use tools that they are already familiar with such as JAWS and IE, and not require them to use a Categories and Subject Descriptors different browser simply because the document they are reading H.5.4 [Information Systems]: Information Interfaces and contains mathematical expressions. Presentation—User Issues. 2. MATHPLAYER FEATURES General Terms MathPlayer is a free plug-in for IE that displays MathML in Web Design, Human Factors. pages. Because MathML is not an image format, MathPlayer is able to dynamically display a mathematical expression that Keywords matches the document’s font properties such as size and color. Hence, if a user chooses to read a document using a larger font Print Disabilities, Visual Impairments, Math Accessibility, size than standard or chooses a particular color scheme, the math Assistive Technology, MathML will also be displayed using that larger font size or color scheme.
    [Show full text]
  • Business Meeting of the Openmath Society 2018
    Business Meeting of the OpenMath Society 2018 Michael Kohlhase (President) Openmath Society http://openmath.org August 13. 2018, Hagenberg Kohlhase: Business Meeting of the OpenMath Society 2018 1 13. 8. 18, Hagenberg OpenMath 2018 Business Meeting (as required by Statutes) 1. Election of Chair of the meeting 2. Election of Secretary and two Minute Checkers (James is in Rio) 3. Annual Report 4. New Members? 5. Adoption of Balance Sheet and discharge of the Executive Committee 6. GDPR/Privacy issues for the Minutes 7. Election of the Executive Committee 8. Adoption of the second revision of the OM2 Standard 9. New OpenMath web site 10. OpenMath in JSON 11. OpenMath3 12. OMCD (management) Issues 13. Any Other Business (please come forward) Kohlhase: Business Meeting of the OpenMath Society 2018 2 13. 8. 18, Hagenberg Annual Report on Activities (2017-2018) I Last Open Business meeting, July 2017 in Edinburgh (internal ones in Spring to keep charter happy) I OM Repositories: Moved all digital assets to http://github.com/OpenMath I OM Web Site: deployed a new web site based on GH Pages (see below) I OM CD Submission Process: based on GitHub now, I OM Standard moved to separate repository, build process renovated, automated by travis. I OM2 Standard: thorough editing, more error fixing (OM binding) I OM3 Standard Effort: not started due to OM2e2 work Kohlhase: Business Meeting of the OpenMath Society 2018 3 13. 8. 18, Hagenberg New Members? I Anybody who has attended 3 OM Workshops or worked on OM for 6 months can become a member (will be generous) I please suggest new members (self-nominations encouraged) I New members proposed by OM Executive Committee I ???? Kohlhase: Business Meeting of the OpenMath Society 2018 4 13.
    [Show full text]
  • Chapter 10 Document Object Model and Dynamic HTML
    Chapter 10 Document Object Model and Dynamic HTML The term Dynamic HTML, often abbreviated as DHTML, refers to the technique of making Web pages dynamic by client-side scripting to manipulate the document content and presen- tation. Web pages can be made more lively, dynamic, or interactive by DHTML techniques. With DHTML you can prescribe actions triggered by browser events to make the page more lively and responsive. Such actions may alter the content and appearance of any parts of the page. The changes are fast and e±cient because they are made by the browser without having to network with any servers. Typically the client-side scripting is written in Javascript which is being standardized. Chapter 9 already introduced Javascript and basic techniques for making Web pages dynamic. Contrary to what the name may suggest, DHTML is not a markup language or a software tool. It is a technique to make dynamic Web pages via client-side programming. In the past, DHTML relies on browser/vendor speci¯c features to work. Making such pages work for all browsers requires much e®ort, testing, and unnecessarily long programs. Standardization e®orts at W3C and elsewhere are making it possible to write standard- based DHTML that work for all compliant browsers. Standard-based DHTML involves three aspects: 447 448 CHAPTER 10. DOCUMENT OBJECT MODEL AND DYNAMIC HTML Figure 10.1: DOM Compliant Browser Browser Javascript DOM API XHTML Document 1. Javascript|for cross-browser scripting (Chapter 9) 2. Cascading Style Sheets (CSS)|for style and presentation control (Chapter 6) 3. Document Object Model (DOM)|for a uniform programming interface to access and manipulate the Web page as a document When these three aspects are combined, you get the ability to program changes in Web pages in reaction to user or browser generated events, and therefore to make HTML pages more dynamic.
    [Show full text]
  • How-To Guide: Copy and Adjust Skins (SAP CRM 7.0).Pdf
    How-to Guide: Copy and Adjust Skins ® SAP CRM 7.0 Target Audience System administrators Technology consultants Document version: 1.1 – December 2008 SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com © Copyright 2007 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their Some software products marketed by SAP AG and its distributors respective logos are trademarks or registered trademarks of SAP AG contain proprietary software components of other software vendors. in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their Microsoft, Windows, Outlook, and PowerPoint are registered respective companies. Data contained in this document serves trademarks of Microsoft Corporation. informational purposes only. National product specifications may vary. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, These materials are subject to change without notice. These materials xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, are provided by SAP AG and its affiliated companies ("SAP Group") Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and for informational purposes only, without representation or warranty of PowerPC are trademarks or registered trademarks of IBM Corporation.
    [Show full text]
  • Head First HTML with CSS & XHTML
    Head First HTML with CSS & XHTML Wouldn’t it be dreamy if there was an HTML book that didn’t assume you knew what elements, attributes, validation, selectors, and pseudo-classes were, all by page three? It’s probably just a fantasy... Elisabeth Freeman Eric Freeman Beijing • Cambridge • Köln • Sebastopol • Taipei • Tokyo Head First HTML with CSS and XHTML by Elisabeth Freeman and Eric Freeman Copyright © 2006 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly Media books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (safari.oreilly.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Associate Publisher: Mike Hendrickson Series Creators: Kathy Sierra, Bert Bates Series Advisors: Elisabeth Freeman, Eric Freeman Editor: Brett McLaughlin Cover Designers: Ellie Volckhausen, Karen Montgomery HTML Wranglers: Elisabeth Freeman, Eric Freeman Structure: Elisabeth Freeman Style: Eric Freeman Page Viewer: Oliver Printing History: December 2005: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. The Head First series designations, Head First HTML with CSS and XHTML, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps.
    [Show full text]
  • Generating Openmath Content Dictionaries from Wikidata
    Generating OpenMath Content Dictionaries from Wikidata Moritz Schubotz Dept. of Computer and Information Science, University of Konstanz, Box 76, 78464 Konstanz, Germany, [email protected] Abstract OpenMath content dictionaries are collections of mathematical sym- bols. Traditionally, content dictionaries are handcrafted by experts. The OpenMath specification requires a name and a textual description in English for each symbol in a dictionary. In our recently published MathML benchmark (MathMLBen), we represent mathematical for- mulae in Content MathML referring to Wikidata as the knowledge base for the grounding of the semantics. Based on this benchmark, we present an OpenMath content dictionary, which we generated auto- matically from Wikidata. Our Wikidata content dictionary consists of 330 entries. We used the 280 entries of the benchmark MathMLBen, as well as 50 entries that correspond to already existing items in the official OpenMath content dictionary entries. To create these items, we proposed the Wikidata property P5610. With this property, everyone can link OpenMath symbols and Wikidata items. By linking Wikidata and OpenMath data, the multilingual community maintained textual descriptions, references to Wikipedia articles, external links to other knowledge bases (such as the Wolfram Functions Site) are connected to the expert crafted OpenMath content dictionaries. Ultimately, these connections form a new content dictionary base. This provides multi- lingual background information for symbols in MathML formulae. 1 Introduction and Prior Works Traditionally, mathematical formulae occur in a textual or situational context. Human readers infer the meaning of formulae from their layout and the context. An essential task in mathematical information retrieval (MathIR) is to mimic parts of this process to automate MathIR tasks.
    [Show full text]
  • Semi-Automated Correction Tools for Mathematics-Based Exercises in MOOC Environments
    International Journal of Artificial Intelligence and Interactive Multimedia, Vol. 3, Nº 3 Semi-Automated Correction Tools for Mathematics-Based Exercises in MOOC Environments Alberto Corbí and Daniel Burgos Universidad Internacional de La Rioja the accuracy of the result but also in the correctness of the Abstract — Massive Open Online Courses (MOOCs) allow the resolution process, which might turn out to be as important as participation of hundreds of students who are interested in a –or sometimes even more important than– the final outcome wide range of areas. Given the huge attainable enrollment rate, it itself. Corrections performed by a human (a teacher/assistant) is almost impossible to suggest complex homework to students and have it carefully corrected and reviewed by a tutor or can also add value to the teacher’s view on how his/her assistant professor. In this paper, we present a software students learn and progress. The teacher’s feedback on a framework that aims at assisting teachers in MOOCs during correction sheet always entails a unique opportunity to correction tasks related to exercises in mathematics and topics improve the learner’s knowledge and build a more robust with some degree of mathematical content. In this spirit, our awareness on the matter they are currently working on. proposal might suit not only maths, but also physics and Exercises in physics deepen this reviewing philosophy and technical subjects. As a test experience, we apply it to 300+ physics homework bulletins from 80+ students. Results show our student-teacher interaction. Keeping an organized and solution can prove very useful in guiding assistant teachers coherent resolution flow is as relevant to the understanding of during correction shifts and is able to mitigate the time devoted the underlying physical phenomena as the final output itself.
    [Show full text]