[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Another published schema broken by XML Schema erratachange

• To: "Henry S. Thompson" <ht@i...>
• Subject: Re: Another published schema broken by XML Schema erratachange
• From: Robert Koberg <rob@k...>
• Date: Wed, 24 Mar 2004 03:47:58 -0800
• Cc: Bob Foster <bob@o...>, xml-dev@l...
• In-reply-to: <f5bu10ey1yn.fsf@e...>
• Organization: liveSTORYBOARD
• References: <20040323222454.716B49BE0D@m...> <4060C9F5.2080808@o...> <f5bu10ey1yn.fsf@e...>
• User-agent: Mozilla Thunderbird 0.5 (Macintosh/20040208)

How do you create a valid JSP that renders HTML?

<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page">
   <html/>
</jsp:root>

since it is not in 'xsd:any namespace' -- how?

I usually just create/render well-formed HTML and then use a servlet 
filter to XSL identity transform to HTML or XHTML(xml).


?
-Rob



Henry S. Thompson wrote:

> Bob Foster <bob@o...> writes:
> 
> 
>>http://java.sun.com/dtd/jspxml.xsd
>>
>>This is the schema for JSP 1.2 XML syntax. If you want to use it, you
>>will need to download a copy, add a \ in front of the - in the
>>definition of the AsciiName entity and use the local copy instead.
>>
>>I mention this not just to further vent my annoyance that this schema
>>and others like it were broken by an "errata" change
> 
> 
> <snip/>
> 
> Are you suggesting the contradiction in the spec. regarding dash as a
> range wasn't an problem?  Or that despite having found the error we
> shouldn't have corrected it?
> 
> In the case of errors like this, which compromise interop because
> different implementations choose different solutions to the problem
> created by the contradiction, it is inevitable that resolving this
> will mean some existing documents which _some_ existing processors
> were happy with become invalid.  The benefits in improved interop are
> worth the resulting need to upgrade, in my opinion.
> 
> In any case, having said all that as my personal opinion.  The
> Proposed Edited Recommendation is just that, proposed, so please
> submit a comment to www-xml-schema-comments@w... objecting to
> erratum E2-18, if indeed you think the problem it addresses [1]
> shouldn't have been fixed in this way.
> 
> ht
> 
> [1] http://www.w3.org/2001/05/xmlschema-rec-comments.html#pfiregexcharRange

• Follow-Ups:
  • Re: Another published schema broken by XML Schema erratachange
    • From: Bob Foster <bob@o...>

• References:
  • Re: ns 1.1
    • From: richard@c... (Richard Tobin)
  • Another published schema broken by XML Schema errata change
    • From: Bob Foster <bob@o...>
  • Re: Another published schema broken by XML Schema erratachange
    • From: ht@i... (Henry S. Thompson)

• Prev by Date: Re: Another published schema broken by XML Schema erratachange
• Next by Date: problems getting the value of a float with XSD
• Previous by thread: Re: Another published schema broken by XML Schema erratachange
• Next by thread: Re: Another published schema broken by XML Schema erratachange
• Index(es):
  • Date
  • Thread