Skip to content

Misleading name as a REST API cannot really be described with SPORE #13

@kephas

Description

@kephas

The core element of REpresentational State Transfer (REST) architecture is that a client will never build URIs themselves with patterns like /foo/:bar but will instead receive URI references in each representation of a resource, indicating which state transfers are possible.

I don't see this in the SPORE spec.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions