menu-brainstorming: Difference between revisions
(Suggests using h-product for menu items. Changes wording on use of h-card.) |
(Notes missing container mf for menu items marked up with h-product) |
||
| Line 10: | Line 10: | ||
The obvious path forward is to use [[h-product]] for menu items. [[h-product]] offers pretty much everything a menu item microformat needs: p-name for the item name, (e.g. mushroom soup), u-photo, e-description, and p-price. There are some additional things in menus, notably calories, that might require a new property. If a menu has a page for individual items, u-url is available. [[h-review]] might be useful for review sites like Yelp or Google (though that might be a disincentive for restaurants, which tend to harbor strong antipathy to review sites in general and Yelp in particular. I'm not sure if p-category can be reused, but some way to tag items -- as vegetarian, gluten-free, etc. -- would be useful. [[User:Btrem|Btrem]] ([[User talk:Btrem|talk]]) 02:12, 4 December 2020 (UTC) | The obvious path forward is to use [[h-product]] for menu items. [[h-product]] offers pretty much everything a menu item microformat needs: p-name for the item name, (e.g. mushroom soup), u-photo, e-description, and p-price. There are some additional things in menus, notably calories, that might require a new property. If a menu has a page for individual items, u-url is available. [[h-review]] might be useful for review sites like Yelp or Google (though that might be a disincentive for restaurants, which tend to harbor strong antipathy to review sites in general and Yelp in particular. I'm not sure if p-category can be reused, but some way to tag items -- as vegetarian, gluten-free, etc. -- would be useful. [[User:Btrem|Btrem]] ([[User talk:Btrem|talk]]) 02:12, 4 December 2020 (UTC) | ||
What's missing is a container for the menu items. Such a menu container microformat could include meta information such as availability (e.g., a dinner menu is available 5pm -10pm). [[User:Btrem|Btrem]] ([[User talk:Btrem|talk]]) 02:14, 4 December 2020 (UTC) | |||
Revision as of 02:14, 4 December 2020
This article is a stub. You can help the microformats.org wiki by expanding it.
Per process, for documenting ideas towards a restaurant menu microformat, based on experience and research into:
And of course using existing microformats as building blocks when appropriate.
Brainstorming
There may be some similarities with h-resume, which also has an h-card for the organization (e.g. restaurant) whom the resume belongs to.
The obvious path forward is to use h-product for menu items. h-product offers pretty much everything a menu item microformat needs: p-name for the item name, (e.g. mushroom soup), u-photo, e-description, and p-price. There are some additional things in menus, notably calories, that might require a new property. If a menu has a page for individual items, u-url is available. h-review might be useful for review sites like Yelp or Google (though that might be a disincentive for restaurants, which tend to harbor strong antipathy to review sites in general and Yelp in particular. I'm not sure if p-category can be reused, but some way to tag items -- as vegetarian, gluten-free, etc. -- would be useful. Btrem (talk) 02:12, 4 December 2020 (UTC)
What's missing is a container for the menu items. Such a menu container microformat could include meta information such as availability (e.g., a dinner menu is available 5pm -10pm). Btrem (talk) 02:14, 4 December 2020 (UTC)
... feel free to add more unstructured thoughts there.