#gRegorThere might be more mf2 hReview out there than mf2 h-review
#gRegorI would expect if we merge, we would still include a note that consumers should check for h-review
#gRegorI have a draft blog post with some thoughts on that specifically for the movie reviewing session we had at IWC SD. short version is basically "check for h-review... if not found then check for h-entry with review-of"
#gRegorHope to have that published this week while it's all still fresh in my mind 🤞
#[tantek]There aren't any known implementations though maybe there are publishers. So it's worth explicitly obsoleting to discourage future consuming implementations
#[tantek]And then figure out what to do with mf1 hReviewAggregate which I believe is consumed by Google (they're the ones that asked for it in the first place)
#gRegorI think capjamesg publishes the aggregates on Breakfast and Coffee
#gRegorah, interesting history. didn't realize that came from google
#[tantek]Google wanted to make it "easier" for them to show a search result snippet with the summary of reviews about an item. So rather than crawling actual reviews they wanted sites to markup their existing visible summaries. What could go wrong?
#capjamesgTo remove h-review-aggregate, could we have a "u-review-of aggregation algorithm" which specifies how to calculate an aggregate of multiple h-entries with the u-review-of attribute?
#capjamesgIf aggregation is left up to the consumer rather than the publisher, we should be clear on how that works.
#gRegorh-review's p-best and p-worst allow customizing the rating scale, but if they're not specified the default is 1-5, 5 being best
#gRegorI expect those properties are pretty rarely published, 1-5 default usually works well
#[tantek]Idk I think the simple algorithms are naive as to the real world abuses and biases of reviews
#[tantek]For example as a consuming implementation I might want to only aggregate reviews from indieweb sites or perhaps also profiles on review sites that have green rel-me checkmarks linking to indieweb sites
[0x3b0b] joined the channel
#gRegorMakes sense, but probably not something the microformats spec would direct on?
#[tantek]correct, it's a reason why the microformats spec for h-review would NOT provide any guidance for how consuming code SHOULD (or SHOULD NOT) aggregate the reviews