From 3b31b7ef690c311f64c4048d04e84c6c18eebf11 Mon Sep 17 00:00:00 2001 From: Vincent Biret Date: Tue, 7 Jan 2025 09:41:12 -0500 Subject: [PATCH 1/2] docs: adds links to annex C in path and server templating sections Signed-off-by: Vincent Biret --- src/oas.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/oas.md b/src/oas.md index 2ffed2bc76..28ea21f529 100644 --- a/src/oas.md +++ b/src/oas.md @@ -62,6 +62,8 @@ sub-delims = "!" / "$" / "&" / "'" / "(" / ")" Here, `pchar`, `unreserved`, `pct-encoded` and `sub-delims` definitions are taken from [RFC 3986](https://tools.ietf.org/html/rfc3986). The `path-template` is directly derived from [RFC 3986, section 3.3](https://datatracker.ietf.org/doc/html/rfc3986#section-3.3). +See also [Appendix C: Using RFC6570-Based Serialization](#appendix-c-using-rfc6570-based-serialization) for additional guidance. + ### Media Types Media type definitions are spread across several resources. @@ -600,6 +602,8 @@ iprivate = %xE000-F8FF / %xF0000-FFFFD / %x100000-10FFFD Here, `literals`, `pct-encoded`, `ucschar` and `iprivate` definitions are taken from [RFC 6570](https://www.rfc-editor.org/rfc/rfc6570), incorporating the corrections specified in [Errata 6937](https://www.rfc-editor.org/errata/eid6937) for `literals`. +See also [Appendix C: Using RFC6570-Based Serialization](#appendix-c-using-rfc6570-based-serialization) for additional guidance. + ##### Fixed Fields | Field Name | Type | Description | From b87e39c4df75053a233ab3c30d8d2be27dd4cb34 Mon Sep 17 00:00:00 2001 From: Vincent Biret Date: Thu, 9 Jan 2025 08:17:01 -0500 Subject: [PATCH 2/2] fix: adds reference to paths object guidance from server variables Signed-off-by: Vincent Biret --- src/oas.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/oas.md b/src/oas.md index 28ea21f529..a54e56835b 100644 --- a/src/oas.md +++ b/src/oas.md @@ -602,7 +602,7 @@ iprivate = %xE000-F8FF / %xF0000-FFFFD / %x100000-10FFFD Here, `literals`, `pct-encoded`, `ucschar` and `iprivate` definitions are taken from [RFC 6570](https://www.rfc-editor.org/rfc/rfc6570), incorporating the corrections specified in [Errata 6937](https://www.rfc-editor.org/errata/eid6937) for `literals`. -See also [Appendix C: Using RFC6570-Based Serialization](#appendix-c-using-rfc6570-based-serialization) for additional guidance. +See the [Paths Object](#paths-object) for guidance on constructing full request URLs. ##### Fixed Fields