[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Empty Elements in .NET
have schemas ( DTD, and W3C) that define some elements as EMPTY. Explicitly in the DTD <!ELEMENT ERROR EMPTY> and implicitly in a W3C schema by having a complex type with no <xs:sequence></xs:sequence> 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. <xsl:strip-space> has no impact on the issue. Is there a place in the XSLT where I should be identifying the output document schema ( in either format) so as to force EMPTY elements to use the short form? Greg Alvord Gallagher Financial Systems 800-989-9996 XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|