DOCSLIB.ORG

Mobile Web Standards

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mobile Web Standards MOBILE WEB STANDARDS Mobile Systems Seminar Talk 7 Francesco Luminati Introduction • The “mobile world” is a booming market • Need of Internet everywhere • Need of same services on every devices • Standards intended to help Developers • Which are the mobile standards • What is the real situation on the web Structure • Organizations • Early standards • Present standards • Future Trends • Browsers • Top1000 research • Conclusion Organizations • Open Mobile Alliance (OMA) • Standards for mobile phone industry • Several important members like Sony-Ericsson, Motorola, Samsung • Union in 2002 • Wireless Access Protocol (WAP) Standard • World Wide Web Consortium (W3C) • Most important web standards organization • HTML 4, XHTML 1, HTML 5, XHTML Basic • Mobile Web Initiative • Improve the mobile web experience • Best Practices Early standards • Situation: • 2G networks, GSM • Constricted hardware • GPRS after 2000 • Wireless Application Protocol (WAP 1.0) • WAP Forum (now OMA) • Set of proprietary standards • Markup language and transport protocols • Wireless Markup Language (WML) • XML based language • Between Internet and the devices there is a WAP Gateway • XHTML Basic 1.0 • W3C • Intended to support most limited devices • Restrictive XHTML with images and basic tables support • No script and frames Present standards • Situation • 3G networks, UMTS • 2G networks still diffused in remote regions • Smartphones • Wireless Application Protocol 2.0 • Redesigned by OMA • TCP/IP and HTTP • XHTML-MP for markup Content standards • XHTML Mobile Profile • Extends XHTML Basic with elements in forms, legacy and presentation and add support to internal style sheets • V. 1.1 support to scripting and events • V. 1.2 full support to form and file upload • XHTML Basic 1.1 • Full support to XHTML forms, presentation, events and style elements • Coordination between W3C and OMA • Very similar standards • Both standards compatible with every XHTML browsers Presentation and multimedia standards • Cascading Style Sheet (CSS) • Wireless CSS in WAP 2.0 (WCSS) • Subset of CSS 2, provide base functionality for mobile devices • CSS Mobile Profile by W3C (CSS-MP) • Similar to WCSS, adds optional set for advanced browsers • If optional set implemented, very similar to CSS 2.1 • Scalable Vector Graphic (SVG) • XML document to describe vector graphics • High scalability • SVG Tiny and Basic • Synchronized Multimedia Integration Language (SMIL) • XML based language to describe animations, timing, visual transitions, … • Multimedia Messaging Service (MMS) Mobile Web Best Practices • Defined by the Mobile Web Initiative (W3C) in 2008 • Set of recommendations finalized to improve the user experience • Give advice about navigation and links, design, layout, content, technical issues and user input • Not concentrated just on technical problems, but also non technical like the delivered content Future trends • “One Web” • Reach the same functionality and content everywhere on every devices • Need of a flexible standard • Web 2.0 from JavaScript to HTML 5 • Now tons of JavaScript code • Future HTML 5 markup • Natively browser-side support Future trends • Web versus App • Fusion of the browser with online and offline application • Chrome OS • HTML 5 • Better layout structure • Offline support • Web application work without connectivity • Natively support of many functionality, like video and audio • HTML 5 as the new “One Web” standard? Browsers • ACID3 test: • Standards compliance test • 100 subtests on various web standards and technology • HTML, XHTML, CSS, JavaScript, … ACID3 results on mobile ACID3 results on desktop browsers browsers 100 100 90 90 80 80 70 70 60 60 50 50 Tests Tests 40 Tests 40 30 30 20 20 10 10 0 Android 2.3 iPhone IE Mobile 7 Firefox Opera Mini 0 Safari 4.3 Mobile 4 Safari 5 Chrome 10 IE 9 Firefox 4 IE 8 IE 6 Mobile browsers Desktop browsers Top1000 research • Top 1000 webpages from alexa.com • 4 User Agents: • Android 2.2 default browser • iPhone 4 Safari browser • Nokia 6600 default browser • Firefox 4 desktop browser • Purpose and motivation of the test: • Evaluate the situation on the web • Check if standards are used and correctly applied • Check if best practices are applied and still actual Standards declared • Markup standards • Retrieved from the “Doctype” declaration (e.g. HTML5: <!DOCTYPE HTML>) Overwiev Mobile vs Desktop standards 900 800 700 600 500 Mobile Standards Pages 400 Desktop Standards Not declared 300 200 100 0 Android UA Iphone UA Nokia UA Firefox UA User Agent Standards declared • Markup standards • Retrieved from the “Doctype” declaration (e.g. HTML5: <!DOCTYPE HTML>) Mobile standards Nokia UA XHTML Mobile 1.0 Iphone UA XHTML Mobile 1.1 XHTML Mobile 1.2 User Agents User XHTML Basic 1.0 XHTML Basic 1.1 Android UA 0 50 100 150 200 250 Pages Standards declared • Markup standards • Retrieved from the “Doctype” declaration (e.g. HTML5: <!DOCTYPE HTML>) Desktop standards Firefox UA Nokia UA HTML 4 HTML 4.01 XHTML 1.0 User Agent User XHTML 1.1 Iphone UA HTML 5 Others Android UA 0 100 200 300 400 500 600 700 800 900 Pages Markup validation • Validator tool of W3C (http://validator.w3.org) • Check a webpage against the grammar it declare to use to find errors • No HTML5 validation Validation errors Firefox UA Nokia UA 0 errors less than 20 errors User Agent User between 20 - 100 errors Iphone UA more than 100 errors Android UA 0 100 200 300 400 500 600 700 Pages Browsers • ACID3 test: • Standards compliance test • 100 subtests on various web standards and technology • HTML, XHTML, CSS, JavaScript, … ACID3 results on mobile ACID3 results on desktop browsers browsers 100 100 90 90 80 80 70 70 60 60 50 50 Tests Tests 40 Tests 40 30 30 20 20 10 10 0 Android 2.3 iPhone IE Mobile 7 Firefox Opera Mini 0 Safari 4.3 Mobile 4 Safari 5 Chrome 10 IE 9 Firefox 4 IE 8 IE 6 Mobile browsers Desktop browsers Webpages size • Total size with external objects (images, scripts, css,…) • Best Practices limit to 20 Kbyte Total size Firefox UA Nokia UA less or equal 20 Kbyte between 20 - 100 Kbyte User Agent User Iphone UA more than 100 Kbyte Android UA 0 100 200 300 400 500 600 700 800 900 1000 Pages Webpages size • Markup size without external objects • Best Practices limit to 10 Kbyte Markup size Firefox UA Nokia UA less or equal 10 Kbyte between 10 - 20 Kbyte User Agent User Iphone UA more than 20 Kbyte Android UA 0 100 200 300 400 500 600 700 800 900 1000 Pages Objects on Webpages • External images, css, javascript, flash, text files • Included in a page with HTML tags, like “img”, “script”, “object” Pages with at least one object 100.00% 90.00% 80.00% 70.00% 60.00% Android UA 50.00% Iphone UA 40.00% Nokia UA Percentof pages Firefox UA 30.00% 20.00% 10.00% 0.00% Images CSS JavaScript Flash Text files Others Object type Objects on Webpages • External images, css, javascript, flash, text files • Included in a page with HTML tags, like “img”, “script”, “object” Average number of ojects per page Firefox UA Nokia UA Images CSS JavaScript User Agent User Iphone UA Flash Text files Android UA 0 10 20 30 40 50 60 70 Objects Objects on Webpages • Images formats/standards Images standards Firefox UA Nokia UA JPEG GIF User Agent User PNG Iphone UA Icon Android UA 0 5000 10000 15000 20000 25000 30000 35000 40000 Images Objects on Webpages • Objects compared with the Markup Average object size 70 60 50 40 Android UA Iphone UA Kbytes 30 Nokia UA Firefox UA 20 10 0 Images CSS JavaScript Flash Text files Markup Object Conclusion • Mobile web standards are a good try, but didn’t achieve a good diffusion • Evolution in hardware was so fast, that they are maybe not necessarily anymore • Effort should be in evolving one universal standard and 100% compatible browsers • Fusion between web and app is around the corner Questions? Question 1 • Do you see the need of intervention about standards and best practices viewing this results? • The web itself should be more conscious of mobile devices? Question 2 • Is a mobile web standard a necessity today? • If yes which kind of standards, still presentation and content or new one for new problems? Question 3 • What do you mean about one universal standard, is it good, is it possible? Question 4 • What do you think about the browser-based operating systems for mobile devices? • Is there no dangers in being always connected? .
Load more

Recommended publications
  • Browser Wars
    Uppsala universitet Inst. för informationsvetenskap Browser Wars Kampen om webbläsarmarknaden Andreas Högström, Emil Pettersson Kurs: Examensarbete Nivå: C Termin: VT-10 Datum: 2010-06-07 Handledare: Anneli Edman "Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of read- ing a document written on another computer, another word processor, or another network" - Sir Timothy John Berners-Lee, grundare av World Wide Web Consortium, Technology Review juli 1996 Innehållsförteckning Abstract ...................................................................................................................................... 1 Sammanfattning ......................................................................................................................... 2 1 Inledning .................................................................................................................................. 3 1.1 Bakgrund .............................................................................................................................. 3 1.2 Syfte ..................................................................................................................................... 3 1.3 Frågeställningar .................................................................................................................... 3 1.4 Avgränsningar .....................................................................................................................
    [Show full text]
  • Using Replicated Execution for a More Secure and Reliable Web Browser
    Using Replicated Execution for a More Secure and Reliable Web Browser Hui Xue Nathan Dautenhahn Samuel T. King University of Illinois at Urbana Champaign huixue2, dautenh1, kingst @uiuc.edu { } Abstract Unfortunately, hackers actively exploit these vulnerabil- ities as indicated in reports from the University of Wash- Modern web browsers are complex. They provide a ington [46], Microsoft [61], and Google [49, 48]. high-performance and rich computational environment Both industry and academia have improved the se- for web-based applications, but they are prone to nu- curity and reliability of web browsers. Current com- merous types of security vulnerabilities that attackers modity browsers make large strides towards improving actively exploit. However, because major browser plat- the security and reliability of plugins by using sandbox- forms differ in their implementations they rarely exhibit ing techniques to isolate plugins from the rest of the the same vulnerabilities. browser [62, 33]. However, these browsers still scatter In this paper we present Cocktail, a system that uses security logic throughout millions of lines of code, leav- three different off-the-shelf web browsers in parallel to ing these systems susceptible to browser-based attacks. provide replicated execution for withstanding browser- Current research efforts, like Tahoma [32], the OP web based attacks and improving browser reliability. Cock- browser [36], the Gazelle web browser [59], and the Illi- tail mirrors inputs to each replica and votes on browser nois Browser Operating System [58] all propose build- states and outputs to detect potential attacks, while con- ing new web browsers to improve security. Although tinuing to run.
    [Show full text]
  • Sample XHTML Code
    Sample XHTML Code Docs version: 2.0 Version date 7/29/2009 Contents • Introduction • Home page • General page structure • Tabbed content • Navigation lists • iPhone action links Introduction These code samples illustrate how we designed and developed the user for the MIT Mobile Web. These code samples are taken from the original XHTML design mockups which were the basis of the final implementation of the live MIT Mobile Web. We’re presenting these design mockups here because showing the final functional code with its back-end integration would make it harder to read the actual markup as the web browser sees it – which is what determines what the end user actually sees and interacts with. The XHTML and CSS generated by the functional code is in any case very close to these original design mockups. We’re not presenting every page for every module here. Rather, we’re showing representative pages that illustrate user-interface patterns that appear throughout the MIT Mobile Web. After studying these code snippets and the patterns they represent, you should be able to easily understand how specific pages in the MIT Mobile Web were built, as well as how to go about building new page layouts sharing a consistent basic structure, function and building blocks. For background on why we optimized the UI for three different categories of devices, please read the Introduction to the Mobile Web document. Commented source code, images and other assets for the entire MIT Mobile Web – including functional code for back-end integration – is online as a SourceForge project at http://sourceforge.net/projects/mitmobileweb/.
    [Show full text]
  • Using Property-Based Testing, Weighted Grammar-Based Generators and a Consensus Oracle to Test Browser Rendering Engines and To
    USING PROPERTY-BASED TESTING, WEIGHTED GRAMMAR-BASED GENERATORS AND A CONSENSUS ORACLE TO TEST BROWSER RENDERING ENGINES AND TO REPRODUCE MINIMIZED VERSIONS OF EXISTING TEST CASES by JOEL DAVID MARTIN Presented to the Faculty of the Graduate School of The University of Texas at Arlington in Partial Fulfillment of the Requirements for the Degree of DOCTOR OF PHILOSOPHY THE UNIVERSITY OF TEXAS AT ARLINGTON December 2019 Supervising Committee: Farhad Kamangar, Supervising Professor David Levine, Supervising Professor Manfred Huber Gergley Zaruba Copyright by Joel David Martin 2019 The copyright of Chapter2 was transferred to the IEEE as part of publication in COMPSAC 2018 (\Property-Based Testing of Browser Rendering Engines with a Consensus Oracle") [1]. Please refer to the IEEE for information about licensing the content from Chapter2. Chapter3 is a manuscript that is intended for separated publication. All copyrights on Chapter3 are currently reserved to Joel Martin. The remainder of this work, excluding Chapter2 and Chapter3, is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. ACKNOWLEDGMENTS Thank you to the members of my Supervising Committee for their support and guidance. In particular, I would like to thank David Levine who spent many long hours with me discussing the research and helping with the numerous large and small details that were necessary to complete my thesis. Many thanks to my employer, Viasat, for the financial investment toward my education. Thank you to my supervisors at Viasat, Ingolf Krueger and Markus Kaltenbach, for their support and encouragement throughout my graduate education. I would like to apologize for the harm done to numerous figurative trees during the completion of this research.
    [Show full text]
  • Internet Explorer 9 Features
    m National Institute of Information Technologies NIIT White Paper On “What is New in Internet Explorer 9” Submitted by: Md. Yusuf Hasan Student ID: S093022200027 Year: 1st Quarter: 2nd Program: M.M.S Date - 08 June 2010 Dhaka - Bangladesh Internet Explorer History Abstract: In the early 90s—the dawn of history as far as the World Wide Web is concerned—relatively few users were communicating across this Internet Explorer 9 (abbreviated as IE9) is the upcoming global network. They used an assortment of shareware and other version of the Internet Explorer web browser from software for Microsoft Windows operating system. In 1995, Microsoft Microsoft. It is currently in development, but developer hosted an Internet Strategy Day and announced its commitment to adding Internet capabilities to all its products. In fulfillment of that previews have been released. announcement, Microsoft Internet Explorer arrived as both a graphical Web browser and the name for a set of technologies. IE9 will have complete or nearly complete support for all 1995: Internet Explorer 1.0: In July 1995, Microsoft released the CSS 3 selectors, border-radius CSS 3 property, faster Windows 95 operating system, which included built-in support for JavaScript and embedded ICC v2 or v4 color profiles dial-up networking and TCP/IP (Transmission Control support via Windows Color System. IE9 will feature Protocol/Internet Protocol), key technologies for connecting to the hardware accelerated graphics rendering using Direct2D, Internet. In response to the growing public interest in the Internet, Microsoft created an add-on to the operating system called Internet hardware accelerated text rendering using Direct Write, Explorer 1.0.
    [Show full text]
  • Tr 126 907 V14.0.0 (2017-04)
    ETSI TR 126 907 V14.0.0 (2017-04) TECHNICAL REPORT Universal Mobile Telecommunications System (UMTS); LTE; HTML5 for a new presentation layer in 3GPP services (3GPP TR 26.907 version 14.0.0 Release 14) 3GPP TR 26.907 version 14.0.0 Release 14 1 ETSI TR 126 907 V14.0.0 (2017-04) Reference RTR/TSGS-0426907ve00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice The present document can be downloaded from: http://www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https://portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.
    [Show full text]
  • University of Camerino Computer Science (LM 18) Browser Evolution
    University of Camerino Computer Science (LM 18) Browser Evolution Project of Web 2.0 Autor: Luciani Alex Prof: Vaccari Carlo License This material is distributed under the Creative Commons "Attribution - NonCommercial - Share Alike - 3.0", available at http://creativecommons.org/licenses/by-nc-sa/3.0/ . What is a Browser? A browser is a software application, it retrieves and shows elements of the web. Story Prehistory 1963: Ted Nelson: Hypertext. 1987: John Bottoms: Silversmith, SGML. 1989: Tim Berners-Lee: WWW, HTML, HTTP, W3C. 1994: Mosaic → Netscape. Story Mosaic screenshot Story First Browser War (1996 - 2004) Story Second Browser War (2004 - ...) Story January 2010, Firefox passed IE Story The Actual Situation (2011) Data from statcounter.com Browser Market Share % Browser Version Market Share % Apr 11 Apr 11 IE 44.52 IE 8.0 30.24 Firefox 29.67 Firefox 3.6 18.91 Chrome 18.29 Chrome 10.0 16.03 Safari 5.04 IE 7.0 7.82 Opera 1.91 Firefox 4.0 7.59 IE 6.0 4.14 Safari 5.0 3.83 IE 9.0 2.32 Firefox 3.5 1.99 Tech Evolution Web Browser Engines They paint the web pages interpreting the client-side scripts. Layout Engine License Main Browser Gecko Free and OpenSource Firefox Presto Proprietary Opera Trident Proprietary Internet Explorer WebKit Free (GNU LGPL) Safari, Chrome Tech Evolution Protocols Connection: HTTP. Security: SSL, HTTPS Languages and Client Side HTML, HTML5 Javascript, Ajax CSS XML, SVG WebGL Tech Evolution Ajax Example Tech Evolution Google Body Browser uses WebGL Tech Evolution GUI Evolution Google 10 Firefox 3.6 Firefox 4 Tech Evolution GUI Evolution Explorer 8 Explorer 9 Tech Evolution Browser Testing Acid Test: testing client side script languages.
    [Show full text]
  • XHTML Mobile Profile Reference
    XHTML Mobile Profile Reference Version 1.0 Openwave Systems Inc. 1400 Seaport Boulevard Redwood City, CA 94063 USA http://www.openwave.com Part Number XHRF-10-004 October 2001 LEGAL NOTICE Copyright © 1994–2001, Openwave Systems Inc. Portions copyright © 1994–1999, Netscape Communications Corporation. Portions copyright © 1994–1999, Oracle Corporation. All rights reserved. These files are part of the Openwave Software Developer’s Kit (SDK). Subject to the terms and conditions of the SDK License Agreement, Openwave Systems Inc. (“Openwave”) hereby grants you a license to use the SDK software and its related documentation. OPENWAVE MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THE SDK SOFTWARE, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES THAT THE SDK SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE, OR NONINFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LICENSED SOFTWARE IS BORNE BY USER. USER UNDERSTANDS AND ACCEPTS THE SDK SOFTWARE AND ANY SOFTWARE SECURITY FEATURES INCLUDED WITH THE SDK SOFTWARE ARE PROVIDED ON AN “AS IS” BASIS FROM OPENWAVE, AND OPENWAVE DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE OF, OR THE RESULTS OF THE USE OF THE SDK SOFTWARE IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL OPENWAVE OR ITS SUPPLIERS OR DISTRIBUTORS BE LIABLE FOR ANY DAMAGES RESULTING FROM OR ARISING OUT OF USER’S USE OF THE SDK SOFTWARE, INCLUDING, WITHOUT LIMITATION, ANY DIRECT, INDIRECT, SPECIAL, INCIDENTIAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES.
    [Show full text]
  • Sprint PCS® Mobile Browser Technology Paper
    Sprint PCS® Mobile Browser Technology Paper Writing Consistent Mobile Browser Content on Sprint PCS Phones Version 1.0 July 2004 ©2004 Sprint and Metrowerks. All rights reserved. Sprint, Sprint PCS, Web, Sprint PCS Phone, Sprint PCS Vision, and the diamond logo are registered trademarks of Sprint Communications Company L. P. All other trademarks are property of their respective owners. Table of Contents Table of Contents..............................................................................................................2 1 Introduction.............................................................................................................3 1.1 Target Audience.....................................................................................................3 1.2 About this document...............................................................................................3 2 Document Conventions..........................................................................................3 3 Overview of Wireless Application Protocol (WAP) 2.0 Markup Language .............3 3.1 XHTML Basic and Mobile Profile............................................................................4 3.2 Key Differences between WML 1.x and XHTML ....................................................5 4 Overview Of Sprint WAP 2.0 Phones and Browsers..............................................7 5 Writing Consistent WAP 2.0 Applications Across Sprint PCS Phones...................8 5.1 Commonly used XHTML Mobile Profile Tags ........................................................8
    [Show full text]
  • Webkit and Blink: Open Development Powering the HTML5 Revolution
    WebKit and Blink: Open Development Powering the HTML5 Revolution Juan J. Sánchez LinuxCon 2013, New Orleans Myself, Igalia and WebKit Co-founder, member of the WebKit/Blink/Browsers team Igalia is an open source consultancy founded in 2001 Igalia is Top 5 contributor to upstream WebKit/Blink Working with many industry actors: tablets, phones, smart tv, set-top boxes, IVI and home automation. WebKit and Blink Juan J. Sánchez Outline The WebKit technology: goals, features, architecture, code structure, ports, webkit2, ongoing work The WebKit community: contributors, committers, reviewers, tools, events How to contribute to WebKit: bugfixing, features, new ports Blink: history, motivations for the fork, differences, status and impact in the WebKit community WebKit and Blink Juan J. Sánchez WebKit: The technology WebKit and Blink Juan J. Sánchez The WebKit project Web rendering engine (HTML, JavaScript, CSS...) The engine is the product Started as a fork of KHTML and KJS in 2001 Open Source since 2005 Among other things, it’s useful for: Web browsers Using web technologies for UI development WebKit and Blink Juan J. Sánchez Goals of the project Web Content Engine: HTML, CSS, JavaScript, DOM Open Source: BSD-style and LGPL licenses Compatibility: regression testing Standards Compliance Stability Performance Security Portability: desktop, mobile, embedded... Usability Hackability WebKit and Blink Juan J. Sánchez Goals of the project NON-goals: “It’s an engine, not a browser” “It’s an engineering project not a science project” “It’s not a bundle of maximally general and reusable code” “It’s not the solution to every problem” http://www.webkit.org/projects/goals.html WebKit and Blink Juan J.
    [Show full text]
  • Wap, Xhtml and Android
    WAP, XHTML AND ANDROID Jaume Barceló University Carlos III of Madrid Antonio de la Oliva Ruben cuevas Service Engineering Laboratory Ignacio soto BACK IN 1999, • Mobile and Internet communications were separate worlds • Nokia 7110, first mobile phone with a WAP browser. • WAP: Wireless Application Protocol. • Extra-simplified access to the Internet, due to terminal limitations and limited available bandwidth. SMALL LIMITATIONS, • Extremely limited bandwidth • SMS • Circuit-switching • Wait-and-pay • A substantial increase thanks to GPRS (2.5G) ~ 56kbps • Memory and processor limitations • Low resolution monochrome screen • No mouse, 15-keys keyboard WAP PROTOCOL STACK Internet Protocol Stack HTML Wireless Application Environment (WAE) JavaScript 1. Wireless Session Layer (WSP) HTTP 2. Wireless Transaction Protocol (WTP) TLS-SSL 3. Wireless Transport Layer Security (WTLS) 4. Wireless Datagram Protocol (WDP) TCP/IP UDP/IP Bearers: SMS USSD CSD CDMA IS-136 CDPD Etc.. A GW WAS REQUIRED WIRELESS APPLICATION ENVIRONMENT In WAP 1.X Wireless Markup Language (WML) Relies on a card/desk paradigm WMLScript WML EXAMPLE <?xml version="1.0"?> <!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml"> <wml> <card id="card1" title="Tutorial"> <do type="accept" label="Answer"> <go href="#card2"/> </do> <p><select name="name"> <option value="HTML">HTML Tutorial</option> <option value="XML">XML Tutorial</option> <option value="WAP">WAP Tutorial</option> </select></p> </card> <card id="card2" title="Answer"> <p>You
    [Show full text]
  • An Intruduction to HTML5
    Agenda * What is HTML5 -- Its history and motivation * HTML/XHTML as Human / Machine Readable Format * HTML and its related technologies * Brief summary of the changes * Models of HTML5 * Examples and demonstrations What is HTML5 -- Its history and motivation * W3C and HTML * Brief history of HTML * WHATWG and HTML5 * 'Working Draft' and 'Recommendation' * HTML5 as IDL -- Interface Definition via IDL What is HTML5 - W3C and HTML What is HTML5 - W3C and HTML What is HTML5 - Brief history of HTML HTML is born for 'Scientists' at CERN. First website (from archive@cern) Tim Berners Lee What is HTML5 - Brief history of HTML HTML (1989; CERN) HTML = HyperText Markup Language HTML 1.0 (1993; IETF) HTML 2.0 (1995; W3C) HTML 3.2 (1997; W3C) XML 1.0 (1998) HTML 4.0.1 (1999; W3C) XHTML 1.0 (2000) XHTML Basic 1.0 (2000) XHTML 1.1 (2001) XHTML Basic 1.1 (2008) What is HTML5 - Brief history of HTML HTML 4.0.1 (1999; W3C) XML 1.0 (1998) XHTML 1.0 (2000) XHTML 1.1 (2001) Extension to HTML4 (2003;Opera) PositionPaper (2004;Opera/Mozilla) What is HTML5 - Brief history of HTML http://www.w3.org/2004/04/webapps-cdf-ws/papers/opera.html What is HTML5 - Brief history of HTML HTML 4.0.1 (1999; W3C) XML 1.0 (1998) XHTML 1.0 (2000) XHTML 1.1 (2001) Extension to HTML4 (2003;Opera) PositionPaper (2004;Opera/Mozilla) WHATWG (2004;Opera/Mozilla/Apple) What is HTML5 - Brief history of HTML The Web Hypertext Application Technology Working Group (WHATWG) What is HTML5 - Brief history of HTML HTML 4.0.1 (1999; W3C) XML 1.0 (1998) XHTML 1.0 (2000) XHTML 1.1 (2001) Extension
    [Show full text]