Cart
[Home] [By Thread] [By Date] [Recent Entries]
> XSD 1.0 had xsi:type because its bogus models of what people > used attributes for was not sustainable. > > XSD 1.1 fixes this a little by allowing selection of type by > a wider range of markup. So I would expect that xsi:type will > wither on the vine over the next decade. I don't know that it > is a show-stopper, because there is a better workaround. > > (The rub being that where companies don't switch to the > latest version of the XSD 1.1 spec, they will be more stuck > with xsi:type. And this rub exists largely because XSD 1.0 is > so monolithic that implementers are loath to re-visit their > implementations.) There are some important specs like FpML that (for better or for worse) place very heavy reliance on xsi:type, and the reality is that they aren't going to change in a hurry: there are zillions of financial transactions whizzing around the world that use this attribute. Incidentally XSLT also makes use of namespaced attributes (e.g. xsl:use-when). They aren't used in every stylesheet, but they serve an important purpose and you can't just get rid of them. Regards, Michael Kay http://www.saxonica.com/ http://twitter.com/michaelhkay
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
