Graph Validation
By default, we perform basic data validation on Schema-related data to ensure it follows official recommendations and best practices. During processing, the following scenarios may generate an error or warning.
- Invalid Term — e.g.
schema:ExampleUnknownis not an official term - Unexpected Object — e.g.
DateTimeis not valid for aBooleanproperty - Unexpected Resource Type — e.g. resource with a
Vehicletype is not valid for anauthor - Actions: Unbound Property Annotation — e.g.
schema:query-inputproperty is not valid for aCreativeWork - Actions: Invalid Property Annotation Constraint Key — e.g.
placeholderis not a valid short-hand key - Roles: Unpropagated Property — e.g.
OrganizationRolefrom amemberproperty must itself includemember
In some cases, a formal interpretation of specifications diverges from recommendations, and we currently do not generate errors for the following, ambiguous scenarios.
As an alternative, the normalization step may be helpful to automatically reconcile some of these errors or transform ambiguous scenarios into more deterministic data structures.