Hi Peter, There is a group of gTLD registries and registrars working on a proposal for a gTLD RDAP profile. I think this is probably a good topic for them to address. I’ll send you a private email to put you in contact with them. Regards, -- Francisco On 8/27/18, 12:28 PM, "gtld-tech on behalf of Peter Davidson" <gtld-tech-bounces@icann.org<mailto:gtld-tech-bounces@icann.org> on behalf of peter.davidson@appdetex.com<mailto:peter.davidson@appdetex.com>> wrote: Hello All, I'm implementing our RDAP Server as a registrar, not a registry and I've run into a couple questions: RFC7483 (RDAP JSON Response) defines handle as DNRs and RIRs have registry-unique identifiers that may be used to specifically reference an object instance. The semantics of this data type as found in this document are to be a registry-unique reference to the closest enclosing object where the value is found. The data type names "registryId", "roid", "nic-handle", "registrationNo", etc., are terms often synonymous with this data type. Should registrant, administrative and technical entities be returned for domains at thin registries? Since thin registries, such as com and net, don't have handles, how should we generate the entity link? Since handle is used in the /entity/XXXX query defined RDAP Query Format [RFC7482], how should we treat handles that are non unique across registries? Thanks in advance - Peter Davidson