Json Schema Specification (Version 4) support #115

Closed
gsferreira opened this Issue Aug 8, 2013 · 39 comments

Comments

Projects
None yet
@gsferreira

Hi,

When do you expect to support the Json Schema Specification (Version 4)?

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Aug 9, 2013

Owner

No plans right now. Months at least.

Owner

JamesNK commented Aug 9, 2013

No plans right now. Months at least.

@kzu

This comment has been minimized.

Show comment
Hide comment

kzu commented Sep 3, 2013

+1 ;)

@augi

This comment has been minimized.

Show comment
Hide comment

augi commented Jan 7, 2014

+1 ;)

@leftclickben

This comment has been minimized.

Show comment
Hide comment

+1

@westcode

This comment has been minimized.

Show comment
Hide comment
@westcode

westcode Feb 10, 2014

Any news on this? :)

Any news on this? :)

@khorvat

This comment has been minimized.

Show comment
Hide comment

khorvat commented Mar 18, 2014

+1

@theteng

This comment has been minimized.

Show comment
Hide comment

theteng commented Mar 20, 2014

+1

@thj-dk

This comment has been minimized.

Show comment
Hide comment
@thj-dk

thj-dk Mar 20, 2014

Would love to see this supported as well.

thj-dk commented Mar 20, 2014

Would love to see this supported as well.

@shneydor

This comment has been minimized.

Show comment
Hide comment
@shneydor

shneydor Apr 9, 2014

+1, definitely.

shneydor commented Apr 9, 2014

+1, definitely.

@warappa

This comment has been minimized.

Show comment
Hide comment

warappa commented May 6, 2014

+1

@paulveitch

This comment has been minimized.

Show comment
Hide comment
@paulveitch

paulveitch May 29, 2014

I'm working on adding JSON HyperSchema (draft 4) support, anyone already working on this or object?

I'm working on adding JSON HyperSchema (draft 4) support, anyone already working on this or object?

@JamesNK JamesNK added the jsonschema label Jun 18, 2014

@bbowyersmyth

This comment has been minimized.

Show comment
Hide comment
@bbowyersmyth

bbowyersmyth Jul 11, 2014

I personally needed this functionality. Added a pull request here #328

I personally needed this functionality. Added a pull request here #328

@TheNewQAGuy

This comment has been minimized.

Show comment
Hide comment

bump.

@IanYates

This comment has been minimized.

Show comment
Hide comment
@IanYates

IanYates Dec 7, 2014

👍
Tricky issue to resolve. Breaking the v4 stuff out as a separate package, and either doing the same for v3 (or just leave it in place) seems to be not too bad an approach. Microsoft did something similar with its new OData libraries - v4 uses different assemblies, namespaces, packages, etc from the v3 stuff so that the two can coexist.

IanYates commented Dec 7, 2014

👍
Tricky issue to resolve. Breaking the v4 stuff out as a separate package, and either doing the same for v3 (or just leave it in place) seems to be not too bad an approach. Microsoft did something similar with its new OData libraries - v4 uses different assemblies, namespaces, packages, etc from the v3 stuff so that the two can coexist.

@gimalay

This comment has been minimized.

Show comment
Hide comment

gimalay commented Dec 8, 2014

+1

@blachniet

This comment has been minimized.

Show comment
Hide comment

👍

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Dec 20, 2014

Owner

Good news! (with a caveat): I'm working on JSON Schema Draft 4 support and it will be a separate package. The caveat is I'm going to make it AGPL with a commercial license option, and an OSS exemption.

Background

The new version will be a complete rewrite. There were a lot of issues with the old JSON Schema implementation. It was written way back in Draft 1/2, and its internals are a mess which is why I've been so hesitant to invest time in it. In the end I've thrown everything away but some of the unit tests and started from scratch.

Starting from scratch is a lot more work but it means I can make it do a lot of things it couldn't previously.

Licensing

As well as AGPL and commercial options, there is an open source exemption to support OSS projects that want to use it but don't want GPL3/AGPL. Basically the licensing will be similar to what RavenDB does. It will be free for open source projects, but will cost a small amount for commercial projects, which seems fair to me. I'm thinking the perpetual license for a developer will be $100.

