Community hub
0 subscribers7 pages, 0 posts
Recent from talks
Be the first to start a discussion here.
Be the first to start a discussion here.
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
Welcome to the community hub built to collect knowledge and have discussions related to Web platform.
Nothing was collected or created yet.
Web platform
View on Wikipediafrom Wikipedia
The Web platform is a collection of technologies developed as open standards by the World Wide Web Consortium and other standardization bodies such as the Web Hypertext Application Technology Working Group, the Unicode Consortium, the Internet Engineering Task Force, and Ecma International.[1] It is the umbrella term introduced by the World Wide Web Consortium, and in 2011 it was defined as "a platform for innovation, consolidation and cost efficiencies" by W3C CEO Jeff Jaffe.[2] Being built on The evergreen Web (where rapid, automatic software updates, vendor co-operation, standardization, and competition take place) has allowed for the addition of new capabilities while addressing security and privacy risks. Additionally, developers are enabled to build interoperable content on a cohesive platform.[3]
The Web platform includes technologies—computer languages and APIs—that were originally created in relation to the publication of Web pages. This includes HTML,[4] CSS, SVG, MathML,[5] WAI-ARIA, ECMAScript, WebGL, Web Storage, Indexed Database API, Web Components, WebAssembly, WebGPU, Web Workers, WebSocket, Geolocation API, Server-Sent Events, DOM Events, Media Fragments, XMLHttpRequest, Cross-Origin Resource Sharing, File API, RDFa, WOFF, HTTP, TLS 1.2, and IRI.[6][7]
Platforms
[edit]HTML
[edit] | This article contains instructions or advice. (November 2025) |
| HTML |
|---|
 |
