Re: Must vs. fatal error

/ Elliotte Rusty Harold <elharo@metalab.unc.edu> was heard to say:
| While attempting to hook XOM up to the xml:id test suite, I've
| uncovered a problem.
|
| On the one hand, "An xml:id processor must assure that the following
| constraints hold for all xml:id attributes...An xml:id error occurs
| for any xml:id attribute that does not satisfy the constraints."
|
| 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.
|
| Given this constraint, I'm not sure if it's possible for XOM to be
| conformant to xml:id.

The WG seeks to resolve this issue by rewording Section 6 as follows:

  A violation of the constraints in this specification results in an
  xml:id error. Such errors are not fatal, but should be reported by
  the xml:id processor. In the interest of interoperability, it is
  strongly recommended that xml:id errors not be silently ignored.

Please let us know if this resolution is unsatisfactory.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.