ZegnatI don’t think publications need to go in a separate property. But interesting question. I’d say: test and document your experiences. But just having h-cites as nested children of an h-resume seem like a pretty clear relation already, at least to me.
jgmac1106, [Khurt], barpthewire and [jgmac1106] joined the channel
[tantek]if you can figure out how to make cite work well for an entire h-cite (including styling, additional semantic markup etc.), please document your results
[tantek]No it is not necessary. As Zegnat noted, no specific HTML tag is "necessary" for mf2. You should be using HTML tags for their own intrinsic semantic benefit (if any), and no more.
[tantek]The real question to ask is what does using any specific markup do for you or your site? Is there consuming code that makes use of it and if so what and how?
[schmarty]i identify with the desire to come up with the "correct" markup for something new from scratch, using what you know about HTML and microformats. it also seems pretty common.
[schmarty]i started with indiewebify.me, then on to bridgy publish, then individual people's websites that show responses (including my own), and beyond. these days i mostly care about aperture / monocle / indigenous.
[schmarty]i might take a stab at a best-guess, but it's very likely that, assuming someone does build a consuming case, where i want my content to be handled well, they'll have a different idea of what "correct" mf2 looks like, and i'll have to rewrite mine anyway.