[Murray]I think I remember seeing somewhere that Telegram didn't like nested `h-entry` but is it generally okay to do so from a spec perspective? Struggling to really find any clear guidelines on structure like that (links also appreciated 🙂 )
Zegnat[Murray]: microformats2 has no limitations on nesting or properties or amount of properties. Spec-wise. So if you have a good use-case, go for it, and preferably document it on a wiki (either microformats.org or indieweb.org depending on your use).
ZegnatBut of course if you are pioneering a new data format, it can be that microformats consumers (like Telegram, webmentions endpoints, etc.) will not know what to do with it yet. Would need to grow into a community convention for tools to start supporting it, usually.
[Murray]Thanks. In terms of use-case, I'm actually wondering if `h-cite` would be more appropriate. Effectively, I'm trying to mark up a "further reading" table, so a list of reference links. The aim here, though, is to also send webmentions when the article is published to all of those links, but I want to be able to control what _kind_ of mention is received. As in, most of the time references will just be mentions, but sometimes they're tantamount
[Murray]I guess that's the tricky part: inherently, I'm doing this so that other people can correctly parse the mention being sent, so it needs to at least be approachable 😄 but I fear I'm doing something which no parsers will treat as valid...
KartikPrabhu, JK_na, [Rose], jalcine[m] and jamietanna[m] joined the channel
ZegnatAh hmm, interesting. I would say there is nothing limiting the root h-entry to be a bookmark-of multiple articles at the same time. So you would end up with one h-entry with multiple u-bookmark-of properties that all contain their own h-cites.
[KevinMarks]The challenge is for the site receiving the mention to make sense of it - they may nor handle being pinged for a nested mention so may either show a generic mention or elide the long entry.
[tw2113], [jgmac1106] and [tantek] joined the channel
[Murray] Thanks. In terms of use-case, I'm actually wondering if `h-cite` would be more appropriate. Effectively, I'm trying to mark up a "further reading" table, so a list of reference links. The aim here, though, is to also send webmentions when the article is published to all of those links, but I want to be able to control what _kind_ of mention is received. As in, most of the time references will just be mentions, but sometimes they're tantamount
[KevinMarks] The challenge is for the site receiving the mention to make sense of it - they may nor handle being pinged for a nested mention so may either show a generic mention or elide the long entry.