RE: [XQuery] MS-XQ-LC1-017

I also think it should be permitted to raise a static error if the
expected type is xs:date* and the supplied type is xs:int*, even though
this will not always fail dynamically, since () is a valid instance of
both types.
 
Michael Kay

-----Original Message-----
From: public-qt-comments-request@w3.org
[mailto:public-qt-comments-request@w3.org] On Behalf Of Don Chamberlin
Sent: 06 February 2004 19:08
To: Michael Rys
Cc: public-qt-comments@w3.org
Subject: Re: [XQuery] MS-XQ-LC1-017



Fixed as suggested. Thanks!
--Don Chamberlin




"Michael Rys" <mrys@microsoft.com> 
Sent by: public-qt-comments-request@w3.org 


01/20/2004 11:40 AM 


To
<public-qt-comments@w3.org> 

cc

Subject
[XQuery] MS-XQ-LC1-017

	





Section 2.2.3.2 Dynamic Analysis Phase                 
Editorial/Technical                 

"If the Static Typing Feature is not in effect, an implementation is
allowed to raise type-related warnings during the static analysis phase,
but it must proceed with the dynamic evaluation phase despite these
warnings. In this case, type errors must be detected and raised during
the dynamic evaluation phase.": This is too strong. If I know for sure
that I always will have a dynamic type error (e.g., the expected type is
xs:string and the passed value is always an instance of xs:int, I should
be able to raise this type error during the static phase even if the
static typing feature is not employed).