I agree that 30D isn't always equal to 1M, I just don't know what to do about it. I don't think there's going to be a way to make everyone happy with timeDuration. If you specify a duration of 1M, do you mean 30D, or "this date next month", or "4 weeks from today"? If you specify 30D, is that less than 1M if you happen to be in January but greater than 1M if you're in February? Should a start instant even be assumed at all? What if you specify a duration of "2000-01-19T13:00:00/P1M"? Is that equal to "2000-02-01T13:00:00/P1M"? Should the start instants be disregarded during comparson? Should you be using recurringInstant instead of timeDuration?
george -----Original Message----- From: Arnold, Curt [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 19, 2000 11:13 AM To: '[EMAIL PROTECTED]' Subject: RE: Proposal for Xerces-J Schema validators for timeInstant and timeDuration I had overlooked those sections. It definitely makes comparision precise. I don't think it is acceptible for an application to not be able to distinguish 30D from 1M since legally they are different things. Hopefully, you could parse out the months and years separately from the precise durations and the do your range checks like (this.months*259200+this.seconds) > (other.months*259200+other.seconds)
