Mathematical Markup Language (Mathml) Version 2.0

Total Page:16

File Type:pdf, Size:1020Kb

Mathematical Markup Language (Mathml) Version 2.0 Mathematical Markup Language (MathML) Version 2.0 W3C Working Draft 28 March 2000 This version: http://www.w3.org/TR/2000/WD-MathML2-20000328 Also available as: HTML zip archive, XHTML zip archive, XML zip archive, PDF (screen), PDF (paper) Latest version: http://www.w3.org/TR/MathML2 Previous versions: http://www.w3.org/TR/2000/WD-MathML2-20000211 http://www.w3.org/TR/1999/WD-MathML2-19991222 http://www.w3.org/TR/1999/WD-MathML2-19991201 Editors: Nico Poppelier (Penta Scope) Robert Miner (Geometry Technologies, Inc.) Patrick Ion (Mathematical Reviews, American Mathematical Society) David Carlisle (NAG) Principal Writers: Ron Ausbrooks, Stephen Buswell, Stéphane Dalmas, Stan Devitt, Angel Diaz, Roger Hunter, Bruce Smith, Neil Soiffer, Robert Sutor, Stephen Watt R Copyright c 1998-2000 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 de- scribing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathe- matics to be served, received, and processed on the World Wide 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 philos- ophy underlying the solutions MathML proposes. MathML can be used to encode both mathematical notation and mathematical content. About thirty of the MathML tags describe abstract notational structures, while another one hun- dred 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 characters and their relation to fonts. While MathML is human-readable, it is anticipated that, in all but the simplest cases, that 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 is the Last Call Working Draft of the MathML 2.0 specification prepared by the W3C Math Working Group. The Last Call review period ends 30 April 2000. The Math Working Group decided to proceed to Last Call with this draft at its recent Ann Arbor face-to-face meeting (minutes message). This is a W3C Working Draft for review by W3C members and other interested parties. It is a draft document and may be updated, replaced or made obsolete by other documents at any time. It is inappropriate to use W3C working drafts as reference material or to cite them as other than ‘work in progress’. This is work in progress and does not imply endorsement by, or the consensus of, either W3C or participants in the Math Working Group. This document has been produced by the W3C Math Working Group. A list of current W3C Technical Reports can be found at http://www.w3.org/TR. This document has been produced as part of the activity of the W3C User Interface Domain. The goals of the W3C Math Working Group are discussed in the W3C Math WG Charter (revised February 2000 from original of 11 June 1998). A list of participants in the W3C Math Working Group is available. The present draft is a revision of the earlier corrected W3C Recommendation MathML 1.01. It differs from it in that all chapters have been updated and two added. Chapters 1 and 2, which are introductory material have been revised to reflect the changes elsewhere in the document, and in the rapidly eveolving Web context. Chapters 3 and 4 have been extended to describe new functionalities added, as well as smaller improvements of material already proposed. Chapter 5 has been newly written to reflect changes in the technology available. The major tables in Chapter 6 have been regenerated to reflect an improved list of Unicode characters useful for mathematics, and the text revised to reflect the new preferred form for accessing them. Chapter 7 has been completely revised for Web technology has changed. A new chapter 8 on the DOM for MathML has been added; the latter points to a new appendix E for a detailed listing. The appendices have been reorganized into normative and non-normative groups. Appendices E and H are completely new. Comments on this document should be sent to the public mailing list of the Math Working Group. 2 Contents 1 Introduction 7 1.1 Mathematics and its Notation 7 1.2 Origins and Goals 8 1.2.1 The History of MathML 8 1.2.2 Acknowledgments 8 1.2.3 Limitations of HTML 9 1.2.4 Requirements for Mathematics Markup 9 1.2.5 Design Goals of MathML 10 1.3 The Role of MathML on the Web 11 1.3.1 Layered Design of Mathematical Web Services 11 1.3.2 Relation to Other Web Technology 12 2 MathML Fundamentals 15 2.1 MathML Overview 15 2.1.1 Taxonomy of MathML Elements 15 2.1.2 Presentation Markup 17 2.1.3 Content Markup 18 2.1.4 Mixing Presentation and Content 18 2.2 Some MathML Examples 19 2.2.1 Presentation Examples 19 2.2.2 Content Examples 21 2.2.3 Mixed Markup Examples 23 2.3 MathML Syntax and Grammar 25 2.3.1 MathML Syntax and Grammar 25 2.3.2 An XML Syntax Primer 25 2.3.3 Children versus Arguments 26 2.3.4 MathML Attribute Values 26 2.3.5 Attributes Shared by all MathML Elements 31 2.3.6 Collapsing Whitespace in Input 32 3 Presentation Markup 34 3.1 Introduction 34 3.1.1 What Presentation Elements Represent 34 3.1.2 Terminology Used In This Chapter 35 3.1.3 Required Arguments 36 3.1.4 Elements with Special Behaviors 37 3.1.5 Summary of Presentation Elements 38 3.2 Token Elements 39 3.2.1 Attributes common to token elements 39 3.2.2 Identifier (mi) 40 3.2.3 Number (mn) 42 3.2.4 Operator, Fence, Separator or Accent (mo) 43 3 3.2.5 Text (mtext) 52 3.2.6 Space (mspace) 54 3.2.7 String Literal (ms) 55 3.2.8 Referring to non-ASCII characters (mchar) 56 3.2.9 Adding new character glyphs to MathML (mglyph) 56 3.3 General Layout Schemata 58 3.3.1 Horizontally Group Sub-Expressions (mrow) 58 3.3.2 Fractions (mfrac) 60 3.3.3 Radicals (msqrt, mroot) 62 3.3.4 Style Change (mstyle) 63 3.3.5 Error Message (merror) 67 3.3.6 Adjust Space Around Content (mpadded) 68 3.3.7 Making Content Invisible (mphantom) 72 3.3.8 Content Inside Pair of Fences (mfenced) 74 3.3.9 Enclose Content Inside Notation (menclose) 77 3.4 Script and Limit Schemata 78 3.4.1 Subscript (msub) 79 3.4.2 Superscript (msup) 79 3.4.3 Subscript-superscript Pair (msubsup) 80 3.4.4 Underscript (munder) 81 3.4.5 Overscript (mover) 82 3.4.6 Underscript-overscript Pair (munderover) 83 3.4.7 Prescripts and Tensor Indices (mmultiscripts) 85 3.5 Tables and Matrices 86 3.5.1 Table or Matrix (mtable) 86 3.5.2 Row in Table or Matrix (mtr) 89 3.5.3 Labeled Row in Table or Matrix (mlabeledtr) 90 3.5.4 Entry in Table or Matrix (mtd) 91 3.5.5 Alignment Markers 92 3.6 Enlivening Expressions 100 3.6.1 Bind Action to Sub-Expression (maction) 100 4 Content Markup 102 4.1 Introduction 102 4.1.1 The Intent of Content Markup 102 4.1.2 The Scope of Content Markup 102 4.1.3 Basic Concepts of Content Markup 103 4.2 Content Element Usage Guide 104 4.2.1 Overview of Syntax and Usage 104 4.2.2 Containers 113 4.2.3 Functions, Operators and Qualifiers 117 4.2.4 Relations 121 4.2.5 Conditions 122 4.2.6 Syntax and Semantics 123 4.2.7 Semantic Mappings 125 4.2.8 Constants and Symbols 125 4.2.9 MathML element types 125 4.3 Content Element Attributes 126 4.3.1 Content Element Attribute Values 126 4.3.2 Attributes Modifying Content Markup Semantics 126 4 4.3.3 Attributes Modifying Content Markup Rendering 128 4.4 The Content Markup Elements 129 4.4.1 Token Elements 133 4.4.2 Basic Content Elements 136 4.4.3 Arithmetic, Algebra and Logic 145 4.4.4 Relations 160 4.4.5 Calculus and Vector Calculus 164 4.4.6 Theory of Sets 173 4.4.7 Sequences and Series 179 4.4.8 Elementary classical functions 183 4.4.9 Statistics 185 4.4.10 Linear Algebra 188 4.4.11 Semantic Mapping Elements 193 4.4.12 Constant and Symbol Elements 195 5 Combining Presentation and Content Markup 202 5.1 Why Two Different Kinds of Markup? 202 5.2 Mixed Markup 203 5.2.1 Reasons to Mix Markup 203 5.2.2 Combinations that are prohibited 205 5.2.3 Presentation Markup Contained in Content Markup 206 5.2.4 Content Markup Contained in Presentation Markup 206 5.3 Parallel Markup 207 5.3.1 Top-level Parallel Markup 207 5.3.2 Fine-grained Parallel Markup 208 5.3.3 Parallel Markup via Cross-References: id and xref 209 5.3.4 Annotation Cross-References using XLink: id and href 210 5.4 Tools, Style Sheets and Macros for Combined Markup 211 5.4.1 Notational Style Sheets 212 5.4.2 Content-Faithful Transformations 213 5.4.3 Style Sheets for Extensions 214 6 Characters, Entities and Fonts 216 6.1 Introduction 216 6.1.1 The Intent of Character Names 216 6.1.2 The STIX Project 216 6.1.3 Character Listings 217 6.1.4 Non-Marking Characters 217 6.1.5 Printing Character Symbol Listings 218 6.1.6 Special Constants 218 6.1.7 Alphabetical Lists 219 6.1.8 ISO Character Set Groupings 219 7 The MathML Interface 221 7.1
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]
  • 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]
  • PDF Brochure
    STAFF SPONSORS *John Toole Executive Director and CEO William B. Pickett, Co-Founder, Historian Dennis Paustenbach, President and CEO, ChemRisk CommerceNet The Computer History Museum Dr. Pickett is a senior professor of history at Rose-Hulman Kirkland and Ellis *Dennis Paustenbach Institute of Technology. He has been a Fulbright professor in Christian Taylor President and CEO, ChemRisk Japan and is the author of numerous books and articles on Rose-Hulman Ventures *Donald Kennedy American political and diplomatic history and the history of Editor in Chief, Science technology. He has taught courses about the historical WEB HISTORY CENTER FOUNDING MEMBERS President Emeritus, Stanford University impact of the Web, and in 2004 he initiated and was co-chair Institutions *David Kirsch of a conference called “The World Wide Web at Ten: The • Center for History and New Media, Director, Dotcom Digital Archive Dream and the Reality” commemorating the 10th George Mason University University of Maryland anniversary of the commercial Web. • CommerceNet • The Computer History Museum *Dave Raggett Marc Weber, Co-Founder, • Digibarn Web Pioneer—HTML Architect Collections and Communications Specialist • International World Wide Web Conference Committee *Christian Taylor Mr. Weber is an award-winning journalist and technology • The Internet Archive Legal and IP Expert writer, and co-founder of Arcady Press. He was the first person • Rose-Hulman Institute of Technology Kirkland and Ellis to research the Web's origins as a historical topic, starting in • Stanford University Libraries *Rob Kusel 1995. He co-founded the World Wide Web History Project in History of Science and Technology Collections Fundraising Advisor • University of Maryland Essex Drake 1996 with the assistance of Sir Tim Berners-Lee and many Dot-Com Archive and Business Plan Archive other Web pioneers.
    [Show full text]
  • Web 2D Graphics: State-Of-The-Art
    Web 2D Graphics: State-of-the-Art © David Duce, Ivan Herman, Bob Hopgood 2001 Contents l 1. Introduction ¡ 1.1 Images on the Web ¡ 1.2 Supported Image Formats ¡ 1.3 Images are not Computer Graphics l 2. Early Vector Graphics on the Web ¡ 2.1 CGM ¡ 2.2 CGM on the Web ¡ 2.3 WebCGM Profile ¡ 2.4 WebCGM Viewers l 3. SVG: an Introduction ¡ 3.1 Arrival of XML ¡ 3.2 Submissions to W3C ¡ 3.3 SVG: an XML Application ¡ 3.4 An introduction to SVG ¡ 3.5 Coordinate Systems ¡ 3.6 Path Expressions ¡ 3.7 Other Drawing Elements l 4. Rendering the SVG Drawing ¡ 4.1 Visual Aspects ¡ 4.2 Text ¡ 4.3 Styling l 5. Filter Effects l 6. Animation ¡ 6.1 Introduction ¡ 6.2 What is Animated ¡ 6.3 How the Animation Takes Place ¡ 6.4 When the Animation Take Place l 7. Scripting and the DOM l 8. Current State and the Future ¡ 8.1 Implementations ¡ 8.2 Metadata ¡ 8.3 Extensions to SVG l A. Filter Primitives in SVG l References -- 1 -- © David Duce, Ivan Herman, Bob Hopgood 2001 1. Introduction l 1.1 Images on the Web l 1.2 Supported Image Formats l 1.3 Images are not Computer Graphics 1.1 Images on the Web The early browsers for the Web were predominantly aimed at retrieval of textual information. Tim Berners-Lee's original browser for the NeXT computer did allow images to be viewed but they popped up in a separate window and were not an integral part of the Web page.
    [Show full text]
  • Dual Presentation with Math Using GELLMU
    Dual Presentation with Math Using GELLMU TEX Users Group (TUG) in San Diego William F. Hammond Dept. of Mathematics & Statistics University at Albany Albany, New York 12222 (USA) http://www.albany.edu/~hammond/ July, 2007 1 The Idea PDF LATEX- like source XHTML + MathML 2 Example The following identity may be regarded as a formulation of the Weierstrass product for the Gamma function. ∞ ∞ 1 x Z dt 1 Y 1 + txe−t = k t x 1 + x 0 k=1 k Understanding the derivation of this identity is reasonable for a bright stu- dent of first year undergraduate calculus in the United States. These are XHTML + MathML slides! 3 Computation of a Continued Fraction √ 1 10 = 3 + √ 1 10−3 1 = 3 + √ 10 + 3 1 = 3 + 1 6 + √ 1 10−3 1 = 3 + 6 + √ 1 10+3 1 = 3 + 1 6 + 1 6+ ... 4 Finding the tangent at a point Curve: y2 = x3 − 7x + 10 Point: B = (1, −2) Use implicit differentiation to find the slope: 2yy0 = 3x2 − 7 Evaluate when (x, y) = (1, −2): y0 = 1 The tangent line at (1, −2) is parallel to any vector with slope 1, e.g., V = (1, 1). Parametric equation: p(t) = B + tV = (1, −2) + t(1, 1) = (1 + t, −2 + t) 2 5 Mozilla MathML Torture Test 13 v u v u u v s u u u r u u u q √ t1 + t1 + t1 + 1 + 1 + 1 + 1 + x 6 Mozilla MathML Torture Test 24 c0 c1 c2 . cn c1 c2 c3 . cn+1 c2 c3 c4 . cn+2 det > 0 .
    [Show full text]
  • Reflections on the REST Architectural Style and “Principled Design of the Modern Web Architecture”
    Reflections on the REST Architectural Style and “Principled Design of the Modern Web Architecture” Roy T. Fielding Adobe Richard N. Taylor University of California, Irvine Justin R. Erenkrantz Bloomberg Michael M. Gorlick University of California, Irvine Jim Whitehead University of California, Santa Cruz Rohit Khare Google Peyman Oreizy Dynamic Variable LLC Outline 1. The Story of REST § Early history of the Web § What REST is (and is not) § Contemporary influences 2. Work inspired by REST § Decentralization § Generalization § Secure computation 3. Reflections on REST § Investing in entrepreneurial students § Role of Software Engineering research ESEC/FSE’17, September 8, 2017, Paderborn, Germany 2 Original proposal for the World Wide Web IBM Computer GroupTalk conferencing Hyper for example Card uucp News ENQUIRE VAX/ NOTES Hierarchical systems for example for example unifies A Proposal Linked "Mesh" CERNDOC information describes describes includes includes C.E.R.N This describes document division "Hypertext" refers group group includes describes to wrote section Hypermedia etc Tim Comms Berners-Lee ACM [Berners-Lee, 1989] ESEC/FSE’17, September 8, 2017, Paderborn, Germany 3 The Web is an application integration system IBM Computer GroupTalk conferencing Hyper for example Card uucp News ENQUIRE VAX/ NOTES Hierarchical systems for example for example unifies A Proposal Linked "Mesh" CERNDOC information describes [Berners-Lee, 1989] ESEC/FSE’17, September 8, 2017, Paderborn, Germany 4 describes includes includes C.E.R.N This describes document
    [Show full text]
  • HTML 4.0 Specification
    HTML 4.0 Specification REC-html40-19980424 HTML 4.0 Specification W3C Recommendation, revised on 24-Apr-1998 This version: http://www.w3.org/TR/1998/REC-html40-19980424 Latest version: http://www.w3.org/TR/REC-html40 Previous version: http://www.w3.org/TR/REC-html40-971218 Editors: Dave Raggett <[email protected]> Arnaud Le Hors <[email protected]> Ian Jacobs <[email protected]> Abstract This specification defines the HyperText Markup Language (HTML), version 4.0, the publishing language of the World Wide Web. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML, HTML 4.0 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4.0 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide. HTML 4.0 is an SGML application conforming to International Standard ISO 8879 -- Standard Generalized Markup Language [ISO8879] [p.327] . 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. W3C recommends that user agents and authors (and in particular, authoring tools) produce HTML 4.0 documents rather than HTML 3.2 documents (see [HTML32] [p.329] ).
    [Show full text]
  • Chapter 7: HTML/XHTML I
    7. HTML and XHTML | Hypertext Markup Language, Part I 7-1 Chapter 7: HTML/XHTML I References: • Erik Wilde: World Wide Web | Technische Grundlagen. Springer, 1999, ISBN 3-540-64700-7, 641 Seiten. • Eric Ladd, Jim O'Donnell, et al.: Using HTML 4, XML, and Java 1.2, Platinum Edition. QUE, 1999, ISBN 0-7897-1759-X, 1282 pages. • Rainer Klute: Das World Wide Web. Addison-Wesley, 1996, ISBN: 389319763X. • Dave Raggett, W3C: HTML 3.2 Reference Specification. [http://www.w3.org/TR/REC-html32.html] • Dave Raggett, Arnaud Le Hors, Ian Jacobs (Eds.): HTML 4.01 Specification. W3C, Dec 24, 1999. [http://www.w3.org/TR/html4/] • User's Guide to ISO/IEC 15445:2000 HyperText Markup Language (HTML) [http://www.cs.tcd.ie/15445/UG.html] • XHTML [tm] 1.0: The Extensible HyperText Markup Language. W3C, Jan 26, 2000. [http://www.w3.org/TR/xhtml1] • Stefan M¨unz:HTML-Dateien selbst erstellen | SELFHTML. [http://www.netzwelt.com/selfhtml/] [http://www.teamone.de/selfaktuell/] • Ian Graham: Introduction to HTML. [http://www.utoronto.ca/webdocs/HTMLdocs/NewHTML/htmlindex.html] • NCSA Beginner's Guide to HTML (no longer maintained). [http://www.ncsa.uiuc.edu/General/Internet/WWW/] Stefan Brass: Grundlagen des World Wide Web Universit¨atHalle, 2016 7. HTML and XHTML | Hypertext Markup Language, Part I 7-2 Objectives After completing this chapter, you should be able to: • develop web pages in strict HTML 4.0/XHTML 1.0. • write syntactically correct HTML/XHTML. • read the HTML and XHTML specifications. • evaluate whether something is possible in HTML. • write a short paragraph about differences between HTML versions.
    [Show full text]
  • Server Program Analysis Based on HTTP Protocol Min CHE1 Ming Fu TUO1 1College of Science, Air Force Engineering University 710051 Xi’An, China
    MATEC Web of Conferences 63, 05023 (2016) DOI: 10.1051/matecconf/20166305023 MMME 2016 Server Program Analysis Based on HTTP Protocol Min CHE1 Ming Fu TUO1 1College of Science, Air Force Engineering University 710051 Xi’an, China Abstract—The overwhelming majority of Web developments are built based on Web application of HTTP protocol. To analyze the server program based on the HTTP protocol and the process of interaction between the browser and server, a simple HTTP-based server program is taken as an example to describe how to use the theories of multi- threading and asynchronous operationˈand the core section of HTTP-based server program is gradually resolved with Winsock programming. This method can achieve the purpose to avoid blocking the calling threadˈand improve the responsiveness of a server program. Keywords- HTTP; HTTP protocol; Server; WinSock 1 INTRODUCTION 2.2. HTTP response consists of three components namely the status line,message header,and response body . Hypertext Transfer Protocol (HTTP) is the protocol of web’s application layer. It is the web's core issue. HTTP can be The format of status line is: HTTP-Version Status-Code Rea- realized in the web client’s program or server’s program. The son-Phrase CRLF. HTTP-Version indicates the version of programs running on different end systems of client and server HTTP protocol used in web server; Status-Code indicates the can exchange with each other through exchanging HTTP status code of a response sent back from web server; Reason- message. Web Page is also called document composed of Phrase indicates the text description of status code.
    [Show full text]
  • High Level Interoperability Testing for the Web of Things
    High Level Interoperability Testing For the Web of Things Dave Raggett <[email protected]> F-Interop is an international project supported by the European Union’s Horizon 2020 programme under Grant Agreement number: 687884 Testing and the Web of Things Two talks: • Dave Raggett on high level interoperability testing • W3C staff activity lead for Data and a champion for Web of Things • Long history of work on web standards (HTML, HTTP, …) • Ege Korkan on testing things exposed by particular devices 2 This work has been supported by F-Interop 3 F-Interop, see www.f-interop.eu • European project supported by the European Commission and the Swiss Government with the following partners • Sorbonne Université, Mandat International, ETSI, imec, EANTC, Digital Catapult, Université du Luxembourg, INRIA, UDG and W3C/ERCIM • Interoperability testing at the protocol level, e.g. HTTP, CoAP • Using AMQP for test control messaging • And a VPN for intercepting packets • Available as Docker images for easy installation • W3C/ERCIM has added support for high level testing for the Web of Things • Moving beyond protocol level testing to ensure application interoperability Horizon 2020 Swiss State European Union Secretariat for Funding for Research Education, Research 4 and Innovation and Innovation The Web of Things 5 The Web of Things • The IoT is fragmented • Lots of incompatible technologies, protocols and standards • This is holding back the potential by increasing costs and risks • Web of Things as a simplifying abstraction layer • Software objects with properties,
    [Show full text]