Generated by GPT-5-mini| Scalable Vector Graphics | |
|---|---|
| Name | Scalable Vector Graphics |
| Developer | World Wide Web Consortium |
| Released | 1999 |
| Programming language | XML |
| Platform | Cross-platform |
| License | W3C Recommendation |
Scalable Vector Graphics is an XML-based vector image format developed to describe two-dimensional vector graphics and mixed vector/raster graphics in a text format. It was standardized by the World Wide Web Consortium and integrates with other web technologies to provide resolution-independent graphics suitable for screens, print, and sensor-driven displays. The format has been influential across web browsers, digital publishing, and graphic design tools.
SVG originated from work by the World Wide Web Consortium with contributions from companies including Adobe Inc., Microsoft, Apple Inc., IBM, and Sun Microsystems. Early design discussions involved public drafts in the late 1990s and the first Recommendation in 2001; subsequent revisions and modularization were informed by feedback from implementers such as Mozilla Foundation, Opera Software, and Google. SVG development intersected with standards and efforts like HTML5, CSS, DOM, and XSLT, and was influenced by predecessors such as PostScript, PDF, and CGM. Industry adoption grew alongside browsers such as Netscape Navigator, Internet Explorer, Mozilla Firefox, Opera, and Google Chrome, and content ecosystems including Wikipedia, W3Schools, and Adobe Illustrator workflows.
SVG uses XML syntax to represent primitives like lines, curves, and shapes, relying on specifications from bodies such as the W3C and APIs like the Document Object Model to enable scripting and dynamic manipulation. Coordinate systems, viewports, and units are defined in terms compatible with CSS and influenced by graphics models from PostScript and PDF. Rendering pipelines in engines—found in projects like Blink and Gecko—map vector descriptions to pixels, employing algorithms studied in computational geometry and rasterization literature associated with research groups at MIT, Stanford University, and ETH Zurich. SVG supports styling via CSS and animation models related to SMIL and scripting via ECMAScript and JavaScript engines such as V8.
An SVG file is a UTF-8 XML document beginning with an XML declaration and an
Rendering of SVG relies on browser engines and graphics subsystems including Skia, Direct2D, Cairo, and Core Graphics to rasterize paths, text, and filters with antialiasing and hardware acceleration provided by APIs like OpenGL, WebGL, and Metal. Interactivity is enabled through event models provided by W3C DOM Events, allowing integration with frameworks such as React, Angular, Vue.js, and visualization libraries like D3.js and Three.js. Accessibility and scripting considerations map to standards and tools from organizations like WAI and WAI-ARIA, while performance profiling often uses tooling from Google Chrome DevTools, Firefox Developer Tools, and profiling suites from Lighthouse.
SVG is used in web icons and responsive UI components by projects like Bootstrap, Material Design, and platforms such as GitHub and GitLab. Technical diagrams, cartography, and mapping integrate SVG with systems like OpenStreetMap and Leaflet; scientific visualization appears in projects tied to NASA, European Space Agency, and academic publishers such as Nature and IEEE. Print and publishing workflows leverage interoperability with PDF and tools like LaTeX and Scribus, while design and prototyping involve applications including Figma and Sketch. Content delivery and optimization are provided by services including Google Fonts, Amazon CloudFront, and Akamai Technologies.
SVG’s XML and scripting capabilities raise security concerns addressed by best practices propagated by OWASP and browser vendors like Mozilla Foundation and Microsoft. Risks include cross-site scripting patterns familiar from guidance by CVE tracking and mitigations such as sanitization libraries used by DOMPurify and server-side validators used in platforms like WordPress, Drupal, and Joomla. Accessibility recommendations follow guidance from the WAI and ARIA practices, encouraging use of titles, descriptions, and keyboard focus conventions adopted by projects including NVDA, JAWS, and VoiceOver. Ongoing standardization and security auditing involve communities around IETF, W3C, and open-source projects such as Chromium and WebKit.
Category:Computer file formats Category:Graphics standards