Features
  • Complete JSON schema Draft 4 support. It will pass every test in the official JSON Schema unit test suite.
  • Complete JSON schema Draft 3 support. It will be backwards compatible and pass every Draft 3 test. The old implementation that comes with Json.NET is missing a number of key Draft 3 features and was only about 75% of the spec.
  • vNext Draft support. I've taken a look at what has been proposed for Draft 5 and this new version should be able to support it while maintaining backwards compatibility.
  • Greatly improved performance. I have not yet begun to optimize but it is already 3 times faster than the old implementation. The old code took 2 seconds to validate an object 5000 times, the new code takes 0.6 seconds. I think I should be able to make some more gains.
  • JObject.IsValid/JArray.IsValid extension methods. No changes here. Porting should only be a couple of minor changes.
  • JSchemaValidatingReader. No changes here either. It will be a simple upgrade.
  • JSchemaValidatingWriter. This is brand new. You will be able to validate JSON as you write it.
  • Excellent API for loading, creating and editing schemas with references. The schema writer will automatically resolve duplicate schema's and insert $ref's for you. The old implementation's problems with circular references won't be an issue anymore
  • Resolve and cache remote schema references
  • JSchemaGenerator will detect data annotation attributes and automatically use them when generating schemas from classes, e.g. a property with RequiredAttribute will be marked as required. Likewise EnumDataTypeAttribute -> enum, MaxLengthAttribute -> maxLength/maxItems/maxProperties, RegularExpressionAttribute -> pattern, etc.
  • An API to customize the JSchemaGenerator. It will probably be something similar to JsonConverter to allow you to override the schema generated for a type.
  • Over a thousand unit tests
  • Much more documentation
  • Future 2.0 feature ideas like attributes you could place on WebAPI methods that will automatically validate JSON going in and out.

Basically the new schema library will be smaller, faster and stronger than what came before it in every way. I'm quite pleased with how it as turned out so far :)

Timelines

The current JSON Schema implementation that is part of Json.NET will stay where it is. Removing it would be a big breaking change, but sometime in the future I'll mark it as obsolete. It won't receive any updates but that isn't anything new, it hasn't been changed in 2 years already.

I don't have an exact release date for this new version. I've been working on it for a month and I think it will probably be another couple of weeks before I ship a beta version. The work in progress code will be on github sometime in the next week. I'll comment here with updates.

Json.NET

I'm still working on Json.NET, it is still MIT OSS and that will never change. In fact I have added half a dozen medium and minor features to Json.NET while working on this new JSON Schema implementation so expect many new features in the next Json.NET

Questions

If you have questions, or feature requests, then feel free to ask.

James

Owner

JamesNK commented Dec 20, 2014

Good news! (with a caveat): I'm working on JSON Schema Draft 4 support and it will be a separate package. The caveat is I'm going to make it AGPL with a commercial license option, and an OSS exemption.

Background

The new version will be a complete rewrite. There were a lot of issues with the old JSON Schema implementation. It was written way back in Draft 1/2, and its internals are a mess which is why I've been so hesitant to invest time in it. In the end I've thrown everything away but some of the unit tests and started from scratch.

Starting from scratch is a lot more work but it means I can make it do a lot of things it couldn't previously.

Licensing

As well as AGPL and commercial options, there is an open source exemption to support OSS projects that want to use it but don't want GPL3/AGPL. Basically the licensing will be similar to what RavenDB does. It will be free for open source projects, but will cost a small amount for commercial projects, which seems fair to me. I'm thinking the perpetual license for a developer will be $100.

Features
  • Complete JSON schema Draft 4 support. It will pass every test in the official JSON Schema unit test suite.
  • Complete JSON schema Draft 3 support. It will be backwards compatible and pass every Draft 3 test. The old implementation that comes with Json.NET is missing a number of key Draft 3 features and was only about 75% of the spec.
  • vNext Draft support. I've taken a look at what has been proposed for Draft 5 and this new version should be able to support it while maintaining backwards compatibility.
  • Greatly improved performance. I have not yet begun to optimize but it is already 3 times faster than the old implementation. The old code took 2 seconds to validate an object 5000 times, the new code takes 0.6 seconds. I think I should be able to make some more gains.
  • JObject.IsValid/JArray.IsValid extension methods. No changes here. Porting should only be a couple of minor changes.
  • JSchemaValidatingReader. No changes here either. It will be a simple upgrade.
  • JSchemaValidatingWriter. This is brand new. You will be able to validate JSON as you write it.
  • Excellent API for loading, creating and editing schemas with references. The schema writer will automatically resolve duplicate schema's and insert $ref's for you. The old implementation's problems with circular references won't be an issue anymore
  • Resolve and cache remote schema references
  • JSchemaGenerator will detect data annotation attributes and automatically use them when generating schemas from classes, e.g. a property with RequiredAttribute will be marked as required. Likewise EnumDataTypeAttribute -> enum, MaxLengthAttribute -> maxLength/maxItems/maxProperties, RegularExpressionAttribute -> pattern, etc.
  • An API to customize the JSchemaGenerator. It will probably be something similar to JsonConverter to allow you to override the schema generated for a type.
  • Over a thousand unit tests
  • Much more documentation
  • Future 2.0 feature ideas like attributes you could place on WebAPI methods that will automatically validate JSON going in and out.

Basically the new schema library will be smaller, faster and stronger than what came before it in every way. I'm quite pleased with how it as turned out so far :)

Timelines

The current JSON Schema implementation that is part of Json.NET will stay where it is. Removing it would be a big breaking change, but sometime in the future I'll mark it as obsolete. It won't receive any updates but that isn't anything new, it hasn't been changed in 2 years already.

I don't have an exact release date for this new version. I've been working on it for a month and I think it will probably be another couple of weeks before I ship a beta version. The work in progress code will be on github sometime in the next week. I'll comment here with updates.

Json.NET

I'm still working on Json.NET, it is still MIT OSS and that will never change. In fact I have added half a dozen medium and minor features to Json.NET while working on this new JSON Schema implementation so expect many new features in the next Json.NET

Questions

If you have questions, or feature requests, then feel free to ask.

James

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Dec 27, 2014

Owner

Source code is on GitHub: Newtonsoft.Json.Schema

Owner

JamesNK commented Dec 27, 2014

Source code is on GitHub: Newtonsoft.Json.Schema

@br15

This comment has been minimized.

Show comment
Hide comment
@br15

br15 Jan 7, 2015

Hi,

I've downloaded the code and built solution just fine. However I need to integrate your code with a .Net 4.0 solution which I can't (for political reasons) upgrade to .Net 4.5 which is the version you've used with your solution.

Any chance you could create a .Net 4.0 version with an associated NuGet package for Newtonsoft.Json 7.0.1-beta1.

Cheers

br15 commented Jan 7, 2015

Hi,

I've downloaded the code and built solution just fine. However I need to integrate your code with a .Net 4.0 solution which I can't (for political reasons) upgrade to .Net 4.5 which is the version you've used with your solution.

Any chance you could create a .Net 4.0 version with an associated NuGet package for Newtonsoft.Json 7.0.1-beta1.

Cheers

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Jan 8, 2015

Owner

I'll look at adding .NET 4. Probably shouldn't be an issue.

FYI there is a limit on the number of schema validations per hour without a license. I should have a website ready for buying a license in a couple of weeks but I wouldn't recommend using it in a live environment until then.

Owner

JamesNK commented Jan 8, 2015

I'll look at adding .NET 4. Probably shouldn't be an issue.

FYI there is a limit on the number of schema validations per hour without a license. I should have a website ready for buying a license in a couple of weeks but I wouldn't recommend using it in a live environment until then.

@br15

This comment has been minimized.

Show comment
Hide comment
@br15

br15 Jan 9, 2015

Hi James,

Thanks for the quick response. I'll definitely be buying a license.
What's the current limit set to for validation per hour?
Could you please notify me as soon as the .Net 4.0 support is available.

Cheers
Keith.

Great work by the way.

On 8 January 2015 at 21:43, James Newton-King notifications@github.com
wrote:

I'll look at adding .NET 4. Probably shouldn't be an issue.

FYI there is a limit on the number of schema validations per hour without
a license. I should have a website ready for buying a license in a couple
of weeks but I wouldn't recommend using it in a live environment until then.


Reply to this email directly or view it on GitHub
#115 (comment)
.

br15 commented Jan 9, 2015

Hi James,

Thanks for the quick response. I'll definitely be buying a license.
What's the current limit set to for validation per hour?
Could you please notify me as soon as the .Net 4.0 support is available.

Cheers
Keith.

Great work by the way.

On 8 January 2015 at 21:43, James Newton-King notifications@github.com
wrote:

I'll look at adding .NET 4. Probably shouldn't be an issue.

FYI there is a limit on the number of schema validations per hour without
a license. I should have a website ready for buying a license in a couple
of weeks but I wouldn't recommend using it in a live environment until then.


Reply to this email directly or view it on GitHub
#115 (comment)
.

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Jan 10, 2015

