> 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 f
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 ta
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 non-
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 system number object classes that are specific to these
registries' business. However, before abandoning the JSContact effort, on
Last note, folks, I promise! The final agenda and registration details are
available and described below.
Scott
From: row-commit...@googlegroups.com On Behalf
Of nicoleta munteanu
Sent: Thursday, June 8, 2023 7:44 AM
Subject: [EXTERNAL] ROW12 agenda & registration
Caution: This email or
I kinda prefer option A, too. Anything we can do to make this easier will be
time well spent.
Scott
> -Original Message-
> From: regext On Behalf Of Gould, James
> Sent: Thursday, June 8, 2023 8:14 AM
> To: a...@hxr.us; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Thoughts on the
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 RDA
