menu-formats: Difference between revisions
Jump to navigation
Jump to search
(Adds schema.org Menu type.) |
m (Adds link to schema Restaurant type; corrects grammar mistakes and normalizes punctuation; adds code markup) |
||
| Line 6: | Line 6: | ||
=== schema.org === | === schema.org === | ||
schema.org has a [https://schema.org/Menu 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: | [https://schema.org/ schema.org] has a [https://schema.org/Menu 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: | ||
; learningResourceType | ; learningResourceType | ||
: a menu is not a learning resource, except I suppose as a way to learn what food they offer, which is sort of tautological | : a menu is not a learning resource, except I suppose as a way to learn what food they offer, which is sort of tautological | ||
; publisherImprint | ; publisherImprint | ||
: | : this is described as "The publishing division which published the comic"; why this property is part of the Menu type is beyond my comprehension | ||
; timeRequired | ; timeRequired | ||
: this | : 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: | The Menu type has other properties that are better handled with existing HTML constructs: | ||
; inLanguage | ; inLanguage | ||
: instead use lang attribute on root element or other container | : authors can instead use the <code>lang</code> attribute, either on the root element or some other suitable container | ||
; educationalAlignment | ; educationalAlignment | ||
: restaurants aren't generally aligned with a school, and they were, that would be better handled with a nested Restaurant type; for microformats, a nested [[h-card]] would be easy and intuitive | : restaurants aren't generally aligned with a school, and if they were, that would be better handled with a nested [https://schema.org/Restaurant Restaurant type]; for microformats, a nested [[h-card]] would be easy and intuitive | ||
; translationOfWork | ; translationOfWork | ||
: | : authors can instead use <code>rel</code> attributes, perhaps on <code>link</code> elements in a document <code>head</code> | ||
The complexity is part of the schema.org philosophy of adding properties 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 [https://schema.org/ schema.org] no longer publishes adoption rates, so it's hard to gauge whether their Menu schema is actually being used in the wild. | 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 [https://schema.org/ schema.org] no longer publishes adoption rates, so it's hard to gauge whether their Menu schema is actually being used in the wild. | ||
Latest revision as of 04:04, 8 December 2020
This article is a stub. You can help the microformats.org wiki by expanding it.
Per process, for documenting existing restaurant menu publishing formats.
See recipe-formats for an example of how to grow this page.
schema.org
schema.org 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:
- learningResourceType
- a menu is not a learning resource, except I suppose as a way to learn what food they offer, which is sort of tautological
- publisherImprint
- this is described as "The publishing division which published the comic"; why this property is part of the Menu type is beyond my comprehension
- timeRequired
- 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:
- inLanguage
- authors can instead use the
langattribute, either on the root element or some other suitable container - educationalAlignment
- 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
- translationOfWork
- authors can instead use
relattributes, perhaps onlinkelements in a documenthead
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.