[xsd-users] <choice> abuse
Boris Kolpackov
boris at codesynthesis.com
Wed Mar 14 11:00:02 EDT 2007
Hi Ray,
Ray Lischner <rlischner at proteus-technologies.com> writes:
> Upon further reflection, I realize that I was wrong. Code Synthesis
> does not enforce other schema restrictions, such as maxOccurs. There
> is no reason to treat <choice> differently or specially.
I think there is. maxOccurs values other than "1" or "unbounded"
are very rare[1]. Both "1" and "unbounded" are supported by the
interface. On the other hand, <choice> is quite common and adding
some extra safety would be a good idea, I think.
1. Some schema processors exhibit very poor performance with
maxOccurs values greater than "1" but less than "unbounded".
The fact that vendors think this is acceptable confirms
that this case is not widely used.
hth,
-boris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 652 bytes
Desc: Digital signature
Url : http://codesynthesis.com/pipermail/xsd-users/attachments/20070314/8a88d32d/attachment.pgp
More information about the xsd-users
mailing list