- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 26 Jul 2007 14:52:49 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4856 ------- Comment #3 from mike@saxonica.com 2007-07-26 14:52 ------- Since raising this I've encountered a use case, where a user defined his own subtype of xs:duration in his schema. He couldn't define it as a subtype of xs:dayTimeDuration, because that's not a type that XML Schema 1.0 recognizes, so it had to be his own type which was equivalent in all but name. (I'm not sure that we consciously recognized when we moved the types from the xdt into the xs namespace, that this would have the consequence that users can no longer use these types in a 1.0 schema.) Arguably this problem will disappear over time, but people will want to write schemas that work under Schema 1.0 for many years to come, and there's no logical reason why we should require someone to cast to our subtypes in cases where there's no logical need for it.
Received on Thursday, 26 July 2007 14:52:54 UTC