Web standards

Short description: Technical standard

Web standards are the formal, non-proprietary standards and other technical specifications that define and describe aspects of the World Wide Web. In recent years, the term has been more frequently associated with the trend of endorsing a set of standardized best practices for building web sites, and a philosophy of web design and development that includes those methods.[1]

## Contents

* 1 Overview
* 2 The web standards movement
* 3 Common usage
* 4 Standards publications and bodies
* 5 Non-standard and vendor-proprietary pressures
* 6 Web Standards Compliance Testing
* 6.1 Compliance tests for website code
* 6.2 Compliance tests for web browsers
* 7 See also
* 8 References
* 9 External links

## Overview

Web standards include many interdependent standards and specifications, some of which govern aspects of the Internet, not just the World Wide Web. Even when not web-focused, such standards directly or indirectly affect the development and administration of web sites and web services. Considerations include the interoperability, accessibility and usability of web pages and web sites.

Web standards consist of the following:

* Recommendations published by the World Wide Web Consortium (W3C),[2] such as HTML/XHTML, Cascading Style Sheets (CSS), image formats such as Portable Network Graphics (PNG) and Scalable Vector Graphics (SVG), as well as accessibility technologies like WAI-ARIA[3]
* Standards and "Living standards" published by the Web Hypertext Application Technology Working Group (WHATWG), such as the HTML Living Standard, DOM Standard, Encoding Standard and URL Standard.[4]
* Standards published by Ecma International (formerly ECMA) [5] such as JavaScript (also known as ECMAScript) and JavaScript Object Notation (JSON) [3]
* Standards published by the International Organization for Standardization (ISO),[6] such as JPEG[3]

More broadly, the following technologies may be referred to as "web standards" as well:

* Request for Comments (RFC) documents published by the Internet Engineering Task Force (IETF)[7]
* The Unicode Standard and various Unicode Technical Reports (UTRs) published by the Unicode Consortium[8]
* Name and number registries maintained by the Internet Assigned Numbers Authority (IANA)[9]

Web standards are evolving specifications of web technologies.[10] Web standards are developed by standards organizations—groups of interested and often competing parties chartered with the task of standardization—not technologies developed and declared to be a standard by a single individual or company. It is crucial to distinguish those specifications that are under development from the ones that already reached the final development status (in case of W3C specifications, the highest maturity level).

## The web standards movement

The earliest visible manifestation of the web standards movement was the Web Standards Project, launched in August 1998 as a grassroots coalition fighting for improved web standards support in browsers.[11]

The web standards movement supports concepts of standards-based web design, including the separation of document structure from a web page or application's appearance and behavior; an emphasis on semantically structured content that validates (that is, contains no errors of structural composition) when tested against validation software maintained by the World Wide Web Consortium; and progressive enhancement, a layered approach to web page and application creation that enables all people and devices to access the content and functionality of a page, regardless of personal physical ability (accessibility), connection speed, and browser capability.

Prior to the web standards movement, many web page developers used invalid, incorrect HTML syntax such as "table layouts" and "spacer" GIF images to create web pages — an approach often referred to as "tag soup". Such pages sought to look the same in all browsers of a certain age (such as Microsoft Internet Explorer 4 and Netscape Navigator 4), but were often inaccessible to people with disabilities. Tag soup pages also displayed or operated incorrectly in older browsers, and required code forks such as JavaScript for Netscape Navigator and JScript for Internet Explorer that added to the cost and complexity of development. The extra code required, and the lack of a caching page layout language, made web sites "heavy" in terms of bandwidth, as did the frequent use of images as text. These bandwidth requirements were burdensome to users in developing countries, rural areas, and wherever fast Internet connections were unavailable.

The Web Standards movement pioneered by Glenn Davis, George Olsen, Jeffrey Zeldman, Steven Champeon, Todd Fahrner, Eric A. Meyer, Tantek Çelik, Dori Smith, Tim Bray, Jeffrey Veen, and other members of the Web Standards Project replaced bandwidth-heavy tag soup with light, semantic markup and progressive enhancement, with the goal of making web content "accessible to all".[12]

