Juniper Corner Cafe: Menu JSON-LD with string prices
Menu JSON-LD with string prices for Juniper Corner Cafe. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$4.75", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.
jsonld
application/ld+json
- Kit
- restaurant-cafe
- 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-cafe
- Industry
- food-service
- Schema Version
- 1
- Synthetic
- true
- As Of
- 2026-09-08
- Currency
- CAD
- Menu Items
- 4
- Offers
- 27
- Intentionally Invalid
- true
- Defect
- offer-price-is-a-string-not-a-number
- Price Type
- string
- Encoding
- UTF-8
- Line Endings
- LF
Testing contract
Expected to fail- Scenario
- Use menu json-ld with string prices in the Juniper Corner Cafe menu, allergen and till import workflow.
- Expected result
- Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$4.75", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.
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
“Juniper Corner Cafe: Menu JSON-LD with string prices” is a deterministic Novus Examples fixture for Data import, Error handling, JSON parsing. 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.
Related files
- jsonldAlder Table Bistro: Menu JSON-LD with string pricesMenu JSON-LD with string prices for Alder Table Bistro. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$11.50", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.
- jsonldCedar Street Tacos: Menu JSON-LD with string pricesMenu JSON-LD with string prices for Cedar Street Tacos. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$13.50", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.
- jsonldCopper Oven Bakery: Menu JSON-LD with string pricesMenu JSON-LD with string prices for Copper Oven Bakery. Intentionally invalid. All 30 Offer nodes carry price as a JSON string with a currency symbol, the first being "$7.50", where menu.jsonld carries the same 30 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.
- jsonldEmber Lane Pizza: Menu JSON-LD with string pricesMenu JSON-LD with string prices for Ember Lane Pizza. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$17.00", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.
- jsonldHarbour Kitchen Group: Menu JSON-LD with string pricesMenu JSON-LD with string prices for Harbour Kitchen Group. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$18.50", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.
- jsonldWillow Event Kitchen: Menu JSON-LD with string pricesMenu JSON-LD with string prices for Willow Event Kitchen. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$21.00", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.
Generated by generation/restaurant_menus.py. Free for any use, no attribution required, license.