LLMpediaThe first transparent, open encyclopedia generated by LLMs

SVG 1.1

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: CSS Hop 3
Expansion Funnel Raw 63 → Dedup 14 → NER 13 → Enqueued 12
1. Extracted63
2. After dedup14 (None)
3. After NER13 (None)
Rejected: 1 (not NE: 1)
4. Enqueued12 (None)
Similarity rejected: 1
SVG 1.1
NameSVG 1.1
DeveloperWorld Wide Web Consortium
Released2003
Latest release2003
GenreVector graphics
LicenseW3C Recommendation

SVG 1.1

SVG 1.1 is a W3C Recommendation for scalable vector graphics that defines an XML-based format for two-dimensional graphics and graphical applications, enabling interoperability among implementations from vendors such as Apple Inc., Microsoft, Mozilla Foundation, Opera Software, Google LLC, and Adobe Systems. The specification describes geometric shapes, text, paint, filters, and scripting interfaces that interact with technologies like ECMAScript, DOM Level 2 Core, and CSS Level 2. SVG 1.1 served as a foundational standard referenced by organizations including the World Wide Web Consortium, the Internet Engineering Task Force, and the International Organization for Standardization in web and publishing toolchains.

Overview

SVG 1.1 specifies an XML vocabulary for describing vector graphics that integrates with standards produced by bodies such as the World Wide Web Consortium, WHATWG, ISO/IEC JTC 1, W3C Working Groups and is consumed by products from Apple Inc., Microsoft, Adobe Systems, Google LLC and Mozilla Foundation. The format allows authors to create resolution-independent imagery referenced by HTML 4.01, XHTML 1.0, SVG Tiny 1.2 profiles, and printing workflows used by Printer Working Group members, and to manipulate graphics via ECMAScript and the Document Object Model. SVG 1.1's modularization strategy influenced later specifications and standards produced by W3C Technical Architecture Group and other consortia.

History and Development

SVG 1.1 evolved from earlier work at the World Wide Web Consortium building on a series of drafts and implementations produced in collaboration with industry stakeholders such as Adobe Systems, IBM, Sun Microsystems, Netscape Communications Corporation, and Macromedia. Key milestones included the initial SVG 1.0 Recommendation and subsequent modularization and errata leading to the SVG 1.1 Recommendation in 2003, which aligned with concurrent standards like XML 1.0, CSS Level 2, and DOM Level 2 Core. Development involved cross-industry interoperability events and test suites coordinated with groups including the W3C SVG Working Group and influenced by prior graphics work from organizations like ISO and ITU. SVG 1.1's maturation paralleled browser engine development at projects such as Gecko (software), WebKit, and Trident (layout engine), and adoption was driven by vendors including Apple Inc. and Google LLC integrating support into platforms like iOS and Android (operating system).

Core Features and Specifications

SVG 1.1 defines primitives for paths, shapes, text, gradients, patterns, clipping, masking, and compositing, and binds them to presentation attributes consistent with CSS Level 2 and scripting via ECMAScript and the DOM Level 2 Events model. The specification includes a set of animation capabilities via SMIL-based timing and animation elements that echo work by groups such as W3C Timed Text Community Group, and it standardizes coordinate systems, transform matrices, viewports, and preserveAspectRatio behavior used by printing workflows in organizations like ISO/IEC JTC 1/SC 34. The modular architecture separates SVG into modules—structure, text, paint, paths, filters—allowing implementations to adopt subsets analogous to profiles from W3C Mobile Web Initiative and industry consortia such as Open Mobile Alliance.

Implementation and Browser Support

Implementations of SVG 1.1 appeared in browser engines and native runtimes developed by Mozilla Foundation, Apple Inc. (WebKit), Google LLC (Blink), and Microsoft (Trident and later EdgeHTML), and in authoring tools from Adobe Systems and Inkscape Project. Platform integration included support in Firefox, Safari (web browser), Google Chrome, and earlier Internet Explorer versions via plugins and native features. SVG 1.1 support also extended to document processors and office suites such as LibreOffice, Microsoft Office, and publishing systems used by Springer Science+Business Media and Elsevier. Industry test suites and conformance efforts involved collaboration among vendors, standards bodies like the World Wide Web Consortium, and research groups at institutions such as MIT and Stanford University.

Extensions and Profiles

SVG 1.1 defined profiles and potential extensions to address device constraints and application niches, including profiles analogous to SVG Tiny, SVG Basic, and authoring extensions implemented by vendors like Adobe Systems and projects such as Inkscape Project. The modular design allowed integration with media technologies such as SMIL 2.0, XLink, and accessibility interfaces advocated by W3C Web Accessibility Initiative partners like World Wide Web Consortium's accessibility working groups and assistive technology vendors. Extensions and profiles enabled embedding in mobile platforms championed by Open Mobile Alliance members and influenced later container formats used in multimedia standards from organizations such as MPEG.

Criticisms and Limitations

Critiques of SVG 1.1 focused on incomplete or inconsistent implementation across engines from Microsoft, Apple Inc., Google LLC, and Mozilla Foundation, limitations in mobile performance cited by developers at Samsung Electronics and LG Electronics, and partial interoperability with presentation and animation models from SMIL 2.0 and CSS3 modules drafted by W3C. The specification's complexity and scope challenged implementers such as open-source projects like Inkscape Project and vendor toolchains at Adobe Systems, while concerns about security and script interaction prompted scrutiny from research groups at University of California, Berkeley and ETH Zurich. These limitations drove continued work in later SVG-related specifications and profiles by the World Wide Web Consortium and allied standards bodies.

Category:Graphics standards