Re: [Saxdotnet-devel] String.Empty vs. null

[Jeff R. <li...@je...>]

> So, I simply don't see a contradiction.

It seems that we are the only ones arguing about this. Elliotte seemed 
to be in favor of string.empty as well and his last email on the subject 
was very strong-- but he also added the caveat that he is a Java guy for 
the sake of this discussion. So if we took a vote:

======================================
2 use string.empty for the URI param
when xmlns="" or xmlns is not present.

1 use null for the above
======================================

This would indicate that we would either need to change such params in 
other callbacks or live with the inconsistency.

Now of course, you are project admin and SAX is historically a 
dictatorship-- as the only other implementer I can tell you that I will 
implement it however you decide.

In any event-- we need to decide, we need to document the decision very 
clearly and we need to make sure our SAX conformance application checks 
for all of the appropriate cases. Which may involve adding a secondary 
test suite.

Cheers,
Jeff