RE: Empty Elements in .NET

> Regardless of the form of schema I use .NET creates
> <ERROR a='data' ...></ERROR>
> 
> Rather than the expected form of
> <ERROR a='data' .../>
> 
> The problem is compounded when <xsl:output indent='yes' /> is 
> used.  In the first form the indentation whitespace makes the 
> instance document invalid against either form of schema.  If 
> the second form were generated the indentation would not be an issue.


Really?  So a schema can tell the difference between 

<node></node>

and 

<node/>?

Is that really the case?


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list