Skip to content

Mandate REST, or include alternatives like GraphQL #5

@clausmullie

Description

@clausmullie

Seems like we mandating to use REST, are we excluding other alternatives, like GraphQL

C.2 API Interface and Behavior
APIs MUST follow RESTful URL conventions with predictable endpoint structures

Does indeed exclude GraphQL

This could either become more open, something like

APIs MUST provide a documented, machine-readable interface that allows programmatic access to data with predictable request and response patterns.

with the risk of becoming too vague and more complex to interpret/implement

Or explicitly include GraphQL

If using REST, APIs MUST follow RESTful URL conventions with predictable endpoint structures
If using GraphQL, APIs MUST includes a consistent schema with clearly defined types, queries, and mutations

Would there be any others to add to this list?

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