A named practitioner's 2011 firsthand account independently corroborates SharePoint's 2001 split into two architecturally different products, but not Reynar's schema/population/maintenance framing of it

semantic-websharepointjeff-reynarcorroborationmicrosoft

claim-reynar-three-2001-2005-knowledge-systems-died-on-schema-population-maintenance describes Microsoft shipping "two SharePoints" in 2001 — Portal Server (taxonomist-oriented, document-and-category-first-class-objects) and Team Services (file-and-site-oriented, asking no particular expertise of users) — and argues the schema-requiring one lost out to the one that asked nothing of users. Robert Bogue, a named, long-tenured SharePoint developer and consultant writing on his own blog in 2011 about his direct experience building on SharePoint from 2001 onward, independently corroborates that the two 2001 products were genuinely different systems at the architecture level: Portal Server ran on the Exchange database engine and treated documents as versioned objects; Team Services (STS) ran on SQL Server and treated content as unversioned lists of items. Bogue also describes operational problems with Portal Server's Exchange-engine backend from his own 2001 deployment work.

Bogue's account corroborates the structural divergence Reynar describes — two 2001 products, different foundations, different audiences — from an independent, named source with firsthand technical experience. It does not independently use or confirm Reynar's specific three-part schema/population/maintenance framing: Bogue's account is about database-engine and feature-parity differences, not about who owned taxonomy design or why one product's metadata practice succeeded where the other's didn't.