Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
kephas opened this issue Dec 24, 2021 · 0 comments
Open

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

kephas opened this issue Dec 24, 2021 · 0 comments

Comments

@kephas
Copy link

kephas commented Dec 24, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant