[weirds] RDAP registrar entities

[Brian Mountford <[e-mail]>]

Hello, all. I have been directed to this list as a possible place to get
some RDAP questions answered. Here's one, regarding RDAP entities, which
appear to include both contacts and registrars. In our system internally,
the two are quite separate, and in fact registrars can themselves have
multiple contacts, just as a domain can. So I'm trying to figure out how to
fit the data into the RDAP format.

First of all, is there a reason why registrars and contacts were lumped
together into one type of thing? Just curious.

The example in RFC 7483 for a registrar included several addresses and
phone numbers, as if the sample registrar also had contacts associated with
it. But none of the addresses and phone numbers were marked with anything
that would distinguish between the contacts (e.g. a type of "admin",
"tech", etc.). Should we just take all the data we have for a registrar,
including all addresses of associated contacts, and throw them into the
entity JSON object one after another? Can we mark them with the contact
role as a type? Or does type always need to be "home" or "work"?

RFC 7482 describes searching for an entity by name. In the case of our
registrars, we have two things that could be a "name": the name of the
registrar itself, and the name of any associated contact. Am I correct that
the search is confined to the registrar name? Or are we supposed to look
through to the contact names, and pass back any registrar with a matching
contact?

Thanks.

Brian