From 31eef03f3e8d0e63c9d6e15aae965a37435ec685 Mon Sep 17 00:00:00 2001 From: Ralf Handl Date: Fri, 12 Sep 2025 14:45:19 +0200 Subject: [PATCH] Consistent use of "JSON Pointer" --- src/oas.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/oas.md b/src/oas.md index f7b626d28c..5f145ec2c8 100644 --- a/src/oas.md +++ b/src/oas.md @@ -160,7 +160,7 @@ Therefore, all implementations SHOULD allow users to provide documents with thei ###### Resolving URI fragments -If a URI contains a fragment identifier, then the fragment should be resolved per the fragment resolution mechanism of the referenced document. If the representation of the referenced document is JSON or YAML, then the fragment identifier SHOULD be interpreted as a JSON-Pointer as per [RFC6901](https://tools.ietf.org/html/rfc6901). +If a URI contains a fragment identifier, then the fragment should be resolved per the fragment resolution mechanism of the referenced document. If the representation of the referenced document is JSON or YAML, then the fragment identifier SHOULD be interpreted as a JSON Pointer as per [RFC6901](https://tools.ietf.org/html/rfc6901). ###### Relative URI References in CommonMark Fields