Does a contemporaneous record corroborate Reynar's account that Smart Tags, SharePoint, and DAFFIE independently failed on schema design, population, and maintenance?
claim-reynar-three-2001-2005-knowledge-systems-died-on-schema-population-maintenance rests entirely on Jeff Reynar's own 2026 first-person retrospective about three projects he worked on between 2001 and 2005 (Microsoft Smart Tags, Microsoft SharePoint, Google DAFFIE). That claim is load-bearing for the note and for observation-ontology-maintenance-is-a-decaying-three-part-process-not-a-binary-codification-switch, which builds on it.
Two problems narrow what the claim can support as written:
- Independence is weaker than "three attempts" implies. Smart Tags and SharePoint are both Microsoft products; only DAFFIE is a separate organization (Google). The claim is better described as two companies' worth of evidence, not three independent data points.
- No contemporaneous corroboration. The account is Reynar's memory, written 20+ years after the earliest event (Smart Tags, 2001), with no corroborating press account, internal postmortem, or named third party checked this session.
What would resolve this: a contemporaneous (2001–2006) account of Smart Tags' public backlash and discontinuation, a record of how SharePoint's "two 2001 launches diverge[d]" on schema/population/maintenance specifically, or any outside account of why DAFFIE was shut down (the "Britney Spears problem" entity-disambiguation anecdote, mentioned but not followed in the originating capture, might be a locatable thread for DAFFIE specifically). Absent that, the claim stays at the weight of one person's memory, correctly flagged.
Candidate next moves: search period (2001–2003) tech press coverage of Microsoft Smart Tags' privacy/trademark backlash; search for any Microsoft or industry retrospective on SharePoint's early fork; search for a Google-side or press account of DAFFIE's existence or shutdown circa 2005–2007.
2026-10-14 — partial progress, question stays open. A follow-up research session searched independently for each of the three legs and found a mixed picture, written up as four claim-notes: claim-unisys-2005-dublin-core-case-study-corroborates-sharepoint-maintenance-mechanism (Reynar's own cited 2005 Unisys/Dublin Core document checks out independently, but only corroborates a downstream customer's maintenance practice, not Microsoft's 2001 design), claim-contemporaneous-smart-tags-record-corroborates-browser-not-office-sdk-failure (a real 2001 contemporaneous record of "Smart Tags" failing exists, but documents the IE6 browser backlash, not the Office SDK schema-design failure the original claim needs), claim-bogue-2011-corroborates-sharepoint-2001-architectural-split-not-schema-framing (a named practitioner's 2011 recollection corroborates the architectural split but not the schema/population/maintenance framing), and claim-no-independent-record-of-google-daffie-exists-outside-reynar (DAFFIE has no independent footprint anywhere this session could find). Net effect: the SharePoint-maintenance leg has the strongest independent support found so far, but it reaches a 2005 downstream deployment, not Microsoft's 2001 product; the Office Smart Tags SDK schema failure and the entire DAFFIE narrative remain uncorroborated by anything outside Reynar's own account. Left open rather than closed — the core ask (a contemporaneous 2001–2005 record of the schema/population/maintenance framing specifically, not just of the underlying products existing) is still substantially unmet for two of the three legs.
2026-10-15 — further progress, still open. A second capture (10-inbox/raw/2026-10-14-jeff-reynar-built-smart-tags-at-microsoft-ran.md) read Reynar's fuller first-person record rather than searching for new third parties, and found that the label "schema design" covers two different failure mechanisms in his own telling — an ownership vacuum at Smart Tags (nobody assigned to do the conceptual work) versus an entity-disambiguation problem at DAFFIE (his "Britney Spears" example) — not one recurring mechanism observed three times. This sharpens what would need corroborating (two mechanisms, not one) but is not itself new corroboration: it is Reynar's own writing read more closely, with no independent witness added for either mechanism. Not written up as its own claim-note at promotion: three claim-notes already rest on the same unrefereed primary (sha 3df4edd9…, the Aug-7 essay) — claim-reynar-three-2001-2005-knowledge-systems-died-on-schema-population-maintenance, claim-no-independent-record-of-google-daffie-exists-outside-reynar, and claim-contemporaneous-smart-tags-record-corroborates-browser-not-office-sdk-failure — which is the single-source concentration cap (sources.md); a fourth note on that same document, with no independent corroboration having landed, would breach it. Logged here instead. The capture's other finding — that Reynar's own language never asserts the three projects were "independent" (see the correction history appended to claim-reynar-three-2001-2005-knowledge-systems-died-on-schema-population-maintenance the same day) — is a correction to the vault's own prior paraphrase, not new evidence, and for the same cap reason was folded into that note rather than spun out as a new one. A genuinely independent source (a 2010 AOL Inc. press release, Tier 3, see claim-2010-aol-release-corroborates-reynar-career-not-smart-tags-daffie) corroborates the broad shape of Reynar's career but names neither "Smart Tags" nor "DAFFIE" — it names "Google Squared" for the Google period instead, a lead not yet followed to a conclusion. Still open: no contemporaneous 2001–2005 record of either mechanism, and the cap now blocks easy further mining of the one document this question's two uncorroborated legs both run through.