On Wed, 2008-04-16 at 16:17 +0200, Marcin Floryan wrote:
Things are funny at times. I have just reached a point where I am slightly confused how the XSD should be written (to define parameters) and so I've looked into your XSD and you seem to have been stuck at the same point :-) There is no neat way to define
<param type="int" ..>int</param> <param type="float">float</param> since XSD does not support element typing based on attribute values (fair enough). So either we have some less strict XSD rules (and relay on further validation in code) or we change that element's name to reflect the type as well (I opt for the latter, but wonder what people here think).
Yes, I'm not quite how to do this in XSD, but it seems that it has to be doable. I'd really hate to have to change the XML format just to be able to represent it in XSD. I'm not sure that's a good trade off.
Can some XML expert step up here? :)
--Ted