- From: Ryan Morrison~Westphal <rwestphal@cyber.law.harvard.edu>
- Date: Fri, 16 Jan 2015 08:53:20 -0500
- To: Herbert Van de Sompel <hvdsomp@gmail.com>
- Cc: Robustness and Archiving Community Group <team-community-process@w3.org>, public-irobar@w3.org
Of course, I understand Memento's place in the stack. I tried to make this post a short intro-type blurb & target a wider audience to give them a few links to click for now. Memento should get it's own post soon, fully explaining what it is. Also, thank you for the concise description here, that will be very helpful. Regarding the actual text of that paragraph, I'm happy to change the wording. The word centralized was intended to modify initiative, not the specific tech, but I can remove the word entirely. How does this sound? Some initiatives, such as the Internet Archive, Perma.cc, and Memento, are attempting to snapshot and preserve the Internet and provide seamless access to the snapshots. See you soon at Berkman! -Ryan On 2015-01-15 16:42, Herbert Van de Sompel wrote: > A correction, if I may: Memento is not attempting to snapshot and > preserve the Internet. The Memento protocol (RFC 7089) specifies an > interoperable mechanism to access resource versions in web archives > and versioning systems. It is an extension to HTTP that introduces > datetime negotiation. Given an "original" URI and a preferred datetime > , the Memento protocol - along with associated infrastructure - allows > seamless access to a snapshot of the URI created on or around the > preferred datetime, irrespective of the web archive (or versioning > system) the snapshot resides in. > > The Memento protocol does not assume centralization but, instead, is > conceived to work in an environment with many distributed web archives > and versioning systems. > > Other than that, I can align with the content of this message. > > Cheers > > Herbert Van de Sompel > > Sent from my iPad > >> On Jan 15, 2015, at 14:11, W3C Community Development Team >> <team-community-process@w3.org> wrote: >> >> Before we enumerate use cases, we can state some initial indications >> of a >> problem. >> >> Whether links fail because of DDoS attacks, censorship, or just plain >> old link >> rot, dead links are a problem for Internet users everywhere. >> >> This isn't a new problem (W3C - Cool URIs don't change). >> 49% of links in Supreme court opinions are dead >> NYT - In Supreme Court Opinions, Web Links to Nowhere >> 136,312 Wikipedia articles contain dead external links >> Wikipedia - Category:All articles with dead external links >> Some centralized initiatives, such as the Internet Archive, Perma.cc, >> and >> Memento, are attempting to snapshot and preserve the Internet. >> >> But more and more, just a handful of centralized entities host >> information >> online. Online centralization creates "choke points" that can restrict >> access to >> web content. >> >> This Community Group intends to pursue complementary solutions to >> missing online >> content from various angles: >> >> date stamped archiving of web content >> enabling content management systems and content authors to embed >> knowledge of >> archives and citation dates into links >> providing browsing users with ways to discover this information >> >> The more routes we provide to information, the more all people can >> freely share >> that information, even in the face of filtering or blockages. >> >> >> >> ---------- >> >> This post sent on Robustness and Archiving Community Group >> >> >> >> 'What's the Problem?' >> >> http://www.w3.org/community/irobar/2015/01/15/whats-the-problem/ >> >> >> >> Learn more about the Robustness and Archiving Community Group: >> >> http://www.w3.org/community/irobar >> >> >>
Received on Friday, 16 January 2015 13:53:49 UTC