http://www.w3.org/Bugs/Public/show_bug.cgi?id=9327 Michael Dyck <jmdyck@ibiblio.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jmdyck@ibiblio.org --- Comment #1 from Michael Dyck <jmdyck@ibiblio.org> 2010-03-27 01:08:11 --- (a) An implementation that does not support the Static Typing Feature will yield an xs:untypedAtomic value as you say. (b) An implementation that supports the STF based on 1st edition FS will, during Static Type Analysis, infer a static type of xs:untypedAtomic for the query, and then proceed as in (a). (c) An implementation that supports the STF based on 2nd edition FS will, during Static Type Analysis, fail to infer a static type for the fn:data() call, and instead raise FOTY0012. The test-case's expected result only admits (c). If we augment the expected result to admit (a), it will also admit (b), and the test-case will cease to have much point. (It certainly would no longer reflect the resolution of 4273 in any useful way.) Instead, perhaps we should simply move the test-case into the StaticTyping test-group, where (as I understand it), the expected results don't have to reflect the behaviour of an implementation that does not support the STF. -- 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 Saturday, 27 March 2010 01:08:13 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:30 UTC