I Can’t Sleep - HTML | Calm Bedtime Reading for Sleep

Episode Date: December 11, 2023

Relax with this calm bedtime reading as Benjamin explores HTML, the hypertext markup language of the web. It’s designed to help you sleep and ease insomnia. You’ll gently learn how tags, elements, and attributes structure pages, the evolution toward HTML5, and how browsers render content and links. Benjamin’s soothing cadence turns technical ideas into peaceful storytelling that lowers stress and anxiety. No whispering or hypnosis—just simple, fact-filled education to settle your mind. Press play, let your thoughts soften, and drift off while we explore how the internet’s pages are built. Want More? Request a Topic: https://www.icantsleeppodcast.com/request-a-topic Ad-Free Episodes: https://icantsleep.supportingcast.fm/ Shop Sleep-Friendly Products: https://www.icantsleeppodcast.com/sponsors Join the Discussion on Discord: https://discord.gg/myhGhVUhn7 This content is derived from the Wikipedia article on HTML, available under the Creative Commons Attribution-ShareAlike (CC BY-SA) license. Read the full article: Wikipedia – HTML. Happy sleeping! Learn more about your ad choices. Visit megaphone.fm/adchoices

You're listening to a Glassbox media podcast. What if I told you that most of the modern day self-help advice you've been hearing could actually make you worse? The key to a better life isn't about feel-good gimmicks that sound catchy. The Mentally Stronger Podcast gives you access to a licensed therapist who shares science-backed tools that will actually change your life. Hi, I'm Amy Morin, psychotherapist, mental strength trainer, and international best-selling author. In each episode, we cover research-back strategies, like how to stop relying on willpower and start creating habits for lasting change. And the five mental strength-building exercises you can do from your couch.

I also speak to world-class experts like Dr. Nicole Kane, who shares how to permanently heal anxiety by addressing the root cause. With over 200 episodes in our catalog, this podcast is for you if you're ready to crush self-doubt, conquer challenges, and become stronger than ever with therapist-approved strategies that can change your life. Listen to Mentally Stronger with Therapist Amy Morin, wherever you get your podcasts. Welcome to the I Can't Sleep Podcast, where I read random articles from across the web to bore you to sleep with my soothing voice.

I'm your host, Benjamin Boster. Today's episode is from a Wikipedia article titled HTML. 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. Web browsers receive HTML documents from a web server or local storage. and render the documents into multimedia web pages. HTML describes the structure of a web page semantically

and originally included cues for its appearance. HTML elements are the building blocks of HTML pages. With HTML constructs, images, and other objects, such as interactive forms, may be embedded into the rendered page. HTML provides a means to create structured. by denoting structural semantics for text, such as headings, paragraphs, lists, links, quotes, and other items. HTML elements are delineated by tags, written using angle brackets. Tags such as IMG and input directly produce content into the page.

Other tags such as paragraph and close paragraphs surround and provide information, about document text and may include sub-element tags. Browsers do not display the HTML tags, but use them to interpret the content of the page. HTML can embed programs written in a scripting language such as JavaScript, which affects the behavior and content of webpages. The inclusion of CSS defines the look and layout of content. The World Wide Web Consortium, W3C, former maintainer of the HTML and current maintainer of the CSS standards, has encouraged the use of CSS over explicit presentational HTML since 1997.

A form of HTML, known as HTML5, is used to display video and audio, primarily using the canvas element, together with JavaScript. In 1980, physicist Tim Berners-Lee, a contractor at CERN, proposed and prototyped Inquir, a system for CERN researchers to use and share documents. In 1989, Berners-Lee wrote a memo proposing an internet-based hypertext system. Berners-Lee specified HTML and wrote the browser and server software in late 1990. That year, Berners Lee and CERN data systems engineer Robert Kalia collaborated on a joint request for funding, but the project was not formally adopted by CERN.

In his personal notes of 1990, Berners-Lee listed some of the many areas in which hypertext used, an encyclopedia is the first entry. Their first publicly available description of HTML was a document called HTML tags, first mentioned on the internet by Tim Berners-Lee in late 1991. It describes 18 elements comprising the initial, relatively simple design of HTML. Except for hyperlink tag, these were strongly influenced by SGML, an in-house standard generalized market language-based documentation format at CERN.

