W3C home > Mailing lists > Public > xmlschema-dev@w3.org > March 2011

RE: What is lost if xsd:choice is jettisoned?

From: Costello, Roger L. <costello@mitre.org>
Date: Thu, 10 Mar 2011 14:36:37 -0500
To: "xmlschema-dev@w3.org" <xmlschema-dev@w3.org>
Message-ID: <9E51F88D5247B648908850C35A3BBB50052E8274F7@IMCMBX3.MITRE.ORG>
> Roger's question is partly of purely theoretical interest, and
> partly as potential advice for people who find themselves
> dissatisfied with the way schema binding tools handle 
> choices.

Thanks Michael. That is correct.

Thanks to everyone who responded. Excellent! I will write a summary of the responses and post it.

/Roger

-----Original Message-----
From: C. M. Sperberg-McQueen [mailto:cmsmcq@blackmesatech.com] 
Sent: Thursday, March 10, 2011 2:25 PM
To: Andy Davidson
Cc: C. M. Sperberg-McQueen; Costello, Roger L.; xmlschema-dev@w3.org
Subject: Re: What is lost if xsd:choice is jettisoned?


On Mar 10, 2011, at 12:07 PM, Andy Davidson wrote:

> Just my 2 cents
> 
> I work on a very large project with over 100 engineers building clients and services using Java and ObjC.  Most of these engineers are fairly inexperience and are not experts on xml schema. <choice> is very easy for them to understand, "ref" causes lots of confusion and bugs.
> 
> We use choice in our request/response definitions. The response is either a "result" or an "error". Switching our interfaces to work this way has dramatically reduced the number of bugs in our system
> 
> Please do not remove <choice>

Don't worry: the chances of choice being removed are zero.

Roger's question is partly of purely theoretical interest, and
partly as potential advice for people who find themselves
dissatisfied with the way schema binding tools handle 
choices.

-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com 
* http://cmsmcq.com/mib                 
* http://balisage.net
****************************************************************
Received on Thursday, 10 March 2011 19:37:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 10 March 2011 19:37:11 GMT