W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > October to December 2011

[Bug 14446] Conflicting statements on pre-override schema documents

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Dec 2011 00:46:38 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1RfhfC-0003GM-14@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14446

--- Comment #2 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> 2011-12-28 00:46:37 UTC ---
I think the conflict is a consequence of inattention rather than two conscious
decisions that conflict with each other.

The XSLT form of the chameleon transformation was introduced in a proposal
primarily aimed at bug 4767
(https://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.b4767.html#chameleon-xslt);
there was no discussion that I can remember or that I have found concerning its
schema-awareness.  

So it may be worth discussing the schema awareness of the transforms (both
chameleon and override).  

The current formulation of the chameleon transform uses schema awareness to
identify attributes of type QName, but I think it could in principle be
rewritten to act on the specific attributes we know are typed as QNames
instead, without schema awareness and thus without any requirement that the
input be schema-valid.  That would allow us to avoid heading back into the
problem of schema-validity for schema documents, which we have not found an
easy one to deal with.

The current formulation of the override transform is also schema-aware, but
there is clearly no problem writing a schema-agnostic version.

-- 
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, 28 December 2011 00:46:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 December 2011 00:46:39 GMT