DOCSLIB.ORG

Mobile and the Web 2.0: from Standards to Technical Issues

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mobile and the Web 2.0: from Standards to Technical Issues Mobile and the Web 2.0: From Standards to Technical Issues Francisco de Freitas Mobile Systems Seminar – Fall ‘09 Agenda • What is Web 2.0? • Mobile 2.0 and Web 2.0 • Mobile Web Standards • Mobile Web Best Practices • WML and XHTML MP • Comparison Between Standards • Trends and the Future of Mobile Web 2.0 • Summary • Discussion Topics What is Web 2.0? ` buzzword – meaningless marketing word, a “piece of jargon”. `(Tim Berners Lee) ` “The next generation of Web sites, applications and processes tied with the Internet.” `(The general Media) ` “It's a story about community and collaboration on a scale never seen before.” `(TIME Magazine) ` “It's the Intelligent Web! The more WE use it, the better it is.” `(Tim O'Reilly) Principles of Web 2.0 ` The Web as Platform ` Medium to share and distribute information ` Harnessing Collective Intelligence ` The read/write Web ` Data is the Next Intel Inside ` Mashups ` End of the Software Release Cycle ` Perpetual Beta / SaaS ` Lightweight Programming Models ` Re-usability - “Some rights reserved” ` Software Above the Level of a Single ` Web is not only on PCs Device ` Rich User Experiences ` GUI-Style user experiences, multimedia Web 2.0 is not AJAX or vice versa But it gives superior user experience and Web 2.0 is not a design aesthetic either! nice forms of data retrieval/creation The Machine is Us/using us ` Play video. Mobile Web Approach(es) and Web 2.0 ` The Mobile World is new: ` Mobile Web X Desktop ` Can it provide the same Web 2.0 experience? ` Limitations of the Mobile Device/Mobile World ` Device Processing Power, Maturity of Standards, Browser Compatibility, Battery capacity, Screen Size, Network Bandwidth, Network Operator Barriers ` The Mobile Web is still stagnated in the 2G era of Mobile Telecom ` “Device heterogeneity” ` The Mobile user is different (according to Google) ` “Repetitive now” (stocks, weather, news, etc) ` “Bored now” (people with time in airports, train stations, cafes, etc) ` “Urgent now” (directions to the airport, buying tickets, urgent email, etc) Challenges of Web 2.0 in Mobiles Impacts Richer User Software above Read/Write Mobile Experience the level of a Web Environment Single Device Limited x x x Functionality Different Users x x Different Mobile x x Manufacturers Mobile 2.0 != Mobile Web 2.0 ` Forget the Web! ` Mobile 2.0 is the evolution of applications that are available when you turn your phone/mobile device on ` Mobile Widgets ` Local Data Storage ` Reaction to Push Messages ` Location Awareness ` Devices are always changing… ` The form of the device is constantly changing and shifting ` More powerful and capable devices Mobile 2.0 != Mobile Web 2.0 ` What is really Mobile Web 2.0 then? ` Leap of the Mobile platform forward to where the Internet is today: ` Mobile Blogging ` Mobile Social Networks ` Mobile RSS Readers ` Location-based Services ` Adaptive Web Sites and Mashups ` Connected applications (e.g. Photo Sharing) ` Services taking advantage of Web Semantics Going towards to the Web 2.0 (the “perfect” integrated world) Mobile Web Standards ` Q: What to consider when designing Web Apps for Mobiles? ` A: Mobile Web Recommendations! ` Overall Behavior ` Device capabilities ` Navigation and Links ` Navigation Mechanisms ` Access Keys ` Refreshing, redirection, external resources Mobile Web Standards ` Page Layout and Content ` Content: scrolling, graphics, colors ` Page Size ` Page Definition ` Structural Elements ` Tables, Frames, Fonts ` Non-text Items, Image Size, Content Type ` User Input ` Forms, Labels ` Tab order Evolution of the WML and XHTML MP Web Standards ` Wireless Markup Language ` Evolution from HDML ` XML 1.0 Strict Syntax ` XHTML Mobile Profile + WML2 ` XHTML Basic + iMode (Japan) + WML 1.x + some elements and attributes from the full version of XHTML ` XHTML MP is an XML document Wireless Markup Language (WML) ` With the simplest (WAP) browser, you can: ` Check train timetables ` Check in for a flight ` Look up sports results ` Purchase tickets online ` Do your banking by mobile phone ` WAP Infrastructure: Content Server, Gateway, etc ` “New” Language: Learning effort ` Screen Resolution Size: ~128x160 and smaller (adMob statistics) [4] ` WML card/deck concept ` Not very used [2] ` Focus is on the efficiency in how tasks can be accomplished in Basic Phones ` Trade-off: More Links ` Most used standard: still a large percent of devices are only WML capable Wireless Markup Language (WML) ` Use of images ` Rely very heavily on text and basic HTML formatting (lightweight Kb page size). ` Navigation: ` WAP sites often have numeric shortcuts that trigger actions. ` Sharing Capabilities ` No file upload (browser dependent) ` Content delivery ` Constrained user interface capabilities ` No “Java scripting” ` WMLScript ` Summary for WML only devices: ` Lack of support for some multimedia types (e.g. video) ` Small screen size causes inadequate navigation ` (Possible) Solution: use applications to deliver the same experience (Google, Yahoo!) XHTML Mobile Profile ` With a XHTML browser, you can: ` everything a WAP browser can with a (somewhat) better user experience ` display media content (device dependent) ` XHTML Basic is a simplified version of XHTML devices with limited processing power and capabilities. ` No CSS, frames, and scripting ` XHTML MP supports a simplified version of CSS called WCSS / WAP CSS ` Screen Resolution Size: ~176x220 and larger (adMob statistics) ` Minimum Effort for learning the language ` Why XHTML MP? ` The WML didn't follow device evolution and so, XHTML MP was created to address some WML restrictions ` Provide new content and WML backward compatibility XHTML Mobile Profile ` Use of images ` XHTML MP sites use images much more extensively ` Navigation ` XHTML MP sites are able to have numeric shortcuts as well. (browser dependent) ` Menu features. ` Page Weight: kept low by validating the documents, creation of CSS. ` Keep link resources low (less markup) ` Sharing capabilities ` Allows file upload (it is a work around but it works) ` Content Delivery ` Richer user experiences: Font Styles, Colored Borders, Better Tables ` Support ` HTML / XHTML pages of your web site can be converted to XHTML MP documents with minor changes ` ECMAScripting MP Images and Heading in different browsers Sony Ericson Sony Ericson Nokia Sony Ericson Nokia T610 T68i Mobile T610 Mobile Browser 4.0 Browser 4.0 Differences between WML and XHTML MP WML XHTML MP Screen Resolution Size 128x160 and smaller 176x220 and larger Device browser type Micro browser Web browser (not full browser) Developing effort High Low Scripting WMLScript ECMAScript MP Content Displaying Content and Layout in the Content and Layout in same document (Basic) separate documents (CSS) Multimedia Delivery No Yes (Limited) Content Delivery Basic Richer user experience Markup size Small documents Larger documents Color Control Support Only Color Images Full Color Control for fonts, backgrounds, borders Web 2.0 Support Hybrid Support Full Support or Hybrid Trends and the Future of Mobile 2.0 and Mobile Web 2.0 ` The future of Mobile 2.0 and Mobile Web 2.0 depends on ` Flat Rates ` Phone API's access ` Better user experience ` Mobile 2.0 approaches: ` Native applications (e.g. Games) ` Web applications (e.g. Browser, Squirrelfish) ` Hybrid applications (e.g. BONDI Specification, PhoneGap) ` Some technologies already available ` Opera Platform ` Mobile AJAX ` J2ME Trends and the Future of Mobile 2.0 and Mobile Web 2.0 ` How to leverage the device's resources ` Location aware approaches: RFID, GPS ` 2D Barcodes, Camera, Accelerometer ` Ubiquitous Web: Social Tagging, GeoFolksonomies, AwareFolksonomies ` Business View of Web 2.0 ` a “business efficiency enabler” ` consumer behavioural changes ` “word of mouth” marketing in a whole new level [3] ` Web Semantic ` Mobile device taking advantage of web semantics to organize information Summary and Conclusions ` Experiencing Web 2.0 in the Mobile World is still not 100% ` However, users can still “collectively harness intelligence” to the Web ` The majority of phones are still able to only deal with WML (constraint) ` Mobile content providing still needs to consider both markup languages: WML/ XHTML MP ` Although there is a lack of rich user interfaces, devices are becoming powerful ` Bandwidth constraint is no longer considered a wide problem, but users need flat rate data plans ` A lot of device capabilities are not yet fully explored (e.g. location awareness) ` With the advent of devices like the iPhone and Android, it seems that the Mobile 2.0 is moving towards a hybrid browsing/smart clients approach References ` [1] O’Reilly Radar; “Google Announces Support for Microformats and RDFa”. Available at: http://radar.oreilly.com/2009/05/google-announces- support-for-m.html ` [2] Timmins et. all, “Characteristics of Mobile Web Content”. http://web.cs.wpi.edu/~cew/papers/hotweb06.pdf ` [3] Topic Overview: Web 2.0, Forrester Research, Inc - © 2007. Available at: http://www.forrester.com ` [4] AdMob Statistics – Mobile Metrics Report Sep ‘09 Discussion Topics ` Social Networks: When users go to Facebook/Twitter/ Blogger/Flickr from their devices, are they only updating status or also retrieving information from their friends? Or, are they really uploading photos, videos, sharing comments, posting in blogs? What do you think it's missing for users to start doing that? Discussion Topics ` "The browser will fade into the background.“ One way that Web 2.0 companies can similarly adjust their services for mobile devices is
Load more

Recommended publications
  • 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]
  • 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]
  • 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]
  • 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]
  • Web Application Developer's Guide for the Polycom® Soundpoint® IP
    Web Application Developer’s Guide for the Polycom® SoundPoint® IP/SoundStation® IP Family SIP 3.1 August, 2008 Edition 1725-17693-310 Rev. A SIP 3.1 Trademark Information Polycom®, the Polycom logo design, SoundPoint® IP, SoundStation®, SoundStation VTX 1000®, ViaVideo®, ViewStation®, and Vortex® are registered trademarks of Polycom, Inc. Conference Composer™, Global Management System™, ImageShare™, Instructor RP™, iPower™, MGC™, PathNavigator™, People+Content™, PowerCam™, Pro-Motion™, QSX™, ReadiManager™, Siren™, StereoSurround™, V2IU™, Visual Concert™, VS4000™, VSX™, and the industrial design of SoundStation are trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. © 2008 Polycom, Inc. All rights reserved. Polycom Inc. 4750 Willow Road Pleasanton, CA 94588-2708 USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format. As between the parties, Polycom, Inc. retains title to, and ownership of, all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g. a book or sound recording). Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc. is not responsible for printing or clerical errors.
    [Show full text]
  • HTML5 Audio 1 HTML5 Audio
    HTML5 Audio 1 HTML5 Audio HTML • HTML and HTML5; HTML editor • Dynamic HTML • XHTML • XHTML Basic (Mobile) • XHTML Mobile Profile and C-HTML • HTML element • Span and div • HTML attribute • Character encodings; Unicode • Language code • Document Object Model • Browser Object Model • Style sheets and CSS • Font family and Web colors • HTML scripting and JavaScript • W3C, WHATWG, and validator • Quirks mode • HTML Frames • HTML5 Canvas, WebGL, and WebCL • HTML5 Audio and HTML5 video • Web storage • Web browser (layout) engine • Comparison of • document markup languages • web browsers • layout engine support for • HTML; Non-standard HTML • XHTML (1.1) • HTML5; HTML5 canvas, • HTML5 media (Audio, Video) • v • t [1] • e HTML5 Audio is a subject of the HTML5 specification, investigating audio input, playback, synthesis, as well as speech to text in the browser. HTML5 Audio 2 <audio> element The <audio> element represents a sound, or an audio stream.[2] It is commonly used to play back a single audio file within a web page, showing a GUI widget with play/pause/volume controls. Supported browsers • PC • Google Chrome • Internet Explorer 9 • Mozilla Firefox 3.5 • Opera 10.5 • Safari 3.1[3] • Mobile • Android Browser 2.3 • Blackberry Browser • Google Chrome for Android • Internet Explorer Mobile 9 • Mobile Safari 4 • Mozilla Firefox for Android • Opera Mobile 11 • Tizen Supported audio codecs This table documents the current support for audio codecs by the <audio> element. Browser Operating Formats supported by different web browsers system Ogg
    [Show full text]
  • Dynamic HTML
    From Wikipedia, the free encyclopedia (Redirected from DHTML) Dynamic HTML, or DHTML, is an umbrella term for a collection of HTML technologies used together to create interactive and animated web sites[1] by using a combination of a static markup language (such as HTML), a client-side scripting language (such as JavaScript), a presentation definition language (such as CSS), and the Document Object Model.[2] DHTML allows scripting languages to change variables in a web page's definition language, which in turn affects the look and function of otherwise "static" HTML page content, after the page has been fully loaded and during the viewing process. Thus the dynamic characteristic of DHTML is the way it functions while a page is viewed, not in its ability to generate a unique page with each page load. HTML and HTML5 Dynamic HTML By contrast, a dynamic web page is a broader concept — any web page XHTML generated differently for each user, load occurrence, or specific variable XHTML Mobile Profile and C-HTML values. This includes pages created by client-side scripting, and ones Canvas element created by server-side scripting (such as PHP, Perl, JSP or ASP.NET) Character encodings where the web server generates content before sending it to the client. Document Object Model Font family HTML editor HTML element HTML Frames HTML5 video 1 Uses HTML scripting 2 Structure of a web page Web browser engine 3 Example: Displaying an additional block of text Quirks mode 4 References Style sheets 5 External links Unicode and HTML W3C and WHATWG Web colors WebGL Web Storage Comparison of DHTML allows authors to add effects to their pages that are otherwise document markup languages difficult to achieve.
    [Show full text]
  • (X)HTML Best Practice Cheat Sheet.Pdf 2007-08-13 17:49 236 KB
    (X)HTML Best Practice Cheat Sheet All elements are sorted ]able ed T within their /[ lac l y ]ep t groups in ish) [R ues prioritized tional sibili eset eset al/ ance t t s r order. ic nline(- m e er iss r ansitiona am asic ] am r r I or s r ] eaning Recommended transi t Mobile Acc 0 st 0 f 1 B 0 N ice 1 stric 1 f 5.0 h)/[ /[ m appea (X)HTML 2 01 & 1. 1.0 1. 1.1 1. 1.1 2. -is ic 4.0 4.0 act versions are L L L L ML k( ible led pr notes ble brow M ML M ML M ML M T is ty mint-colored. ML 3. ML ML 4. ML T T T O ]loc mant s T T T T HT HT HT HT nv sability est n X)H ] H H H H X XH X XH X XH X ( [B [I Se U B SE Nota U Element Standards Information Document structure <html> N Viewport in XHTML <head> I The main Viewport in HTML. <body> B N content of the Margin: 8px; document The Highly ranked and Make unique for <title> I documents will be the link- Text on the title-bar every page title or name text Only ”name = <meta> I 'description'” is useful Indicates explicit relationship between this <link> I document and other resources. As such there are many good uses! External style <style> I sheets are usually best Unobtrusive Test for Keep scripts Script may have <script> I DOM-scripts, capabilities, not external output please! browsers! Unnecassary with unobtrusive Not ignored by true <noscript> BI I scripting techniques! Forbidden in s XML parsers! XHTML 5.
    [Show full text]
  • An Introduction to Character Encoding Issues in the Mobile Web
    An introduction to character encoding 1 (12) issues in the mobile Web Eduardo CASAIS TECHNICAL PAPER 2008-12-08 AN INTRODUCTION TO CHARACTER ENCODING ISSUES IN THE MOBILE WEB Eduardo Casais areppim AG Bern, Switzerland 1. A LINGERING ISSUE Character encoding – the binary representation of every symbol in documents delivered to mobile terminals – is often treated as an afterthought in mobile Web development. Many developers simply rely upon ISO-8859-1; not a bad choice, as this encoding efficiently supports all important Western European languages, has long been available in the mobile and fixed Internet, is widespread among low-end phones, and is the default encoding in the HTTP standard. Astute software engineers prefer UTF-8; this encoding supports Unicode, and hence the widest range of languages and associated glyphs – great for multilingual “world” applications. It is also a default for several application formats, most popular in the WWW, and available in newer mobile terminals. Even in Japan, i-mode gateways may take care of the complex mapping from UTF-8 to Shift_JIS-only capable terminals. Producing content in one of these two major encodings and configuring a WWW server to advertise the content type and encoding properly generally suffices for mainstream applications. There can be complications however – especially when dealing with advanced functions or developing for exotic markets – and it is preferable to be aware of them. The article examines the situation in the context of mobile browsing. 2. THE DOCUMENT CHARACTER SET Let us briefly recapitulate some concepts. A character set is a repertoire of abstract symbols (e.g.
    [Show full text]
  • Track 3: Extending Blackberry Beyond Email Extending Web-Based Applications with the Blackberry Browser Agenda
    Track 3: Extending BlackBerry Beyond Email Extending Web-Based Applications with the BlackBerry Browser Agenda • Introduction to BlackBerry® Browser • Mark-Up Language, Security and Connectivity Options • Optimizing Web Content for BlackBerry • Server-Side PUSH Applications • What’s New in BlackBerry Enterprise Server™ and BlackBerry Browser v4.0 •Demo BlackBerry Solution: Architecture Recap .NET Corporate Application Servers J2EE Corporate Application Servers HTTP(S) BlackBerry Corporate Systems Enterprise (ERP, CRM, Databases, etc.) Server Web Servers (IIS, Apache-Tomcat) Extending Browser-Based Solutions to BlackBerry From the developer’s perspective… HTTP HTML / WML BlackBerry Web / App Browser 3DES Encryption Server Push and Pull of Data Network-independent BlackBerry Browser Overview • Main BlackBerry Browser versions include: – BlackBerry Browser v3.6 and v3.7 • All GPRS, iDEN and CDMA Java™-enabled BlackBerry handhelds • Support for color and monochrome screen handhelds – BlackBerry Browser v3.8 and v4.0 • Upgrade from BlackBerry Browser v3.7 with new features (JavaScript, Offline Forms, etc.) – RIM Browser v2.5 and v2.6 • RIM 850™, RIM 857™, RIM 950™ and RIM 957™ handhelds • DataTAC and Mobitex wireless networks in North America Mark-up Connectivity Wireless Browser-Based Security User Experience Solutions in the Enterprise Dynamic Content Push • Key questions for consideration: 1. What mark-up languages are supported? 2. How will I connect to my corporate web servers? 3. Is security important? If so, how can I address this? 4.
    [Show full text]