[ 
http://issues.apache.org/jira/browse/XERCESC-1442?page=comments#action_12313607 
] 

Jesse Pelton commented on XERCESC-1442:
---------------------------------------

Xerces is doing the right thing. According to the schema spec, the value of a 
source attribute must be a URI. (See 
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#element-documentation.)
This is clearly not the case (or even the intent) in the affected schema.

This bug is invalid.

> XSD validaton error from SCMPrint sample
> ----------------------------------------
>
>          Key: XERCESC-1442
>          URL: http://issues.apache.org/jira/browse/XERCESC-1442
>      Project: Xerces-C++
>         Type: Bug
>   Components: Samples/Tests, Validating Parser (Schema) (Xerces 1.5 or up 
> only)
>     Versions: 2.6.0
>  Environment: OS: Windows XP; SP : MSVC++ 6.0
>     Reporter: Anu Joseph

>
> When I tried to validate the XSD available at 
> http://eudravigilance.emea.eu.int/schema/XEVMPD.xsd using Xerces2.60 SCMPrint 
> Sample I'm getting paring errors like 
> Error at file C:\XEVMPD.xsd, line 409, char 91
>   Message: Value 'The type of the operation for this entity.' is NOT a valid 
> URI
> Error at file C:\XEVMPD.xsd, line 410, char 83
>   Message: Value ' 1 = Insert 2 = Update 4 = Nullify' is NOT a valid URI
> Error at file C:\XEVMPD.xsd, line 450, char 91
>   Message: Value 'The type of the operation for this entity.' is NOT a valid 
> URI
> ..................
> But the same file is validating finely in XML Spy. I'm not getting any clue 
> why this parser is happening from the specifed XSD. All error reported is in 
> 'xs:documentation source'; Seems to be a limitation

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to