You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inspired by snarfed/granary#169. mf1 (both [hAudio](http://microformats.org/wiki/haudio and hCalendar) used to recommend ISO 8601 durations for duration properties. This made it clear for both authors and consumers what sort of value they could expect.
Currently we do not specify any duration format for h-event’s dt-duration. Would it be a good idea if we did?
I would lean towards specifying HTML’s duration syntax. This will mean it stays compatible with HTML datetime properties.
The text was updated successfully, but these errors were encountered:
Inspired by snarfed/granary#169. mf1 (both [hAudio](http://microformats.org/wiki/haudio and hCalendar) used to recommend ISO 8601 durations for
duration
properties. This made it clear for both authors and consumers what sort of value they could expect.Currently we do not specify any duration format for h-event’s
dt-duration
. Would it be a good idea if we did?I would lean towards specifying HTML’s duration syntax. This will mean it stays compatible with HTML
datetime
properties.The text was updated successfully, but these errors were encountered: