Collisions with identifiers in DOMError.type

Hello,

The changes are high that I have misinterpreted how DOM 3 Core's DOMError 
should be used, but currently I see that DOMError.typeS could lead to 
"symbol" collisions, that identifiers implementors chooses for its own 
purposes can collide with other implementors choices or future developments 
of DOM.

In other words, if for code of mine decides to submit DOMErrorS of type 
"my-type", how do I know W3C doesn't pick that type name for a future 
specification, or that a user install software that also happens to use that 
identifier?

From what I can tell, the only way to avoid collisions, is to constrain the 
DOMError.type to "context" and "time", but that is a complicated discussion.

Assuming I now am right so far, I think the solution would be to base DOMError 
"identification" around URIs. That a DOMError, in addition to its type, had 
an URI, and hence made it QName-like.

After a quick thought, it seems possible to introduce such a mechanism without 
breaking backwards compatibility. Discussion provided on request.


Regards,

		Frans

KDE Developer

Received on Monday, 4 April 2005 11:43:05 UTC