[Bug 13674] [XQ30] schema-element() types behave differently in different modules.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13674

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |

--- Comment #12 from Michael Kay <mike@saxonica.com> 2011-10-07 14:44:44 UTC ---
(In reply to comment #11)
> (In reply to comment #7)
> > Reopening because I don't think the issue has been adequately addressed.
> 
> What is the issue? Could you please clearly state what problem needs to be
> solved?

It is explained in great detail in the initial bug report, and is then
generalised to a wider problem in the first paragraph of comment #1. In
summary, different modules can have different schemas and this means that an
element validated with type T in one module can be invalid against type T in
another module, which violates type soundness. My proposal in comment #7 is to
"fix" this by strengthening the existing rules requiring the schemas used by
different modules to be consistent with each other.

-- 
Configure bugmail: http://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 Friday, 7 October 2011 14:44:50 UTC