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

Update RFCXXX references and IETF as Change controller #491

Merged
merged 2 commits into from
Jul 26, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions draft-ietf-jsonpath-base.md
Original file line number Diff line number Diff line change
Expand Up @@ -2020,6 +2020,12 @@ for which no standard JSON escape, such as `\n`, is available.

# IANA Considerations {#IANA}

[^replace-xxxx]: RFC Ed.: throughout this section, please replace
RFCXXXX with the RFC number of this specification and remove this
note.

[^replace-xxxx]

## Registration of Media Type application/jsonpath

IANA is requested to register the following media type {{RFC6838}}:
Expand Down Expand Up @@ -2131,8 +2137,9 @@ Reference:
extension

Initial entries in this sub-registry are as listed in {{pre-reg}}; the
Column "Change Controller" always has the value "IESG" and the column
"Reference" always has the value "{{fnex}} of RFCthis":
entries in the Column "Change Controller" all have the value "IETF"
and the entries in the column
"Reference" all have the value "{{fnex}} of RFCXXXX":

| Function Name | Brief description | Parameters | Result |
| length | length of string, array, object | `ValueType` | `ValueType` |
Expand Down
Loading