Comment/Suggestion: DOM L3 L&S

With the current interfaces there is good no way for a calling application 
to programatically decide what action to take according to the reason for 
parsing failure.

My suggestion is to extent the exising DOMError interface to include two 
more read only attributes: domain (DOMString) and error code (unsigned 
short).  W3C could define a set of general error codes that parser 
implementations can choose to implement, but allows different 
implementations to extend the error code set in seperate domains.  This 
way calling applications can look at the domain and error code and easily 
make a decision on what action to take (eg poorly formed XML versus I/O 
error versus validation error).

Received on Thursday, 29 August 2002 22:55:46 UTC