I disagree that the distinction isn't significant. For instance in XQuery this means
fn:data(/time);
could return xdt:anyAtomicType, thus
fn:get-hours-from-time(/time)
cannot be checked statically but instead must resort to dynamic failures. This is just one of many places where W3C XML Schema's inconsistent rules cause problems for type checking in XQuery.
________________________________
From: Jeni Tennison [mailto:]
Sent: Tue 9/9/2003 8:40 AM
To: Dare Obasanjo
Cc:
Subject: Re: [xml-dev] Re: RE : [xml-dev] Text or tags choice with XSD
Hi Dare,
> I remember that errata, it causes a few problems for XQuery and IMHO
> shouldn't have been accepted. A simple type being the derived type
> of a complex type is just weird.
I agree that deriving a simple type from a complex type would be
horrible. But in this case you're deriving a complex type with simple
content from a complex type with complex content, which is somewhat
different (though you might still think it's weird, I suppose).
Cheers,
Jeni
---
Jeni Tennison
http://www.jenitennison.com/
