[Esip-preserve] [FOO] Foo Project moves to Google Spreadsheets

[alicebarkstrom at frontier.com]

Do we have any analysis that quantifies the probability that the
identifiers will be disconnected from the file contents?
I don't think we've had any consideration of why we think the
identifiers will remain reliable - nor have I seen any analysis
of how we would be able to test for corruption - whether by
hardware failure, software obsolescence, operator error, or
by malicious attacks.  Since the usual DOI/URL/PURL/.../UUID's
do not have direct ties to the file (or larger collections),
I don't think you could rely on these to detect changes.

Bruce B.
----- Original Message -----
From: "Curt Tilmes" <Curt.Tilmes at nasa.gov>
To: "ESIP Preservation cluster" <esip-preserve at rtpnet.org>
Sent: Monday, October 11, 2010 2:52:58 PM
Subject: [Esip-preserve] [FOO] Foo Project moves to Google Spreadsheets


This is a read/only link:

https://docs.google.com/leaf?id=0BztPCL0EZx_3NWI4OTQwN2ItMjU3OC00ZGIwLWFlNjUtNWY1OTE3MGJjNDUw&hl=en

Mostly cut/pasted from my earlier emails.

I did add one additional file, a "FOOLUT" lookup table that is an
input to APP_L2.  We can change the version of the APP independently
from the version of the LUT and explore the various provenance graphs.

I'm attaching a basic data flow diagram.  (I also pasted an SVG
version of this diagram into the spreadsheet, but it doesn't come
through every browser.)

I'm also trying to always include the "[FOO]" tag so you can filter
your ESIP-Preserve list if you aren't following this scenario and
want to trim down the clutter.

So far, this simple scenario has:

1. Shown how DOI works well to identify and locate "ESDT+Collection".

2. Show how DOI doesn't precisely identify sets of granules.

3. Show how UUID can be used to unambiguously refer to individual granules.

Curt

_______________________________________________
Esip-preserve mailing list
Esip-preserve at lists.esipfed.org
http://www.lists.esipfed.org/mailman/listinfo/esip-preserve