Skip to content
Novus Examples
jsonld13.2 KB

Copper Oven Bakery: Menu as schema.org JSON-LD

Menu as schema.org JSON-LD for Copper Oven Bakery. A schema.org Menu document with 6 MenuSection nodes, 4 of them top level, and 30 MenuItem nodes carrying 30 Offer nodes, each with price as a JSON number and priceCurrency CAD. Modifiers are menuAddOn MenuItems and every declared allergen travels as an additionalProperty PropertyValue. This is the structured data shape a search engine reads, and it is rare as a downloadable fixture.

jsonld

application/ld+json

13.2 KB
Kit
restaurant-bakery
Industry
food-service
Schema Version
1
Synthetic
true
As Of
2026-09-08
Currency
CAD

Binary jsonld: no in-browser preview. Download it above to open in a compatible application.

Specifications

Kit
restaurant-bakery
Industry
food-service
Schema Version
1
Synthetic
true
As Of
2026-09-08
Currency
CAD
Menu Items
30
Offers
30
Menu Sections
6
Price Type
number
Vocabulary
schema.org
Encoding
UTF-8
Line Endings
LF

Testing contract

Expected to pass
Scenario
Use menu as schema.org json-ld in the Copper Oven Bakery menu, allergen and till import workflow.
Expected result
A schema.org Menu document with 6 MenuSection nodes, 4 of them top level, and 30 MenuItem nodes carrying 30 Offer nodes, each with price as a JSON number and priceCurrency CAD. Modifiers are menuAddOn MenuItems and every declared allergen travels as an additionalProperty PropertyValue. This is the structured data shape a search engine reads, and it is rare as a downloadable fixture.

What is a .jsonld file?

JSON-LD (JSON for Linking Data) is a W3C-standard way of writing linked data as ordinary JSON. A document carries an @context that maps its plain keys onto a shared vocabulary, and an @type that says what the thing is, so a consumer can read a Menu, a Product or an Event without agreeing on field names in advance. The media type is application/ld+json, and on the web it is usually embedded in a page inside a script tag rather than served as a file.

How to use this file

Use an example JSON-LD file to test structured-data extraction and validation, context expansion and compaction, and the consumers that read schema.org markup. A file with the right shape but the wrong value types, such as a price written as a string where a number is required, is the case worth testing: it parses as JSON and still fails the vocabulary.

How to use this file for testing

“Copper Oven Bakery: Menu as schema.org JSON-LD” is a deterministic Novus Examples fixture for Data import, JSON parsing, Schema validation. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: UTF-8 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Generated by generation/restaurant_menus.py. Free for any use, no attribution required, license.