[
https://issues.apache.org/jira/browse/XERCESJ-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Gandhi updated XERCESJ-1508:
----------------------------------
Fix Version/s: 2.12.0
> implementation of XSD 1.1 type tables equivalence, for element declaration
> consistent constraint
> ------------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1508
> URL: https://issues.apache.org/jira/browse/XERCESJ-1508
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema 1.1 Structures
> Affects Versions: 2.11.0
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Fix For: 2.12.0
>
>
> I'm creating this JIRA issue for tracking purpose.
> XML Schema 1.1 enhances the constraint, "Schema Component Constraint: Element
> Declarations Consistent" with following additional clause (the clause
> numbered 4 below):
> (quoted from the XML Schema 1.1 language specification)
> If the {particles} property contains, either directly, indirectly (that is,
> within the {particles} property of a contained model group, recursively), or
> - implicitly- , two or more element declarations with the same expanded name,
> 1 ...
> 2 ...
> 3 ...
> 4 All their {type table}s are either all - absent- or else all are present
> and - equivalent- .
> The equivalence of type tables is defined as follows:
> [Definition:] A Type Table T1 is equivalent to a Type Table T2 if and only if
> all of the following are true:
> 1 T1.{alternatives} has the same length as T2.{alternatives} and their
> corresponding entries are - equivalent- .
> 2 T1.{default type definition} and T2.{default type definition} are -
> equivalent- .
> We implemented this constraint, post Xerces 2.11.0 release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
