W3C home > Mailing lists > Public > www-svg@w3.org > October 2002

Re: Fallback for broken references.

From: Robin Berjon <robin.berjon@expway.fr>
Date: Tue, 29 Oct 2002 11:52:54 +0100
Message-ID: <3DBE6886.3090308@expway.fr>
To: Jim Ley <jim@jibbering.com>
Cc: www-svg@w3.org

Jim Ley wrote:
> In SVG, you can include content from one document in another, this is
> very useful of course, the problem comes that when it fails, we get no
> indication of anything going wrong, meaning you can get odd results if
> the link is broken (perhaps because the SVG was saved locally, or the web
> connection broke mid transfer)
> 
> The meaning of a document can radically change. I've got a rather
> contrived Llama demo <URL: http://jibbering.com/2002/8/thellamas.svg > *
> which gives a very different message in Batik and ASV (which doesn't
> support external TREF's). Dean Jackson's SVG to text converter also
> demonstrates the problem which shows how much cleverer SVG Access
> Technologies need to be due to the ability to refer to external
> documents, although the TEXT to HTML at least makes the user aware.
> 
> I'm not sure what suggestion to make, perhaps even just require user
> agents to make the user aware that some content is missing, as the
> duplicating of fallback content rather defeats the object.


Is that not a job for setting externalResourcesRequired[1] to true? I 
don't think ASV supports it, but is there anything beyond that which you 
think is required?

[1]http://www.w3.org/TR/SVG11/struct.html#ExternalResourcesRequired


-- 
Robin Berjon <robin.berjon@expway.fr>
Research Engineer, Expway
7FC0 6F5F D864 EFB8 08CE  8E74 58E6 D5DB 4889 2488
Received on Tuesday, 29 October 2002 06:02:31 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:23 GMT