also see voxpelli/webpage-webmentions#10

looks like php-mf2 also auto-generates p-name from entire h-entry text, not just from e-content, so i guess that is correct.

hrmph. now i'm even more unsure of what the right thing is to do. hopefully some of the cc'ed mf2 gurus can weigh in.

I would recommend using the whole e-content content as the p-name. The length is not a big deal and will be dealt with by clients — people can already put whatever they want in whatever property they want so consumers already have to make intelligent, robust decisions to prevent abuse or weird looking content. Additionally, making the name and content the same makes it trivially easy for consumers to figure out when the name should be displayed separately (rather than trimming ellipses and searching for substrings), and therefore is most likely to result in a good experience for the person on the other side of the screen.

Microformats should always have a name property even if the thing they represent doesn’t have a “title” as such. It’s the only property which is guaranteed to exist and therefore can be used in, e.g. a list of microformats on a page. The implied name from text content rule a) ensures this will always be the case and b) allows minimal markup like <span class="h-card">Ryan</span>.

(P.S. I proposed a little while ago to add additional implied parsing rules to take the textcontent of the first descendant <h1-6> element as the p-name if none is given, which could improve the state of implied name parsing, but not for the note case)

thanks @barnabywalters! sgtm. i'll stop ellipsizing and copy the full e-content into p-name.

If it's any easier implementation-wise, I see a lot of sites just use <div class="p-name e-content"> for notes

deployed! example: https://brid-gy.appspot.com/comment/twitter/gRegorLove/512645549208514560/512646384059572224