[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: XML Schema complex type restriction
XSD misses at least five important mechanisms needed for practical schemas. First, it does not allow parameterization: i.e. parameters supplied that can be used to create cohesive subsets. Interestingly, one of the extensions (pushed by mathematician Dave Peterson IIRC) mooted for SGML in the early 1990s was to turn the parameter entity mechanism into a proper logical expression language (with not, or, and combiners). It is ridiculous that an abstract schema cannot be instantiated just by filling in the missing blanks, but the relentless focus on databases and databinding requirements of XSD shows. Forth, it provides no lifecycle mechanism. For example, there is no way to mark elements as deprecated, and to get validation reports that can tell whether obsolete elements have been used. Fifth, it limits its scope to only the information in a single document. While the most important classes of documents are compound (eBooks, websites, OOXML, etc). And there is an important sixth shortfall: there is no standard XML format for representing the results of validation. So there is no standard way to take the validation results as part of an XSLT toolchain and do stuff with it. (Schematron has ISO SVRL reporting language for this.) You might say that XML Schemas is a technology for constructing dead-ends for your XML. ...perhaps too harsh... Regards Rick On Tue, Sep 26, 2017 at 8:07 AM, u123724 <u123724@gmail.com> wrote: I'd like to share my experience here with the ISO 20012 schema to
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|