- From: John Cowan <cowan@ccil.org>
- Date: Mon, 20 Mar 2006 11:26:12 -0500
- To: Elliotte Harold <elharo@metalab.unc.edu>
- Cc: Michael Kay <mike@saxonica.com>, 'xom-interest' <xom-interest@lists.ibiblio.org>, 'Wolfgang Hoschek' <whoschek@lbl.gov>, public-xml-id@w3.org
Elliotte Harold scripsit: > Yes, this sort of non-fatal error is an especial pain for XOM because > it has no non-fatal errors. The only thing it does to report an error > is throw an exception. There's no ErrorHandler as in SAX, nor does > XOM have any other means of talking to the end user. If xml:id errors were marked "fatal", then *every* implementation would have to treat them as fatal. However, there is nothing stopping XOM from (a) treating the errors as fatal in every case, or (b) providing a switch the user can set to "Ignore xml:id errors" or "Treat xml:id errors as fatal", or (c) providing a hook such that elements with xml:id errors are passed to the hook, or .... -- Samuel Johnson on playing the violin: John Cowan "Difficult do you call it, Sir? cowan@ccil.org I wish it were impossible." http://www.ccil.org/~cowan
Received on Monday, 20 March 2006 16:26:18 UTC