Status — Published as a design exploration
Structured-data schema-builder interaction
Question
Does letting readers edit a schema in the browser improve their understanding of extraction trade-offs?
Hypothesis
Editing fields surfaces the optional-versus-required decision, which is the decision that most affects downstream validation.
Who it concerns
Developers designing extraction pipelines.
Intervention
A schema starter with add, rename, remove, and type controls plus a live sample output object.
What would be observed
- Whether users mark fields optional after seeing the sample output
- Which preset use case is opened most
What would count as a useful signal
Users produce schemas with fewer required fields than the preset default.
Notes
Next step: add a validation-failure preview.
structured datainteractive tools
This entry records a design intention. It does not report measured results, traffic, rankings, or customer outcomes.