--- 1/draft-ietf-regext-rdap-sorting-and-paging-19.txt 2020-11-30 01:14:03.300251718 -0800
+++ 2/draft-ietf-regext-rdap-sorting-and-paging-20.txt 2020-11-30 01:14:03.448255509 -0800
@@ -1,21 +1,21 @@
Registration Protocols Extensions M. Loffredo
Internet-Draft M. Martinelli
Intended status: Standards Track IIT-CNR/Registro.it
-Expires: April 7, 2021 S. Hollenbeck
+Expires: June 3, 2021 S. Hollenbeck
Verisign Labs
- October 4, 2020
+ November 30, 2020
Registration Data Access Protocol (RDAP) Query Parameters for Result
Sorting and Paging
- draft-ietf-regext-rdap-sorting-and-paging-19
+ draft-ietf-regext-rdap-sorting-and-paging-20
Abstract
The Registration Data Access Protocol (RDAP) does not include core
functionality for clients to provide sorting and paging parameters
for control of large result sets. This omission can lead to
unpredictable server processing of queries and client processing of
responses. This unpredictability can be greatly reduced if clients
can provide servers with their preferences for managing large
responses. This document describes RDAP query extensions that allow
@@ -30,21 +30,21 @@
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
- This Internet-Draft will expire on April 7, 2021.
+ This Internet-Draft will expire on June 3, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
@@ -970,20 +970,28 @@
pagination.html>.
[GOESSNER-JSON-PATH]
Goessner, S., "JSONPath - XPath for JSON", 2007,
.
[HATEOAS] Jedrzejewski, B., "HATEOAS - a simple explanation", 2018,
.
+ [JSONPATH-COMPARISON]
+ "JSONPath Comparison", 2020,
+ .
+
+ [JSONPATH-WG]
+ "JSON Path (jsonpath)", 2020,
+ .
+
[OData-Part1]
Pizzo, M., Handl, R., and M. Zurmuehl, "OData Version 4.0.
Part 1: Protocol Plus Errata 03", June 2016,
.
[REST] Fielding, R., "Architectural Styles and the Design of
Network-based Software Architectures", 2000,
@@ -1022,20 +1030,24 @@
Additionally, the specification permits implementations to support
arbitrary script expressions. These can be used to index into an
object or array, or to filter elements from an array. While script
expression behavior is implementation-defined, most implementations
support the basic relational and logical operators, as well as both
object member and array item access, sufficiently similar for the
purpose of this document. Commonly-supported operators/functions
divided into "top-level operators" and "filter operators" are
documented in Table 2 and Table 3 respectively.
+ For more information on implementation interoperability issues, see
+ [JSONPATH-COMPARISON]. As at the time of writing, work is beginning
+ on a standardization effort, too: see [JSONPATH-WG].
+
+-------------------+-----------------------------------------+
| Operator | Description |
+-------------------+-----------------------------------------+
| $ | Root element |
| . | Object member access (dot-notation) |
| [''] | Object member access (bracket-notation) |
| [] | Array item access |
| * | All elements within the specified scope |
| [?()] | Filter expression |
+-------------------+-----------------------------------------+
@@ -1350,20 +1362,24 @@
* added JSONPath union operator in Table 2 of "Appendix B"
* changed the explanation of offset and limit operators in
"Appendix B";
* converted the figures containing only RDAP queries into texts;
* changed the wildcard prefixed patterns into wildcard suffixed
in all the RDAP queries;
* cleaned the text.
19: Replaced the words "encryption/encrypt" with "obfuscation/
obfuscate" in the ""cursor" Parameter" section.
+ 20: Added a final paragraph to Appendix A to reference the
+ comparison between JSONPath operators and IETF JSONPath WG web
+ site.
+
Authors' Addresses
Mario Loffredo
IIT-CNR/Registro.it
Via Moruzzi,1
Pisa 56124
IT
Email: mario.loffredo@iit.cnr.it
URI: http://www.iit.cnr.it