This article is a stub. You can help the microformats.org wiki by expanding it.
See recipe-formats for an example of how to grow this page.
- 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
langattribute, 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
relattributes, perhaps on
linkelements in a document
The complexity is part of the schema.org 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 schema.org no longer publishes adoption rates, so it's hard to gauge whether their Menu schema is actually being used in the wild.