[tantek]no matter how we move forward with h-review, we'll try to maintain some degree of backward compatibility so that folks that have published h-review pages/posts can still have them processed by consuming code
btremOther type is not yet published. It's on my localhost dev server. I am using h-recipe to track home ferments (e.g., sauerkraut), and then using h-review to rate the results of the ferment.
btremI have created a new url scheme, but I really don't want to redirect my old urls. So I'm inclined to get a new domain for the recipes/reviews thing. But I haven't yet decided on a domain name. Maybe .me, maybe .dev....
btremThere are other problems with the recipe/reviews. Like the fact that I'm using h-recipe in an unusual way, to track individual executions of the same recipe. For example, each time I make a new batch of pickled beets, I create a new h-recipe, even though most of the info is the same (typically .e-instructions are entirely the same, and .p-ingredients are like 95% the same).
btremI was using "require" in the colloquial sense, not the ietf/w3c/what have you legal sense. So not trying to stir the pot. Just wondering what changes I might need to make.
btrem (I'm referring to the note on top of https://microformats.org/wiki/h-review mentioned in yesterday's chat.)