Skip to content

[Tag Review] - Structured Output #181

@etiennenoel

Description

@etiennenoel

From: w3ctag/design-reviews#1093 (comment)

It’s not clear whether models, underlying platforms, and frameworks will interoperably support the JavaScript flavor of Regular Expressions and JSON Schemas. Was that considered and validated when making this choice? We caution that it may be premature to settle on JSON Schema or JS RegEx as the format here out of an abundance of caution and interoperability concerns.

If the responses need to be processed anyway, why not do the schema and RegEx checks in JS (while acknowledging this may reduce developer ergonomics)?

The omitResponseConstraintInput and responseConstraint, plus adding constraints to the prompt might have unintended consequences. The fact that you can mix response guidance into the prompt itself may end up confusing the model in contradictory ways… what if the user or developer also asks for other formats themselves?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions