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

A client should be able to discover which profiles are supported by a server, and with which content types or other properties, in order to receive the representation most appropriate for their use. #285

Closed
nicholascar opened this issue Jun 27, 2018 · 4 comments
Closed

A client should be able to discover which profiles are supported by a server, and with which content types or other properties, in order to receive the representation most appropriate for their use. #285

nicholascar opened this issue Jun 27, 2018 · 4 comments
Labels
due for closing Issue that is going to be closed if there are no objection within 6 days plenary-approved profile-negotiation requirement requires discussion Issue to be discussed in a telecon (group or plenary)

Comments

@nicholascar
Copy link
Contributor

Entered from Google Doc
@nicholascar nicholascar added requirement profile-guidance requires discussion Issue to be discussed in a telecon (group or plenary) content-negotiation labels Jun 27, 2018
@nicholascar nicholascar changed the title Requirement: a client should be able to determine which profiles are supported by a server, and with which content types or other properties, in order to receive the one most appropriate for their use. A client should be able to determine which profiles are supported by a server, and with which content types or other properties, in order to receive the one most appropriate for their use. Sep 1, 2018
@larsgsvensson larsgsvensson mentioned this issue Oct 22, 2018
Closed
@larsgsvensson
Copy link
Contributor

Perhaps the latter part of the sentence should read "the representation most appropriate for their use".

@dr-shorthair dr-shorthair changed the title A client should be able to determine which profiles are supported by a server, and with which content types or other properties, in order to receive the one most appropriate for their use. A client should be able to discover which profiles are supported by a server, and with which content types or other properties, in order to receive the one most appropriate for their use. Oct 24, 2018
@nicholascar nicholascar changed the title A client should be able to discover which profiles are supported by a server, and with which content types or other properties, in order to receive the one most appropriate for their use. A client should be able to discover which profiles are supported by a server, and with which content types or other properties, in order to receive the representation most appropriate for their use. Oct 24, 2018
@nicholascar
Copy link
Contributor Author

Changed as per Lars' suggesting.

These requirements retain lineage - to check that changes like this don't break with the original intention - by being linked to from the originals in the Google Doc.

@rob-metalinkage
Copy link
Contributor

Addressed in document.

@rob-metalinkage rob-metalinkage added the due for closing Issue that is going to be closed if there are no objection within 6 days label Feb 20, 2019
@larsgsvensson
Copy link
Contributor

Closed in conneg meeting 2019-03-13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
due for closing Issue that is going to be closed if there are no objection within 6 days plenary-approved profile-negotiation requirement requires discussion Issue to be discussed in a telecon (group or plenary)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@larsgsvensson @nicholascar @rob-metalinkage