Skip to content

Commit 1d0ad9e

Browse files
David Jonesbrettz9
authored andcommitted
Update links to RFC 6901 JSON Pointer
Previous links to `rfc-base.org` were broken.
1 parent d2a05b7 commit 1d0ad9e

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ evaluate method (as the first argument) include:
155155
- ***resultType*** (**default: "value"**) - Can be case-insensitive form of
156156
"value", "path", "pointer", "parent", or "parentProperty" to determine
157157
respectively whether to return results as the values of the found items,
158-
as their absolute paths, as [JSON Pointers](http://www.rfc-base.org/txt/rfc-6901.txt)
158+
as their absolute paths, as [JSON Pointers](https://tools.ietf.org/html/rfc6901)
159159
to the absolute paths, as their parent objects, or as their parent's
160160
property name. If set to "all", all of these types will be returned on
161161
an object with the type as key name.
@@ -224,7 +224,7 @@ evaluate method (as the first argument) include:
224224
constructions `~` and `^` and type operators like `@string()` are
225225
silently stripped.
226226
- ***JSONPath.toPointer(pathAsArray)*** - Accepts a path array and
227-
converts to a [JSON Pointer](http://www.rfc-base.org/txt/rfc-6901.txt).
227+
converts to a [JSON Pointer](https://tools.ietf.org/html/rfc6901).
228228
The string will be in a form like: `/aProperty/anotherProperty/0`
229229
(with any `~` and `/` internal characters escaped as per the JSON
230230
Pointer spec). The JSONPath terminal constructions `~` and `^` and

0 commit comments

Comments
 (0)