On Mon, 6 Nov 2000, its me wrote: > Now this would be implemented by adding an attribute to the "<img>" tag and > having the browser support the tar file format in some fashion. This new > attribute will be called "archive" and will point to the archvive and the > file name inside the archive. For example: > > <img archive="template.tar file-in-template.jpeg> This has already been done with the object element. tar may not be the best choice, as there are several ever-so-slightly incompatible versions, which will mostly cooperate nicely, but will sometimes bring inconvenient surprises. What about using MIME multipart messages? One could either use the cid: URI scheme in the data attribute, or for backwards compatibility provide usable http: URIs, identified with body parts by Content-Location headers. Tim BagotReceived on Tuesday, 7 November 2000 07:55:50 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:49:22 GMT