HTML Working Group

Last updated

The HTML Working Group was an Internet Engineering Task Force (IETF) working group from 1994 to 1996, and a World Wide Web Consortium (W3C) working group from 1997 to 2015. [1]

Contents

The working group was co-chaired by Paul Cotton, Sam Ruby, and Maciej Stachowiak.

Members

Members of the HTML Working Group included representatives from the following organizations:

W3C had also invited several experts to collaborate with the working group including:

Internal working system

The HTMLWG had members from a diverse community such as content providers, content authors, and anyone interested in the work on HTML.

Participation

To participate in the group, the steps involved having a W3C account and filling out a form for copyright, content etc. policies. Steps are different for people who are affiliated with W3C Member organization and those who are not. [2]

Communication methods

Meetings

See HTML/wg/WorkMode for more details about the way a member can participate in, responsibilities of Editor, various types of meetings that members can attend, etc.

Interest Groups

To encourage broad participation, three locale-based interest groups were set up: the Chinese, Japanese and Korean Interest Groups. The HTML5 Chinese Interest Group had over 1000 members.

History

The creation of an HTML Working Group was first proposed at the 30th Internet Engineering Task Force (IETF) meeting in Toronto, on 26 July 1994. [3] The Group was founded with the adoption of its charter in September 1994 [4] and was chaired by Eric Sink. [5]

The IETF HTML Working Group oversaw the creation and publication of RFC 1866 in November 1995, the document which defines HTML 2.0. The Group also published RCF 1942 in May 1996, a document which provides an experimental description of an extended set of HTML tables. [6]

The IETF Group was dissolved in September 1996. [6] [5]

Change in working direction

In 1999, W3C released HTML 4.01 and then stopped continuing the evolution of HTML, as the W3C's HTMLWG announced it would change their direction to exploitation of XML-based version of HTML (named XHTML 2.0), which has a stricter standard.

The traditional version of HTML allowed uncertainties in code review, which means even there are some mistakes in the web pages, browser will still display the contents through error detection and correction. "Nowadays, there would be at least one mistake existing in over 99% HTML web pages. " estimated by the Google senior programmer Mark Pilgrim. [7]

The W3C HTMLWG hoped to boost a more regulated development of the future of the Internet through rigorous standards. While the popularization and application of XHTML had not received many responses from the public.

Collaboration 

Messenger 1

In 2004, Mozilla and Opera put forward a plan based on HTML 4, as they wanted to continue the evolution of HTML. The plan was not passed. Then they decided to form WHATWG, in order to pursue the future of HTML along with W3C’S HTMLWG but in different direction. [7]

In 2006, WHATWG made a breakthrough while XHTML 2.0 was still impractical. As a result, Tim Berners-Lee, the inventor of W3C announced that the W3C's HTMLWG would stop to jointly develop HTML5 with WHATWG. Ian Hickson was responsible for both editing the two groups' specifications. [8]

In October 2009, W3C dismissed the XHTML 2 group.

Split

In July 2012, W3C's HTMLWG and WHATWG officially parted ways about working on HTML5. WHATWG evolved HTML5 and W3C worked on a more static "snapshot". Therefore, there are two versions of HTML5 - one is a "living standard" and the other one is "snapshots". The split between two bodies was due to conflicts. [9]

Regarding fears of this split from the public, then head of WHATWG, Ian Hickson said the split would not be as harmful as people thought. "It's certainly possible that the specs will fork, but it's unlikely, or at least, unlikely to happen in a way that is harmful." In his opinion, possible conflicts will lead to a more precise standard. And "Browser vendors will just know to use the more precise one." [10]

Differences between WHATWG and HTMLWG

WHATWG maintains a living standard and stopped using version numbers. W3C's HTMLWG leaves the WHATWG spec in order to stick producing snapshots. [11] [12]

See also

About the HTMLWG, a brief summary of HTMLWG.

Related Research Articles

<span class="mw-page-title-main">Document Object Model</span> Convention for representing and interacting with objects in HTML, XHTML, and XML documents

The Document Object Model (DOM) is a cross-platform and language-independent interface that treats an HTML or XML document as a tree structure wherein each node is an object representing a part of the document. The DOM represents a document with a logical tree. Each branch of the tree ends in a node, and each node contains objects. DOM methods allow programmatic access to the tree; with them one can change the structure, style or content of a document. Nodes can have event handlers attached to them. Once an event is triggered, the event handlers get executed.

