---
title: "Comment by David Kemp on \"What is \"Modern\" JSON Schema?\" | Hashnode"
description: "\"The \"additionalProperties\" keyword can't see into the example.com/schemas/sharedproperties schema, so it doesn't matter what it contains.\" Is this required beh"
url: "https://hashnode.com/posts/what-is-modern-json-schema/636c43c03de309d1606aa33b/comment/664e3faeba320c095497f658"
---

[Discussion](https://hashnode.com/posts/what-is-modern-json-schema/636c43c03de309d1606aa33b)

Comment [What is "Modern" JSON Schema?](https://hashnode.com/posts/what-is-modern-json-schema/636c43c03de309d1606aa33b)

[David Kemp](https://hashnode.com/@davi9)

[May 22, 2024](https://hashnode.com/posts/what-is-modern-json-schema/636c43c03de309d1606aa33b/comment/664e3faeba320c095497f658)

"The "additionalProperties" keyword can't see into the example.com/schemas/sharedproperties schema, so it doesn't matter what it contains."

Is this required behavior in classic JSON Schema, or just the result of poor execution? In other words, could the problem be fixed with conformance requirements without any change to schema syntax?