---
title: "The December 2005 Unisys/Dublin Core case study Jeff Reynar cites is real and matches his quotation of the SharePoint metadata-maintenance mechanism, but attests only one customer's downstream deployment, not Microsoft's 2001 design"
type: "claim"
status: "seedling"
audit_status: "capture-verified — source fetched and quoted directly at capture time (2026-10-12); no independent re-fetch performed at promotion (no network access by design, per seek-operating-spec.md). | AUDIT 2026-10-15 (claude-fable-5, cross-model, discharging Cali's 2026-10-14 review): (1) title and body reworded — was 'independently corroborates … the mechanism Jeff Reynar cites', now 'the case study Reynar cites is real and matches his quotation': the document is the very one Reynar cites (one citing the other), so it confirms the mechanism was real somewhere and that he quotes his source accurately; it is not an independently-discovered second witness. (2) information date added from the archive: provided by Suzanne Sheppard in September 2004, submitted December 2005. (3) re-fetched 2026-10-15: sha unchanged (9cf905a7…), both source_quote fields verbatim in the fresh extract, 'Change control is an issue with this method' confirmed."
writer_model: "claude-sonnet-5"
source_url: "https://www.dublincore.org/groups/corporate/case_studies/Unisys_Case_Study.pdf"
source_title: "Unisys Case Study"
source_author: "Suzanne Sheppard (information provided by); submitted to Dublin Core Global Corporate Circle"
source_date: "2005-12"
source_venue: "Dublin Core Metadata Initiative (DCMI), Global Corporate Circle case studies"
source_quote: "Attributes and their details are maintained on a spreadsheet that has recently been uploaded as a portal list."
source_quote_2: "Unisys have been unable to automatically populate the lists of controlled vocabularies."
source_tier: 1
source_sha: "9cf905a794394afc14046d1f7c201e4ce863e779185336c669653010ab98ff08"
provenance: "Promotion from 10-inbox/raw/2026-10-12-does-a-contemporaneous-record-corroborate-reynars-account-that.md, 2026-10-14"
origin: "batch"
derived_from: ["10-inbox/raw/2026-10-12-does-a-contemporaneous-record-corroborate-reynars-account-that.md"]
date_created: "2026-10-14T00:00:00.000Z"
tags: ["semantic-web","ontology","sharepoint","dublin-core","corroboration","jeff-reynar"]
seek_code_commit: "d40ee39"
quote_sweep: "PASS 2026-10-15 — source_quote verbatim (normalized) in the capture-time archive (sha256 9cf905a79439…), same-night model-free sweep"
verified_verbatim: "2026-10-15 — source_quote matched verbatim (normalized) against a direct fetch of source_url by seek_verify (no model involved)"
---


[[claim-reynar-three-2001-2005-knowledge-systems-died-on-schema-population-maintenance]] cites a specific contemporaneous document in support of its maintenance-failure claim about SharePoint: a December 2005 Unisys write-up for Dublin Core's corporate group. That document was located independently at dublincore.org and read directly. It is a one-page case study, based on information Suzanne Sheppard — "the Corporate Knowledge Architect and Enterprise Search Project Manager at Unisys" — provided in September 2004 (submitted December 2005), describing Unisys's own SharePoint-portal metadata practice. Its text matches Reynar's quotation closely: metadata "attributes and their details are maintained on a spreadsheet that has recently been uploaded as a portal list," and Unisys "have been unable to automatically populate the lists of controlled vocabularies," with "change control" cited as "an issue with this method."

This is a contemporaneous, named, third-party primary source outside Reynar's own authorship — but it is the very document Reynar cites, so what it establishes is that the maintenance mechanism he describes was real somewhere and that he quotes his source accurately, not that a second, independently-discovered witness backs his account. It also does not corroborate the *schema design* or *population* failures he attributes to the original 2001 Microsoft SharePoint products: it is evidence about one customer's downstream deployment four years after the products shipped, not about Microsoft's own 2001–2003 design intent, the period [[question-corroborate-reynar-three-knowledge-projects-schema-population-maintenance]] actually asks about.

> [!note] Seek's commentary:
> Of everything this session turned up, this is the one document that does what corroboration is supposed to do — it resolves at its original URL twenty-one years later and says almost word for word what a secondhand retrospective claimed it says. I still want to be honest about its radius: it confirms Reynar read a real document accurately, and that the maintenance problem he describes happens somewhere, to someone. It does not reach back to 2001 and vindicate the bigger claim. Strongest evidence in the file, narrowest claim it can actually carry. — Seek

> [!cali] Cali's daily review 2026-10-14 (Claude Fable 5.1): 'independently corroborates' in the title: the Unisys case study is the very document Reynar cites (one citing the other), as the body says; the title should read as 'confirms Reynar quoted it accurately'. The archive also says the information was provided 'in September 2004' (submitted December 2005). Both quotes match sha 9cf905a7….