Amen. This is why we're building BuenaCarta.com - example page:
http://www.buenacarta.com/restaurantes/buenos-aires/palermo-... (very early alpha)... We're starting with South America but we're planning on releasing a white label version of the product for other markets (and not just restaurants). Our focus is right now on getting reviews 'right', before we start building content, because we still believe there's not a truly good restaurant/bar/store review site whose reviews aren't ranked using hidden magic, astroturfed, or just really, really bland.
We've spent a lot of time on the "Open Hours" feature - we want people to view a page and see "Open NOW", "Open Later Today", "Closed Today", etc. so that they're sure it's really open, or it will be when they take a cab across town, or so its really clear they're closed mondays and you don't go all the way there only to find that out.
However, we also want to be able to search the data ourselves, and we want it to be localized into two or three languages. So we can't just store the open hours as a string, we need to render the open hours as text but it needs to be stored as data. Generating the English/Spanish/Portuguese from the data is a lot of fun.
We've spent a lot of time on the "Open Hours" feature - we want people to view a page and see "Open NOW", "Open Later Today", "Closed Today", etc. so that they're sure it's really open, or it will be when they take a cab across town, or so its really clear they're closed mondays and you don't go all the way there only to find that out.
However, we also want to be able to search the data ourselves, and we want it to be localized into two or three languages. So we can't just store the open hours as a string, we need to render the open hours as text but it needs to be stored as data. Generating the English/Spanish/Portuguese from the data is a lot of fun.