Following a discussion of a presentation (https://github.com/TEIC/atop/blob/dev/Documentation/presentations/Council_repeatability_after_auto-deletion.odp) by @sydb at today's Council meeting, Council arrived at a consensus to the effect that the problem that arises when deletions result in a single wrapper element ( <sequence>, <alternate>, or <interleave>) containing only one child (e.g. <elementRef>) can be circumvented if this scenario is allowed and considered valid. Therefore the <constraintSpec>s "alternatechilden", "interleavechilden", and "sequencechildren" should be removed.
The idea would then be that the @minOccurs and @maxOccurs on the wrapper elements would act in the normal way, combining with those on the single child, to give the actual range of instances allowed.
Following a discussion of a presentation (https://github.com/TEIC/atop/blob/dev/Documentation/presentations/Council_repeatability_after_auto-deletion.odp) by @sydb at today's Council meeting, Council arrived at a consensus to the effect that the problem that arises when deletions result in a single wrapper element (
<sequence>,<alternate>, or<interleave>) containing only one child (e.g.<elementRef>) can be circumvented if this scenario is allowed and considered valid. Therefore the<constraintSpec>s "alternatechilden", "interleavechilden", and "sequencechildren" should be removed.The idea would then be that the
@minOccursand@maxOccurson the wrapper elements would act in the normal way, combining with those on the single child, to give the actual range of instances allowed.