throbber
30 January 2020
`
`Jordan,
`
`I have a long history with the Internet Archive, and I have gone to great lengths to obtain HTML source
`
`for web pages in both litigation and post-grant proceedings. I do not understand how you might think
`that either my expert or I might be misreading the Archive.
`
`The screenshots that Evan provided today refer to the FRAME set, not the individual items that are
`
`displayed in it. Indeed, if you look closely at the scree shots (taken by Evan today I presume), you will
`see a number of URLs for subitems on the page. In red, there is a legend for each item that says “+8
`
`years, 7 months.” This is the time difference between the archival date of the FRAME set document,
`
`and each sub-item that appears in the page. If you hover a cursor over the red text for an item, it will
`
`give you the timestamp for the specific item, generally Thu, August 8, 2019. There are other indexes
`that provide this information; I find it disconcerting that you are asking for further proof from us when
`
`at least some of it is in plain sight.
`
`Mr. Klosson asserts in his testimony that every screenshot in Ex. 1004 was captured by the Archive on
`
`February 1, 2011. As he is not an employee of the Archive, I do not understand how he could have
`
`personal knowledge of this; it is literally a false statement.
`
`The physical evidence tells a different story as illustrated by the HTML included in our response. Recall
`
`that the HTML for the Introduction page (Ex. 2010) states:
`
`<!-- FILE ARCHIVED ON 07:44:37 Aug 08, 2019 AND RETRIEVED FROM THE INTERNET ARCHIVE ON
`08:55:43 Jan 21, 2020. JAVASCRIPT APPENDED BY WAYBACK MACHINE, COPYRIGHT INTERNET
`
`ARCHIVE. ALL OTHER CONTENT MAY ALSO BE PROTECTED BY COPYRIGHT (17 U.S.C. SECTION
`
`108(a)(3)). -->
`
`This is the earliest date that this page was stored by the Archive.
`
`By way of further example, I attach screenshots from another child pages below. I would use the
`“Introduction” page, but it appears that someone (definitely not me) has been initiating “Save Page”
`
`events on it through out the day.
`
`The Military.htm child webpage has been captured one time in the history of the Archive. It shows that
`page was captured by the “Live Web Proxy Crawl” on August 8 2019. “Live web proxy“ did not exist in
`
`February 2011.
`
`

`

`
`
`Below is an example of what a sub-object viewed as a standalone object outside the FRAME set would
`
`appear. As you can see, it was captured 1 time in the history of the Archive, one day before the IPR was
`filed.
`
`
`
`
`
`Below is a screenshot illustrating the “About this capture” popup associated with the same sub-object.
`
`It states in greater detail that the object was captured using the “Live Web Proxy Crawl” – primarily
`associated with the “Save Page” feature. This feature appears when a user attempts to click on a sub-
`
`object that has not been stored by the Archive, but exists on the live web. When a person clicks the link,
`
`it initiates a crawl of the associated object.
`
`

`

`If
`
`
`
`Ex. 1004 as filed presents each child page in the FRAME set, and falsely suggests that each page was
`
`archived on that date. The Archive itself states that objects in a FRAME set may have very different
`
`dates and that each object within the FRAME must be examined individually – the header information
`
`displayed above the FRAME cannot be relied upon.
`
`I do not believe that the screenshots Evan provided today refute Mr. Howell’s conclusions. Rather, as
`
`explained above, it reinforces them.
`
`If you have HTML source showing an earlier archive date for the child pages (which contain the content
`
`upon which your IPR arguments are premised), I would be happy to review them.
`
`Best Regards,
`
`
`
`Rick
`
`
`
`
`
`
`
`
`
`
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket