Schema validation in 2.3.0 version

Subjects

•	Home
•	VOTE Move XML Commons to Xerces
•	Commented: (XERCESJ 589) Bug with pattern restriction on long strings
•	: Xerces J 2 8 1 Release on Wednesday, September 13th
•	: Xerces J 2 9 0 Release on Wednesday, November 22nd
•	Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
•	Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
•	Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
•	Some consideration about the xerces DOM implementation
•	Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
•	Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
•	retain exception stack traces
•	Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
•	Future of NekoHTML
•	Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
•	DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
•	: xml commons external 1 3 04 Release on Wednesday, November 22nd
•	Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
•	XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
•	First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
•	: xml commons resolver 1 2 Release on Wednesday, November 22nd
•	Typo in RangeToken java Please check
•	Validator features
•	java lang ClassCastException when adopting Node
•	using the org apache xerces impl xs identity package
•	Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
•	Problem with ref attributes and schema validation
•	Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
•	Performance problem under load Xerces with Weblogic 9 x
•	remove ignored memory allocation
•	Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
•	Commented: (XERCESJ 977) Null pointer exception during DOM parsing
•	Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
•	Commented: (XERCESJ 1201) Initial contribution for StAX Event API
•	Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
•	Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
•	Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
•	Updated: (XERCESJ 589) Bug with pattern restriction on long strings
•	StackOverflow
•	xerces Range unnecessarily not garbage collectable if not detached
•	Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
•	Bug in xs:redefine
•	Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
•	Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
•	Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
•	Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
•	Google Summer of Code 2007
•	Xerces J and XInclude relative path issue
•	Assigned: (XERCESJ 206) Stack overflow when using a schema validation
•	Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
•	Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
•	non overriding equals methoda
•	Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
•	Xerces AS3 port
•	Updated: (XERCESJ 325) Regular Expression; Pattern "\| " clause order de
•	Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
•	Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
•	Created: (XERCESJ 1124) Nonspecific schema error message
•	a bug in xerces
•	Updated: (XERCESJ 1201) Initial contribution for StAX Event API
•	Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report

Links

Home

Oracle database error code

Schema validation in 2.3.0 version

Schema validation in 2.3.0 version

2003-03-13 - By Tosello Davide

Reply: 1 2

Hi all,
I am currently triyng to validate W3C VoiceXML documents under many XML
validators.
The current schema has been validated without errors on Xerces-J 2.0.2, XSV
2002/01/11,
IBM SQC 2.1.1 and XMLSpy 4.4.
Using the latest Xerces/J 2.3.0, I cannot parse the latest VoiceXML 2.0
Candidate
Recommendation schema. Here is a simple "Hello world" VoiceXML:

<?xml version="1.0" encoding="UTF-8"?>
<vxml version="2.0" xmlns="http://www.w3.org/2001/vxml"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2001/vxml
http://www.w3.org/TR/voicexml20/vxml.xsd">
<form>
<block>
Hello,world
</block>
</form>
</vxml>

The error message the SAX parser returns is:

org.xml.sax.SAXException: Error parsing XML at line: 363, column: 72 of
http://www.w3.org/TR/voicexml20/synthesis-core.xsd.
Error Message is: a-props-correct.2: Invalid value constraint value
'100.0' in attribute 'volume'

Since Xerces is a fully-conforming Schema parser, I would like to understand if
there is a
bug into Xerces-J/2.3.0 (other validators parse without errors) or if the
synthesis-core.xsd
needs to be modified.

Regards,
Davide

====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please contact us by
replying to MailAdmin@(protected) Thank you
====================================================================

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">