The Web Standards movement declared that HTML, CSS, and JavaScript were more than simply interesting technologies. "They are a way of creating Web pages that will facilitate the twin goals of sophisticated and appropriate presentation and widespread accessibility."[12] The group succeeded in persuading Netscape, Microsoft, and other browser makers to support these standards in their browsers. It then set about promoting these standards to designers, who were still using tag soup, Adobe Flash, and other proprietary technologies to create web pages.

In 2007, Douglas Vos initiated the Blue Beanie Day, inspired by Jeffrey Zeldman, who is shown with a blue cap on the book cover of his 2003 book Designing with Web Standards.[13] Since then, the 30 November is the annual international celebration of web standards and web accessibility.[14]

## Common usage

When a web site or web page is described as complying with web standards, it usually means that the site or page has valid HTML, CSS and JavaScript. The HTML should also meet accessibility and semantic guidelines. Full standard compliance also covers proper settings for character encoding, valid RSS or valid Atom news feed, valid RDF, valid metadata, valid XML, valid object embedding, valid script embedding, browser- and resolution-independent codes, and proper server settings.

When web standards are discussed, the following publications are typically seen as foundational:

* Recommendations for markup languages, such as Hypertext Markup Language (HTML), Extensible Hypertext Markup Language (XHTML), and Scalable Vector Graphics (SVG) from W3C.
* Recommendations for stylesheets, especially Cascading Style Sheets (CSS), from W3C.
* Standards for ECMAScript, more commonly JavaScript, from Ecma International.
* Recommendations for Document Object Models (DOM), from W3C.
* Properly formed names and addresses for the page and all other resources referenced from it (URIs), based upon RFC 2396, from IETF.[15]
* Proper use of HTTP and MIME to deliver the page, return data from it and to request other resources referenced in it, based on RFC 2616, from IETF.[16]

Web accessibility is normally based upon the Web Content Accessibility Guidelines[17] published by the W3C's Web Accessibility Initiative.

Work in the W3C toward the Semantic Web is currently focused by publications related to the Resource Description Framework (RDF), Gleaning Resource Descriptions from Dialects of Languages (GRDDL) and Web Ontology Language (OWL).

## Standards publications and bodies

A W3C Recommendation is a specification or set of guidelines that, after extensive consensus-building, has received the endorsement of W3C Members and the Director.

An IETF Internet Standard is characterized by a high degree of technical maturity and by a generally held belief that the specified protocol or service provides significant benefit to the Internet community. A specification that reaches the status of Standard is assigned a number in the IETF STD series while retaining its original IETF RFC number.

## Non-standard and vendor-proprietary pressures

HTML 5 contains numerous "willful violations" of other specifications, in order to accommodate limitations of existing platforms.[18]

## Web Standards Compliance Testing

There are compliance tests both for HTML code generated by websites as well as for the faithful interpretation of HTML code by web browsers.

### Compliance tests for website code

W3C offers online services to test websites directly for both web site developers, as well as for website users. These include:

* Markup Validation Service to check the markup (HTML, XHTML, ...) of Web documents
* CSS Validation Service to check Cascading Style Sheets (CSS) and (X)HTML documents with style sheets

### Compliance tests for web browsers

The Web Standards Project (WaSP), although development is officially inactive, continues to offer two levels of testing services for web browsers:

* Acid2 Browser Test
* Acid3 Browser Test

## See also

* Acid3
* Designing with Web Standards
* Open Web Foundation (OWF)
* Responsive web design (RWD)
* W3C Markup Validation Service
* WebPlatform.org
* Web Standards Project

## References