11 of these elements still exist in HTML4. HTML is a markup language that web browsers use to interpret and compose text, images, and other material into visible or audible web pages. Default characteristics for every item of HTML markup are defined in the browser, and these characteristics can be altered or enhanced by the web page designer's additional use of CSS. Many of the text elements are mentioned in the 1988 ISO Technical Report, TR-9537 techniques for using SGML, which describes the features of early text formatting languages such as that used by the runoff command developed in the early 1960s for the CTSS compatible time sharing system operating system. These formatting commands were derived from the commands used by typesetters to manually format documents. However, the SGML concept of generalized markup is based on elements, nested annotated ranges with attributes rather than merely print effects with separate structure of markup.

HTML has been progressively moved in this direction with CSS. Berners-Lee considered HTML to be an application of SGML. It was formally defined as such by the Internet Engineering Task Force IETF, with the mid-1993 publication of the first proposal for an HTML specification, the hypertext markup language internet draft by Berners Lee and Dan Connolly, which included an SGML document type definition to define the syntax. The draft expired after six months, but was notable for its acknowledgement of the NCSA Mosaic Browser's Custom Tag

for embedding inline images, reflecting the IETF's philosophy of basing standards on successful prototypes. Similarly, Dave Ragget's competing Internet draft HTML Plus hypertext markup format from late 1993 suggested standardizing already implemented features like tables and fill-ups, platforms. After the HTML and HTML Plus drafts expired in early 1994, the IETF created an HTML working group. In 1995, this working group completed HTML 2.0. The first HTML specification intended to be treated as a standard against which future implementations should be based.

Further development under the auspices of the IETF was stalled by competing interests. Since 1996, the HTML specifications have been maintained with input from commercial software vendors by the World Wide Web Consortium. In 2000, HTML became an international standard. HTML 4.01 was published in late 1999 with further errata published through 2001. In 2004, development began on HTML5 in the web hypertext. application technology working group, which became a joint deliverable with the W3C in 2008 and was completed and standardized on the 28th of October 2014. HTML version timeline HTML 2 November 24th, 1995.

HTML 2.0 was published as RFC 1866. Supplemental RFCs added capabilities. November 25th, 1995, RFC 1867, form-based file upload. May, 1996, RFC-1942, Tables. August, 1996, RFC-1980, client-side image maps. January 1997, RFC 2070, Internationalization. January 14, 1997. HTML 3.2 was published as a W3C recommendation.

It was the first version developed and standardized exclusively by the W3C, as the IETF had closed its HTML working group on September 12, 1996. Initially, codenamed Wilbur, HTML 3.2 dropped math formulas entirely, reconciled overlap among various proprietary extensions and adopted most of Netscape's visual markup tags. Netscape's blink element and Microsoft's marquee element were omitted due to a mutual agreement between the two companies. A markup for mathematical formulas, similar to that of HTML,

was standardized 14 months later in MathML, HTML 4, December 18, 1997. HTML 4 was published as a W3C recommendation. It offers three variations. Strict in which deprecated elements are forbidden. Transitional in which deprecated elements are allowed. Frame said in which mostly only frame-related elements are allowed. Initially code-named Cougar, HTML 4.0 adopted many browser-specific element types and attributes, but also sought to phase out Netscape's visual markup features by marking them as deprecated in favor of style sheets. H-TML 4 is an S-GML application conforming to ISO-8879

S-S-GML. April 24 is 1998. H-TML 4.0 was reissued with minor edits without incrementing the version number. December 24th, 1999, HTML 4.01 was published as a W3C recommendation. It offers the same three variations as HTML 4.0, and its last errata were published on May 12, 2001. May 2000, ISO IEC 15445, 2000, ISO-Html based on HTML4. was published as an ISO IEC International Standard. In the ISO, this standard is in the domain of the ISO IEC JTC 1SC34. After HTML 4.01, there were no new versions of HTML for many years

as the development of the parallel XML-based language, X-Html, occupied the W3C's HTML Working Group, HTML 5 October 28, 2014, HTML 5 was published as a W3C recommendation. November 1st, 2016, HTML 5.1 was published as a W3C recommendation. December 14th, 2017, HTML 5.2 was published as a W3C recommendation.

HTML draft version timeline. October 1991. HTML tags, an informal CERN document listing 18 HTML tags was first mentioned in public. June 1992, first informal draft of the HTML DTD with seven subsequent revisions, July 15th, August 6th, August 18th, November 17th, November 19th, November 20th, November 22nd. November 1992, HTML DTD 1.1, the first with a version number based on RCS revisions, which start with 1.1 rather than 1.0, an informal draft. June 1993.

Hypertext markup language was published by the IETF-IIR Working Group as an Internet draft, a rough proposal for a standard. It was replaced by a second version one month later. November 1993, HTML Plus was published by the IETF as an internet draft and was a competing proposal to the hypertext markup language draft. It expired in July 1994. November 1994 First draft, version 0.0 of HTML 2.0 published by IETF itself, called as HTML 2.9,

called as HTML 2.0 from Revision 02. That finally led to the publication of RFC 1866 in November 1995. April 1995, authored March 1995, HTML 3.0 was proposed as a standard for the IETF, but the proposal expired five months later, without further action. It included many of the capabilities that were in Ragged's HTML Plus proposal, such as support for tables, text flow around figures, and the display of complex mathematical formulas. W3C began development of its own arena browser as a testbed for HTML3 and

cascading style sheets, but HTML 3.0 did not succeed for several reasons. The draft was considered very large at 150 pages, and the pace of browser development, as well as the number of interested parties had outstripped the resources of the IETF. Browser vendors, including Microsoft and Netscape at the time, chose to implement different subsets of HTML3's draft features, as well as to introduce their own extensions to it. These included extensions to control stylistic aspects of documents, contrary to the belief of the academic engineering community,

that such things as text color, background texture, font size, and font face, were definitely outside the scope of a language when their only intent was to specify how a document would be organized. Dave Ragget, who has been a W3C fellow for many years, has commented, for example, to a certain extent, Microsoft built its business on the web by extending HTML features. January 2008, HTML5 was published as a working draft by the W3C. Although its syntax closely resembles that of SGML,

HTML5 has abandoned any attempt to be an SGML application and has explicitly defined its own HTML serialization, in addition to an alternative XML-based X-Html5 serialization. 2011 HTML5 Last Call In the 14th of February 2011, the W3C extended the charger of its HTML Working Group with clear milestones for HTML5. In May 2011, the Working Group advanced HTML5 to Last Call, an invitation to communities inside and outside W3C to confirm the technical soundness of the specification. The W3C developed a comprehensive test suite to achieve broad interoperability for the full specification by 2014, which was the target date for recommendation.

In January 2011, the WHATWG renamed its HTML5 Living Standard to HTML. The W3C nevertheless continues its project to release HTML5. 2012 HTML5, candidate recommendation. In July 2012, WHATWG and W3C decided on a degree of separation. W3C will continue with HTML5 specification work, focusing on a single definitive standard, which is considering a snapshot by WHATWG. The WHATWG organization will continue its work with HTML5 as a living standard. living standard. The concept of a living standard is that it is never complete and is always being updated and improved. New features can be added, but functionality will not be removed.

In December 2012, W3C designated HTML5 as a candidate recommendation, the criterion for advancement to W3C recommendation is to 100% complete and fully interoperable implementations. 2014 HTML5 proposed recommendation and recommendation. In September 2014, W3C moved HTML 5 to proposed recommendation. On 28th of October, 2014, HTML5 was released as a stable W3C recommendation, meaning the specification process is complete. X-Html is a separate language that began as a reformulation of HTML 4.01, using XML 1.0.

It is now referred to as the XML syntax for HTML, and no longer being developed as a separate standard. XHtml 1.0 was published as a W3C recommendation on January 2016-2000, and was later revised and republished on August 1, 2002. It offers the same three variations as HTML 4.0 and 4.01. reformulated in XML with minor restrictions. X-Html 1.1 was published as a W3C recommendation on May 31, 2001. It is based on X-Html 1.0 strict, that includes minor changes, can be customized,

and is reformulated using modules in the W3C recommendation, modularization of X-Html, which was published on April 10, 2000. X-Html 2.0 was a working draft. Work on it was abandoned in 2009 in favor of work on HTML 5 and X-Html 5. X-Html 2.0 was incompatible with X-Html 1.X and therefore would be more accurately characterized as an X-Html-inspired new language than an update to X-Html 1.X. 28 of May 2019, the W3C announced that WHATWG would be the sole publisher of the HTML and DOM standards. The W3C and the WHATWG had been publishing competing standards since 2012. While the W3C standard was identical to the WHATWG in 2007, the standards have since progressively diverged due to different design decisions.

HATWG living standard has been the de facto web standard for some time. HTML markup consists of several key components, including those called tags and their attributes, character-based data types, character references, and entity references. HTML tags most commonly come in pairs like H1 and N-H-1, although some represent empty elements and so are unpaired, for example, IMG. The first tag in such a pair is the start tag, and the second is the end tag. They are also called opening tags and closing tags. Another important component is the HTML document type declaration,

which triggers standards mode rendering. The following is an example of a classic Hello World program. Doc type HTML, HTML, head, title, this is a title, this is a type, Title, End title. End head. Body. Div. Paragraph.

Hello world. End paragraph. End div. End body. End. The text between HTML and end HTML describes the web page. And the text between body and end body is the visible page content. The markup text, title, this is a title, end title.

defines the browser page title shown on browser tabs and window titles, and the tag Div defines a division of the page used for easy styling. Between head and endhead, a meta element can be used to define web page metadata. The document type declaration doc type HTML is for HTML5. If a declaration is not included, various browsers will revert to quirks mode for render HTML documents imply a structure of nested HTML elements. These are indicated in the document by HTML tags enclosed in angle brackets. In the simple general case, the extent of an element is indicated by a pair of tags,

a start tag, paragraph, and end tag, n paragraph. The text content of the element, if any, is placed between these tags. Tags may also enclose further tag markup between the start and end, including a mixture of tags and text. This indicates further nested elements as children of the parent element. The start tag may also include the elements attributes within the tag. These indicate other information such as identifiers for sections within the document, identifiers used to bind style information to the presentation of the document, and for some tags such as the image used to embed images,

to reference to the image resource in the format like this. IMG source equals example.com forward slash example.jpg. Some elements such as the line break do not permit any embedded content, either in text or further tags. These require only a single empty tag akin to a start tag and do not use an end tag. Many tags, particularly the closing end tag for the very commonly used paragraph element, are optional. An HTML browser or other agent can infer the closure for the end of an element from the context and the structural rules defined by the HTML standard. These rules are complex and not widely understood by most HTML authors.

The general form of an HTML element is therefore tag, attributes, 1 equals value 1, attribute 2 equals value 2. Content, tag. Some HTML elements are defined as empty elements, and take the form, tag attribute 1 equals value 1, attribute 2 equals value 2. Empty elements may enclose no content, for instance, the break tag or the inline image tag. The name of an HTML element is the name used in the tags. The N tag's name is preceded by a slash character,

and that in empty elements the N tag is neither required nor allowed. If attributes are not mentioned, default values are used in each case. Element examples. Headings HTML headings are defined with the H1 to H6 tags with H1 being the highest or most important level, and H6 the least. CSS can drastically change the rendering.

Paragraphs. Line breaks. The difference between break and paragraph is that break breaks a line without altering the semantic structure of the page, whereas paragraph sections the page into paragraphs. The element break is an empty element in that although it may have attributes, it can take no content and it may not have an end tag.

Inputs. There are many possible ways a user can give inputs, like input type equals text, input type equals file, input type equals checkbox. Comments. Comments can help in the understanding of the markup and do not display in the web page. There are several types of markup elements used in HTML. Structural markup indicates the purpose of text, for example H2, Gulf, Close H2, establishes golf as a second-level heading. Structural markup does not denote any specific rendering, but most web browsers have default styles for element formatting.

Content may be further styled using cascading style sheets, CSS. Presentational markup indicates the appearance of the text, regardless of its purpose. For example, bold text indicates that visual output devices should render, boldface and bold text, but gives a little indication what devices that are unable to do this, such as oral devices that read the text aloud, should do. In the case of both bold text and italic text, there are other elements that may have equivalent visual renderings, but that are more semantic in nature, such as strong text and emphasized text respectively.

It is easier to see how an oral user agent should interpret the latter two elements. However, they are not equivalent to their presentational counterparts. It would be undesirable for a screen reader to emphasize the name of a book, for instance, but on a screen, such a name would be italicized. Most presentational markup elements have become deprecated under the HTML 4.0 specification in favor of using CSS for styling.

Hypertext markup makes parts of a document into links to other documents. An anchor element creates a hyperlibrillment, creates a hyperlink in the document, and its H-RF attribute sets the links target URL. For example, the HTML markup AH-RF equals HTTPS-Colon forward-slash-F-E-N. dot Wikipedia.org forward-slash will render the word Wikipedia as a hyperlink. To render an image as a hyperlink, an image element is inserted as content into the A element. Like break, image is an empty element with attributes, but no content or closing tag. A-H-Ref equals H-T-TPS,

colon, forward-slash-for-slash-example.org, image-source equals image.gif. Alt equals descriptive text, width equals 50, height equals 50, order equals zero. Attributes Most of the attributes of an element are name-value-pary separated by equals, and written within the start tag of an element after the element's name. The value may be enclosed in single or double quotes, although values consisting of certain

characters can be left unquoted in HTML, but not X-Html. Leaving attribute values unquoted is considered unsafe. In contrast with name value pair attributes, there are some attributes that affect the elements simply by their presence in the start tag of the element, like the isMap attribute for the image element. There are several common attributes that may appear in many elements. The ID attribute provides a document-wide unique identifier for an element. This is used to identify the element so that style sheets can alter its presentational properties, and scripts may alter, animate, or delete its content or presentation.

Appended to the URL of the page, it provides a globally unique identifier for the element, typically a subsection of the page. For example, the ID attributes in https colon forward slash fj.org. www.org. forward slash wiki forward slash HTML attributes. The class attribute provides a way of classifying similar elements. This can be used for semantic or presentation purposes. For example, an HTML document might semantically use the designation class equals notation

to indicate that all elements with this class value are subordinate to the main text of the document. In presentation, such elements might be gathered together and presented as footnotes on a page instead of appearing in the place where they occur in the HTML source. Class attributes are used semantically in microformats. Multiple class values may be specified. For example, class equals notation import puts the element into both the notation and the import classes. An author may use the style attribute to assign presentational properties to a particular element. It is considered better practice to use an element's ID or class attributes to select the element from

within a style sheet, though sometimes this can be too cumbersome for a simple, specific, or ad hoc styling. The title attribute is used to attach a subtextual explanation of an element. In most browsers, this attribute is displayed as a tooltip. The Leng attribute identifies the natural language of the element's contents, which may be different from that of the rest of the document. For example, in an English language document, paragraph O.L. Span-L-L-L-L-L-L-L-L-L-L-L-L-L-L-E-L-L-E-L-L-L-E-L-L-L-D-L-L-D, close-Span, close paragraph. The abbreviation element ABBR can be used to demonstrate some of these attributes. Abbreviation ID equals NID, class equals chargon, style equals color purple, title equals hypertext markup language, HTML, close abbreviation.

This example displays as HTML, and most browsers pointing the cursor at the abbreviation should display the title text, hypertext markup language. Most elements take the language-related attribute, EIR, to specify text direction, such as with RTL for right-to-left text in, for example, Arabic, Persian, or Hebrew. Character and Entity References As of Version 4.0, HTML defines a set of 252 character entity references and a set of 1,114,0-50 numeric character references. both of which allow individual characters to be written via simple markup, rather than literally. A literal character and its markup counterpart are considered equivalent and are rendered identically.

The ability to escape characters in this way allows for the characters less than and anpersan when written as ampersen-l-t-semi-colon and ampersan amp-p-m-psey-micolon, to be interpreted as character data rather than markup. For example, a literal less-than normally indicates the start of a tag, and ampersan normally indicates the start of a character entity reference or numeric character reference, writing it as ampersan ampersan amp semicolon, or ampersan hashtag x26 semicolon, or ampersan hashtag 38 semicolon,

allows ampersand to be included in the content of an element or in the value of an attribute. The double quote character, when not used to quote an attribute value, must also be escaped as ampersan quote, semicolon, or ampersan hashtag X22 semicolon, or ampersan hashtag 34 semicolon, when it appears within the attribute value itself. Equivalently, the single quote character, when not used to quote an attribute value, must also be escaped as anper-sand-h-h-T-T-T-S-27-colon or ampersan-h-T-N-P-A-P-O-S-P-E-L-S-E-L-P

when it appears within the attribute value itself. If document authors overlook the need to escape such characters, Some browsers can be very forgiving and try to use context to guess their intent. The result is still invalid markup, which makes the document less accessible to other browsers and other user agents that may try to parse the document for search and indexing purposes, for example. Escaping also allows for characters that are not easily typed or that are not available in the document's character encoding

to be represented within the element and attribute content. For example, the acute accented E, a character typically found only on Western European and South American keyboards, can be written in any HTML document as the entity reference ampersan E acute, semicolon, or as the numeric reference, ampersan hashtag XE9, semicolon, or ampersan hashtag 233, semicolon. using characters that are available on all keyboards and are supported in all character encodings.

Unicode character encoding such as UTF8 are compatible with all modern browsers and allow direct access to almost all the characters of the world's writing systems. Data types HTML defines several data types for element content, such as script data and style sheet data, and a plethora of types for attribute values, including IDs, names, URIs, numbers, units of length, languages, media descriptors, colors, character encodings, dates and times, and so on. All of these data types are specializations of character data.

Document type declaration HTML documents are required to start with a document type declaration, informally a doc type. In browsers, the dock type helps to define the rendering mode, particularly whether to use quirks mode. The original purpose of the dock type was to enable the parsing and validation of HTML documents by SGML tools, based on the document type definition, DTD. The DTD, to which the doc type refers, contains a machine-readable grammar specifying the permitted and prohibited content for a document, conforming to such a DTD. browsers, on the other hand, do not implement HTML as an application of SGML, and as consequence, do not read the DTT. HTML 5 does not define a DDD, therefore in HTML 5, the docktype declaration is simpler and shorter. Doc type HTML.

For example, an HTML 4 doc type. doc type HTML Public dash forward slash forward slash W3C forward slash forward slash DTD HTML 4.01 forward slash foresl forward slash EN H TPS colon forward slash forward slash www.w.w.w3.org forward slash TR forward slash HTML4 forward slash strict dot DTD. This declaration references the DTD for the strict version of HTML 4.01.

STML-based validators read the DTD in order to properly parse the document and to perform validation. In modern browsers, a valid doc type activates standards mode as opposed to quirks mode. In addition, HTML 4.01 provides transitional and frame-set DTDs as explained below. The transitional type is the most inclusive, incorporating current tags as well as older or deprecated tags, with the strict DTD excluding deprecated tags. The frame set has all tags necessary to make frames on a page along with the tags included in transitional type. Semantic HTML

Symantec HTML is a way of writing HTML that emphasizes the meaning of the encoded information over its presentation or look. HTML has included semantic markup from its inception, but has also included presentational markup such as font, italics, and center tags. There are also the semantical neutral div and span tags. Since the late 1990s, when cascading style sheets were beginning to work in most browsers, web authors have been encouraged to avoid the use of presentational. HTML markup with a view to the separation of content and presentation.

In a 2001 discussion of the semantic web, Tim Berners-Lee and others gave examples of ways in which intelligent software agents may one day automatically crawl the web and find, filter, and correlate previously unrelated published facts for the benefit of human users. Such agents are not commonplace even now, but some of the ideas of the ideas of the Web 2.0 mashups and price comparison websites may be coming close. The main difference between these web application hybrids and Berners-Lee's semantic agents lies in the fact that the current aggregation and hybridization of information is usually designed by web developers, who already know the web locations and the API semantics of

