The document discusses a talk titled "JSON Validation using JSON Schema and Jackson" by Stephane Rondal. It provides an overview of JSON, describing its prevalence in web and mobile applications and role in data exchange. It then introduces JSON Schema as a way to represent the structure of JSON documents, similar to how XML Schema defines the structure of XML documents. Examples of JSON Schema are provided.

1. {
“Talk” :
“JSON Validation
using JSON Schema and
Jackson”,
“by” : “Stephane Rondal”
}

2. stephane.rondal@arexo.be
@stephanerondal

3. JSON

4. JSON
• Very present in Web 2.0 and mobile apps

5. JSON
• Very present in Web 2.0 and mobile apps
• With REST, typically serves as the data exchange format

6. JSON
• Very present in Web 2.0 and mobile apps
• With REST, typically serves as the data exchange format
• Sometimes even derived automatically from POJOs

7. JSON
• Very present in Web 2.0 and mobile apps
• With REST, typically serves as the data exchange format
• Sometimes even derived automatically from POJOs
• Part of the interface between client and server

8. JSON
• Very present in Web 2.0 and mobile apps
• With REST, typically serves as the data exchange format
• Sometimes even derived automatically from POJOs
• Part of the interface between client and server
• Stability / Backward-compatibility??

9. JSON
• Very present in Web 2.0 and mobile apps
• With REST, typically serves as the data exchange format
• Sometimes even derived automatically from POJOs
• Part of the interface between client and server
• Stability / Backward-compatibility??

10. JSON Schema

11. JSON Schema
Represents the structure of a JSON document

12. Much like XML Schema does for XML documents

13. n’t r un
a it, do
X ML ?W t!
ay ye
aw
Much like XML Schema does for XML documents

14. Keeping the simple and
lightweight aspects of JSON we
have all come to love

15. JSON Schema

16. JSON Schema
• A schema is a JSON document

17. JSON Schema
• A schema is a JSON document
• Specifies
• Properties
•Type (simple, complex)
•Required/Optional
•Simple constraints
• And more...

18. {
"description": "An Address following the convention ...",
"type":"object",
"properties": {
"post-office-box": { "type": "string" },
"extended-address": { "type": "string" },
"street-address": { "type": "string" },
"locality":{ "type": "string", "required": true },
"region": { "type": "string", "required": true },
"postal-code": { "type": "string" },
"country-name": { "type": "string", "required": true}
},
"dependencies": {
"post-office-box": "street-address",
"extended-address": "street-address"
}
}

19. An IETF draft standard (3rd version)

20. Why
use
JSON
Schema ?

22. Documentation

23. Automation
Code / UI Generation

24. Or Why Not ?

25. Demo

26. References
• www.json.org
• json-schema.org
• tools.ietf.org/html/draft-zyp-json-schema-03
• github.com/fge/json-schema-validator

28. Q&A