Re: [regext] 7482bis: Search Path Segment Specification Clarification

Mario Loffredo <mario.loffredo@iit.cnr.it> Thu, 23 January 2020 16:42 UTC

Return-Path: <mario.loffredo@iit.cnr.it>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E73712090B for <regext@ietfa.amsl.com>; Thu, 23 Jan 2020 08:42:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kopVcEfFTUwg for <regext@ietfa.amsl.com>; Thu, 23 Jan 2020 08:42:24 -0800 (PST)
Received: from smtp.iit.cnr.it (mx4.iit.cnr.it [146.48.98.151]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0639D120902 for <regext@ietf.org>; Thu, 23 Jan 2020 08:42:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.iit.cnr.it (Postfix) with ESMTP id EAB44B8042A; Thu, 23 Jan 2020 17:42:21 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mx4.iit.cnr.it
Received: from smtp.iit.cnr.it ([127.0.0.1]) by localhost (mx4.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ys95FExdpJXR; Thu, 23 Jan 2020 17:42:19 +0100 (CET)
X-Relay-Autenticated: yes
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Mario Loffredo <mario.loffredo@iit.cnr.it>
Mime-Version: 1.0
Message-Id: <1615CAE7-6697-45BF-AA2A-62D4249F657E@iit.cnr.it>
Date: Thu, 23 Jan 2020 17:42:18 +0100
Cc: "regext@ietf.org" <regext@ietf.org>
To: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/RL4Y2ZcREA1gRAOhiKg6ha1-CZg>
Subject: Re: [regext] 7482bis: Search Path Segment Specification Clarification
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2020 16:42:26 -0000



Inviato da iPhone

> Il giorno 23 gen 2020, alle ore 15:21, Hollenbeck, Scott <shollenbeck=40verisign.com@dmarc.ietf.org> ha scritto:
> 
> Section 3.2 contains this text:
> 
> "The HTTP query string is formed using a concatenation of the question mark character ('?', US-ASCII value 0x003F), the JSON object value associated with the object being searched for, the equal sign character ('=', US-ASCII value 0x003D), and the search pattern."
> 
> Proposed change:
> 
> "The HTTP query string is formed using a concatenation of the question mark character ('?', US-ASCII value 0x003F), [a noun representing the JSON object property] associated with the object being searched for, the equal sign character ('=', US-ASCII value 0x003D), and the search pattern."
> 
> What do people think about this proposal?

This sentence seems to exclude any future use of additional parameters in the query string.

Having said that, partial-response and sorting-and-paging would be uncompliant with 7482bis.

Similarly, I would consider such possibility for lookup queries.

Mario


> Scott
> 
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext