W3C home > Mailing lists > Public > public-svg-wg@w3.org > July to September 2008

ISSUE-2023 (Unresolved Resources In Error): Should unresolved resources be categorized as "unsupported values" or "in error"? [SVG Tiny 1.2]

From: SVG Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Sat, 26 Jul 2008 11:20:15 +0000 (GMT)
To: public-svg-wg@w3.org
Message-Id: <20080726112015.85DA46B62A@kent.w3.org>

ISSUE-2023 (Unresolved Resources In Error): Should unresolved resources be categorized as "unsupported values" or "in error"? [SVG Tiny 1.2]

http://www.w3.org/Graphics/SVG/WG/track/issues/2023

Raised by: Doug Schepers
On product: SVG Tiny 1.2

Currently, the spec says, "When attribute externalResourcesRequired has been set to true on the referencing element or one of its ancestors, then an unresolved external IRI reference (i.e., a resource that cannot be located) shall represent an error (see Error processing)."
http://dev.w3.org/SVG/profiles/1.2T/publish/linking.html#ReferenceRestrictions

And Error Processing says, "A document can go in and out of error over time. For example, document changes from the SVG uDOM or from animation can cause a document to become in error and a further change can cause the document to become correct again.  When a document is in error the SVG user agent must provide a highly perceivable indication of error."
http://dev.w3.org/SVG/profiles/1.2T/publish/implnote.html#ErrorProcessing

I question whether an unresolved resource, whether required or not, should ever put the document in error; rather, it should be treated as an unsupported value:
http://dev.w3.org/SVG/profiles/1.2T/publish/implnote.html#UnsupportedProps

We should resolve this one way or another and clarify it in the spec.
Received on Saturday, 26 July 2008 11:21:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:09 UTC