CACrown ArchivesThe cinema collection
EN/FR
Search
Menu
Research dossier · General Reference

Timeline of Delft

Open-knowledge reference entry

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionSep 12, 2026
Entity authorityQ28223803 ↗
Source-derived summary

The following is a timeline of the history of the municipality of Delft, Netherlands.

Prior to 18th century

1075 - Town established by Godfrey III, Duke of Lower Lorraine. (Godfrey III died in 1069; perhaps it was his son Godfrey the Hunchback)

1246 - Delft granted city rights by William II of Holland.

1250 - St. Bartholomew's Church construction begins.

1383 - Nieuwe Kerk (Delft) (church) construction begins.

1389 - Canal to the Meuse river created.

1400 - Eastern Gate (Delft) built.

1403 - Agathaklooster (convent) established.

1470 - Carthusian monastery established.

Editorial summary

This brief starts where responsible research should: with the source description of “Timeline of Delft” as open-knowledge reference entry. Everything that follows is an evidence route, not borrowed authority.

Editorial reviewA concise reference frame for defining the subject, testing terminology and identifying the institution closest to the evidence. The current lead gives the account dated anchors—1075, 1069, 1246, 1250—that can be checked directly. The selected authority fields contribute no independent date. The account is most persuasive where Timeline, Delft and Open-knowledge can be independently traced.
Editorial analysis

Why this record matters

The subject matters to the general reference register because the source frames it as open-knowledge reference entry. Its deeper value depends on whether names, dates, institutions and citations support that framing.

Evidence profile

Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 12, 2026. The linked authority identifier is Q28223803. The first chronological checks are 1075, 1069, 1246 and 1250.

Critical limits

Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. 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

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “Timeline of Delft”, its source revision and the description used here.
  2. Expand the search: follow Timeline of Delft primary sources, Timeline of Delft archive and Timeline research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Timeline of Delft”?
  2. What terminology or title could unlock a more precise catalogue search?
  3. Which cited source is closest to the event, object or claim?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Timeline of Delft” 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.