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

Improvement of text explaining Figure 16 #46

Closed
larsgsvensson opened this issue Aug 7, 2023 · 1 comment
Closed

Improvement of text explaining Figure 16 #46

larsgsvensson opened this issue Aug 7, 2023 · 1 comment

Comments

@larsgsvensson
Copy link
Member

In Figure 16 the server answers an unsuccessful request with 422 and includes a Link header stating which profiles it can handle for the selected resource. The text explaining the figure does not mention this link header which leaves its nature unclear.
Suggestion (to be added between "... the resource at hand." and "Such a response ...":

The server includes a Link header indicating that the resource http://example.org/bibrecord/1/DC supports the profile http://purl.org/dc/terms/ and the media type "application/xml", so that the client can re-send its request.

(If we decide to use Request Content Negotiation Style as proposed in #38, the profile would go in a Accept-Profile heading and the text be changed accordingly).

@hvdsomp
Copy link
Collaborator

hvdsomp commented Aug 8, 2023

Addressed in 64a4154

@hvdsomp hvdsomp closed this as completed Aug 8, 2023
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

2 participants