 Hello. Let's take a look at how we can use JSON schema files for providing intelligence and validation to our JSON documents. JSON schema is conceptually the same as an XML schema or XSD file, but it's all expressed in JSON. And so let's take a look at what I've got here in the project. I have document JSON and schema.json. And so my idea is that I want to define the rules and the format and all this sort of stuff in my schema file, and I want to fill in all the values that it adheres to that format in my document file, document.json in this case. So right off the bat, if you just have an empty JSON file, you get no intelligence, right? It doesn't know what you're about to do, so it has no concept of intelligence for this, obviously. So let's go ahead and define the schema file. So the very first thing we have to do is to add a dollar schema property. And I have to select the JSON schema.org draft for value here. This will now make this, this schema file is now an official JSON schema. That's all we have to do to make it official schema, but of course it doesn't really do anything yet. I haven't defined any properties. And so let's go ahead and do that. So because I now have defined what my schema is, in this case, the draft for schema, which was through knows how to provide intelligence for me. And so I'm going to add a property here called URL. And this is of type string. And the format is URI. So I'm going to save my schema file. And now I'm going to go back to my document file. And I have to tell my document what schema to use. So I can just go up here and select an existing schema or type in the address of any schema that I want. Or since it's in the same project, I'm just going to drag schema JSON up to that dropdown and hit enter. And now I get intelligence for the URL property that I just defined. You see here, it gives me an error, a validation error says, hey, this has to be a valid URI. So here's my website. Oh, but it's actually not a valid URI because I forgot the protocol. And here we go. So now I have both intelligence for my properties as well as validation going on here. And I can make it even better. I can add a description here. And we can call this the address off your website. So now when we go back here and hover, we can see that we actually get that nice tool tip about what the URL property is doing. But we can go even further. And so we can say and say we have something where you're going to select an enum value. Let's let's do a version. So this is a type enum. Nope. Sorry, I don't have to do that. There we go. Enum values. So let's say version. What version of this document, for instance, of this schema are you going to use? We can now do this. If we go back after saving, I can now see that I have versions showing up here. And I get intelligence for the two possible values that I can choose. There's a lot more to JSON schema than just strings and enums as I showed here. There's arrays and objects and a bunch more stuff. And you can actually be very expressive in the rules that you want to apply to your document. So whether you want to have your schema file in the same project or solution as your documents or you want to put them on a network share or a web address somewhere, it all works in Visual Studio. You just type the path of the URL to the schema up here and apply to the document. And it will be saved in the project system so that anyone on the team opens the same project, the same schema will apply to those documents. And so this is a really rich experience and this is a really great place to write JSON schemas. So this is available in Visual Studio, not just the latest version, but since 2013. And so I hope you enjoy it. Thank you.