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.

Sign up for GitHub

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

Jump to bottom

Make conformance clauses more future-proof #391

Closed
ralfhandl opened this issue Mar 20, 2024 · 0 comments · Fixed by #225
Closed

Make conformance clauses more future-proof #391

ralfhandl opened this issue Mar 20, 2024 · 0 comments · Fixed by #225
Assignees
@ralfhandl
Labels
Protocol Protocol, URL Conventions V4.02

Comments

@ralfhandl
Copy link
Contributor

The current Conformance clauses require services to fail with 501 Not Implemented for unsupported functionality.

This is problematic when adding new functionality in later specification versions that is unknown to services conforming with earlier specification versions: do they become non-conforming by responding with 400 Bad Request to the new functionality?

Proposal

#225

Imported from ODATA-1624
@ralfhandl ralfhandl added Protocol Protocol, URL Conventions V4.02 labels Mar 20, 2024
@ralfhandl ralfhandl self-assigned this Mar 20, 2024
@HeikoTheissen HeikoTheissen modified the milestone: 4.02 Mar 22, 2024
@ralfhandl ralfhandl mentioned this issue Apr 23, 2024
Merged
ralfhandl added a commit that referenced this issue May 8, 2024
@ralfhandl
ODATA-1624 (#225)
7f4c4e3 
Fixes #391
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ralfhandl ralfhandl

Labels
Protocol Protocol, URL Conventions V4.02
Projects
OData TC
Status: Closed
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ODATA-1624 oasis-tcs/odata-specs
2 participants
@ralfhandl @HeikoTheissen