W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2012

[Bug 14734] [XSLT 2.0] Literal result elements should not be laxly validated

From: <bugzilla@jessica.w3.org>
Date: Wed, 04 Apr 2012 12:57:32 +0000
To: public-qt-comments@w3.org
Message-Id: <E1SFPmG-0000dL-8h@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14734

Jirka Kosek <jirka@kosek.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jirka@kosek.cz

--- Comment #2 from Jirka Kosek <jirka@kosek.cz> 2012-04-04 12:57:30 UTC ---
I have made more investigation and testing.

Mike conclusions are 100% correct and we can not improve situation if we want
to rely only on XML schemas.

Best what we can do is to keep schema as it is and put additional note into
spec saying something like:

"During validation only this schema should be used. Supplying schemas for
namespaces of literal result elements will likely produce false error messages
because of W3C XML Schema limitations."

If we could use NVDL, situation will be much better, we can strip elements in
non-XSLT namespaces before validation and we can then use existing XSLT 2.0
schema.

If WG thinks that it is worth we can produce WG Note which will show how to use
NVDL for this or how to modify existing schemas to work with XSLT 2.0 schema
even when processContents="lax" is used (putting wildcards into schemas for
literal result elements).

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 4 April 2012 12:57:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:38 UTC