Hi all,
I have some questions about RFC 7482.
I'm quite a newbie in RDAP (I have implemented a prototype of a RDAP
server) so I don't know if they can be considered as matters of an RDAP
profile or matters of the RDAP standard or simply trivial matters.
I have a background on digital libraries and, it seems to me that some
solutions found in that field could be applied to registration data
search and retrieval.
Question 1.
Looking at search path segments, I think that, in some cases, there
should be a way to restrict the possible results, particularly when
partial string matching is used.
A typical example coming in my mind is searching for entities with a
certain role.
Maybe one can be interested in searching only for registrants or
registrars but, at the moment, it is not possible.
Do you agree about it?
If so, what is the best way to restrict the search? To create custom
paths? To extend the search operators and allow conditions on the other
fields?
Question 2.
The paragraph "4.2. Associated Records" states:
"Note that there might not be a single, static information return policy
that applies to all clients equally. Client identity and
associated authorizations can be a relevant factor in determining how
broad the response set will be for any particular query."
Therefore a client cannot set the response format; even if it is
recommended to have different return policies, the response format is
fixed according to the client authorization.
I think that, at least, an optional "brief" response should be
available. Maybe it could correspond to the response of unauthenticated
client.
A "brief" response could be used to collect search query results while
the "full" response could be used in targeted lookup queries.
Clients could request the brief response as a query operator. For
example, https://example.com/rdap/entities?fn=Bobby%20Joe*&response=brief
Furthermore if a brief response format was standardized, it could
improve interoperability between client and servers.
What do you think about it?
Question 3.
What do you think about using the help response to return structured
information about the implemented profile (standard paths, custom paths,
additional search operators, access levels, and so on) ?
It could enable RDAP clients to configure themselves thus speeding up
interaction between clients and servers.
In the standard ANSI/NISO Z39.50 about search and retrieval, there was a
similar facility called Explain.
Thanks for your answers,
Mario
--
Dr. Mario Loffredo
Servizi Internet e Sviluppo Tecnologico
Unità Sistemi e Servizi Registro .it
CNR - Istituto di Informatica e Telematica
via G. Moruzzi 1, I-56124 PISA, Italy
E-Mail:[email protected]
Phone: +39 050 3153497
Web:http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext
