World Library  
Flag as Inappropriate
Email this Article

HTML5 video

Article Id: WHEBN0026099252
Reproduction Date:

Title: HTML5 video  
Author: World Heritage Encyclopedia
Language: English
Subject: HTML5 Audio, Internet Explorer 9, Comparison of layout engines (HTML5), HTML, WebGL
Collection: Html5
Publisher: World Heritage Encyclopedia

HTML5 video

The HTML5 specification introduced the video element for the purpose of playing videos,[1] partially replacing the object element. HTML5 video is intended by its creators to become the new standard way to show video on the web without plugins, instead of the previous de facto standard of using the proprietary Adobe Flash plugin, but has been hampered by lack of agreement as to which video coding formats should be supported in web browsers.


  • History of 1
  • 2
    • Multiple sources 2.1
  • Supported video formats 3
    • Free formats 3.1
      • MPEG-DASH Support via the HTML5 Media Source Extentions (MSE) 3.1.1
      • Google's purchase of On2 3.1.2
    • Non-free formats 3.2
      • Cisco makes a licensed H.264 binary module available for free 3.2.1
  • Browser support 4
  • Digital rights management (Encrypted Media Extensions) 5
  • Usage 6
  • See also 7
  • References 8
  • External links 9

History of


The following HTML5 code fragment will embed a WebM video into a web page.

The "controls" attribute enables the browser's own user interface for controlling playback. Alternatively, playback can be controlled with JavaScript, which the web designer can use to create a custom user interface. The optional "poster" attribute specifies an image to show in the video's place before playback is started. Its purpose is to be representative of the video.

Multiple sources

Video format support varies among browsers (see below), so a web page can provide video in multiple formats. For other features, browser sniffing is used sometimes, which may be error-prone: any web developer's knowledge of browsers will inevitably be incomplete or not up-to-date. The browser in question "knows best" what formats it can use. The "video" element supports fallback through specification of multiple sources. Using any number of elements, as shown below, the browser will choose automatically which file to download. Alternatively, the JavaScript canPlayType() function can be used to achieve the same. The "type" attribute specifies the MIME type and possibly a list of codecs, which helps the browser to determine whether it can decode the file. Even with only one choice, such hints may be necessary to a browser for querying its multimedia framework for third party codecs.

Supported video formats

The HTML5 specification does not specify which video formats browsers should support. User agents are free to support any video formats they feel are appropriate, but content authors cannot assume that any video will be accessible by all complying user agents, since user agents have no minimal set of video formats to support.

The HTML5 Working Group considered it desirable to specify at least one video format which all user agents (browsers) should support. The ideal format in this regard would:

  • Have good compression, good image quality, and low decode processor use.
  • Be royalty-free.
  • In addition to software decoders, a hardware video decoder should exist for the format, as many embedded processors do not have the performance to decode video.

Initially, Ogg Theora was the recommended standard video format in HTML5, because it was not affected by any known patents. But on December 10, 2007, the HTML5 specification was updated,[6] replacing the reference to concrete formats:

User agents should support Theora video and Vorbis audio, as well as the Ogg container format.

with a placeholder:[7]

It would be helpful for interoperability if all browsers could support the same codecs. However, there are no known codecs that satisfy all the current players: we need a codec that is known to not require per-unit or per-distributor licensing, that is compatible with the open source development model, that is of sufficient quality as to be usable, and that is not an additional submarine patent risk for large companies. This is an ongoing issue and this section will be updated once more information is available.[8]

The result has been the polarisation of HTML5 video between ISO-defined but patented formats, and free, open formats.

Free formats

Although Theora is not affected by known non-free patents, Apple[9] has expressed concern about unknown patents that might affect it, whose owners might be waiting for a corporation with extensive financial resources to use the format before suing.[10][11] Formats like H.264 might also be subject to unknown patents in principle, but they have been deployed much more widely and so it is presumed that any patent-holders would have already made themselves known. Apple has also opposed requiring Ogg format support in the HTML standard (even as a "should" requirement) on the grounds that some devices might support other formats much more easily, and that HTML has historically not required particular formats for anything.[11]

Some web developers criticized the removal of the Ogg formats from the specification.[12] A follow-up discussion also occurred on the W3C questions and answers blog.[13]

Mozilla and Opera support only the open formats of Theora and WebM. Google stated its intention to remove support for H.264 in 2011, specifically for the HTML5 video tag.[14] Although it has been removed from Chromium, it has yet to be removed from Google Chrome over a year later.[15]

MPEG-DASH Support via the HTML5 Media Source Extentions (MSE)

The adaptive bitrate streaming standard MPEG-DASH can be used in Web browsers via the HTML5 Media Source Extensions (MSE)[16] and JavaScript-based DASH players. Such players are, e.g., the open-source project dash.js[16] of the DASH Industry Forum, but there are also products such as bitdash[17] (using HTML5 with JavaScript, but also a Flash-based DASH players for legacy Web browsers not supporting the HTML5 MSE).

Google's purchase of On2

Google's acquisition of On2 in 2010 resulted in its acquisition of the VP8 video format. Google has provided a royalty-free license to use VP8.[18] Google also started WebM, which combines the standardized open source VP8 video codec with Vorbis audio in a Matroska based container. The opening of VP8 was welcomed by the Free Software Foundation.[19]

When Google announced in January 2011 that it would end native support of H.264 in Chrome,[20] criticism came from many quarters including Peter Bright of Ars Technica[21] and Microsoft web evangelist Tim Sneath, who compared Google's move to declaring Esperanto the official language of the United States.[22] However, Haavard Moen of Opera Software strongly criticized the Ars Technica article[23] and Google responded to the reaction by clarifying its intent to promote WebM in its products on the basis of openness.[14]

After the launch of WebM, Mozilla and Opera have called for the inclusion of VP8 in HTML.[24]

On March 7, 2013, Google Inc. and MPEG LA, LLC announced agreements covering techniques that "may be essential" to VP8, with Google receiving a license from MPEG LA and 11 patent holders, and MPEG LA ending its efforts to form a VP8 patent pool.[25][26][27][28]

Non-free formats

H.264/MPEG-4 AVC is widely used, and has good speed, compression, hardware decoders, and video quality, but is patent-encumbered.[29] Users of H.264 need licenses either from the individual patent holders, or from the MPEG LA, a group of patent holders including Microsoft and Apple, except for some Internet broadcast video uses.[30] H.264 is usually used in the MP4 container format, together with Advanced Audio Coding (AAC) audio. AAC is also patented in itself, so users of MP4 will have to license both H.264 and AAC.

In June 2009, the WHATWG concluded that no existing format was suitable as a specified requirement.[31]

Apple and Microsoft support only H.264.

Cisco makes a licensed H.264 binary module available for free

On October 30, 2013, Cisco announced that they were making a binary H.264 module available for download. Cisco will pay the costs of patent licensing for those binary modules when downloaded by the using software while it is being installed, making H.264 free to use in that specific case.[32]

In the announcement, Cisco cited its desire of furthering the use of the WebRTC project as the reason, since WebRTC's video chat feature will benefit from having a video format supported in all browsers.[33] The H.264 module will be available on "all popular or feasibly supportable platforms, which can be loaded into any application".[34]

Cisco is also planning to publish source code for those modules under BSD license, but without paying the royalties,[32] so the code will practically be free software only in countries without H.264 software patents, which has already been true about other existing implementations.

Also on October 30, 2013, Mozilla's Brendan Eich announced that Firefox would automatically download Cisco's H.264 module when needed by default. He also noted that the binary module is not a perfect solution, since users do not have full free software rights to "modify, recompile, and redistribute without license agreements or fees". Thus Xiph and Mozilla continue the development of Daala.[34][35]

The release concerns only H.264 video and not AAC audio formats, since "the standards bodies have aligned on Opus and G.711 as the common audio codecs for WebRTC".[33] So software to play MP4 video (H.264+AAC) is still not freely (as in beer) available, and there is doubt as to whether a capped global licensing like like Cisco's for H.264 can be created.[34][36]

Browser support

This table shows which video formats are likely to be supported by a given user agent. Most of the browsers listed here use a multimedia framework for decoding and display of video, instead of incorporating such software components. It is not generally possible to tell the set of formats supported by a multimedia framework without querying it, because that depends on the operating system and third party codecs.[37] In these cases, video format support is an attribute of the framework, not the browser (or its layout engine), assuming the browser properly queries its multimedia framework before rejecting unknown video formats. In some cases, the support listed here is not a function of either codecs available within the operating system's underlying media framework, or of codec capabilities built into the browser, but rather could be by a browser add-on that might, for example, bypass the browser's normal HTML parsing of the

