Thanks, Mike for reply and thoughts.
On Thu, May 24, 2018 at 12:38 PM, Michael Kay mike(_at_)saxonica(_dot_)com <
xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Practically, no, because (a) there isn't going to be another XSLT
specification in the foreseeable future, and (b) there wouldn't be enough
implementors to justify a standard.
Technically, schema validation is closely tied in with the XDM type
system, and this has the consequence that XDM never exposes nodes for which
validation has failed (that is to say, for which the outcome of validation
is "invalid"). It would be possible to relax this, but it would need
careful thought: it would involve a different kind of validation, in which
(a) validation never causes a dynamic error, but (b) data that has been
subjected to validation cannot be assumed to conform to the type against
which it was validated.
There is also an effect on streaming. XSD is designed so that you know,
while processing a start tag, what the type of the element is supposed to
be; but you don't know until you hit the end tag whether the element is
actually valid against that type. This means that if invalid data is to be
made visible to the application, then in a streaming environment the PSVI
data for an element can't be exposed until you reach the end tag.
Of course, there are applications for which it would be very useful to
allow an invalid document to be processed and inspected, but it's probably
a minority requirement.
--
Regards,
Mukul Gandhi
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--