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

[Andy Newton <[e-mail]>]

Agreed, especially considering other tech is being built upon JSContact.

RPP needs to be more than EPP-in-JSON, otherwise it will be an annoyance instead of a game-changer.

This is also why discovery is important.

-andy, as an individual

On 17-03-2026 2:03 AM, Jasdip Singh wrote:
> Hi,
> 
>  From technology-as-an-accelerator perspective, leveraging JSContact for RPP seems like a good idea. Since RPP (like RDAP) has the concept of profiles, an RPP profile that constricts the data requirements for JSContact for domain name use cases (EPP contact model) could come handy. If there were, say, number resources-related provisioning scenarios for RPP in the future, another JSContact profile could be defined for that.
> 
> Thanks,
> Jasdip
> 
> 
> *From: *Pawel Kowalik <kowalik=[e-mail]>
> *Date: *Monday, March 16, 2026 at 10:42 AM
> *To: *Mario Loffredo <mario.loffredo=[e-mail]>, [e-mail] <[e-mail]>
> *Subject: *[rpp] Re: An implementation of JSContact in JSON Schema
> 
> Hi Mario,
> 
> On 16.03.26 15:14, Mario Loffredo wrote:
>  > Do you think that the "rdap" profile is comprehensive enough for use
>  > in the RPP context ?
> 
> I think it still has too many options for the same data. For RPP it
> needs to be more strict and aligned with EPP contact model.
> 
> Kind Regards,
> Pawel
> 
> 
> _______________________________________________
> rpp mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]