[rpp] Re: An implementation of JSContact in JSON Schema

[Stephane Bortzmeyer <[e-mail]>]

On Mon, Mar 16, 2026 at 09:29:49AM +0100, Pawel Kowalik wrote:

> If RPP were to use JSContact it would have to define a different profile of
> it imho.

Yes, JSContact is very lax and many things which are probably
mandatory for us (like the postal address) can be ommited. I think
that our goal should be that every RPP "document" describing a
contact/entity must be a valid JSContact card but the opposite does
not have to be true.

> Your implementation for example used name components for first and last
> name,

Which violates
<https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/>,
yes.

> what is not fitting domain registration data model defined in EPP.

The model of RFC 5733 is more correct but it can be represented in
JSContact with the "full" property (RFC 9553, section 2.2.1.1). So,
instead of:

"name": {"components": [{"kind": "given","value": "Li"},
			 {"kind": "surname","value": "Ping"}

use:

"name": {"full": "Li Ping"}