Topic
Practical schema design, event envelopes, compatibility rules, and validation boundaries for dependable data exchange.
4 articles
Data Contracts
Use a null-marker map when member names vary but every dynamic member must carry one deliberately narrow value: JSON null. This approach rejects false and zero markers while retaining extensibility; use a closed object when dynamic names are not part of the contract.
Data Contracts
A troubleshooting-oriented approach to distinguishing omission, null, and unknown members while keeping a stable JSON core closed and routing approved change through a named extension boundary.
Data Contracts
Use OpenAPI 3.1.1 to describe the HTTP exchange, and use JSON Schema Draft 2020-12 to express how a JSON payload is evaluated. This guide maps responsibilities, shows where a request-body schema fits, and offers a boundary-based troubleshooting approach.
Data Contracts
Make partial-update behavior predictable by assigning business meaning to omission, null, and empty values before encoding field rules in JSON Schema.