Hi Jasdip,
thanks a lot for this job.
Let me share some thoughts.
Think that one of the reasons why RDAP (and modern REST APIs in general)
returns a JSON response is that JSON is schemaless so it implicitly
reduces the risk of introducing breaking changes in responses by design.
Given that
> -Original Message-
> From: Tom Harrison
> Sent: Thursday, May 19, 2022 8:44 PM
> To: Gould, James
> Cc: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: Re: Re: Re: [regext] Extension Prefixes, JSON
> Values, and URI Path Segments
[SAH] snip
> > Agreed, the uniqueness is
Dear Murray,
Thank you for your review!
On Tue, May 17, 2022 at 7:28 PM Murray S. Kucherawy
wrote:
> Hi all, thanks for sending this along. And thanks for including Section 7.
>
> 1) In Section 3, you have:
>
> "The validation rules introduced in RFC 6531 are considered to be
> followed."
>
>
On Thu, May 19, 2022 at 8:44 PM Tom Harrison wrote:
>
> RFC 7483 was pretty clear about this:
>
> When custom JSON values are inserted into responses, conformance
> to those custom specifications MUST use a string prefixed with the
> appropriate identifier from the IANA RDAP Extensions