Owner

1000 an hour, resetting each time you debug an application or rebuild a website. Lots for development purposes.

I've added .NET 4.0 support and uploaded a beta release to myget here: https://www.myget.org/F/json-net/api/v2

Json.NET Schema uses a new feature in json.net that hasn't been offically released yet, so your reference to Json.NET will be updated on install.

Owner

JamesNK commented Jan 10, 2015

1000 an hour, resetting each time you debug an application or rebuild a website. Lots for development purposes.

I've added .NET 4.0 support and uploaded a beta release to myget here: https://www.myget.org/F/json-net/api/v2

Json.NET Schema uses a new feature in json.net that hasn't been offically released yet, so your reference to Json.NET will be updated on install.

@br15

This comment has been minimized.

Show comment
Hide comment
@br15

br15 Jan 10, 2015

That was quick. Marvellous!

Cheers

Keith

From: James Newton-King [mailto:notifications@github.com]
Sent: 10 January 2015 03:49
To: JamesNK/Newtonsoft.Json
Cc: br15
Subject: Re: [Newtonsoft.Json] Json Schema Specification (Version 4) support (#115)

1000 an hour, resetting each time you run an application or rebuild a website. Lots for development purposes.

I've added .NET 4.0 support and uploaded a beta release to myget here: https://www.myget.org/F/json-net/api/v2

It uses a new feature I've added to json.net that hasn't been released yet so that will be updated to a beta version as well.


Reply to this email directly or view it on GitHub #115 (comment) . https://github.com/notifications/beacon/AHQF4B55yXwqGcIKifZ4HOBXmwbjToGaks5ngJiRgaJpZM4A4peM.gif

br15 commented Jan 10, 2015

That was quick. Marvellous!

Cheers

Keith

From: James Newton-King [mailto:notifications@github.com]
Sent: 10 January 2015 03:49
To: JamesNK/Newtonsoft.Json
Cc: br15
Subject: Re: [Newtonsoft.Json] Json Schema Specification (Version 4) support (#115)

1000 an hour, resetting each time you run an application or rebuild a website. Lots for development purposes.

I've added .NET 4.0 support and uploaded a beta release to myget here: https://www.myget.org/F/json-net/api/v2

It uses a new feature I've added to json.net that hasn't been released yet so that will be updated to a beta version as well.


Reply to this email directly or view it on GitHub #115 (comment) . https://github.com/notifications/beacon/AHQF4B55yXwqGcIKifZ4HOBXmwbjToGaks5ngJiRgaJpZM4A4peM.gif

@br15

This comment has been minimized.

Show comment
Hide comment
@br15

br15 Jan 12, 2015

Hi James,

The link to the .Net 4 code doesn't seem to work. I just get this in the browser:

This XML file does not appear to have any style information associated with it. The document tree is shown below.


atom:titleDefault/atom:title

atom:titlePackages/atom:title


atom:titleScreenshots/atom:title


br15 commented Jan 12, 2015

Hi James,

The link to the .Net 4 code doesn't seem to work. I just get this in the browser:

This XML file does not appear to have any style information associated with it. The document tree is shown below.


atom:titleDefault/atom:title

atom:titlePackages/atom:title


atom:titleScreenshots/atom:title


@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Jan 12, 2015

Owner

It's a NuGet feed URL. You don't download packages from it using a browser, you add it as a package source to the NuGet Package Manager in Visual Studio. Once you've done that then add packages to your project like you normally would.

http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog#Package_Sources

The name is up to you, source is https://www.myget.org/F/json-net/api/v2

Owner

JamesNK commented Jan 12, 2015

It's a NuGet feed URL. You don't download packages from it using a browser, you add it as a package source to the NuGet Package Manager in Visual Studio. Once you've done that then add packages to your project like you normally would.

http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog#Package_Sources

The name is up to you, source is https://www.myget.org/F/json-net/api/v2

@br15

This comment has been minimized.

Show comment
Hide comment
@br15

br15 Jan 12, 2015

Hi James,

When I try to install the package I get an error:

Install failed. Rolling back...
Failed to initialize the PowerShell host. If your PowerShell execution
policy setting is set to AllSigned, open the Package Manager Console to
initialize the host first.

I found a couple of articles on stackoverflow that suggested setting an
execution policy to RemoteSigned or Unrestricted . When I go to the NuGet
Console (Tools | NuGet Package Manager | Package Manager Console) to try to
change the execution policy to unrestricted I get:

PM> Set-ExecutionPolicy Unrestricted
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust.
Changing the execution policy might expose you to the security risks
described in the about_Execution_Policies help topic. Do you want to change
the execution policy?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"):Y
Set-ExecutionPolicy : Windows PowerShell updated your execution policy
successfully, but the setting is overridden by a policy defined at a
more specific scope. Due to the override, your shell will retain its
current effective execution policy of "RemoteSigned". Type "Get-Exec
utionPolicy -List" to view your execution policy settings. For more
information, please see "Get-Help Set-ExecutionPolicy."
At line:1 char:20

  • Set-ExecutionPolicy <<<< Unrestricted
    • CategoryInfo : PermissionDenied: (:) [Set-ExecutionPolicy],
      SecurityException
    • FullyQualifiedErrorId :
      ExecutionPolicyOverride,Microsoft.PowerShell.Commands.SetExecutionPolicyCommand
      PM>

Any suggestions?

Cheers
Keith

On 12 January 2015 at 10:24, James Newton-King notifications@github.com
wrote:

It's a NuGet feed URL. You don't download from it using a browser, you
need to add it as a package source to the NuGet Package Manager in Visual
Studio.

http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog#Package_Sources

Name is up to you, source is https://www.myget.org/F/json-net/api/v2


Reply to this email directly or view it on GitHub
#115 (comment)
.

br15 commented Jan 12, 2015

Hi James,

When I try to install the package I get an error:

Install failed. Rolling back...
Failed to initialize the PowerShell host. If your PowerShell execution
policy setting is set to AllSigned, open the Package Manager Console to
initialize the host first.

I found a couple of articles on stackoverflow that suggested setting an
execution policy to RemoteSigned or Unrestricted . When I go to the NuGet
Console (Tools | NuGet Package Manager | Package Manager Console) to try to
change the execution policy to unrestricted I get:

PM> Set-ExecutionPolicy Unrestricted
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust.
Changing the execution policy might expose you to the security risks
described in the about_Execution_Policies help topic. Do you want to change
the execution policy?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"):Y
Set-ExecutionPolicy : Windows PowerShell updated your execution policy
successfully, but the setting is overridden by a policy defined at a
more specific scope. Due to the override, your shell will retain its
current effective execution policy of "RemoteSigned". Type "Get-Exec
utionPolicy -List" to view your execution policy settings. For more
information, please see "Get-Help Set-ExecutionPolicy."
At line:1 char:20

  • Set-ExecutionPolicy <<<< Unrestricted
    • CategoryInfo : PermissionDenied: (:) [Set-ExecutionPolicy],
      SecurityException
    • FullyQualifiedErrorId :
      ExecutionPolicyOverride,Microsoft.PowerShell.Commands.SetExecutionPolicyCommand
      PM>

Any suggestions?

Cheers
Keith

On 12 January 2015 at 10:24, James Newton-King notifications@github.com
wrote:

It's a NuGet feed URL. You don't download from it using a browser, you
need to add it as a package source to the NuGet Package Manager in Visual
Studio.

http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog#Package_Sources

Name is up to you, source is https://www.myget.org/F/json-net/api/v2


Reply to this email directly or view it on GitHub
#115 (comment)
.

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Jan 12, 2015

Owner

I found this: http://stackoverflow.com/questions/23353951/cant-install-nuget-package-because-of-failed-to-initialize-the-powershell-host

You need to be running a PowerShell console window in admin mode.

If the PowerShell console window is 64bit you should call:

start-job { Set-ExecutionPolicy Unrestricted } -RunAs32 | wait-job | Receive-Job

And it sounds like you need to restart VS afterwards.

Owner

JamesNK commented Jan 12, 2015

I found this: http://stackoverflow.com/questions/23353951/cant-install-nuget-package-because-of-failed-to-initialize-the-powershell-host

You need to be running a PowerShell console window in admin mode.

If the PowerShell console window is 64bit you should call:

start-job { Set-ExecutionPolicy Unrestricted } -RunAs32 | wait-job | Receive-Job

And it sounds like you need to restart VS afterwards.

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Jan 13, 2015

Owner

If you are still having problems with NuGet then the dlls can now be downloaded in a zip file as well: https://github.com/JamesNK/Newtonsoft.Json.Schema/releases

Requires Json.NET 6.0.8

Owner

JamesNK commented Jan 13, 2015

If you are still having problems with NuGet then the dlls can now be downloaded in a zip file as well: https://github.com/JamesNK/Newtonsoft.Json.Schema/releases

Requires Json.NET 6.0.8

@br15

This comment has been minimized.

Show comment
Hide comment
@br15

br15 Jan 13, 2015

Thanks

On 13 January 2015 at 11:21, James Newton-King notifications@github.com
wrote:

If you are still having problems with NuGet then the dlls can now be
downloaded in a zip file as well:
https://github.com/JamesNK/Newtonsoft.Json.Schema/releases


Reply to this email directly or view it on GitHub
#115 (comment)
.

br15 commented Jan 13, 2015

Thanks

On 13 January 2015 at 11:21, James Newton-King notifications@github.com
wrote:

If you are still having problems with NuGet then the dlls can now be
downloaded in a zip file as well:
https://github.com/JamesNK/Newtonsoft.Json.Schema/releases


Reply to this email directly or view it on GitHub
#115 (comment)
.

@digitalgym

This comment has been minimized.

Show comment
Hide comment
@digitalgym

digitalgym Jan 14, 2015

I am also in urgent need of 0.4 schema support, does the 1.0.1-beta3 release contain support for this?

I am also in urgent need of 0.4 schema support, does the 1.0.1-beta3 release contain support for this?

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Jan 14, 2015

Owner

Yes

Owner

JamesNK commented Jan 14, 2015

Yes

@digitalgym

This comment has been minimized.

Show comment
Hide comment
@digitalgym

digitalgym Jan 14, 2015

Ok thanks, I have the .dll referenced how do I get JsonSchemaGenerator to output the v4 schema?
var jsonSchemaGenerator = new JsonSchemaGenerator(); var myType = typeof(Foo); var schema = jsonSchemaGenerator.Generate(myType);

Ok thanks, I have the .dll referenced how do I get JsonSchemaGenerator to output the v4 schema?
var jsonSchemaGenerator = new JsonSchemaGenerator(); var myType = typeof(Foo); var schema = jsonSchemaGenerator.Generate(myType);

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Jan 14, 2015

Owner

JSchemaGenerator

The API is pretty much exactly the same as v3, except JsonSchema has been replaced with JSchema.

Owner

JamesNK commented Jan 14, 2015

JSchemaGenerator

The API is pretty much exactly the same as v3, except JsonSchema has been replaced with JSchema.

@fractos

This comment has been minimized.

Show comment
Hide comment
@fractos

fractos Jan 14, 2015

Awesome. Just in time for me needing it :)

fractos commented Jan 14, 2015

Awesome. Just in time for me needing it :)

