Hello, As far as I know, the value of the "type" attribute always applies to the resource at the end of the "href" attribute.  (Not what is nested in/under the <a> element.) See ya <div>On 1/31/06, brian suda <<a href="mailto:brian.suda@gmail.com">brian.suda@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Be aware that the 'a' element has a 'type' attribute: type = content-type [CI] This attribute gives an advisory hint as to the content type of the content available at the link target address. It allows user agents to opt to use a fallback mechanism rather than fetch the content if they are advised that they will get content in a content type they do not support. Authors who use this attribute take responsibility to manage the risk that it may become inconsistent with the content available at the link target address. For the current list of registered content types, please consult [MIMETYPES]. You could easily put something like: <a href="checksum.md5" type="text/md5">687926...32b9</a> The downside is that you would for all HASHES to be links and they also must have mimetypes. -brian Charles Iliya Krempeaux wrote: > Hello Anthony, > > As you mentioned, some people do pay attention to checksums and > hashes.  So why not keep it in the open.  How about something like: > >     >         <a rel="bookmark" href="...">Download OOo</a> >         e0d123e5f316bef78bfdf5a008837577 >     > > Note, with Microformats you can throw a whole bunch of stuff in there > to make it look nice.   (If you're not sure what I mean, I can > explain.) And you could put those "class" attributes on other tags > besides the . > > > See ya > > > On 1/30/06, anthony l. bryan <<a href="mailto:albryan@comcast.net">albryan@comcast.net</a>> wrote: > >> Hello everyone, >> >> I've been following the discussions for a few days & just wanted to say hi. >> You guys are doing some interesting cool stuff. >> >> I'd like to propose a simple format that I would find useful. I'm new at >> this, so please correct my errors! >> >> Basically, checksums (MD5 & SHA-1 hashes) are offered for software >> releases/files to prove they haven't been tampered with. >> >> No average people use them. I think its safe to say only technical people >> do, and probably not as often as they should/could. What I think a >> microformat could do is make it easier to automatically use them and verify >> files. If you aren't familiar, check out >> <a href="http://download.openoffice.org/2.0.1/md5sums.html">http://download.openoffice.org/2.0.1/md5sums.html</a> and >> <a href="http://www.openoffice.org/dev_docs/using_md5sums.html"> http://www.openoffice.org/dev_docs/using_md5sums.html</a> . >> >> Here's a few examples of what they might look like. I'm not familiar w/ >> "rel" but I see you guys use it quite a bit. If it's ok to create a new >> element, I would say "hash" or "checksum" would be better. I believe MD5 is >> 32 characters and SHA-1 is 40, so you should be able to tell the difference >> by length. >> >> <a >> href="<a href="http://mirrors.isc.org/pub/openoffice/stable/2.0.1/OOo_2.0.1_LinuxInte">http://mirrors.isc.org/pub/openoffice/stable/2.0.1/OOo_2.0.1_LinuxInte</a> >> l_install.tar.gz" rel="md5:e0d123e5f316bef78bfdf5a008837577"> OpenOffice.org >> 2.0.1 for Linux</a> >> >> (use sha-1:xxxxxx for sha-1 etc) >> >> <a >> href="<a href="http://mirrors.isc.org/pub/openoffice/stable/2.0.1/OOo_2.0.1_LinuxInte"> http://mirrors.isc.org/pub/openoffice/stable/2.0.1/OOo_2.0.1_LinuxInte</a> >> l_install.tar.gz" hash="e0d123e5f316bef78bfdf5a008837577">OpenOffice.org >> 2.0.1 for Linux</a> >> >> <a >> href="<a href="http://mirrors.isc.org/pub/openoffice/stable/2.0.1/OOo_2.0.1_LinuxInte">http://mirrors.isc.org/pub/openoffice/stable/2.0.1/OOo_2.0.1_LinuxInte</a> >> l_install.tar.gz" checksum="e0d123e5f316bef78bfdf5a008837577"> OpenOffice.org >> 2.0.1 for Linux</a> >> >> Anyways, you get the idea. A browser/extension/plugin/download manager could >> easily read this, then verify if the file is good (actually, just alert them >> if its bad would probably be easier). >> >> Another nice thing about the checksum is that it references a specific file. >> Some installation files don't contain a version number in them, so they all >> have the same filename (iTunes 5, 6, 6.0.1, 6.0.2 wer all called >> iTunesSetup.exe, all versions of Skype are SkypeSetup.exe, or documents, >> etc) so you could reference a specific version of a file & maybe find it >> with a search engine that stores hashes. </blockquote></div> --     Charles Iliya Krempeaux, B.Sc.     charles @ <a href="http://reptile.ca">reptile.ca</a>     supercanadian @ <a href="http://gmail.com">gmail.com</a>     developer weblog: <a href="http://ChangeLog.ca/">http://ChangeLog.ca/</a>