This repository was archived by the owner on Apr 13, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Requirements
Herbert Van de Sompel edited this page Apr 24, 2017
·
3 revisions
- Indicating the profile of an entity body
- A server should be able to indicate that an entity body conforms to a single profile.
- A server should be able to indicate that an entity body conforms to multiple profiles.
- A server should be able to indicate supported profiles of alternate representations.
- Indicating the desired profiles
- A client should be able to indicate which profiles it supports.
- A client should be able to indicate which combinations of profiles it supports?
- A client should be able to indicate which combinations of profiles and media types it supports?
- A client should be able to indicate which profiles it prefers.
- A client should be able to indicate which profiles it supports.
- Compatibility
- A client that does not support this RFC should still be able to correctly identify the media type of the response.
- An intermediary (proxy/cache) should understand the implications of profile-based negotiation on cacheability.