This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The expected results for op-subtract-dayTimeDurations-2 show successful execution, but the test should fail FORG0006 because the EBV of a duration is not defined. Michael Kay
Applies also to: op-multiply-dayTimeDuration-2 op-multiply-dayTimeDuration-12 op-divide-dayTimeDuration-2
Also affects: op-subtract-dates-yielding-DTD-4
Also affects op-add-yearMonthDuration-to-dateTime-2 op-add-yearMonthDuration-to-dateTime-3 op-add-yearMonthDuration-to-dateTime-4 op-add-yearMonthDuration-to-dateTimealt-5 op-add-yearMonthDuration-to-dateTime-9 op-add-yearMonthDuration-to-dateTime-10 op-add-yearMonthDuration-to-dateTime-12
Also affects: op-add-dayTimeDuration-to-dateTime-2 op-add-dayTimeDuration-to-dateTime-3 op-add-dayTimeDuration-to-dateTime-4 op-add-dayTimeDuration-to-dateTime-5 op-add-dayTimeDuration-to-dateTime-9 op-add-dayTimeDuration-to-dateTime-10 op-add-dayTimeDuration-to-dateTime-12
Also affects op-subtract-yearMonthDuration-from-dateTime-2 op-subtract-yearMonthDuration-from-dateTime-3 op-subtract-yearMonthDuration-from-dateTime-4 op-subtract-yearMonthDuration-from-dateTime-5 op-subtract-yearMonthDuration-from-dateTime-9 op-subtract-yearMonthDuration-from-dateTime-10 op-subtract-yearMonthDuration-from-dateTime-12
Also affects: op-subtract-dayTimeDuration-from-dateTime-2 op-subtract-dayTimeDuration-from-dateTime-3 op-subtract-dayTimeDuration-from-dateTime-4 op-subtract-dayTimeDuration-from-dateTime-5 op-subtract-dayTimeDuration-from-dateTime-9 op-subtract-dayTimeDuration-from-dateTime-10 op-subtract-dayTimeDuration-from-dateTime-12
Also affects: op-add-yearMonthDuration-to-date-2 op-add-yearMonthDuration-to-date-3 op-add-yearMonthDuration-to-date-4 op-add-yearMonthDuration-to-date-5 op-add-yearMonthDuration-to-date-9 op-add-yearMonthDuration-to-date-10 op-add-yearMonthDuration-to-date-12 op-add-dayTimeDuration-to-datealt-2 op-add-dayTimeDuration-to-date-3 op-add-dayTimeDuration-to-date-4 op-add-dayTimeDuration-to-date-5 op-add-dayTimeDuration-to-date-9 op-add-dayTimeDuration-to-date-10 op-add-dayTimeDuration-to-date-12
Also affects: op-subtract-yearMonthDuration-from-date-4 op-subtract-yearMonthDuration-from-date-5 op-subtract-yearMonthDuration-from-date-9 op-subtract-yearMonthDuration-from-date-10 op-subtract-yearMonthDuration-from-date-12 op-subtract-yearMonthDuration-from-date-17 op-subtract-yearMonthDuration-from-date-18
Also applies to op-subtract-dayTimeDuration-from-date-2 op-subtract-dayTimeDuration-from-date-3 op-subtract-dayTimeDuration-from-date-4 op-subtract-dayTimeDuration-from-date-5 op-subtract-dayTimeDuration-from-date-9 op-subtract-dayTimeDuration-from-date-10 op-subtract-dayTimeDuration-from-date-12
Also applies to op-subtract-dayTimeDuration-from-time-3 op-subtract-dayTimeDuration-from-time-4 op-subtract-dayTimeDuration-from-time-5 op-subtract-dayTimeDuration-from-time-9 op-subtract-dayTimeDuration-from-time-10 op-subtract-dayTimeDuration-from-time-12
Applies also to op-subtract-dayTimeDuration-from-time-15 op-subtract-dayTimeDuration-from-time-16
Applies also to op-subtract-dayTimeDuration-from-time-17
Fixed: Tests were changed to use the string value of the type (date, time, dateTime, etc.) Tests and results were resubmitted. Please Close the bug if you agree with resolution. Thanks, Carmelo Montanez
I'm still somewhat mystified by *why* these durations are being converted to booleans - it seems to have the consequence that the processor can produce almost any non-error result from the duration arithmetic and still pass the test - but I'll close it anyway.