search

microformats / h-entry

For collecting and handling issues with the h-entry vocabulary specification: http://microformats.org/wiki/h-entry
17 stars 5 forks source link

Proposed Duration Property #21

Open dshanske opened 4 years ago

dshanske commented 4 years ago

Identified is a need to define a duration property, which is published by several individuals but with no clear definition.

See Discussion in https://github.com/snarfed/granary/issues/169 summarized below.

The proposed definition is the duration of an audio or video file in the entry, however duration is also used for other items, so it should be only the duration of an audio or video file if there is a video/audio property.

Should the value be the ISO8601 duration format, the derived HTML duration, or just integer seconds? Also, the proposal note in the wiki states p-duration, where it probably should be dt-duration, to match h-event.

iCal and hCalendar use ISO8601 duration format, Media RSS uses seconds. Whatever format is adopted for h-event should be adopted for h-entry for consistency.

Related: http://microformats.org/wiki/h-event defines duration with no format defined. See https://github.com/microformats/h-event/issues/7

dshanske commented 4 years ago

Related: https://github.com/microformats/h-event/issues/7

dshanske commented 4 years ago

Need to discuss/define other items other than audio/video where a duration might be appropriate. Read posts?

capjamesg commented 4 years ago

@dshanske I display a "read time" on my blog. It is somewhat subjective but I know of at least one other person on the IndieWeb displaying read times. Although I do wonder whether this is a piece of information that needs to be marked up in microformats.

As for the format of the value, I can see most use cases would probably be related to audio/video and so integer seconds may be best. Although ISO8601 may be more consistent. I am just giving my first thoughts :)