Re: What to do when an <output> link fails

I see that the spec says:



Failure to render the content should <https://www.w3.org/community/xformsusers/wiki/XForms_2.0#intro-reading>  result in a (non-fatal) xforms-output-error <https://www.w3.org/community/xformsusers/wiki/XForms_2.0#evt-output-error> . Failure can occur for many reasons, such as:

The data to be decoded does not conform to the format of xs:base64Binary or xs:hexBinary;
The data does not conform to the mediatype;
An error dereferencing the URI in a item of or derived from type xs:anyURI;
A data format error (e.g. incorrect or unsupported image format);
An unrecognized mediatype identifier string.

so I'm not sure now where we got the idea that a separate event was dispatched for dereferencing a URI.


On the other hand, I see that output-error has no context information.


Steven


On Friday 26 September 2025 13:49:50 (+02:00), Steven Pemberton wrote:



With respect to: https://lists.w3.org/Archives/Public/public-xformsusers/2025Aug/0005

Steven: What to do when failing to dereference a URI
… I believe it should be nonfatal

Erik: I agree, though submit-error is odd

Steven: It's what we use for <instance>
… I'm happy to invent a new error , eg xforms-link-warning

Erik: It is convenient that submit-error already exists, it's just not the right name...

Steven: Let's have time to think it over, and discuss again next time.