> Le 7 juin 2023 à 14:26, Andrew Newton a écrit :
>
> Hi All,
>
...
> By contrast, JSContact JSON objects are much more than simple JSON
> objects as found in RDAP. Here is an example of JSContact person
> titles:
>
> "titles": {
> "le9": {
>"kind": "title",
>"name": "Research
@dmarc.ietf.org" ,
"regext@ietf.org" , Tom Harrison , George
Michaelson , Andy Newton
Subject: Re: [regext] Thoughts on the fundamental premise of JSContact
Hi Jasdip,
Il 13/06/2023 16:01, Jasdip Singh ha scritto:
Cool, so looks like the Jackson library affords a seamless way to
org" ,
"regext@ietf.org" , Tom Harrison , George
Michaelson , Andy Newton
Subject: Re: [regext] Thoughts on the fundamental premise of JSContact
Hi Jasdip,
Il 12/06/2023 22:24, Jasdip Singh ha scritto:
Hello Mario,
After reviewing the PatchObject data type [1] in JSCon
Hi Jasdip,
Il 12/06/2023 22:24, Jasdip Singh ha scritto:
Hello Mario,
After reviewing the PatchObject data type [1] in JSContact, one question: How
would the JSON serialization/deserialization work for a JSONPointer as a key
(read: member name) in a PatchObject, given a programming language
Hi Mario,
On Fri, Jun 09, 2023 at 10:58:14AM +0200, Mario Loffredo wrote:
> Il 08/06/2023 15:39, Jasdip Singh ha scritto:
>> True, we could define an entity object class that serves the DNR
>> and RIR purposes with a simpler JSON, just like we chose to define
>> domain, IP network, and autonomous
Hello Mario,
After reviewing the PatchObject data type [1] in JSContact, one question: How
would the JSON serialization/deserialization work for a JSONPointer as a key
(read: member name) in a PatchObject, given a programming language like Java
does not allow a forward slash ( '/' ) in a
Hi Andy,
please find my comments below.
Il 09/06/2023 17:41, Andrew Newton ha scritto:
On Fri, Jun 9, 2023 at 10:03 AM Jasdip Singh wrote:
Hello Mario,
Your answer made my day! :) I'm still LOL about your "it wouldn't be short-sighted
but completely blind" point. Yah, good to think this
es
Sent: Thursday, June 8, 2023 8:14 AM
To: a...@hxr.us <mailto:a...@hxr.us> <mailto:a...@hxr.us <mailto:a...@hxr.us>>; regext@ietf.org
<mailto:regext@ietf.org> <mailto:regext@ietf.org <mailto:regext@ietf.org>>
Subject: [EXTERNAL] Re: [regext] Thoughts on the fun
On Fri, Jun 9, 2023 at 10:03 AM Jasdip Singh wrote:
>
> Hello Mario,
>
> Your answer made my day! :) I'm still LOL about your "it wouldn't be
> short-sighted but completely blind" point. Yah, good to think this through
> before we as a WG take the next step. I recall one of the laws of
t; On Behalf
>> Of Gould, James
>> Sent: Thursday, June 8, 2023 8:14 AM
>> To: a...@hxr.us <mailto:a...@hxr.us> <mailto:a...@hxr.us
>> <mailto:a...@hxr.us>>; regext@ietf.org <mailto:regext@ietf.org>
>> <mailto:regext@ietf.org <mailto:r
-Original Message-
From: regext mailto:regext-boun...@ietf.org>> On
Behalf Of Gould, James
Sent: Thursday, June 8, 2023 8:14 AM
To: a...@hxr.us <mailto:a...@hxr.us>; regext@ietf.org <mailto:regext@ietf.org>
Subject: [EXTERNAL] Re: [regext] Thoughts on the fundamental premise
> Le 7 juin 2023 à 14:26, Andrew Newton a écrit :
>
> Hi All,
>
> Very recently I have had the displeasure of implementing jCard for an
> RDAP client, and in so doing have taken a closer look at JSContact and
...
>
> #3 JSContact Implementations and Scope
>
> I did a little hunting around
Hi Andy,
thanks for sharing your thoughts about JSContact.
Please find my comments below.
Il 07/06/2023 20:26, Andrew Newton ha scritto:
Hi All,
Very recently I have had the displeasure of implementing jCard for an
RDAP client, and in so doing have taken a closer look at JSContact and
have
Hi Andy,
I made the original proposal to replace jCard, with a straight mapping of
RFC5733 contact objects into JSON, back in 2019:
https://mailarchive.ietf.org/arch/msg/regext/bZA9yGAdy2fPaDxiMuMr5CE-z74/
A certain Mr Newton (perhaps you know him) raised the point that this would
exclude
;> On
> Behalf Of Gould, James
> Sent: Thursday, June 8, 2023 8:14 AM
> To: a...@hxr.us <mailto:a...@hxr.us>; regext@ietf.org <mailto:regext@ietf.org>
> Subject: [EXTERNAL] Re: [regext] Thoughts on the fundamental premise of
> JSContact
>
> Caution: This email origin
egext] Thoughts on the fundamental premise of
> JSContact
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open attachments unless you recognize the sender and know the content is
> safe.
>
> Andy,
>
> I believe creating a sim
Andy,
I believe creating a simple RDAP extension for contacts (Path-forward #A) is
best. jCard and JSContact are much more generic and complex than what is
needed. The mandatory UID field of JSContact is a perfect example of how the
intended purpose of JSContact does not meet the needs of
Hi All,
Very recently I have had the displeasure of implementing jCard for an
RDAP client, and in so doing have taken a closer look at JSContact and
have talked to a few people privately about it. Both I and they
believed that JSContact would be much better than jCard. However,
after looking at
18 matches
Mail list logo
