D3.js
JavaScript data visualization library using SVG and CSS
D3.js (also known as D3, short for Data-Driven Documents) is a JavaScript library for producing dynamic, interactive data visualizations in web browsers. It makes use of Scalable Vector Graphics (SVG), HTML5, and Cascading Style Sheets (CSS) standards. It is the successor to the earlier Protovis framework. Its development was noted in 2011, as version 2.0.0 was released in August 2011. With the release of version 4.0.0 in June 2016, D3 was changed from a single library into a collection of smaller, modular libraries that can be used independently.
Context
There have been various previous attempts to bring data visualization to web browsers. The most notable examples were the Prefuse, Flare, and Protovis toolkits, which can all be considered as direct predecessors of D3.js.
Prefuse was a visualization toolkit created in 2005 that required usage of Java, and visualizations were rendered within browsers with a Java plug-in. Flare was a similar toolkit from 2007 that used ActionScript, and required a Flash plug-in for rendering.
In 2009, based on the experience of developing and utilizing Prefuse and Flare, Jeffrey Heer, Mike Bostock, and Vadim Ogievetsky of Stanford University's Stanford Visualization Group created Protovis, a JavaScript library to generate SVG graphics from data.
“D3.js” enters the record as javaScript data visualization library using SVG and CSS. Crown Archives preserves that source wording while asking what JavaScript, data and visualization can confirm, complicate or overturn.
Why this record matters
“D3.js” is worth following because a concise public description often conceals a longer documentary argument. Here, JavaScript, data and visualization provides the most credible route into that argument.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Sep 1, 2026. The linked authority identifier is Q3011087. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2011, 2016, 2005 and 2007.
A single description cannot reconcile every naming convention, rebuilding phase or administrative transfer associated with a place. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “D3.js”, its source revision and the description used here.
- Expand the search: follow D3.js primary sources, D3.js archive and JavaScript research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “D3.js”?
- Which earlier names or jurisdictions may reveal additional records?
- What physical evidence or contemporary plan supports the description?
Search terms from this dossier
This entry incorporates text from “D3.js” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.