Lists Home |
Date Index |
Thanks for the reminder and the answer :)
> >I have a problem using XML/XHTML for binary images. I cannot have
> >externally resolved links within the document.
> Can you give an example of what you mean by "externally
> resolved links"?
Externally resolved link (to me) indicates a reference to an external
(outside the file) definition. E.g. a pointer.
<img src="/images/dot.gif" />
<img src="http:://www.mydomain.com/images/dot.gif" />
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>>" />
I understand that copying the gif data within each file is fat and
'violates' the spirit of the URI concept. 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.
In a sample use imagine the following xhtml page the end user sees
within a browser:
Your interest rate is:
<The browser displays a gif of the image for 5%>
At some point in the future, due to a number of reasons, the ratex.gif
referenced in the file could be unavailable, overwritten by a different
file or simply gone. This would substantively change the content without
changing the original document.
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?
> >Is there an allowance for CDATA within an attribute?
> Nope. You will have to use an element and come up with a way
> to decode the data on the client.
In other words, no standard parser would understand it.
Is this an issue to anyone but me?