From Microformats Wiki
Jump to navigation Jump to search

This article is a stub. You can help the wiki by expanding it.

Per The microformats process, for documenting existing restaurant menu publishing formats.

See recipe-formats for an example of how to grow this page. has a menu type with a high degree of complexity. There are over 100 properties associated with it, many of which have little or nothing to do with restaurant menus:

a menu is not a learning resource, except I suppose as a way to learn what food they offer, which is sort of tautological
this is described as "The publishing division which published the comic"; why this property is part of the Menu type is beyond my comprehension
this indicates the time it takes to read the work; the time it takes to read a menu is hardly relevant for a web author or user

The Menu type has other properties that are better handled with existing HTML constructs:

authors can instead use the lang attribute, either on the root element or some other suitable container
restaurants aren't generally aligned with a school, and if they were, that would be better handled with a nested Restaurant type; for microformats, a nested h-card would be easy and intuitive
authors can instead use rel attributes, perhaps on link elements in a document head

The complexity is part of the philosophy of adding properties and types for every possible variation and contingency of web publishing, at the expense of making it difficult and intimidating for web authors to adopt. It appears that no longer publishes adoption rates, so it's hard to gauge whether their Menu schema is actually being used in the wild.

See Also