1. ↑ "Mission - Web Standards Project". WaSP. http://www.webstandards.org/about/mission/.
2. ↑ "W3C Technical Reports and Publications". W3C. http://www.w3.org/TR/#Recommendations.
3. ↑ 3.0 3.1 3.2 Allsopp, John (2009-12-09). Developing with Web Standards. Berkeley: New Riders. p. 11. ISBN 978-0-321-70271-5.
4. ↑ "WHATWG Standards". https://spec.whatwg.org/.
5. ↑ "Ecma formal publications". Ecma. http://www.ecma-international.org/publications/index.html. ,
6. ↑ "Search for World Wide Web in ISO standards". ISO. http://www.iso.org/iso/search.htm?qt=world+wide+web&published=on&active_tab=standards.
7. ↑ "IETF RFC page". IETF. http://www.ietf.org/rfc.html.
8. ↑ "Unicode Technical Reports". Unicode Consortium. https://www.unicode.org/reports/index.html.
9. ↑ "IANA home page". IANA. https://www.iana.org/.
10. ↑ Leslie Sikos (2011). Web standards - Mastering HTML5, CSS3, and XML. Apress. ISBN 978-1-4302-4041-9. http://www.masteringhtml5css3.com/.
11. ↑ Sliwa, Carol (1998-08-17). "Browser standards targeted". Computerworld 32 (33): pp. 76. ISSN 0010-4841.
12. ↑ 12.0 12.1 "Web Standards Mission". Archive.webstandards.org. http://archive.webstandards.org/mission.html.
13. ↑ Zeldman, Jeffrey (2008-11-20). "Blue Beanie Day II". http://www.zeldman.com/2008/11/19/blue-beanie-day-ii/.
14. ↑ Walker, Alissa (2009-11-30). "Why Is Your Web Designer Wearing a Blue Hat Today?". https://www.fastcompany.com/1472960/why-your-web-designer-wearing-blue-hat-today.
15. ↑ Berners-Lee, Tim; Fielding, Roy T.; Masinter, Larry (1998), Uniform Resource Identifiers (URI): Generic Syntax, IETF, doi:10.17487/RFC2396, RFC 2396, https://tools.ietf.org/html/rfc2396, retrieved 2009-10-27
16. ↑ Fielding, Roy T.; Gettys, James; Mogul, Jeffrey C.; Nielsen, Henrik Frystyk; Masinter, Larry; Leach, Paul J.; Berners-Lee, Tim (1999), Hypertext Transfer Protocol -- HTTP/1.1, IETF, doi:10.17487/RFC2616, RFC 2616, https://tools.ietf.org/html/rfc2616, retrieved 2009-10-27
17. ↑ "Web Content Accessibility Guidelines 1.0, W3C Recommendation 5-May-1999". W3C. 1999. http://www.w3.org/TR/WAI-WEBCONTENT/.
18. ↑ "HTML 5 - A vocabulary and associated APIs for HTML and XHTML - Compliance with other specifications". https://www.w3.org/TR/html5/introduction.html#compliance-with-other-specifications.

## External links

* W3C homepage
* The Internet Engineering Task Force

* v
* t
* e

Web interfaces

Server-side|

| Protocols|

* HTTP
* CGI
* SCGI
* FCGI
* AJP
* WSRP
* WebSocket

|

Server APIs|

* C NSAPI
* C ASAPI
* C ISAPI
* COM ASP
* Java servlet
* container
* CLI OWIN
* ASP.NET Handler
* Python WSGI
* Ruby Rack
* JavaScript JSGI
* Perl PSGI
* Lua WSAPI
* Portlet
* container

Apache modules|

* mod include
* mod jk
* mod lisp
* mod mono
* mod parrot
* mod perl
* mod php
* mod proxy
* mod python
* mod wsgi
* mod ruby
* Phusion Passenger

Topics|

* Web resource vs. Web service
* Open API
* Webhook
* Application server
* comparison
* Scripting

Client-side|

| Browser APIs|

* C NPAPI
* LiveConnect
* XPConnect
* C NPRuntime
* C PPAPI
* NaCl
* ActiveX
* BHO
* XBAP

|

Web APIs|

| W3C|

* Audio
* Canvas
* CORS
* DOM
* DOM events
* EME
* File
* Geolocation
* IndexedDB
* MSE
* SSE
* SVG
* Video
* WebAuthn
* WebRTC
* WebSocket
* Web messaging
* Web storage
* Web worker
* XMLHttpRequest
* WebAssembly

|

Khronos|

* WebCL
* WebGL

Others|

* Gears
* Web SQL Database (formerly W3C)
* WebUSB

Topics|

* Ajax and Remote scripting vs. DHTML
* Mashup
* Web IDL
* Scripting

Topics|

* Dynamic web page
* Web standards
* Rich web application
* Web API security
* Web application
* Web framework

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Web standards. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Web_standards&oldid=316072"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template