From 0c48e5de5a63233867246717f5bc175ad3d236b8 Mon Sep 17 00:00:00 2001 From: Panagiotis Vretanos Date: Mon, 6 Jul 2026 09:53:21 -0400 Subject: [PATCH] Fix a tiny typo. --- core/sections/clause_7_core.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/sections/clause_7_core.adoc b/core/sections/clause_7_core.adoc index de2a35ff..34334875 100644 --- a/core/sections/clause_7_core.adoc +++ b/core/sections/clause_7_core.adoc @@ -264,7 +264,7 @@ include::../recommendations/core/REC_html.adoc[] The use of generic media types such as `application/json` makes it difficult to request or identify different flavors or profiles of a resource. For example, the media type `application/json` could be used to describe an <> as well as an https://documentation.dataspace.copernicus.eu/APIs/openEO/Processes.html[OpenEO process description document]. -Therefore, a mechanism for requesting a profile of a resource would be useful. Although there is a new HTTP header, `Accept-Profile`, that is to be defined in an upcoming https://profilenegotiation.github.io/I-D-Profile-Negotiation/I-D-Profile-Negotiation[Internet-Draft], there is currently no standardized was to request a profile of a resource. Existing standards, however, do provide mechanisms for specifying profile information in HTTP headers. Specifically (see https://www.w3.org/TR/dx-prof-conneg/#bib-prof-ietf[Content Negotiation by Profile]) profiles of a resource may be requested by: +Therefore, a mechanism for requesting a profile of a resource would be useful. Although there is a new HTTP header, `Accept-Profile`, that is to be defined in an upcoming https://profilenegotiation.github.io/I-D-Profile-Negotiation/I-D-Profile-Negotiation[Internet-Draft], there is currently no standardized way to request a profile of a resource. Existing standards, however, do provide mechanisms for specifying profile information in HTTP headers. Specifically (see https://www.w3.org/TR/dx-prof-conneg/#bib-prof-ietf[Content Negotiation by Profile]) profiles of a resource may be requested by: * Using the `profile` parameter if the media type includes provisions for such a parameter (e.g. https://www.iana.org/assignments/media-types/application/ld+json[`application/ld+json profile=http://www.w3.org/ns/json-ld#context`]), * Using the `Accept-Profile` header if the intended media type does not include provisions for a `profile` parameter and can, thus, not be specified in the `Accept` header,