- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 17 Feb 2009 20:44:51 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4273 --- Comment #49 from Michael Dyck <jmdyck@ibiblio.org> 2009-02-17 20:44:51 --- Here is (I hope) my final summary of the possible resolutions for this bug, in order of increasing impact (as judged by me): 0) Do nothing, leave the 'data on' judgment unsound. 1) In the case of an element type whose type annotation is a complex type of mixed content, where the 'data on' judgment currently has a rule that infers xs:untypedAtomic (which is unsound), instead raise a type error. (So, remove the rule and put in a paragraph saying it's an error.) This is the minimal change that achieves soundness. 2) Write rules to examine the type hierarchy in the ISSD. In some cases (where the ISSD contains no complex types of element-only content), static analysis could avoid raising a type error from 'data on'. But inferring xs:untypedAtomic would still be unsound, we would have to infer xs:anyAtomicType* (which might cause subsequent type errors, depending on the context). 3) Change fn:data's type error err:FOTY0012 to a dynamic error, so static analysis is no longer required to raise it statically. 4) Changes beyond that are probably out of scope for the 1.0/2.0 second edition timeframe. -- 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 Tuesday, 17 February 2009 20:45:01 UTC