OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Resolving Images

[ Lists Home | Date Index | Thread Index ]
  • To: "Andrew Dubinsky" <andy@encomia.com>
  • Subject: RE: [xml-dev] Resolving Images
  • From: "Manos Batsis" <m.batsis@bsnet.gr>
  • Date: Wed, 24 Jul 2002 17:03:49 +0300
  • Cc: <xml-dev@lists.xml.org>
  • Thread-index: AcIzGZplDV9QSeHqTJyy9l+/QlkbPAAAGOPQ
  • Thread-topic: [xml-dev] Resolving Images

> From: Andrew Dubinsky [mailto:andy@encomia.com] 

> A fully resolved link would include the data within the same file
> resource. E.g. a copy of the resource.
> <img src="<<binhex data of gif>>" />

Sorry Andrew, that doesn't seem right at all. Even if it did, it won't
be usable.

> I understand that copying the gif data within each file is fat and
> 'violates' the spirit of the URI concept.

Yes you can say that again :-)

> However, in our use, we must
> have the data bound directly to a digitally signed file. In the normal
> use of links, the underlying content of the link could be changed
> without modifying the hashed value of the document. 

How about bundling the files (html, images and the like) to an

> Any usages of legal documents pointing to user agreements, or other
> click-through agreements fall within the category. E.g. Which 
> agreement
> did you agree to if it was included by reference (and not by direct
> inclusion) if the agreement is no longer available?

Perhaps you need to use SVG instead of HTML.

> In other words, no standard parser would understand it.




News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS