[
https://issues.apache.org/jira/browse/XERCESC-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Cantor updated XERCESC-1970:
----------------------------------
Affects Version/s: 3.0.0
3.0.1
3.1.0
3.1.2
3.1.3
3.1.4
> Lax validation skips "known" child elements but partially processes IDs
> -----------------------------------------------------------------------
>
> Key: XERCESC-1970
> URL: https://issues.apache.org/jira/browse/XERCESC-1970
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4
> Reporter: Scott Cantor
>
> When schema wildcards have lax validation, Xerces apparently skips unknown
> children, as it should, but fails to validate known/recognized children
> nested further in the tree, which I'm led to believe is not compliant.
> What's more concerning is that in ignoring such children, the parser *still*
> recognizes attributes of type "ID" and places them into the ID map for the
> document, but does NOT detect or report validation errors if those ID values
> collide with others in the document. Either handle them as an ID or not, but
> don't do it halfway.
> An example like so:
> <Known ID="foo">
> <Extensions>
> <Unknown>
> <Known ID="foo">
> If Extensions is lax, the spec apparently requires that the nested <Known>
> element also be validated, but not only does Xerces not do this, it fails to
> detect the duplicate ID, BUT inserts both ID attributes into the map that
> getElementById uses.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
