Processor
Working with Schema-related data is complex due to the lax syntax and graph conventions that publishers are able to use. This also means consumers can be less certain of the shapes and types they need to support. Our processor can handle a broad range of conventions from around the web and we categorize the steps under the following topics:
- Mapping — ensure the data uses acceptable values and data types.
- Validation — ensure the data is contextually and structurally acceptable.
- Normalization — ensure the data uses shapes and types that are acceptable to consumers.
Profiles
A profile determines what policies are used during processing, validation, and normalization. We currently offer a single profile, although versioned profiles are expected in the future.
Default Profile
Based on official recommendations, industry best practices, and ensuring downstream data consumers require simple implementations. Currently using Release 29.2.