This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
QT approved comment In 3.3.7.1 it's not clear why the seconds component of a duration is modelled as precisionDecimal rather than decimal, or whether this gives QT any compatibility problems. This seems to be saying that PT1S is not identical to PT1.0S, which would imply that a QT implementation is expected to maintain the distinction; it's not clear that this is useful or desirable, especially as there is no distinction between PT1M and PT60S. It seems very odd that an enumeration facet of "PT60S" should permit "PT1M" but disallow "PT60.0S".
(In reply to comment #0) > In 3.3.7.1 it's not clear why the seconds component of a duration is modelled > as precisionDecimal rather than decimal, or whether this gives QT any > compatibility problems. Fear not; this is a typo and it will be corrected to read 'decimal'.
The WG concurred with your comment, and the status quo document has been changed accordingly. Please let us know that you agree with this resolution of your issue, by adding a comment to the issue record and changing the Status of the issue to Closed. (Or, if you do not agree with this resolution, please add a comment explaining why. If you wish to appeal the WG's decision to the Director, then also change the Status of the record to Reopened. If you wish to record your dissent, but do not wish to appeal the decision to the Director, then change the Status of the record to Closed.) If we do not hear from you in the next two weeks, we will assume you agree with the WG decision.
Fine