Novus Examples, Real, documented example files for testing

JSON Schema Edge: Array Unique Items

Minimal JSON Schema SAMPLE focusing on array unique items constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge: Dependent Required

Minimal JSON Schema SAMPLE focusing on dependent required constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge: Enum Currency

Minimal JSON Schema SAMPLE focusing on enum currency constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge: Format Uri Email

Minimal JSON Schema SAMPLE focusing on format uri email constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge: Nullable Optional

Minimal JSON Schema SAMPLE focusing on nullable optional constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge: One Of Status

Minimal JSON Schema SAMPLE focusing on one of status constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge: Pattern Sku

Minimal JSON Schema SAMPLE focusing on pattern sku constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema oneOf Union

JSON Schema with a oneOf union over string vs number tagged objects, for testing union validation.

File: JSON · Schema
Use case: Schema / OpenAPI testing

Json Schema Reference That Validates The Hdf5 Decoded-Result Contract

JSON Schema reference that validates the HDF5 decoded-result contract, kept beside the binary source for semantic rather than byte-level comparison. Stable P8 artifact p8-convert-hdf5-schema.

File: JSON · P8 Convert
Use case: Conversion testingScientific data+1· Conversion set

JSON Schema Schema Evolution - Backward-Compatible

The compatible member of a JSON Schema 2020-12 customer contract. Backward compatible: existing instances remain valid because email is optional.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

JSON Schema Schema Evolution - Baseline

The baseline member of a JSON Schema 2020-12 customer contract. Reference contract: id and name are required strings.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

JSON Schema Schema Evolution - Breaking

The breaking member of a JSON Schema 2020-12 customer contract. Breaking relative to baseline: id changes from string to integer and tenantId becomes required.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

JSON Schema: Empty Schema Accepts Any Instance

The empty schema is valid and accepts every instance. The old invalid label was incorrect; no type or required-property constraint exists.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling

JSON Schema: Optional Properties without a Type Constraint

Omitting type is legal JSON Schema. The x property has an empty subschema, x is optional, and non-object instances are not rejected by properties.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling

Preview of JSON with Duplicate Keys — Actual file preview for JSON with Duplicate Keys

A JSON object that repeats several member names (name, tags, timeout, active). RFC 8259 permits duplicate keys but leaves the result parser-defined: most keep the last. A fixture for testing how a JSON parser resolves duplicates.

File: JSON · Edge Cases
Use case: JSON parsingError handling

JSON-LD @graph with @id cross-references

A single @graph holding four nodes wired together by @id rather than by nesting - the shape most CMS plugins emit - including a SearchAction, a breadcrumb whose last item has no URL, and one reference to a product node that lives on another page. For testing graph flattening and reference resolution.

File: JSON · Social · UTF-8
Use case: Web assetsJSON parsing+2· Conversion set

JSON-LD Event with offers and a location

A valid Event record for a hybrid event: both a physical Place with a postal address and geo coordinates and a VirtualLocation, plus a free Offer and a capacity. For testing array-valued properties and event date/timezone handling.

File: JSON · Social · UTF-8
Use case: Web assetsJSON parsing+2· Conversion set

JSON-LD LocalBusiness with opening hours

A valid LocalBusiness (as a SportingGoodsStore subtype) with a postal address, geo coordinates, weekday and Saturday opening hours, and a 00:00-00:00 specification marking a holiday closure. For testing opening-hours parsing and the closed-all-day convention.

File: JSON · Social · UTF-8
Use case: Web assetsJSON parsing+2· Conversion set

JSON-LD missing required properties (deliberately invalid)

A deliberately invalid Product record: no name, an Offer with a currency but no price, a brand with no @type, a Review with no rating, an AggregateRating with no ratingValue, and an availability given as a bare token instead of a schema.org URL. Valid JSON throughout, so the failure is semantic.

File: JSON · Social · UTF-8
Use case: Web assetsJSON parsing+2· Conversion set

JSON-LD NewsArticle with author and publisher

A valid NewsArticle with two authors, a publisher whose logo carries explicit pixel dimensions, three images at the aspect ratios news results expect, and both publication and modification timestamps. For testing article extraction and date normalisation.

File: JSON · Social · UTF-8
Use case: Web assetsJSON parsing+2· Conversion set

JSON-LD Product with Offer and AggregateRating

A valid Product record with a nested Offer carrying price, currency, availability, condition and shipping details, plus an AggregateRating. For testing rich-result validators and structured-data extractors against a document that should pass cleanly.

File: JSON · Social · UTF-8
Use case: Web assetsJSON parsing+2· Conversion set

JSON-LD Recipe with steps and nutrition

A valid Recipe with ISO 8601 durations, four ingredients, and instructions that mix flat HowToStep nodes with a nested HowToSection. For testing duration parsing and recursive instruction extraction.

File: JSON · Social · UTF-8
Use case: Web assetsJSON parsing+2· Conversion set

JSON-LD with wrong value types and a relative context (deliberately invalid)

A deliberately invalid Recipe carrying six unambiguously wrong-typed values - a numeric datePublished, a prose prepTime where an ISO 8601 duration belongs, an object recipeYield, two non-numeric ratings and a misspelled @type - plus a relative @context that never resolves, an untyped image object and two ingredients crammed into one string. For testing the limits of type coercion.

File: JSON · Social · UTF-8
Use case: Web assetsJSON parsing+2· Conversion set

JSON-LD: Breadcrumb SAMPLE

schema.org JSON-LD SAMPLE (breadcrumb) for SEO/structured-data validators.

File: JSON · Social
Use case: Web assetsJSON parsing+1· Conversion set

Explore the test library

Filter the library

5297 results