The video format can be specified by MIME type in HTML (see example). MIME types are used for querying multimedia frameworks for supported formats.[38]

Of these browsers, only Firefox and Opera employ libraries for built-in decoding. In practice, Internet Explorer and Safari can also guarantee certain format support, because their manufacturers also make their multimedia frameworks. At the other end of the scale, Konqueror has identical format support to Internet Explorer when run on Windows, and Safari when run on Mac, but the selected support here for Konqueror is the typical for GNU/Linux, where Konqueror has most of its users. In general, the format support of browsers is much dictated by conflicting interests of vendors, specifically that Media Foundation and QuickTime support commercial standards, whereas GStreamer and Phonon cannot legally support other than free formats by default on the free operating systems that they are intended for.[39]
Browser Operating system Latest stable release Video formats supported
Theora H.264 (MP4) VP8 (WebM) VP9 (WebM)
Android browser Android 4.4.4 "KitKat" (June 19, 2014 (2014-06-19)) [40] 2.3[41] 3.0[41] 2.3[41] No
Chromium Unix-like and Windows N/A r18297[42] Manual install[note 1][44] r47759[45] r172738[46]
Google Chrome
Windows, OS X, Linux

39.0.2171.71 (November 25, 2014 (2014-11-25)[47])

3.0[48][49] 3.0[49][note 2] 6.0[51][52] 29.0[note 3]
Internet Explorer Windows 11.0.12 (v11.0.9600.17278)[55] (9 September 2014 (2014-09-09)[56]) Manual install 9.0[57] Manual install No
Windows Phone 11.0 (November 21, 2012 (2012-11-21)) No 9.0[58] No
Windows RT 10.0 10.0[58]
Konqueror All supported 4.14.2 (October 14, 2014 (2014-10-14)) [59] 4.4[note 4]
Mozilla Firefox Windows 7+

34.0.5 (December 1, 2014 (2014-12-01)[61])
ESR 31.3.0 (December 1, 2014 (2014-12-01)[62])

3.5[63] 21.0[note 5] 4.0[66][67] 28.0[68][69]
Windows Vista 22.0[70]
Windows XP manual install[71][note 6]
Linux 26.0 (using GStreamer)[note 7]
Android 17.0[75]
OS X 34.0[76]
Firefox OS 1.1[77]

26.0.1656.86386 (December 1, 2014 (2014-12-01)[78])

Symbian S60

12.0.22 (June 24, 2012 (2012-06-24)[79])

Windows Mobile

10.0 (March 16, 2010 (2010-03-16)[80])

No 11.50 15.0 16.0
Windows, OS X, Linux

26.0.1656.32 (December 3, 2014 (2014-12-03)[81])

10.50[82] 24.0[83] 10.60[84][85] No
Safari iOS
for OS X Yosemite

8.0 (October 16, 2014 (2014-10-16)[86])

for OS X Mavericks

7.1 (September 18, 2014 (2014-09-18)[87])

for OS X Mountain Lion

6.2 (September 18, 2014 (2014-09-18)[87])

No 3.1[88][89] No No
OS X Manual install Manual install[90]
Web (previously Epiphany) All supported 3.14.2 (November 13, 2014 (2014-11-13)) [91]

2.28[note 8]
  1. ^ Third-party codec packages are available.[43]
  2. ^ On 11 January 2011 the removal of support for H.264 was announced on Chromium Blog.[50] As of 8 September 2012 neither actual support was removed, nor the change to this plan was announced.
  3. ^ VP9 support in 25, turned off by default.[53] Enabled by default in version 29.[54]
  4. ^ Any format supported by Phonon on Qt 4.5.[60] Any format supported by Phonon backend. Available Phonon backends include DirectShow, QuickTime, GStreamer and xine; backends using MPlayer and VLC are in development.
  5. ^ As of version 20, prefed off by default.[64] Enabled by default beginning in version 21.[65]
  6. ^ DivX supports HTML5 integration only in Web Player version 2.x.[72]
  7. ^ Disabled by default until version 26.[73] Also, depends on the codec on the system.[74]
  8. ^ Any format supported by GStreamer on Webkit/GTK+.[92] The support for Ogg Theora, WebM and h.264 formats is included with base, good, and bad plugins respectively.[93]

