> On the other hand, "Such errors are not fatal, but must be reported by > the xml:id processor to the application invoking it." > XOM can check all the constraints. However, it has no concept of a > non-fatal error or a warning. For XOM, errors are either fatal or > nonexistent. XOM can either report a fatal error on spotting a violation > of am xml:id MUST or it can do nothing. It does seem worth allowing for processors that can't return any non-fatal errors when they are otherwise successful. We are considering removing the phrase "to the application invoking it" from the quoted sentence, so that it would acceptable merely to print a warning to the user. We are not however happy with the idea of these errors being silently ignored - that would not help interoperability. Does that help you? -- RichardReceived on Wednesday, 11 May 2005 13:30:36 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:38 GMT