| HTML and variants |
| HTML elements and attributes |
| Editing |
| Character encodings and language |
| Document and browser models |
| Client-side scripting and APIs |
| Graphics and Web3D technology |
| Comparisons |
Hypertext Markup Language (HTML) is the standard markup language[a] for documents designed to be displayed in a web browser. It defines the content 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 from 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 documents 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 introduce content into the page. Other tags such as <p> and </p> 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 web pages. 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.[update][9] A form of HTML, known as HTML5, is used to display video and audio, primarily using the <canvas> element, together with JavaScript.
CSS
[edit]Cascading Style Sheets (CSS) is a simple mechanism for adding style (e.g., fonts, colors, spacing) to Web documents.[10]
Scalable Vector Graphics
[edit]| Scalable Vector Graphics |
|---|
|
|
Scalable Vector Graphics (SVG) is an XML-based vector graphics format for defining two-dimensional graphics, having support for interactivity and animation. The SVG specification is an open standard developed by the World Wide Web Consortium since 1999.
SVG images are defined in a vector graphics format and stored in XML text files. SVG images can thus be scaled in size without loss of quality, and SVG files can be searched, indexed, scripted, and compressed. The XML text files can be created and edited with text editors or vector graphics editors, and are rendered by most web browsers. SVG can include JavaScript, potentially leading to cross-site scripting.
See also
[edit]Notes
[edit]- ^ A markup language, such as HTML, is classified as distinct from a programming language even though both control the behavior of a computer. Both are classified as computer language.[8]
References
[edit]- ^ "100 Specifications for the Open Web Platform and Counting". W3C. 2011-01-29. Archived from the original on 2020-08-08. Retrieved 2015-12-04.
- ^ Henry S. Thompson (2011-03-28). "The future of applications: W3C TAG perspectives". W3C. Archived from the original on 2020-12-30. Retrieved 2011-05-15.
- ^ "The evergreen web". W3C. 2001. Archived from the original on 2020-07-10. Retrieved 2018-04-07.
- ^ "HTML5: The jewel in the Open Web Platform". W3C. 2010-10-08. Archived from the original on 2013-05-30. Retrieved 2010-11-20.
- ^ "W3C Integrates Math on the Web with MathML 3 Standard". W3C. 2010-10-21. Archived from the original on 2020-07-05. Retrieved 2010-11-20.
- ^ "The Next Open Web Platform - Short list". W3C. 2011-01-29. Archived from the original on 2022-01-21. Retrieved 2011-01-29.
- ^ "WG Decision to publish HTML Microdata as a WG Note". W3C. 2013-10-02. Archived from the original on 2020-07-06. Retrieved 2014-08-15.
No one has volunteered to edit the HTML Microdata specification as per the call for volunteers … Therefore, the HTML WG hereby resolves that the HTML WG cannot productively carry this work any further
- ^ Hermans, Felienne; Schlesinger, Ari (2024-10-17). "A Case for Feminism in Programming Language Design". Proceedings of the 2024 ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Software. ACM. pp. 205–222. doi:10.1145/3689492.3689809. ISBN 979-8-4007-1215-9.
- ^ "HTML 4.0 Specification — W3C Recommendation — Conformance: requirements and recommendations". World Wide Web Consortium. December 18, 1997. Archived from the original on July 5, 2015. Retrieved July 6, 2015.
- ^ "What is CSS?". W3. Archived from the original on 2020-12-24. Retrieved 2023-05-31.
Web platform
View on Grokipediafrom Grokipedia
The Web platform, also known as the Open Web Platform, is a collection of royalty-free, open technologies that enable the creation, distribution, and interaction with content on the World Wide Web, ensuring interoperability across browsers, devices, and platforms without licensing restrictions or proprietary barriers.[1]
At its core, the platform comprises foundational standards such as HTML for structuring documents, CSS for styling and layout, ECMAScript (commonly known as JavaScript) for adding interactivity and logic, the Document Object Model (DOM) for programmatic manipulation of page content, and supporting technologies like SVG for vector graphics, MathML for mathematical expressions, HTTP for data transfer, and URIs for resource identification.[1] These elements collectively allow developers to build accessible, scalable web applications that function consistently in modern browsers.
The platform's development is driven by collaborative organizations including the World Wide Web Consortium (W3C), which standardizes web technologies; the Web Hypertext Application Technology Working Group (WHATWG), which maintains living standards like HTML; and the Internet Engineering Task Force (IETF), which oversees protocols such as HTTP.[2] Originating from Tim Berners-Lee's 1989 proposal for a hypertext system at CERN, the platform evolved with the W3C's founding in 1994 to promote open standards, followed by the WHATWG's formation in 2004 to address rapid web application needs.[3][2]
This open ecosystem has enabled the web's growth into a global, democratic medium, emphasizing accessibility, security, and innovation through ongoing evolution, such as the integration of web APIs for features like geolocation and media capture.[4][5]
, , and
Overview
Definition and scope
The web platform refers to the ecosystem of open, royalty-free standards and technologies that collectively enable the creation, rendering, and interaction with web content across diverse browsers and devices. This platform encompasses markup languages for structuring content, styling specifications for presentation, scripting languages for dynamic behavior, and application programming interfaces (APIs) for advanced functionalities such as multimedia handling and user interactions. By design, these elements promote interoperability without reliance on proprietary software, ensuring that developers can build applications that function consistently regardless of the underlying browser engine.[1] The scope of the web platform is primarily limited to client-side technologies, focusing on how content is rendered, styled, and made interactive in the user's browser environment. It includes mechanisms for parsing and displaying documents, handling user inputs, and integrating multimedia elements, as well as web protocols such as HTTP for client-server communication, but excludes server-side application logic, data storage on remote systems, or development paradigms for native mobile or desktop applications. This boundary emphasizes the platform's role in delivering universal access to web experiences through standardized, browser-native capabilities, fostering an environment free from vendor lock-in.[1][6] Foundational to the web platform are core tenets such as platform independence, which ensures content works across different operating systems, devices, and browsers; accessibility, which mandates inclusive design for users with disabilities through guidelines like perceivable, operable, understandable, and robust principles; and progressive enhancement, a strategy that starts with basic, accessible content and layers on advanced features for capable environments. These principles underpin the platform's evolution, prioritizing resilience and broad usability over feature-specific optimizations. The World Wide Web Consortium (W3C) plays a central role in defining and maintaining this scope through collaborative standardization efforts.[7] The term "web platform" gained prominence in the early 2010s as the web matured from static document delivery to a robust foundation for interactive applications, reflecting the integration of technologies like HTML5 with broader APIs. This shift highlighted the platform's growth beyond simple pages into a versatile stack for modern web development, driven by collaborative initiatives to expand its capabilities while preserving openness.[8][9]Key principles and openness
The web platform is fundamentally built on the principle of openness, ensuring it remains a public, non-proprietary ecosystem where specifications are freely available and implementable by anyone without licensing restrictions. This openness fosters widespread adoption and innovation by allowing developers, organizations, and individuals to contribute to and extend the platform without barriers, as articulated in W3C's design principles that emphasize royalty-free standards and transparent protocols.[5][10] A core tenet is backward compatibility and graceful degradation, which guarantee that new features do not break existing content, enabling the platform to support older devices, browsers, and user agents effectively. Specifications are crafted to handle poorly formed markup and provide fallbacks, such as alternative content within elements like<canvas>, so that legacy web pages continue to function reliably even as the platform evolves.[11] This approach ensures durability and broad reach, prioritizing the robustness of the web over rigid enforcement of new rules.
Accessibility is integrated as a built-in expectation, with standards like the Web Content Accessibility Guidelines (WCAG) guiding the design of features to support users with diverse disabilities, including visual, auditory, and cognitive impairments. Technologies must be perceivable, operable, understandable, and robust, avoiding practices that detect or undermine assistive tools, thereby making the platform inclusive by default.[12][13]
Decentralization underpins the platform's structure, preventing any single entity from exerting control and instead promoting a distributed model where community contributions drive progress. This vendor-neutral ethos, which discourages features tied to specific browsers or hardware, enables global participation and reduces single points of failure, empowering independent developers and organizations alike.[13][10]
The "web for all" motto encapsulates these principles, influencing feature design to prioritize low technical literacy, intuitive behaviors, and equitable access across devices and bandwidths, as seen in the emphasis on internationalization and privacy in core technologies like HTML.[13][11]
History
Origins in the early web
In March 1989, Tim Berners-Lee, a British computer scientist working at CERN, proposed a global hypertext system to facilitate the management and sharing of information among researchers, addressing challenges like high staff turnover and fragmented documentation.[14] This initiative aimed to create a distributed network of linked documents accessible across diverse computer systems, laying the groundwork for what would become the World Wide Web.[15] By late 1990, Berners-Lee had developed the necessary software, including the first web browser and server, and in 1991, he launched the inaugural website at CERN on his NeXT computer, hosted at info.cern.ch, which explained the project's goals and invited contributions.[3] On April 30, 1993, CERN announced that it would release the World Wide Web software into the public domain later that year, making it freely available for universal use and fostering global adoption without licensing restrictions.[15] In June 1993, the Internet Engineering Task Force (IETF) published the first draft specification for Hypertext Markup Language (HTML), a straightforward markup language designed to structure hypertext documents for the emerging web, enabling the representation of textual information, metadata, and inline graphics in a platform-independent format.[16] HTML drew from Standard Generalized Markup Language (SGML) and was intended as a simple, universal standard for linking and displaying content across the internet, supporting applications like online documentation and collaborative hypermedia.[17] The release of the NCSA Mosaic browser in 1993 marked a pivotal moment in web accessibility, as the first freely available graphical browser that seamlessly integrated text and images, making the web visually engaging and user-friendly for non-experts.[18] Developed by Marc Andreessen and Eric Bina at the University of Illinois' National Center for Supercomputing Applications (NCSA), Mosaic rapidly gained traction, with over 5,000 downloads per month by December 1993 and becoming the preferred tool for more than a million users within 18 months.[19] Building on this momentum, Netscape Communications Corporation released Netscape Navigator 1.0 in December 1994, the first commercial web browser, which further accelerated adoption by offering enhanced performance, security features like SSL, and free access for non-commercial users, quickly capturing a dominant market share.[20] Despite these advances, the early web suffered from a lack of unified standards, leading to the "browser wars" in the mid-1990s, where developers like Netscape and Microsoft introduced proprietary extensions to HTML and other protocols to differentiate their products and attract users, resulting in incompatible implementations that fragmented the platform.[21] This competition prioritized innovation over interoperability, with browsers supporting unique features such as Netscape's JavaScript and layers, exacerbating compatibility issues for web developers.[22] To mitigate these challenges and promote open standards, Tim Berners-Lee founded the World Wide Web Consortium (W3C) in October 1994 at the Massachusetts Institute of Technology, establishing an international body dedicated to developing and maintaining web technologies for long-term compatibility and growth.[23]Evolution and standardization
The early 2000s marked a significant shift toward dynamic web applications, driven by the adoption of the XMLHttpRequest object, originally developed by Microsoft in 1999 for Outlook Web Access and increasingly implemented across browsers by 2005.[24] This technology enabled asynchronous data retrieval without full page reloads, laying the groundwork for Asynchronous JavaScript and XML (AJAX), a term coined by Jesse James Garrett in February 2005 to describe the technique's potential for creating more responsive user interfaces. The rise of AJAX facilitated the development of interactive features like real-time updates, exemplified in applications such as Google Maps launched in 2005, transforming the web from static pages to dynamic platforms.[25] The concept of Web 2.0, popularized by Tim O'Reilly at the inaugural Web 2.0 Conference in 2004, further emphasized user-generated content, collaboration, and interactivity, influencing the platform's evolution toward participatory experiences.[26] This era saw the proliferation of platforms like blogs, wikis, and social networks, which leveraged AJAX and related technologies to enable seamless user contributions and real-time interactions, shifting the web from a read-only medium to one fostering collective intelligence.[26] In response to the W3C's focus on XHTML 2.0, which prioritized strict XML compliance over practical web development needs, representatives from Apple, Mozilla, and Opera formed the Web Hypertext Application Technology Working Group (WHATWG) in June 2004 following a W3C workshop on Web Applications and Compound Documents.[2] The WHATWG aimed to maintain HTML's evolution in a more implementation-driven manner, producing living standards that addressed real-world browser behaviors and developer requirements, contrasting with the W3C's more formal process.[27] The HTML5 initiative, launched as the WHATWG's HTML specification in 2004 and published as the W3C's First Public Working Draft in January 2008, represented a major overhaul of the core web markup language.[28] It integrated native support for multimedia elements like audio and video, eliminating reliance on plugins, and introduced semantic structures such asReferences
- https://wiki.whatwg.org/wiki/OffscreenCanvas
- https://wiki.whatwg.org/wiki/W3C