the specific data they wish to mash, compare, and combine. An important type of web agent that does crawl and read web pages automatically without prior knowledge of what it might find is the web crawler or search engine spider. These software agents are dependent on the semantic clarity of web pages they find as they use various techniques and algorithms to read and index millions of web pages a day and provide web users with search facilities without which the World Wide Web's usefulness would be greatly reduced. In order for search engine spiders to be able to rate the significance of pieces of text they find in HTML documents, and also for those creating mashups and other hybrids as well as for more automated agents as they are developed, the semantic structures that exist in HTML need to be widely and uniformly applied to bring out the meaning of the published text. Presentational markup tags are deprecated in current HTML and N. X HTML recommendations.

A majority of presentational features from previous versions of HTML are no longer allowed, as they lead to poor accessibility, higher cost of site maintenance, and larger document sizes. Good semantic HTML also improves the accessibility of web documents.

For example, when a screen reader or audio browser can correctly ascertain the structure of a document, it will not waste the visually impaired user's time by reading out repeated or irrelevant information when it has been marked up correctly. HTML documents can be delivered by the same means as any other computer file. However, they are most often delivered either by HTTP from a web server or by email. The World Wide Web is composed primarily of HTML documents transmitted from web servers to web browsers, using the hypertext transfer protocol, HTTP.

However, HTTP is used to serve images, sound, and other content in addition to HTML. To allow the web browser to know how to handle each document it receives, other information is transmitted along with the document. This metadata usually includes the M-I-M-E type, e.g. text forward slash HTML or application forward slash Xhtml plus XML and the character encoding. In modern browsers, the mime type that is sent with the HTML document may affect how the document is initially interpreted. A document sent with the X HTML mime type is expected to be well-formed XML. Syntax errors may cause the browser to fail to render it.

The same documents sent with the HTML mime type might be displayed successfully since some browsers are more lenient with HTML. The W3C recommendations state that XHtml 1.0 documents that follow guidelines set forth in the recommendations Appendix C may be labeled with either mime type. XHtml 1.1 also states that XHtml 1.1 documents should be labeled with either mime type. their mime type. Most graphical email clients allow the use of a subset of HTML, often ill-defined, to provide formatting and semantic markup not available with plain text. This may include typographic information like colored headings, emphasized in quoted text, inline images, and diagrams. Many such clients include both a GUI editor for composing HTML email messages and a rendering engine for for displaying them.

Use of HTML and email is criticized by some because of compatibility issues, because it can help disguise fishing attacks, because of accessibility issues for blind or visually impaired people, because it can consume spam filters, and because the message size is larger than plain text. The most common file name extension for files containing HTML is dot HTML. A common abbreviation of this is dot-html. H-TM, which originated because some early operating systems and file systems such as DOS and the limitations imposed by FAT data structure, limited file extensions to three letters.

An HTML application, HTA, file extension.hda, is a Microsoft Windows application that uses HTML and dynamic HTML in a browser to provide the application's graphical interface. A regular HTML file is confined to the security model of the web browser's security, communicating only to web servers, and manipulating only web page objects and site cookies. NHTA runs as a fully trusted application and therefore has more privileges, like creation, editing, removal of files, and Windows registry entries. Because they operate outside the browser's security model, HTAs can be executed via HTTP, but must be downloaded, just like an EXE file,

and executed from local file system. Since its inception, HTML and its associated protocols gained acceptance relatively quickly. However, no clear standards existed in the early years of the language, though its creators originally conceived of HTML as a semantic language, language devoid of presentation details. Practical uses pushed many presentational elements and attributes into the language, driven largely by the various browser vendors. The latest standards surrounding HTML reflect efforts to overcome the sometimes chaotic development of the language, and to create a rational foundation for

building both meaningful and well-presented documents. To return HTML to its role as semantic language, the W3C has developed style languages such as CSS and XSL to shoulder the burden of presentation. In conjunction, the HTML specification has slowly reigned in the presentation elements. There are two axes differentiating various variations of HTML, as currently specified. SGM-based HTML versus XML-based HTML, referred to as X-Html, on one axis, and strict versus transitional, loose versus frame set on the other axis.