DOCSLIB.ORG

What Are Web Standards? ‣Why Do We Use Them? ‣What Is HTML and How Does It Work? ‣Anatomy of a Web Page ‣The Different HTML Versions

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
What Are Web Standards? ‣Why Do We Use Them? ‣What Is HTML and How Does It Work? ‣Anatomy of a Web Page ‣The Different HTML Versions HTML basics and Web standards concepts Friday, 27 April 2012 What we’ll cover ‣What are web standards? ‣Why do we use them? ‣What is HTML and how does it work? ‣Anatomy of a web page ‣The different HTML versions Friday, 27 April 2012 What are open web standards? Friday, 27 April 2012 What are open web technologies? ‣Technologies that the web is built on: ‣Web infrastructure technologies (HTTP, TCP/IP, etc.) ‣Technologies we build web sites with (HTML, CSS, JavaScript, SVG, etc.) Friday, 27 April 2012 Are all technologies open? ‣No. ‣Some technologies are closed/proprietary. ‣They are created by only one company. ‣And/or they are not interoperable with other open technologies. Friday, 27 April 2012 Open technologies ‣Are developed in cooperation by multiple companies. ‣With standards bodies (Like W3C) curating them. ‣They are interoperable with each other. ‣They are not dependant on patents, and free to use by anyone. Friday, 27 April 2012 Why are open technologies good? ‣The web should be open to anyone to use and develop. ‣Not only those with the right political influence. ‣Or those who can afford expensive software. Friday, 27 April 2012 Standards? ‣In real life standards are all around us. ‣Traffic lights, common icons, screws, shoe sizes. ‣They ensure things will just work. Friday, 27 April 2012 From standards to web standards ‣Web standards do the same thing for the Web. ‣They are defined in big specification documents. ‣Browser vendors are encouraged to implement them equally. ‣So the same code will work across browsers. ‣Today this is mostly the case. In the old days we used to have the browser wars. Friday, 27 April 2012 The browser wars ‣The late 90s and early 00s were dark times. ‣Netscape and IE fought to win market share by implementing features in incompatible ways. ‣Terrible for both developers and users. Friday, 27 April 2012 The browser wars ‣The late 90s and early 00s were dark times. ‣Netscape and IE fought to win market share by implementing features in incompatible ways. ‣Terrible for both developers and users. Friday, 27 April 2012 What is a web site made up of? Friday, 27 April 2012 A web site is made by ‣Choosing a domain name and linking it to that web server. ‣Putting several different files together. ‣Uploading them to a web server using FTP. Friday, 27 April 2012 Choosing a domain name ‣You buy one from a domain registration company, like GoDaddy or 123-Reg ‣You find ‣Choosing a domain name and linking it to that web server Friday, 27 April 2012 Getting hosting space ‣Hosting space is bought form a hosting company, like Rackspace or Media Temple ‣It sometimes comes with the domain name ‣Connect the hosting space to the domain name via nameservers Friday, 27 April 2012 FTP ‣FTP is a web standard: File Transfer Protocol ‣An FTP program is used to upload your web files onto your hosting space Friday, 27 April 2012 Types of file on the Web ‣.html: Contains the content of our pages and defines its structure and purpose ‣.css: Contains styling information to define how the content should look ‣.js: Applies dynamic interactive behaviour to the content Friday, 27 April 2012 Types of file on the Web ‣.php, .net: server-side languages — these contain dynamic code that generates different client-side content depending on variables ‣Images and video — media files that are used as part of the content ‣Non-web files: .doc, .pdf and other non-web content that aren’t interpreted by the web browser Friday, 27 April 2012 Client-side vs server-side ‣Also known as static vs dynamic. ‣HTML/CSS/JS are static — they’re downloaded as is, then rendered by the browser and displayed. ‣PHP etc. are dynamic — they are rendered on the server, generating different client-side depending on what variables are fed to them. Friday, 27 April 2012 Creating a site folder ‣index.html ‣other pages (sometimes in folders) ‣styles folder ‣scripts folder ‣folders for assets — fonts, images, video, etc. Friday, 27 April 2012 Creating a site folder ‣index.html ‣other pages (sometimes in folders) ‣styles folder ‣scripts folder ‣folders for assets — fonts, images, video, etc. Friday, 27 April 2012 The anatomy of HTML Friday, 27 April 2012 HTML is... ‣What we structure our content in. ‣It’s a tag-based language. ‣You wrap your content in tags to give it meaning and structure. ‣Let’s have a look. Friday, 27 April 2012 <a href=”http://www.amazon.co.uk”>Link to Amazon</a> ‣ <a href=”http://www.amazon.co.uk”>: The opening tag of the element. ‣ </a>: The closing tag of the element. ‣ Link to Amazon: The content of the element. We’re wrapping them in tags to make a link. Friday, 27 April 2012 <a href=”http://www.amazon.co.uk”>Link to Amazon</a> ‣ href=”http://www.amazon.co.uk”: An attribute — attributes modify element behaviour. In this case, it defines that the link is going to point to amazon.co.uk ‣ href: The attribute name. ‣ http://www.amazon.co.uk: The attribute value. Friday, 27 April 2012 Some simple rules ‣Always put attribute values in quotes, even though you don’t really have to. Makes it easier to read. ‣Always close elements that you open: <p>This paragraph is not ok. ‣Always nest elements correctly: <p><a>This isn’t ok either</p></a> Friday, 27 April 2012 Not all elements have content! ‣Some elements don’t surround any content. For example: ‣ <img src=”kittens.jpg”> ‣These are called “empty elements” or sometimes “self-closing elements” Friday, 27 April 2012 Block and inline elements ‣Block level elements start on a new line and stretch across the browser window. Examples: <p>, <div> ‣Inline elements don’t start on a new line, and only stretch as far as the content they encapsulate. Examples: <em>, <span> Friday, 27 April 2012 More complex attribute example ‣ <img src=”kittens.jpg” alt=”a beautiful black kitten” class=”animal masthead”> ‣Note you can have multiple attributes. ‣They should all have a space between them. ‣The attribute name, equals sign, quotes and value shouldn’t have any spaces between them. Friday, 27 April 2012 DOCTYPES ‣historically these defined the version of HTML the document is written in so it can be validated against a specific ruleset ‣Let’s look at some examples Friday, 27 April 2012 DOCTYPES ‣HTML 4.01 strict ‣ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> ‣XHTML 1.0 transitional ‣ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/ xhtml1-transitional.dtd"> Friday, 27 April 2012 DOCTYPES ‣But all they ever did was put browsers in “standards mode” versus “quirks mode” ‣Because of this, you still need to include a doctype. ‣But they were so long and unwieldy Friday, 27 April 2012 DOCTYPES ‣HTML5 was therefore rewritten to include the shortest DOCTYPE possible that would put browsers into standards mode. ‣ <!doctype html> Friday, 27 April 2012 The structure of an HTML document ‣First you have the DOCTYPE. ‣Then you have the <html> element, which wraps all other content. ‣Then you have the <head>, which contains all the page’s meta data, data about the page, such as linked stylesheets and keywords. ‣Then you have the <body>, which is where all the page content goes. Friday, 27 April 2012 HTML versus XHTML Friday, 27 April 2012 HTML vs XHTML ‣Developers used to talk about whether they preferred XHTML or HTML. ‣HTML is a specialised markup language designed for marking up documents. ‣XHTML is a reformulation of HTML as an XML vocabulary Friday, 27 April 2012 XHTML was a good idea... ‣...in principle because it has stricter rules than HTML, so enforced better quality markup. Friday, 27 April 2012 XHTML: ‣self closing tags include trailing slash: <img src="kittens.jpg" />. ‣ attribute values always quoted. ‣ attributes can't be minimized: checked="checked". ‣ code should all be lower case. Friday, 27 April 2012 HTML: ‣self closing tags needn’t include trailing slash: <img src="kittens.jpg">. ‣ attribute values don’t always have to be quoted. ‣ attributes can be minimized: checked. ‣ code can be upper or lower case. Friday, 27 April 2012 But XHTML never caught on ‣Old versions of IE wouldn’t serve it properly. ‣Proper XHTML refuses to display at all if it contains ANY errors: not great for the Web. ‣XHTML 2.0 was not compatible with the existing Web. Friday, 27 April 2012 In reality... ‣Professional developers use a variety of different styles. ‣Most use a mixture of HTML and XHTML rules. ‣HTML5 doesn’t care whether you use XHTML or HTML rules. Friday, 27 April 2012 Deprecated elements Friday, 27 April 2012 Back in the old days... ‣...before CSS was popular and well-supported, we used to use HTML to do all our styling and layout. ‣Some elements were abused (e.g. tables for layout) ‣Some elements were presentational Friday, 27 April 2012 Deprecated examples ‣These are no longer included in the HTML spec: ‣ <bgcolor> for setting background colour. ‣ <font> for setting fonts. ‣ <center> for centering content. ‣ <strike> for striking through content. Friday, 27 April 2012 HTML5 has repurposed... ‣...some old deprecated elements to give them new semantic meaning. ‣ <small> is now for small/fine print, not just to make text small. ‣ <b> is for drawing attention to text without giving it extra meaning, not just for bolding text. Friday, 27 April 2012.
Load more