Digital rights management (Encrypted Media Extensions)

HTML has support for digital rights management (DRM, restricting how content can be used) via the HTML5 Encrypted Media Extensions (EME). The addition of DRM is controversial because it allows restricting users' freedom to use media restricted by DRM, even where fair use gives users the legal right to do so.[94] A main argument in W3C's approval of EME was that the video content would otherwise be delivered in plugins and apps, and not in the web browser.[95]

In 2013 Netflix added support for HTML5 video using EME, beside their old delivery method using a Silverlight plugin (also with DRM).[96]


As of April 2010, in the wake of Apple iPad launch, a number of high-profile sites have started to serve H.264 HTML5 video instead of Flash for user-agents identifying as iPad.[97]

As of May 2010, HTML5 video is not currently as widespread as Flash videos, though recent rollouts of experimental HTML5-based video players from DailyMotion (using Ogg Theora and Vorbis format),[98] YouTube (using the H.264 and WebM formats),[99] and Vimeo (using the H.264 format)[100] suggest that interest in adopting HTML5 video is increasing.

Some major video-providing websites have announced decisions to continue using technologies other than HTML5 video.[101][102][103] According to a YouTube blog post from June 2010, the

On January 11, 2011, Google's Chromium Project announced on their blog that support for closed codecs (particularly H.264) would be removed from future releases of Chrome. The Chromium announcement specifically mentioned that this removal was an effort to increase the use of license-free HTML5 and the

See also


  1. ^ "The video element". HTML5: A vocabulary and associated APIs for HTML and XHTML.  
  2. ^ van Kesteren, Anne (28 February 2007). "[whatwg]
  3. ^ "Browser War: Episode II – Attack of the DOMs". Retrieved 10 April 2012. 
  4. ^ "SV Web Builders Event – World Premier of Opera with builtin video support". Retrieved 10 April 2012. 
  5. ^ "A Call for Video on the Web". Retrieved 10 April 2012. 
  6. ^ Hickson, Ian (10 December 2007). "Video codec requirements changed". What WG mailing list. Retrieved 2008-02-25.
  7. ^ "(X)HTML5 Tracking".  
  8. ^ Amador, Manuel (2011-12-11). "Removal of Ogg is *preposterous*". . Retrieved 2009-08-25.
  9. ^ "Steve Jobs: mystery patent pool to attack Ogg Theora". The Register. Retrieved 9 July 2011. 
  10. ^ Hickson, Ian (2007-12-11). "Re: Removal of Ogg is *preposterous*". . Retrieved 2008-02-25.
  11. ^ a b Stachowiak, Maciej (2007-03-21). "Codecs (was Re: Apple Proposal for Timed Media Elements)". WHATWG mailing list.
  12. ^ "[whatwg] Removal of Ogg is *preposterous*". . Retrieved 2009-08-25.
  13. ^ Connolly, Dan (December 18, 2007). "When will HTML 5 support
  14. ^ a b Jazayeri, Michael 'Mike' (2011-01-14). "More about the Chrome HTML Video Codec Change".  
  15. ^ Shankland, Stephen (2012-03-14). "Mozilla execs capitulate in H.264 Web-video war". CNET. 
  16. ^ a b HTML5 MSE
  17. ^ bitdash MPEG-DASH Player (HTML5 & Flash)
  18. ^ Google. "Additional IP Rights Grant (Patents)". Google. 
  19. ^ Lee, Matt (May 19, 2010). "Free Software Foundation statement on WebM and VP8".  
  20. ^ Jazayeri, Michael 'Mike'. "HTML Video Codec Support in Chrome". The Chromium Blog. 
  21. ^ Bright, Peter (2011-01-12). "Google's dropping H.264 from Chrome a step backward for openness".  
  22. ^ Sneath, Tim (2011-01-11). "An Open Letter from the President of the United States of Google".  
  23. ^ Moen, Haavard K (2011-01-13). "Is the removal of H.264 from Chrome a step backward for openness?".  
  24. ^ Metz, Cade (2010-05-28). "Mozilla and Opera call for Google open codec in HTML5 spec". The Register. 
  25. ^ djwm (2013-03-07). "Google and MPEG LA make a deal over VP8 codec - Update".  
  26. ^
  27. ^ "VP8 and MPEG LA". WebM Project blog. 2013-03-07. Retrieved 2013-04-03. 
  28. ^
  29. ^ "AVC/H.264 Patent List" (PDF). MPEG LA. 2010-02-01. 
  30. ^ AVC/H.264 Licensors,  
  31. ^ Hickson, Ian (2009-06-29). "Codecs for
  32. ^ a b
  33. ^ a b "Open-Sourced H.264 Removes Barriers to WebRTC". Cisco. 2013-10-30. Retrieved 2013-10-30. 
  34. ^ a b c Brendan Eich (2013-10-30). "Cisco’s H.264 Good News". Brendan Eich's blog. 
  35. ^ Monty Montgomery. "Comments on Cisco, Mozilla, and H.264". Monty Montgomery blog. 
  36. ^
  37. ^ "Phonon documentation of backends", Qt, Nokia, retrieved 2011-06-03 
  38. ^ "Phonon documentation of querying", Qt, Nokia, retrieved 2011-06-03 
  39. ^ "GNU GPL - GNU General Public License Version 3 Free Software Foundation", 29 June 2007, retrieved 2013-04-27 
  40. ^ "Google Rolling Out Android 4.4.4 Update (KTU84P) With A Security Fix, Factory Images/Binaries Up For Nexus Devices". 2014-06-19. Retrieved 2014-08-03. 
  41. ^ a b c Kyrnin, Jennifer, Understanding HTML5 Video Formats, About, retrieved 2012-01-01 
  42. ^ Issue 4363: [HTML5-Video] Enable HTML5 video/audio elements, Google, retrieved 2010-09-10 
  43. ^ "Get Chromium on Ubuntu To Play MP4, H.264, MP3 & view PDF files natively", OMG Ubuntu, 2010-11-21, retrieved 2011-11-12 
  44. ^
  45. ^ "Issue 2093007: Chromium side changes for enabling VP8 and WebM support", Code review, Google, retrieved 2010-09-10 
  46. ^
  47. ^ "Stable Channel Update". Chrome Releases.  
  48. ^ "Google Chrome support Theora and Vorbis", Code, Google, 2010-05-20 
  49. ^ a b Google Chrome 3.0 will support ,  
  50. ^ Mike, Jazayeri (11 January 2011). "Chromium Blog: HTML Video Code Support in Chrome". The Chromium Blog. Retrieved 22 April 2012. 
  51. ^ Bankoski, Jim (2010-05-19), "WebM and VP8 land in Chromium", Chromium ( 
  52. ^ Kersey, Jason (2010-06-03), "Dev Channel Update", Chrome Releases, Google, retrieved 2010-07-01 
  53. ^ Chrome Adds Support for the Next-Generation VP9 Video Codec and Mozilla's Opus Audio 
  54. ^ Chrome Now Supports Google's Next-Gen VP9 Video Codec by Default 
  55. ^ "Microsoft Has Just One Critical Patch in September Patch Tuesday".  
  56. ^ "Microsoft Security Bulletin MS14-052 - Critical Cumulative Security Update for Internet Explorer (2977629)". Security TechCenter.  
  57. ^ McCracken, Harry (2010-03-16), Microsoft Previews the Revamped Internet Explorer 9 Platform, Technologizer 
  58. ^ a b HTML5 Video Support in IE9 Mobile, Microsoft, 2011-10-13, retrieved 2014-03-11 
  59. ^ "KDE Ships Applications and Platform 4.14.2".  
  60. ^ Vestbø, Tor Arne (2008-05-13), Top Secret, Hush Hush!, Nokia, retrieved 2010-03-14 
  61. ^ "Firefox — Notes (34.0.5) — Mozilla".  
  62. ^ "Firefox — Notes (31.3.0) — Mozilla".  
  63. ^ Firefox 3.5 (release notes), Mozilla, 2009-06-30, retrieved 2010-02-15 
  64. ^ Bug 799315 – Windows Media Foundation backend for media playback, Mozilla, retrieved 2012-12-21 
  65. ^ Bug 837859 – Enable WMF backend, Mozilla, retrieved 2013-04-05 
  66. ^ Bug 566243 – Merge mozilla-webmedia repository to mozilla-central, Mozilla 
  67. ^ Firefox Nightly Builds, Mozilla 
  68. ^ [Phoronix] Mozilla Firefox Enables VP9 Video Codec By Default, Phoronix, retrieved 2013-12-08 
  69. ^
  70. ^ Bug 825153 - Add support for Windows Vista WMF and prepend the system32 directory path to dll names, Mozilla, retrieved 2013-03-28 
  71. ^
  72. ^
  73. ^ Bug 886181 - Pref on gstreamer backend, Mozilla, retrieved 2013-09-21 
  74. ^ Bug 794282 - Enable GStreamer in official builds, Mozilla, retrieved 2013-06-23 
  75. ^
  76. ^ Bug 1070703 - Add mp4 support in 10.6 and 10.7 on Aurora, Mozilla, retrieved 2014-10-02 
  77. ^
  78. ^ "Opera browser for Android". 2014-12-01. Retrieved 2014-12-03. 
  79. ^ "Opera Mobile 12.0.2 for S60". 2012-06-24. Archived from the original on 2014-02-25. Retrieved 2014-10-16. 
  80. ^ "No mobile phone left behind: Opera Mini 5 and Opera Mobile 10 introduced in final, consumer-ready versions". 2010-03-16. Retrieved 2014-10-16. 
  81. ^ "Opera 26 for computers: My way to share bookmarks". 2014-12-03. Retrieved 2014-12-03. 
  82. ^ Jägenstedt, Philip (2009-12-31), "(re-)Introducing  
  83. ^
  84. ^ Lie, Håkon Wium (2010-05-19), Welcome, WebM , Opera 
  85. ^ Mills, Chris (2010-05-19), Opera supports the WebM video format, Opera 
  86. ^ "Apple - Safari - Browse the web in smarter, more powerful ways.".  
  87. ^ a b "About the security content of Safari 6.2 and Safari 7.1".  
  88. ^ "HTML5 video formats", Web design, About .
  89. ^ "Media formats supported by the HTML audio and video elements", Developer, Mozilla .
  90. ^ "WebM plugin available", Code, Google, retrieved 2011-06-23 
  91. ^ "GNOME 3.14.2 is out". GNOME mailing list. November 13, 2014. Retrieved November 13, 2014. 
  92. ^ Persch, Christian (April 1, 2008), "The Future of Epiphany" (announcement), epiphany mailing list-list 
  93. ^ "Overview of available plug-ins",  
  94. ^
  95. ^
  96. ^
  97. ^ "iPad-ready websites". Apple. Retrieved 2010-04-05. 
  98. ^ "Watch Video…without Flash". Dailymotion. 2009-05-27. Retrieved 2010-05-18. 
  99. ^ Carle, Kevin; Zacharias, Chris (2010-01-20). "Introducing YouTube HTML5 Supported Videos". Youtube. Google. Retrieved 2010-03-07. 
  100. ^ Dougherty, Brad (2010-01-21). "Try our new HTML5 player!". Vimeo. Retrieved 2010-03-07. 
  101. ^ Herrman, Johan (2010-02-03). "Giz Explains: Why HTML5 Isn't Going to Save the Internet".  
  102. ^ a b "Netflix has no plans to use HTML5", Gigaom .
  103. ^ "Why HTML5 won't replace Flash", Pseudocoder .
  104. ^ "Flash and the HTML5  
  105. ^ "Pardon Our Dust  
  106. ^ "PCMag", PC Magazine  .
  107. ^ Caldato, Claudio (2011-02-02). "Greater Interoperability for Windows Customers With HTML5 Video" (blog).  

External links

  • "HTML5 – The Video Element", What WG, W3C .
  • Daoust, Francois; Hoschka, Philipp; Patrikakis, Charalampos Z (2010), Towards Video on the Web with HTML5 ( .
  • Lawson, Bruce; Lauke, Patrick H. (2010-02-11), Introduction to HTML5 video, Opera .
  • HTML5 Video  video platform software and news.
  • Pieters, Simon (2010-03-03), Everything you need to know about HTML5 video and audio, Opera 
  • HTML5 Video: A Practical Guide: Convert, Embed, Javascript and Flash Fallback for HTML5 Videos
  • Mozilla's overview of media formats supported by browsers
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.