I agree with you on this one, C. If an attribute doesn't have a value it shouldn't be in the XML. If there is a need to have a different case for "no attribute" vs "empty attribute", then they should rethink their XML design, possibly utilizing another attribute to indicate the on/off condition. However, I doubt that it would be necessary to differentiate between the two.
...Glenn On Wed, Oct 8, 2008 at 2:41 PM, Cerebrus <[EMAIL PROTECTED]> wrote: > > I doubt it. Elements can be set to xs:nillable, but not attributes. > IMHO, if an attribute or element has a null value, it shouldn't exist > in the XML at all. Because if it does, how do you differentiate > between a NULL value and an empty string? > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/DotNetDevelopment You may subscribe to group Feeds using a RSS Feed Reader to stay upto date using following url <a href="http://feeds.feedburner.com/DotNetDevelopment";> http://feeds.feedburner.com/DotNetDevelopment</a> -~----------~----~----~----~------~----~------~--~---
