#microformats 2020-08-23

2020-08-23 UTC
[tantek], [chrisaldrich], [tw2113], [fluffy], strugee, KartikPrabhu, [Joe_Crawford], [James_Gallaghe], kieron-androidtv, craftyphotons, Phae_ and peterrother joined the channel
#
@JamieTanna ↩️ Have you looked into https://indieweb.org by any chance? There's some great stuff we're doing with standards like https://microformats.io/ to make a better Web work alongside the old Web, because adding a hard switchover between new/old unfortunately… https://www.jvt.me/mf2/2020/08/c0tcc/ (twitter.com/_/status/1297476341848330240)
[tantek], rodolfojcj and [tb] joined the channel
#
[tb] So unless I'm reading incorrectly, the mf2 h-entry spec seems to imply that you would only ever have a single value for in-reply-to, like-of, repost-of, and bookmark-of. I'm trying to normalize 'first value only' vs 'accepts multiple values' in my parsing/database schema
#
[tb] Also (and totally tangential question to the first one) — if I have a video post with multiple `u-video` s that are just different derivative encodings, do I put the sizes for each of them into `p-size` and just expect clients to interpret those in parse order as associated to their respective `u-video` URLS? (And similarly for `p-duration` if the `u-video`s are actually different clips from each other)
[snarfed] joined the channel
#
GWG [tb]: There is not yet a derivative recording microformat, but there are proposals
#
[tb] Ah I got the impression that was all the current spec supported because of the example here: https://www.w3.org/TR/jf2/#multiple-urls
#
[tb] In that case though, there would be more than one value for `p-size`
#
GWG https://indieweb.org/User:Vanderven.se_martijn/feed-entries-with-post-type-video
[James_Gallaghe] joined the channel
#
Zegnat Currently there is no system for linking properties together. You would need to create a different h-object for that. But an h-entry can contain any number of properties and duplicate properties as far as mf2 is concerned. Whether consumers like Micropub and Microsub support that is up to each implementation.
#
GWG Zegnat: That would be the h-media proposal, I think.
[JuJu], jeremy, jeremy-, [schmarty], [fluffy] and [tantek] joined the channel
#
[tantek] [tb], jf2 is much smaller subset of mf2json and still quite in flux (eg spec is not up to date with what implementations are doing, might need to do a popup on that)
#
[tantek] h-entry should not have an opinion about singular or plural properties like of those you mentioned. Could you quote from the spec what gave you the impression of “only ever have a single value”?
#
[tantek] More property-specific multivalve indieweb uses we can discuss in #indieweb-dev
#
[tantek] Also size and duration are not h-entry last I checked. Are they even proposed?
#
[tantek] GWG, you’re right, better to work on iterating on h-media to capture sets of photo/video/audio, size, duration
[tb] joined the channel
#
[tb] • [tantek] I think when reading through the core properties http://microformats.org/wiki/h-entry#Core_Properties here, I took the singular vs plural description at face value (i.e. *`p-category`* - entry categories/tags as talking about potentially having multiple and *`u-url`* - entry permalink URL talking as a singular value)
#
[tantek] Ok I can add clarifying informative text that notes that per mf2 general spec, make no cardinality assumptions
jeremy, strugee, [KevinMarks], jamietanna, [eddie], peterrother, [tb] and [chrisaldrich] joined the channel