On an Item, it will validate the fields in properties, assets, and raster:bands if it exists in an asset. It does not require any of these.
On a Collection, it will validate the fields in assets, item_assets, raster:bands if it exists in an asset or item_asset, and summaries. It does not require any of these.
I believe this covers all the uses that have been discussed. Note that "fields" refers to classification:classes and classification:bitfields.
Format Note
I diverged from the latest schema template (from the Template Extension) for the Collection portion. I avoided the "anyOf" array, as that will validate successfully as long as one of the array entries is correct, even if another entry is incorrect. I did a sanity check with the Scientific Extension (which uses the "anyOf" array) to confirm this seemingly incorrect behavior, but perhaps I'm misunderstanding something.
Things the schema does:
properties,assets, andraster:bandsif it exists in an asset. It does not require any of these.assets,item_assets,raster:bandsif it exists in an asset or item_asset, andsummaries. It does not require any of these.I believe this covers all the uses that have been discussed. Note that "fields" refers to
classification:classesandclassification:bitfields.Format Note
"anyOf"array, as that will validate successfully as long as one of the array entries is correct, even if another entry is incorrect. I did a sanity check with the Scientific Extension (which uses the"anyOf"array) to confirm this seemingly incorrect behavior, but perhaps I'm misunderstanding something.