Web standards
From Wikipedia, the free encyclopedia
Web standards is a general term for the formal 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]
Many interdependent standards and specifications, some of which govern aspects of the Internet, not just the World Wide Web, 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, in the broader sense, consist of the following:
- Recommendations published by the World Wide Web Consortium (W3C)[2]
- Internet standard (STD) documents published by the Internet Engineering Task Force (IETF)
- Request for Comments (RFC) documents published by the Internet Engineering Task Force [3]
- Standards published by the International Organization for Standardization (ISO) [4]
- Standards published by Ecma International (formerly ECMA) [5]
- The Unicode Standard and various Unicode Technical Reports (UTRs) published by the Unicode Consortium [6]
- Name and number registries maintained by the Internet Assigned Numbers Authority (IANA) [7]
Contents |
[edit] 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 or nearly valid HTML, CSS and JavaScript. The HTML should also meet accessibility and semantic guidelines.
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), Scalable Vector Graphics (SVG), and XForms, 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[8]
- 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[9]
Web accessibility is normally based upon the Web Content Accessibility Guidelines[10] 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).
[edit] 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.
[edit] Non-standard and vendor-proprietary pressures
In the current Working Draft of the HTML 5 proposed standard document[11], the W3C has a section entitled "Relationship to Flash, Silverlight, XUL and similar proprietary languages" that says, "In contrast with proprietary languages, this specification is intended to define an openly-produced, vendor-neutral language, to be implemented in a broad range of competing products, across a wide range of platforms and devices. This enables developers to write applications that are not limited to one vendor's implementation or language. Furthermore, while writing applications that target vendor-specific platforms necessarily introduces a cost that application developers and their customers or users will face if they are forced to switch (or desire to switch) to another vendor's platform, using an openly-produced and vendor neutral language means that application authors can switch vendors with little to no cost."
[edit] See also
[edit] References
- ^ "Mission - Web Standards Project". WaSP. http://www.webstandards.org/about/mission/. Retrieved on 2009-01-19.
- ^ "W3C Technical Reports and Publications". W3C. http://www.w3.org/TR/#Recommendations. Retrieved on 2009-01-19.
- ^ "IETF RFC page". IETF. http://www.ietf.org/rfc.html. Retrieved on 2009-01-19.
- ^ "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. Retrieved on 2009-01-19.
- ^ "Ecma formal publications". Ecma. http://www.ecma-international.org/publications/index.html. Retrieved on 2009-01-19.
- ^ "Unicode Technical Reports". Unicode Consortium. http://www.unicode.org/reports/index.html. Retrieved on 2009-01-19.
- ^ "IANA home page". IANA. http://www.iana.org/. Retrieved on 2009-01-19.
- ^ "Uniform Resource Identifiers (URI): Generic Syntax". IETF. 1998. http://ftp.ics.uci.edu/pub/ietf/uri/rfc2396.txt. Retrieved on 2009-02-17.
- ^ "Hypertext Transfer Protocol -- HTTP/1.1". IETF. 1999. http://www.rfc-editor.org/rfc/rfc2616.txt. Retrieved on 2009-02-17.
- ^ "Web Content Accessibility Guidelines 1.0, W3C Recommendation 5-May-1999". W3C. 1999. http://www.w3.org/TR/WAI-WEBCONTENT/. Retrieved on 2009-02-18.
- ^ "HTML 5 A vocabulary and associated APIs for HTML and XHTML, W3C Working Draft 12 February 2009". W3C. http://dev.w3.org/html5/spec/Overview.html#relationship-to-flash-silverlight-xul-and-similar-proprietary-languages. Retrieved on 2009-02-17.
