JsonSchema.Net.Data

6.1.0

Updated to use JsonSchema.Net v7.0.0, which contains breaking changes (release notes).

6.0.0.x

#711 - Nuget package meta-data updates; no functional changes from previous version.

6.0.0

Updated for multi-framework support with .Net Standard 2.0 and .Net 8 with Native AOT support, including updating System.Text.Json from v6 to v8.

Breaking changes

Dropping support for .Net Standard 3.1 - May still be used, but exact behavior cannot be guaranteed.

Additions

OptionalDataKeyword (should have been in v5… oversight)
JsonSchemaBuilderExtensions.OptionalData()
JsonSchemaExtensions.OptionalData()

5.0.1

Corrected meta-schema URIs.

Was:

Vocab meta-schema: https://json-everything.net/schema/meta/vocab/data-2023
2020-12 meta-schema: https://json-everything.net/schema/meta/data-2023

Is:

Vocab meta-schema: https://json-everything.net/meta/vocab/data-2023
2020-12 meta-schema: https://json-everything.net/meta/data-2023

5.0.0

Updated to support new Data 2023 vocabulary.

Breaking changes

Library has been updated to .Net Standard 2.1 in order to reference JsonPath.Net.
Metaschema has been split into one for the vocabulary itself (.Data) and one for the 2020-12 extension (.Data_202012).
All URIs updated from *-2022 to *-2023.

Migration

References to MetaSchemas.Data will need to be changed to MetaSchemas.Data_202012.

Additions

data now supports JSON Path references. See vocabulary spec for an example.

4.1.0

#549 - Expose JSON converters for all types to support JSON source generation.

4.0.1

Fixes an internal reflection issue caused by updating JsonSchema.Net to v5.2.3.

4.0.0

Updated in accordance with JsonSchema.Net v5.

3.1.0 (#326 / #389 / #392)

Updated to use JsonSchema.Net v4.

Fixed deserialization bug.

DataKeyword.ExternalDataRegistry is actually used. Previously, checking this registry was skipped (an oversight) before moving on to fetching the data. Also fixed the type of the property to store JsonNode instead of JsonValue to support the full range of JSON.

Added JsonSchemaExtensions.GetData() to enable easy access to data keyword.

3.0.1

Fixed bug where URI-encoded JSON Pointers where being handled as instance locations instead of schema locations. (Thanks new test suite!)

3.0.0

Supports the 2022 version of the vocabulary. This is a breaking change from the previous version.

Breaking changes

References no longer just support URIs. Instead several formats are used to indicate the source document:

JSON Pointers (not URI fragments) and Relative JSON Pointers indicate locations within the instance
Fragment-only URI-encoded JSON Pointers indicate locations within the host schema (just like a $ref would)
Absolute URIs (optionally with URI-encoded JSON Pointer fragments) are used to access external data

The first point is the primary change.

Migration

URI-encoded JSON Pointer fragments used to resolve to the instance first. These will need to be changed to plain JSON Pointers.

From
#/foo/1/bar

To
/foo/1/bar

Absolute URIs that indicate the host schema may be changed to URI-encoded JSON Pointer fragments. This is not strictly necessary as the resolution of the full URI will still occur.

From
https://example.com/schema#/$defs/somedef

To
#/$defs/somedef

2.0.1 (no PR)

#288 - Just bumping version to pick up the latest Json.More.Net by default. This package pull Json.More.Net transitively via JsonPointer.Net which wasn’t updated with the move to JsonNode.