Thanks! JSON Schema is very important (and underrated, IMHO) because... tech stacks these days often integrate from various sources, outside the control of the organization. Bad data can cause software to misbehave. But, you can protect against both of these risks with a good validation schema. I became a big fan of schemas when I worked in Point of Sale. Those systems ingest gigabytes of information each day... yet also, require 100.00000% uptime. So having a thorough schema is key to balancing both of these requirements.
Excellent, thanks! Schemas are a great way of having a contract of what type of data can be exchanged among different organizations. I saw them a lot more in XML/XSD, though I'm starting to see a bit more use in JSON. Structure means we have better data in and out, which means our systems are less error prone.
Actually... mostly Java and Android, in the School of Information Technology (CECH). I also have a once per year, half-semester course in MS-IS program at the Lindner College of Business, which uses .Net and Visual Studio 2019. It's currently called "XML and Web Services", but is going to change to "Integrating Data APIs." I made this video for that course. :)
@@discospiff very good video! Very clear explanation of the concepts. I graduated from Lindner College of Business (MS-IS) in 2011. I wish I had taken your class
Ever seen a JSON Schema pattern for supporting column level ACL (access control list)? I’m enforcing it on the server, but the ACL in the JSON Schema in the client would let me generate forms with just the right amount of viewable and editable fields.
Great video as it helps to unpack JSON schema 😂
Thanks!
JSON Schema is very important (and underrated, IMHO) because... tech stacks these days often integrate from various sources, outside the control of the organization. Bad data can cause software to misbehave. But, you can protect against both of these risks with a good validation schema.
I became a big fan of schemas when I worked in Point of Sale. Those systems ingest gigabytes of information each day... yet also, require 100.00000% uptime. So having a thorough schema is key to balancing both of these requirements.
Thank you so much for this video, it's help for me
Excellent, thanks! Schemas are a great way of having a contract of what type of data can be exchanged among different organizations. I saw them a lot more in XML/XSD, though I'm starting to see a bit more use in JSON. Structure means we have better data in and out, which means our systems are less error prone.
Nice video as always! Are you using/teaching mostly c# these days?
Actually... mostly Java and Android, in the School of Information Technology (CECH). I also have a once per year, half-semester course in MS-IS program at the Lindner College of Business, which uses .Net and Visual Studio 2019. It's currently called "XML and Web Services", but is going to change to "Integrating Data APIs." I made this video for that course. :)
Interesting. They are very well done videos. Thanks for putting them together and making them available!
@@discospiff very good video! Very clear explanation of the concepts. I graduated from Lindner College of Business (MS-IS) in 2011. I wish I had taken your class
@@adolfo1981 Thanks! I am LCB MBA, 2004... I bet we had some of the same professors.
could you send the files?
Sure. They are in this repo: github.com/discospiff/PlantDiary001
Ever seen a JSON Schema pattern for supporting column level ACL (access control list)? I’m enforcing it on the server, but the ACL in the JSON Schema in the client would let me generate forms with just the right amount of viewable and editable fields.