Shapes are used to define patterns of data, which can be used to match or validate state and operations.
Declaration of a shape does not provide any runtime function by itself, but they can be used by other extensions and app code.
While this class implements
MeldConstraint, shape checking is semantically
weaker than constraint checking, as a violation
(non-conformance) does not produce an exception but instead resolves a
validation result. However, the constraint apply will attempt a
correction in response to a non-conformance.
Capture precisely the data being affected by the given update which correspond to this shape, either before or after the update is applied to the state.
In respect of SHACL concepts, correspondence is based on targets and paths (if applicable), but not constraints; so that non-validating state (either before or after the update) is included.
filtered updates where the affected subject corresponds to this shape