 |
|
|
Hi Folks,
In XSD 1.1 vendors are allowed to extend the language with additional (vendor-unique) datatypes and facets.
Example: In some countries the decimal point symbol is the comma; so a vendor may provide a new decimal datatype and a new facet for specifying the decimal point symbol:
<xs:simpleType name="money">
<xs:restriction base="vendor:decimal">
<vendor:delimiter value="," />
<xs:restriction>
</xs:simpleType>
This is very useful.
However, this capability represents an uncertainty in what things are in the language ("If you're using this XSD 1.1 tool then these x,y,z things are in the language, if you're using that XSD 1.1 tool then these a,b,c things are in the language"). For some of my clients:
uncertainty = risk
For those clients, risk must be mitigated.
Thus, I issue a plea to all XSD 1.1 vendors: please provide a switch to turn on/off vendor-unique extensions.
I believe that providing a switch to turn on/off vendor-unique extension will give vendors a market advantage.
Thanks for your time.
/Roger
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
