Address #556 and #557.

The only slightly unusual thing here is that while additionalItems only takes effect when items is present, due to the more dynamic nature of unevaluatedItems, I decided that it could take place whether items is present anywhere or not.

I believe the restriction on additionalItems is to avoid an ambiguity where you can use either items or additionalItems to perform the same assertion. Requiring additionalItems to be ignored in the absence of items makes the single-schema use of items unambiguously the only way to validated every item in an array.

For unevaluatedItems, it seems more correct for it to apply even when no array elements have had a schema evaluated against them, rather than requiring that somewhere in the depths of subschemas there must have been an array-form items. I could be persuaded otherwise, but with this approach, the single schema form of items becomes a way to unconditionally apply a schema to the enter array, while unevaluatedItems has an inherently conditional behavior- it applies to all only if none were already evaluated.

unevaluatedProperties has no such ambiguities, and I believe is specified exactly as it has been extensively discussed.