- From: <Paul.V.Biron@kp.org>
- Date: Thu, 20 Apr 2006 13:19:03 -0700
- To: edday@obj-sys.com
- Cc: gcowe@origoservices.com, public-xsd-databinding@w3.org, public-xsd-databinding-request@w3.org
Received on Thursday, 20 April 2006 20:23:40 UTC
> I have seen this mentioned as a limitation in some binding products > and, quite frankly, I don't understand it. In general, all a binder > needs to do is examine the start tag of the element and it can > determine the contents. It can then use something like a union type > in C to hold the different alternatives or a base class with > generated derived classes in an OO language. It shouldn't be that hard to do. or you can always include each child of the choice as member variables and add a bit of conditional code to constructors and setters to keep things consistent. I agree that implementing choice shouldn't be rocket science :-( pvb
Received on Thursday, 20 April 2006 20:23:40 UTC