Figure out a pattern for cutting down noisy validation errors about schemarama HOT 3 OPEN

See https://github.com/shexSpec/shex/blob/master/status.md under "discriminators@.

As described by @ericprud back in 2020:

the idea is that if you're validating something as a CreativeWork and it has a type of Recipe but doesn't actually satisfy Recipe, ShEx won't drown you in errors about every kind of CreativeWork that it fails, but instead it will just tell you why it doesn't satisfy Recipe
(and yes, danbri, i know it's not "failing", but you get the idea)
if y'all think the above description is missing some use case or nuance, let us know

Draft spec and examples: https://hackmd.io/1fpnYHxoSYOQhvYxHXddjA

from schemarama.

ShEx service-specific shape examples for Recipe and Dataset, https://github.com/google/schemarama/tree/main/demo/validation/shex/specific/ServiceB

from schemarama.

We want the bit of ShEx that checks for 'name' property in the shape to be able to link to something like https://developers.google.com/search/docs/advanced/structured-data/recipe#the_bit_of_the_docs_that_talks_about_name_property.

Realistically this might need initially to be done via out-of-band info rather than assuming all the shex from Google carries such details. Hence shapepath / IDs being an issue.

from schemarama.