3. IANA Considerations
3. IANA Considerations
3.1. Registration of Media Type application/jsonpath
IANA has registered the following media type [RFC6838]:
Type name: application
Subtype name: jsonpath
Required parameters: N/A
Optional parameters: N/A
Encoding considerations: binary (UTF-8)
Security considerations: See the Security Considerations section of RFC 9535.
Interoperability considerations: N/A
Published specification: RFC 9535
Applications that use this media type: Applications that need to convey queries in JSON data
Fragment identifier considerations: N/A
Additional information:
Deprecated alias names for this type: N/A Magic number(s): N/A File extension(s): N/A Macintosh file type code(s): N/A
Person & email address to contact for further information: [email protected]
Intended usage: COMMON
Restrictions on usage: N/A
Author: JSONPath WG
Change controller: IETF
3.2. Function Extensions Subregistry
Per this specification, IANA has created a new "Function Extensions" subregistry in a new "JSONPath" registry. The "Function Extensions" subregistry has the policy "Expert Review" (Section 4.5 of [RFC8126]).
The experts are instructed to be frugal in the allocation of function extension names that are suggestive of generally applicable semantics, keeping them in reserve for functions that are likely to enjoy wide use and can make good use of their conciseness. The expert is also instructed to direct the registrant to provide a specification (Section 4.6 of [RFC8126]) but can make exceptions, for instance, when a specification is not available at the time of registration but is likely forthcoming. If the expert becomes aware of function extensions that are deployed and in use, they may also initiate a registration on their own if they deem such a registration can avert potential future collisions.
Each entry in the subregistry must include the following:
Function Name: A lowercase ASCII [RFC0020] string that starts with a letter and can contain letters, digits, and underscore characters afterwards ([a-z][_a-z0-9]*). No other entry in the subregistry can have the same function name.
Brief description: A brief description
Parameters: A comma-separated list of zero or more declared types, one for each of the arguments expected for this function extension
Result: The declared type of the result for this function extension
Change Controller: See Section 2.3 of [RFC8126].
Reference: A reference document that provides a description of the function extension
The initial entries in this subregistry are listed in Table 19; the entries in the "Change Controller" column all have the value "IETF", and the entries in the "Reference" column all have the value "Section 2.4 of RFC 9535":
| Function Name | Brief Description | Parameters | Result |
|---|---|---|---|
| length | length of string, | ValueType | ValueType |
| array, or object | |||
| count | size of nodelist | NodesType | ValueType |
| match | regular expression | ValueType, | LogicalType |
| full match | ValueType | ||
| search | regular expression | ValueType, | LogicalType |
| substring match | ValueType | ||
| value | value of the single | NodesType | ValueType |
| node in nodelist |
Table 19: Initial Entries in the Function Extensions Subregistry