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

semantic-webontologysharepointdublin-corecorroborationjeff-reynar

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.