W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2002

F&O WD: Issue 150: Should we support comparisons of date/time types that return indeterminate results?

From: Jeni Tennison <jeni@jenitennison.com>
Date: Thu, 9 May 2002 08:36:47 -0400 (EDT)
Message-ID: <1251482335966.20020509133642@jenitennison.com>
To: public-qt-comments@w3.org
Hi,

You ask for comments on Issue 150: Should we support comparisons of
date/time types that return indeterminate results?

I strongly believe that you should support comparisons between
date/time types that return indeterminate results, and between
duration types that return indeterminate results. I think that this is
a question of finding a balance between logical robustness and
usability, and that usability should be more important. People
should be able to test whether a year is longer than a second, or
whether 35 days is longer than a month.

Given that there's support for dealing properly with error values in
logical expressions, why not have indeterminate results return an
error? Users can then choose to treat that error as true or false, or
deal with it specially, as their application requires.

I think that this is particularly important not for individual
comparisons but for the effect that it has on sorting. From what I can
tell, it's currently not possible to sort elements on attributes that
are declared with the type xs:duration, without taking extra steps to
convert them into one of the two xs:duration subtypes. I don't think
that users should be made to jump through this hoop -- it should "just
work".

Cheers,

Jeni
---
Jeni Tennison
http://www.jenitennison.com/
Received on Thursday, 9 May 2002 14:45:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:22 GMT