Also, something else to think about is that, under certain conditions, this info could potentially be passed along via HTTP headers.
Maybe something like:
HTTP/1.1 200 OK
Link: < urn:sha1:dRDPBgZzTFq7Jl2Q2N/YNghcfj8=>; rel="hash"
See ya
On 11/7/06, Charles Iliya Krempeaux <
[EMAIL PROTECTED]> wrote:
Hello,
Here's something else related...
http://microformats.org/wiki/hash-examples
See yaOn 11/7/06, Charles Iliya Krempeaux <[EMAIL PROTECTED]> wrote:Hello,
Aren't URNs already being very commonly used for hashes. For example...
urn:sha1:dRDPBgZzTFq7Jl2Q2N/YNghcfj8=
urn:md5:FNG4c6MJLdDEY1rcoGb4pQ==
urn:kzhash:0bf4c9a50c1058fb6887ad0419ecfc06dc192c69163ea2c45c632dab1cab1e1fbd6fbf1e
urn:tiger:tree:ZAJPZOPES4YGIPNHLHDQHD5FHSAFSPIYG7IOO3Y
urn:bitprint:QLFYWY2RI5WZCTEP6MJKR5CAFGP7FQ5X.VEKXTRSJPTZJLY2IKG5FQ2TCXK26SECFPP4DX7I
Perhaps it would be good to keep with that format.
See ya--On 11/7/06, XcomCoolDude < [EMAIL PROTECTED]> wrote:How about a hash attribute for all elements that link to external files (a, img, etc.)?
It would allow you to pass an MD5, SHA-1, SHA-256, or other hash to a user-agent for automatic comparison with the linked file.
I'd suggest a format where the hash algorithm is listed, followed by a forward slash and then the hash itself
Examples:
hash="MD5/9e107d9d372bb6826bd81d3542a419d6"
hash="SHA-1/2fd4e1c6 7a2d28fc ed849ee1 bb76e739 1b93eb12"
hash="SHA-256/d7a8fbb3 07d78094 69ca9abc b0082e4f 8d5651e4 6d3cdb76 2d02d0bf 37c9e592"
See my thread over at mozillaZine for more info and other ideas: http://forums.mozillazine.org/viewtopic.php?p=2234056
--Wulf
Charles Iliya Krempeaux, B.Sc.
charles @ reptile.ca
supercanadian @ gmail.com
developer weblog: http://ChangeLog.ca/
--
Charles Iliya Krempeaux, B.Sc.
charles @ reptile.ca
supercanadian @ gmail.com
developer weblog: http://ChangeLog.ca/
--
Charles Iliya Krempeaux, B.Sc.
charles @ reptile.ca
supercanadian @ gmail.com
developer weblog: http://ChangeLog.ca/
