SV: Schema help

>Yes, this has come up a number of times recently, but I personally didn't 
>find the solutions particularly appealing!

>Maybe people that want to do this sort of thing should consider
re-modelling 
>their data so that it works to XSD's strengths. 
I found this amusing in a twisted way, it struck me that working to XSD's
strengths was synonymous with producing particularly ugly XML. 

><task>
>    <!-- common task elements here -->
>    <taskType1>
>        <!-- Task 1 things -->
>    </taskType1>
></task>

>or:

><task>
>    <!-- common task elements here -->
>    <taskType2>
>        <!-- Task 1 things -->
>    </taskType2>
></task>

I'm sorry but are you suggesting that task has a choice of taskType1
taskType2 and so forth? Sometimes I think the worse thing that was ever put
in the xml spec was that thing about verbosity not being a problem.


Of course I've been ranting this for years (the anti xml schema stuff), they
called me mad at the academy, etc. etc. 

Cheers,
Bryan Rasmussen

Received on Tuesday, 15 November 2005 08:55:14 UTC