ISSUE-2023: Should unresolved resources be categorized as "unsupported values" or "in error"?
Unresolved Resources In Error
Should unresolved resources be categorized as "unsupported values" or "in error"?
- State:
- CLOSED
- Product:
- SVG Tiny 1.2
- Raised by:
- Doug Schepers
- Opened on:
- 2008-07-26
- Description:
- 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. - Related Actions Items:
ACTION-2144 on Cameron McCormack to Rework the invalid IRI reference section (14.1.4) as in the minutes here - due 2008-08-28, closed- Related emails:
- ISSUE-2023 (Unresolved Resources In Error): Should unresolved resources be categorized as 'unsupported values' or 'in error'? [SVG Tiny 1.2] (from sysbot+tracker@w3.org on 2008-07-26)
Related notes:
No additional notes.
Display change log