<span class="mw-page-title-main">HTML</span> HyperText Markup Language

The HyperText Markup Language or HTML is the standard markup language for documents designed to be displayed in a web browser. It defines the meaning and structure of web content. It is often assisted by technologies such as Cascading Style Sheets (CSS) and scripting languages such as JavaScript.

<span class="mw-page-title-main">World Wide Web Consortium</span> Main international standards organization for the World Wide Web

The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web. Founded in 1994 and led by Tim Berners-Lee, the consortium is made up of member organizations that maintain full-time staff working together in the development of standards for the World Wide Web. As of 5 March 2023, W3C had 462 members. W3C also engages in education and outreach, develops software and serves as an open forum for discussion about the Web.

An HTML element is a type of HTML document component, one of several types of HTML nodes. The first used version of HTML was written by Tim Berners-Lee in 1993 and there have since been many versions of HTML. The most commonly used version is HTML 4.01, which became official standard in December 1999. An HTML document is composed of a tree of simple HTML nodes, such as text nodes, and HTML elements, which add semantics and formatting to parts of document. Each element can have HTML attributes specified. Elements can also have content, including other elements and text.

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.

In web development, "tag soup" is a pejorative for syntactically or structurally incorrect HTML written for a web page. Because web browsers have historically treated structural or syntax errors in HTML leniently, there has been little pressure for web developers to follow published standards, and therefore there is a need for all browser implementations to provide mechanisms to cope with the appearance of "tag soup", accepting and correcting for invalid syntax and structure where possible.

David Hyatt is an American software engineer and a Shadowrun game expansion author. Employed by Apple starting in 2002, he was part of the Safari web browser and WebKit framework development team. He also helped develop the HTML 5, XBL, and XUL specifications.

The canvas element is part of HTML5 and allows for dynamic, scriptable rendering of 2D shapes and bitmap images. It is a low level, procedural model that updates a bitmap. HTML5 Canvas also helps in making 2D games.

RDFa or Resource Description Framework in Attributes is a W3C Recommendation that adds a set of attribute-level extensions to HTML, XHTML and various XML-based document types for embedding rich metadata within Web documents. The Resource Description Framework (RDF) data-model mapping enables its use for embedding RDF subject-predicate-object expressions within XHTML documents. It also enables the extraction of RDF model triples by compliant user agents.

<span class="mw-page-title-main">HTML5</span> Fifth and current version of hypertext markup language

HTML5 is a markup language used for structuring and presenting content on the World Wide Web. It is the fifth and final major HTML version that is a World Wide Web Consortium (W3C) recommendation. The current specification is known as the HTML Living Standard. It is maintained by the Web Hypertext Application Technology Working Group (WHATWG), a consortium of the major browser vendors.

The Web Hypertext Application Technology Working Group (WHATWG) is a community of people interested in evolving HTML and related technologies. The WHATWG was founded by individuals from Apple Inc., the Mozilla Foundation and Opera Software, leading Web browser vendors, in 2004.

<span class="mw-page-title-main">Acid3</span> Online HTML rendering test

The Acid3 test is a web test page from the Web Standards Project that checks a web browser's compliance with elements of various web standards, particularly the Document Object Model (DOM) and JavaScript.

<span class="mw-page-title-main">Ian Hickson</span>

Ian "Hixie" Hickson is the author and maintainer of the Acid2 and Acid3 tests, the WHATWG HTML 5 specification, and the Pingback specification, and the early working draft of Web Applications 1.0. He is known as a proponent of Web standards, and has played a crucial role in the development of specifications such as CSS. Hickson was a co-editor of the CSS 2.1 specification.

Extensible HyperText Markup Language (XHTML) is part of the family of XML markup languages. It mirrors or extends versions of the widely used HyperText Markup Language (HTML), the language in which Web pages are formulated.

The HTML5 draft specification adds video and audio elements for embedding video and audio in HTML documents. The specification had formerly recommended support for playback of Theora video and Vorbis audio encapsulated in Ogg containers to provide for easier distribution of audio and video over the internet by using open standards, but the recommendation was soon after dropped.

A web worker, as defined by the World Wide Web Consortium (W3C) and the Web Hypertext Application Technology Working Group (WHATWG), is a JavaScript script executed from an HTML page that runs in the background, independently of scripts that may also have been executed from the same HTML page. Web workers are often able to utilize multi-core CPUs more effectively.

<span class="mw-page-title-main">WebSocket</span> Computer network protocol

WebSocket is a computer communications protocol, providing full-duplex communication channels over a single TCP connection. The WebSocket protocol was standardized by the IETF as RFC 6455 in 2011. The current API specification allowing web applications to use this protocol is known as WebSockets. It is a living standard maintained by the WHATWG and a successor to The WebSocket API from the W3C.

Microdata is a WHATWG HTML specification used to nest metadata within existing content on web pages. Search engines, web crawlers, and browsers can extract and process Microdata from a web page and use it to provide a richer browsing experience for users. Search engines benefit greatly from direct access to this structured data because it allows them to understand the information on web pages and provide more relevant results to users. Microdata uses a supporting vocabulary to describe an item and name-value pairs to assign values to its properties. Microdata is an attempt to provide a simpler way of annotating HTML elements with machine-readable tags than the similar approaches of using RDFa and microformats.

The HTML5 specification introduced the video element for the purpose of playing videos, partially replacing the object element. HTML5 video is intended by its creators to become the new standard way to show video on the web, instead of the previous de facto standard of using the proprietary Adobe Flash plugin, though early adoption was hampered by lack of agreement as to which video coding formats and audio coding formats should be supported in web browsers. As of 2020, HTML5 video is the only widely supported video playback technology in modern browsers, with the Flash plugin being phased out.

<span class="mw-page-title-main">Dave Raggett</span> English computer specialist

Dave Raggett is an English computer specialist who has played a major role in implementing the World Wide Web since 1992. He has been a W3C Fellow at the World Wide Web Consortium since 1995 and worked on many of the key web protocols, including HTTP, HTML, XHTML, MathML, XForms, and VoiceXML. Raggett also wrote HTML Tidy and is currently pioneering W3C's work on the Web of Things. He lives in the west of England.

References

  1. 1 2 Cotton, Paul; Ruby, Sam; Stachiowak, Maciej; Smith, Michael; Berjon, Robin (2014-10-10). "W3C HTML Working Group". W3C. Archived from the original on 2015-10-02. Retrieved 2018-04-03.
  2. "How YOU can join the W3C HTML5 Working Group in 4 easy steps". the paciello group. Steve Faulkner. 2 December 2011. Retrieved 2 December 2011.
  3. Berners-Lee, Tim (1994-07-26), IETF HTML BOF Minutes 26 July 1994, W3c, retrieved 2018-04-02
  4. Raggett, Dave (1998). "A history of HTML". Raggett on HTML. Harlow, Essex: Addison Wesley Longman. Retrieved 2018-04-02.
  5. 1 2 Connolly, Dan (2000-01-31). "IETF HTML Working Group". W3C. Retrieved 2018-04-03.
  6. 1 2 Hoffmann, Markus; Beaumont, Leland R. (2005). Content Networking: Architecture, Protocols, and Practice. Elsevier. p. 294.
  7. 1 2 Guan, Wang. "HTML5:正在发生的未来". China Economic Herald. IT经理世界. Retrieved 13 November 2012.
  8. "The Difference Between the WHATWG and the HTMLWG". WebMonkey. Archived from the original on 18 February 2011.
  9. "HTML is the new HTML5". the WHATWG blog. Ian Hickson. Retrieved 19 January 2011.
  10. "W3C and WHATWG finalize split on HTML5 spec, forking 'unlikely'". The Verge. Jeff Blagdon. 22 July 2012. Retrieved 22 July 2012.
  11. "HTML5 Work Splits Into 'Living' And 'Snapshot' Standards. Developers Need Not Worry, Says Living Standard Leader". techcrunch. Ingrid Lunden (@ingridlunden). 22 July 2012. Retrieved 22 July 2012.
  12. "HTML5 Definition Complete, W3C Moves to Interoperability Testing and Performance". semanticweb. Eric Franzon. Retrieved 17 December 2012.