The validator should default to generating an error or warning if a extension-definition does not have a jsonschema associated with it

[rpiazza]

Perhaps we can include a command line argument to ignore these these situations.

Right now, the validator will accept any use of an extension definition for which there is no jsonschema.

The reason behind this is to put the onus on bad syntax on the user, not the validator.