- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 11 Feb 2009 00:18:00 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4273 --- Comment #29 from Michael Dyck <jmdyck@ibiblio.org> 2009-02-11 00:18:00 --- Whoops! It has come to my attention that it's impossible to derive types from xs:untyped. Therefore, 'data on element(*,xs:untyped)' can be xs:untypedAtomic without having to worry about subtypes. Consequently, I'll revise some statements about the examples in my comment #26: If construction mode is 'strip': -- The static type of <a>2</a> is element(a,xs:untyped). -- The static type of fn:data(<a>2</a>) is xs:untypedAtomic. -- The static type of 1 + <a>2</a> is xs:integer. But if construction mode is 'preserve', then what I said before holds: -- The static type of <a>2</a> is element(a,xs:anyType). -- Currently, static analysis of fn:data(<a>2</a>) or 1+<a>2</a> must raise type error FOTY0012. -- If we made FOTY0012 a dynamic error, the static type of fn:data(<a>2</a>) would be xs:anyAtomicType*, and static analysis of 1+<a>2</a> would have to raise type error XPTY0004. -- 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 Wednesday, 11 February 2009 00:18:10 UTC