<META content="MSHTML 6.00.2713.1100" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=645473613-13032003><FONT face=Arial size=2>Hi
all,</FONT></SPAN></DIV>
<DIV><FONT face=Arial><FONT size=2><SPAN class=645473613-13032003>I am
currently
triyng to validate W3C VoiceXML documents under many XML
validators.</SPAN></FONT></FONT></DIV><SPAN class=645473613-13032003>
<DIV><FONT face=Arial size=2>The current schema </FONT><FONT face=Arial
size=2>has been validated without errors on Xerces-J 2.0.2, XSV 2002/01/11,
</FONT></DIV>
<DIV><FONT face=Arial><FONT size=2><FONT>IBM SQC<SPAN class=645473613-13032003>
</SPAN></FONT>2.1.1 and XMLSpy 4.4.</FONT></FONT></DIV></SPAN>
<DIV><FONT face=Arial><FONT size=2><FONT>Using the latest Xerces/J 2.3.0, I
cannot parse the latest VoiceXML 2.0<SPAN class=645473613-13032003>
</SPAN></FONT>C<SPAN class=645473613-13032003>andidate
</SPAN></FONT></FONT></DIV>
<DIV><FONT><SPAN class=645473613-13032003></SPAN><FONT face=Arial size=2>R<SPAN
class=645473613-13032003>e</SPAN><SPAN
class=645473613-13032003>commendation</SPAN> schema. </FONT></FONT><FONT
face=Arial size=2>Here is a simple "Hello world" VoiceXML:</FONT></DIV>
<DL>
<DD><FONT face="Courier New"><FONT size=2><?xml version="1.0"
encoding="UTF-8"?></FONT> </FONT></DD>
<DD><FONT face="Courier New"><FONT size=2><vxml version="2.0"
xmlns="http://www.w3.org/2001/vxml"</FONT> </FONT></DD>
<DD><FONT face="Courier New"><FONT size=2><SPAN
class=645473613-13032003>       
</SPAN>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"</FONT>
</FONT></DD>
<DD><FONT face="Courier New"><FONT size=2><SPAN
class=645473613-13032003>       
</SPAN>xsi:schemaLocation="http://www.w3.org/2001/vxml</FONT> </FONT></DD>
<DD><FONT face="Courier New"><FONT size=2><SPAN
class=645473613-13032003>        
   
</SPAN>http://www.w3.org/TR/voicexml20/vxml.xsd"></FONT></FONT></DD>
<DD><FONT face="Courier New"><FONT size=2><SPAN
class=645473613-13032003>   
</SPAN><form></FONT></FONT></DD>
<DD><FONT face="Courier New"><FONT size=2><SPAN
class=645473613-13032003>       
</SPAN><block></FONT></FONT></DD>
<DD><FONT face="Courier New"><FONT size=2><SPAN
class=645473613-13032003>        
   
</SPAN>Hello,world</FONT></FONT></DD>
<DD><FONT face="Courier New"><FONT size=2><SPAN
class=645473613-13032003>       
</SPAN></block></FONT></FONT></DD>
<DD><FONT face="Courier New"><FONT size=2><SPAN
class=645473613-13032003>   
</SPAN></form></FONT></FONT></DD>
<DD><FONT face="Courier New" size=2></vxml></FONT></DD></DL>
<DIV><FONT size=2><FONT face=Arial>The error message the SAX parser returns
is:</FONT> </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face="Courier New" size=2>org.xml.sax.SAXException: Error parsing
XML
at line: 363, column: 72 of</FONT></DIV>
<DIV><FONT face="Courier New"
size=2>http://www.w3.org/TR/voicexml20/synthesis-core.xsd. </FONT></DIV>
<DIV><FONT face="Courier New" size=2>Error Message is: a-props-correct.2:
Invalid value constraint value</FONT></DIV>
<DIV><FONT face="Courier New" size=2>'100.0' in attribute 'volume'</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT size=2><FONT><FONT face=Arial><SPAN class=645473613-13032003>Since
Xerces is</SPAN> a fully-conforming Schema parser<SPAN
class=645473613-13032003>, I would like to understand if there is
a </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT><FONT face=Arial><SPAN class=645473613-13032003>bug
into Xerces-J/2.3.0</SPAN></FONT></FONT> <SPAN
class=645473613-13032003><FONT face=Arial>(other validators parse without
errors) or if the synthesis-core.xsd </FONT></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=645473613-13032003>needs to be
modified.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=645473613-13032003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=645473613-13032003>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=645473613-13032003>Davide</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV><p></p><p>=====================
===============================================<br>CONFIDENTIALITY NOTICE<br
>This message and its attachments are addressed solely to the persons<br>above
and may contain confidential information. If you have received<br>the message
in error, be informed that any use of the content hereof<br>is prohibited.
Please return it immediately to the sender and delete<br>the message. Should
you have any questions, please contact us by<br>replying to MailAdmin@(protected)
. Thank you<br>=================================================================
===</BODY></HTML>