@JamesNK

This comment has been minimized.

Show comment
Hide comment
Owner

JamesNK commented Jan 20, 2015

Json.NET Schema is now on nuget.org

https://www.nuget.org/packages/Newtonsoft.Json.Schema

@br15

This comment has been minimized.

Show comment
Hide comment

@JamesNK JamesNK referenced this issue in JamesNK/Newtonsoft.Json.Schema Jan 22, 2015

Closed

V4 validation issue #3

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@JamesNK

JamesNK Jan 22, 2015

Owner

I've created an issue in the schema project: JamesNK/Newtonsoft.Json.Schema#3

Owner

JamesNK commented Jan 22, 2015

I've created an issue in the schema project: JamesNK/Newtonsoft.Json.Schema#3

@JamesNK

This comment has been minimized.

Show comment
Hide comment
@pcibraro

This comment has been minimized.

Show comment
Hide comment
@pcibraro

pcibraro Feb 27, 2015

I've read about the FOSS exception for your new project jsonschema, but I have a concern. If I include a reference to jsonschema in my open source project. Based on your understanding, is the AGPL license transitive to any commercial software written by my open source project as well ?. It would be great if you can clarify that for me, as I'm looking for a way to support json schema in one of the open source projects where I am currently working on.

Thanks

I've read about the FOSS exception for your new project jsonschema, but I have a concern. If I include a reference to jsonschema in my open source project. Based on your understanding, is the AGPL license transitive to any commercial software written by my open source project as well ?. It would be great if you can clarify that for me, as I'm looking for a way to support json schema in one of the open source projects where I am currently working on.

Thanks

@StefH StefH referenced this issue in cvent/deprecated-json-schema-2-poco Jun 17, 2015

Open

The "required" property is not supported ? #24

Repository owner locked and limited conversation to collaborators Nov 15, 2016

@JamesNK JamesNK closed this Nov 15, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.