Recommended publications
  • Applying World Wide Web Standards to Embedded Systems
    NASA / TMm2002-211199 AIAA-2001-5107 Embedded Web Technology: Applying World Wide Web Standards to Embedded Systems Joseph G. Ponyik and David W. York Glenn Research Center, Cleveland, Ohio March 2002 The NASA STI Program Office... in Profile Since its founding, NASA has been dedicated to CONFERENCE PUBLICATION. Collected the advancement of aeronautics and space papers from scientific and technical science. The NASA Scientific and Technical conferences, symposia, seminars, or other Information (STI) Program Office plays a key part meetings sponsored or cosponsored by in helping NASA maintain this important role. NASA. The NASA STI Program Office is operated by SPECIAL PUBLICATION. Scientific, Langley Research Center, the Lead Center for technical, or historical information from NASA's scientific and technical information. The NASA programs, projects, and missions, NASA STI Program Office provides access to the often concerned with subjects having NASA STI Database, the largest collection of substantial public interest. aeronautical and space science STI in the world. The Program Office is also NASA's institutional TECHNICAL TRANSLATION. English- mechanism for disseminating the results of its language translations of foreign scientific research and development activities. These results and technical material pertinent to NASA's are published by NASA in the NASA STI Report mission. Series, which includes the following report types: Specialized services that complement the STI TECHNICAL PUBLICATION. Reports of Program Office's diverse offerings include completed research or a major significant creating custom thesauri, building customized phase of research that present the results of data bases, organizing and publishing research NASA programs and include extensive data results.., even providing videos.
    [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]
  • Websockets, JSON, HTML, CSS) Webpods When Installed Motivation Create Web Pages to Display Control System Data
    Web pods Accessing Control Data Through Web Standards (WebSockets, JSON, HTML, CSS) WebPODS when installed Motivation Create web pages to display control system data WebPODS (Protocol Oriented Distribution Service) • The Web PODS aims to provide real-time publish/subscribe communication using • WebSockets • JSON • Pure HTML/CSS widgets • Main benefits: • Uses web standards (any web client in any language) • Widgets can be configured through standard CSS • Data access outside of control network (possibly WAN) • Web pages do not need to live on the same server where the gateway is Chrome extension: Simple Web Socket Client HTML Probe (Danielle Connolly, UMich) Test javascript client (Danielle Connolly, UMich) Text monitor examples LED examples WebPODS Specify server location Adding text-monitor Adding led Specify color for “LOW” enum value GWT client (Enrique Schuhmacher, BNL) Using CS-Studio off site through Web Pods WebPODS Architecture WebPODS clients WebPODS Server Web Pods server configuration [xxx@diirt ~]# more .diirt/pods/web/mappings.xml <?xml version='1.0' encoding='UTF-8'?> <mappings version="1"> <mapping channel="calibration/constants" substitution="file:///path/to/file/table.csv" permission="READ_ONLY"/> <mapping channel="public-.*" permission="READ_WRITE"/> <mapping channel="cf-tag-(.\w)" substitution="=cfQuery($1)" permission="READ_ONLY"/> <mapping channel="sim/(.*)" substitution="sim://$1" permission="READ_ONLY"/> </mappings> Access security planned, not yet implemented • Use wss (like https) for authentication • Use username/role/unix group/host for authorization Be careful not to expose too much Web Pods • Rebroadcast data using Web sockets and JSON • Play nice with firewalls, get WAN notifications, data available to web tools, server is one class (no logic, a pass-through to pvmanager), should scale (different sockets on different servers, not tested) • Not a substitute to CA/PVA.
    [Show full text]
  • A Light-Weight Time Protocol Based on Common Web Standards
    A light-weight time protocol based on common web standards M. Gutbrod, T. Klein, D. Sibold Physikalisch-Technische Bundesanstalt 38116 Braunschweig, Germany [email protected] Abstract—Distributed systems are an essential part of Industry Highest accuracy can be reached by using PTP (Precision 4.0 and IoT. In order to perform properly they depend on time Protocol) if the IT infrastructure fully complies to PTP unambiguous time information while their stripped-down requirements [4]. The current standard only provides an hardware prevents the use of extensive protocols and algorithms. experimental annex for the integrity protection of PTP messages We developed a light-weight protocol for time transmission aiming which was never well adopted and implemented. Thus, the for simplicity, security and broad applicability by relying solely on current effort to revise the PTP specification includes a plan to common web standards. In this paper the new websocket time provide a new security mechanism for PTP. protocol (WST) will be presented. Our aim was to develop a light-weight and secure time Keywords—time protocol, websocket, ntp, time transmission, protocol that is universally usable. Therefore, it is solely based WST on technologies that are available on virtually every IoT device communicating via internet. I. INTRODUCTION The digital transformation is, among others, driven by the II. WEBSOCKET emergence of distributed systems which may for example Websocket was developed to allow efficient bidirectional consist of a large number of sensors performing measuring tasks. communication with low overhead over TCP connections and is In order to correlate their data, it is important that all sensors, or designed to be compatible with the HTTP protocol.
    [Show full text]
  • An Introduction to AJAX
    An Introduction to AJAX By : I. Moamin Abughazaleh Page 2 /25 How HTTP works? Classical HTTP Process 1. The visitor requests a page Page 3 /25 2. The server send the entire HTML, CSS and Javascript code at once to the client 3. So, the communication is synchronious Page 4 /25 What is Javascript programming actually? What is Javascript programming? It is programming the browsers. So, we are limited to the objects that the Page 5 /25 browser presents us An Alternative for Managing requests - AJAX AJAX stands for Asynchronous JavaScript And XML. AJAX is based on XMLHttpRequest object of Page 6 /25 Javascript - so the browser and XMLHttpRequest is a standard http://www.w3.org/TR/XMLHttpRequest/ It was introduced with IE-5.0 as an ActiveX object (1999) Later all the major browsers added XMLHttpRequest into their object bases. AJAX = Asynchronous JavaScript and XML It is a technique for creating better, faster, and more interactive web applications With XMLHttpRequest object JavaScript can trade data with a web server, without reloading Page 7 /25 the page AJAX uses “asynchronous data transfer” => allowing web pages to request small bits of information from the server instead of whole pages We can create desktop application like web applications using AJAX, this paradigm is also called “WEB 2.0” programming AJAX - Based on Web Standards AJAX is based on the following web standards: XHTML and CSS Presentation DOM Dynamic display of and interaction with data XML and XSLT Tranfering data back and forth Page 8 /25 XMLHttpRequest Asynchronous transfer of data Javascript Bring these technologies together AJAX applications are browser and platform independent The XMLHttpRequest object is supported in Internet Explorer 5.0+, Safari 1.2, Mozilla 1.0 / Firefox, Opera 8+, and Netscape 7.
    [Show full text]
  • Web-Based Information Visualisation Using Javascript and Webgl
    Eurographics Conference on Visualization (EuroVis) (2014) Short Papers N. Elmqvist, M. Hlawitschka, and J. Kennedy (Editors) FluidDiagrams: Web-Based Information Visualisation using JavaScript and WebGL Keith Andrews1 and Benedict Wright2 1Institute for Information Systems and Computer Media (IICM), Graz University of Technology, Austria 2Institute for Software Technology (IST), Graz University of Technology, Austria Abstract Much attention has been focused on the provision of information graphics and visualisations inside a web browser. Currently available infovis toolkits produce graphical output by either injecting SVG nodes into the DOM or using the JavaScript Canvas 2D API. FluidDiagrams is a prototype information visualisation framework written in JavaScript which uses the WebGL 3D JavaScript API for its output, falling back to Canvas 2D as necessary, via the Three.js library. Six visualisations are currently implemented: bar chart and line chart, scatter plot and parallel coordinates for multidimensional data, and cone tree and hyperbolic for hierarchies. Anecdotally, visualisations using SVG nodes in the DOM for output can become rather sluggish when display- ing more than a few dozen items. Visualisations using Canvas 2D exhibit similarly slow performance. WebGL utilises hardware acceleration where available and promises much better performance for complex visualisations, potentially in the order of many thousands of items without becoming unresponsive. A comparison of parallel coordinates visualisations with 100 records in 20 dimensions compared three imple- mentations: FluidDiagrams (WebGL), FluidDiagrams (Canvas 2D), and D3 (using SVG nodes). They achieved 62, 6, and 10 frames per second respectively. The FluidDiagrams (WebGL) implementation was able to render 1,000 records in 20 dimensions at 18 frames per second, compared to 1 and 6 respectively.
    [Show full text]
  • WTP-101 Developing Web Applications with Standards Using W3C Org Standard Technologies Such As, HTML, CSS, XML, XSD and XSL Attributions
    WTP-101 Developing Web Applications with Standards using W3C org standard technologies such as, HTML, CSS, XML, XSD and XSL Attributions • World Wide Web Consortium – http://www.w3c.org • Sandra Clark – CSS for Better Sites – CFUN04 – http://www.cfconf.org/ This course is made available under a Creative Commons Attribution-Share Alike 3.0 License Copyright 2008, Eteration A.S. Web Standards Module Road Map ●Web Standards ●Web Architecture: Resources, URI and HTTP ●HTML and XHTML ●XML, XML Schemas and XML Parsing ●CSS ●XSLT This course is made available under a Creative Commons Attribution-Share Alike 3.0 License Copyright 2008, Eteration A.S. What are Web Standards • Worldwide Web Consortium (W3C) – Recommends Standards for Web Development • Recommendations: http://www.w3.org Specifications for the Web's formats and protocols must be compatible with one another and allow (any) hardware and software used to access the Web to work together This course is made available under a Creative Commons Attribution-Share Alike 3.0 License Copyright 2008, Eteration A.S. w3c.org – The “one” web • The W3C Technology Stack Figure: http://www.w3.org/Consortium/technology This course is made available under a Creative Commons Attribution-Share Alike 3.0 License Copyright 2008, Eteration A.S. What Standards? • Standards for the Web means: – Structural Languages • HTML – Publishing Language of the Web • XHTML - Extensible Hypertext Markup Language 1.0 and 1.1 • XML - Extensible Markup Language 1.0 – Transformations • XSL - Extensible Stylesheet Language • XPath – XML Path Language – Presentation • CSS - Cascading Style Sheets Levels 1 and 2 – as well as emerging standards, such as those for television and PDA based User Agents This course is made available under a Creative Commons Attribution-Share Alike 3.0 License Copyright 2008, Eteration A.S.
    [Show full text]
  • Design and Implementation of a Web-Based Application for the Visualization of Large Scale Photogrammetric and Cartographic Data
    DESIGN AND IMPLEMENTATION OF A WEB-BASED APPLICATION FOR THE VISUALIZATION OF LARGE SCALE PHOTOGRAMMETRIC AND CARTOGRAPHIC DATA Maria Spanaki a, Lysandros Tsoulos b a Surveying Eng. MSc Geomatics – PhD Student, b Assoc. Professor NTUA Cartography Laboratory, Faculty of Rural and Surveying Engineering National Technical University of Athens 9 H. Polytechniou, 157 80 Zographou Campus, Athens, Greece [email protected], [email protected] KEY WORDS: Photogrammetry, Cartography, Web-based, Standards, Open systems ABSTRACT: The objective of this paper is to show the way multiple source data like aerial photos, maps and descriptive information are combined and amalgamated to form an Internet or Intranet application. The visual outcome is a large scale, precise and detailed image/map displaying the interiors of buildings in a layered fashion, enabling the user to interact with the objects shown on it. Scalable Vector Graphics - SVG is an XML language for the encoding/representation of two dimensional vector data, especially designed for integration with other web standards. SVG provides those basic structures, which are needed for map generation and overcomes the disadvantages inherent to bitmap images displaying spatial data. In the domain of spatial data, SVG constitutes a new powerful standard for visualization and has a great potential along with other XML encoding languages like Geographic Markup Language - GML, Extensible Stylesheet Language Transformation – XSLT and Cascading Style Sheets – CSS for the development of Web- based applications utilizing open source software and standards. This paper elaborates on the way SVG data is generated from existing cartographic and photogrammetric sources and the use of scripts in order to provide the user with interactive and animation capabilities, resulting to a comprehensive and user friendly map in the Internet.
    [Show full text]
  • Guideline for Securing Your Web Browser P a G E | 2
    CMSGu2011-02 CERT-MU SECURITY GUIDELINE 2011 - 02 Mauritian Computer Emergency Response Team Enhancing Cyber Security in Mauritius Guideline For Securing Your Web Browser National Computer Board Mauritius JuJunene 2011 2011 Version 1.7 IssueIssue No. No. 4 2 National Computer Board © Table of Contents 1.0 Introduction .......................................................................................................................... 7 1.1 Purpose and Scope ........................................................................................................... 7 1.2 Audience........................................................................................................................... 7 1.3 Document Structure.......................................................................................................... 7 2.0 Background .......................................................................................................................... 8 3.0 Types of Web Browsers ....................................................................................................... 9 3.1 Microsoft Internet Explorer .............................................................................................. 9 3.2 Mozilla Firefox ................................................................................................................. 9 3.3 Safari ................................................................................................................................ 9 3.4 Chrome ..........................................................................................................................
    [Show full text]
  • Why Web Standard Are Important: an Overview of W3C, Its Operation and Current Technical Directions
    Why Web Standard are Important: An overview of W3C, its operation and current technical directions AusWeb 2006, Australia, 3rd July, 2006 Why Web Standards are Important... World Wide Web Consortium (W3C) “To lead the World Wide Web to its full potential by developing protocols and guidelines that ensure long-term growth for the Web” Founded by Tim Berners-Lee in 1994 Develops open Recommendations (Web Standards) over eighty so far… Engages in education, outreach, develops guidelines… A neutral forum for building consensus around Web standards Ivan Herman, W3C Why Web Standards are Important... Just a glimpse (we will come back to this later)… Ivan Herman, W3C Why Web Standards are Important... W3C is international… W3C Hosts (in red) and W3C Offices (in blue) around the Globe Ivan Herman, W3C Why Web Standards are Important... Some guiding principles at W3C Web Technologies should be interoperable the Web is based on a large palette of technologies no technology can pretend to cover all needs on the Web hence the interoperability of technologies necessary Web Standards should be open, i.e., non-proprietary The Web should be accessible to all Ivan Herman, W3C Why Web Standards are Important... W3C’s long term goals Web for Everyone regardless of language, user capabilities, geographical location, device used for access,… Web on Everything not only PC-s, but Phones, PDA-s, Television,… Knowledge Base, Advanced data searching and sharing information for both human and machine processing Trust and Confidence technologies for collaborative environment a Web with accountability, security, confidence, and confidentiality Ivan Herman, W3C Why Web Standards are Important..
    [Show full text]
  • HCL Nomad Web
    HCL Nomad Web Thomas Hampel Director @ Product Management HCL Digital Solutions [email protected] @thomashampel Please note HCL’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice and at HCL’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard HCL benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. Copyright © 2020 HCL Technologies Limited | www.hcltechsw.com The HCL Digital Solutions Product Strategy Apps that run your Business Business-critical Digital Experiences • Domino App Dev • Multi-experience (MXDP) • Low-code portfolio • DXP
    [Show full text]
  • Blazor – a Dream Come True for C# Developers
    Blazor – A Dream Come True for C# Developers Tismo Technology Solutions (P) Ltd Bangalore, India JavaScript is the spine of any modern web app. Over the last few years, it has become one of the most widely used programming languages, helping front end developers build beautiful user interfaces on mobile and web. But this left .NET developers at a disadvantage. Now imagine this - .NET running on the browser. No add-ons, no plugins, no transpilation wizardry. Not possible you say. Well, say hello to Blazor from Microsoft! What is Blazor? Blazor is a .NET web framework that runs on the browser. Think React or Angular, but propelled by C# and Razor, a mark-up syntax that lets you embed server-based code into web pages. Blazor executes .NET assemblies using the Mono .NET runtime, a free and open-source project, implemented via WebAssembly. It uses the latest web standards and does not require any additional plugins or add-ons to run. It allows full stack web development with the stability, consistency and productivity of .NET. Blazor offers all the benefits of the rich, modern single-page application (SPA) platform. Additionally, it allows developers to write the code for the client and server in the same technology (.NET). Also, the same classes can be shared by both client and server code. Figure 1: Highlights of Blazor Copyright © 2020 Tismo Technology Solutions (P) Ltd 1/4 WebAssembly - The Secret Sauce that makes Blazor Possible WebAssembly is a web standard similar to lower level assembly language. It enables execution of code almost as fast as executing native machine code.
    [Show full text]