Thad, I think you are right on the money with this.👍👍 Thanks, —David On Wed, Jun 30, 2021 at 12:33 PM Thad Guidry <thadguidry(a)gmail.com> wrote: -- David McDonell Co-founder & CEO ICONICLOUD, Inc. "Illuminating the cloud" M: 703-864-1203 EM: david(a)iconicloud.com URL: http://iconicloud.com

Thanks for sharing I wrote about Swedish runestones people that in 1750 wrote books with identifiers we still use today * Structured data for GLAM-Wiki/Roundtripping/KMB<https://meta.wikimedia.org/wiki/Structured_d… * I will mention this in my LD4 session<https://sites.google.com/stanford.edu/2021ld4conf/sessions/sessi… [cid:41dea86d-0ed4-4a93-8c9d-87283fa116e0] * * Feels sad that things that already 1750 was obvious is missed in a project like Europeana<http://minancestry.blogspot.com/2020/03/carl-larsson-who-is-th… and no one one except en:Wikipedia start complaining.... Regards, Magnus twitter salgo60<https://twitter.com/salgo60> ________________________________ From: Young,Jeff (OR) &lt;jyoung(a)oclc.org&gt; Sent: Wednesday, June 30, 2021 8:51 PM To: Discussion list for the Wikidata project &lt;wikidata(a)lists.wikimedia.org&gt; Subject: [Wikidata] Re: [External] On the subject of Linked Data Availability and Retention This reminds me a bit of Ted Nelson’s Xanadu project. https://kottke.org/tag/Ted%20Nelson From: Thad Guidry &lt;thadguidry(a)gmail.com&gt; Date: Wednesday, June 30, 2021 at 12:33 PM To: Discussion list for the Wikidata project. &lt;wikidata(a)lists.wikimedia.org&gt; Subject: [External] [Wikidata] On the subject of Linked Data Availability and Retention Hi Community! We often act like and think that things are, well ... forever (even our own lives!). But Time waits for no one. So... I had posted this over in the LD4 Slack channel but thought that this would be good for folks here to at least always be aware of and think about in our growing Linked Data world. ---- All Linked Data efforts need stable identifiers (on both ends of a "link"). I.E. linking is only good if the other side will be retrievable and available (online or offline through web/archives/files) throughout the expected lifetime of an effort and beyond. Think closely about "knowledge retention" (libraries/books hold knowledge for hundreds of years!) and what the Linked Data lifecycle itself that ideally will do that for your projects. Then look towards not the tools, but instead the communities that are well established and have the likelihood to continue to provide stable identifiers that are retrievable well into the future + another 100+ years. This might include government efforts, or communities that have foundations behind them that are well grounded through philanthropic means with perpetuity ... to avoid link rot or non-retrievability through complete void of the knowledge or stable identifiers in the future. I'm hopeful that communities will think about data retention policies and generally "Linked Data Availability" much more deeply and seriously. This could be likened to something like GitHub's Arctic Vault, Internet Archive, or decentralized storage solutions like Filecoin, to be able to backup and retain the knowledge for thousands of years, if need be. --- Thad https://www.linkedin.com/in/thadguidry/ https://calendly.com/thadguidry/