Subject: RE: [xsl] Empty Elements in .NET From: "Andrew Welch" <AWelch@xxxxxxxxxxxxxxx> Date: Thu, 5 Feb 2004 14:47:58 -0000 |
> 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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Empty Elements in .NET, David Carlisle | Thread | Re: [xsl] Empty Elements in .NET, Oleg Tkachenko |
RE: [xsl] Value at position(), SHEIKH Sajjad | Date | [xsl] dynamic sorting, Peter Billen |
Month |