Re: [regext] rdap mobile app avail

Hi Marc,

First, sorry that you are feeling frustrated.

With regards to null vs empty string, in my opinion both are
incorrect. If your registry does not have the value or is not allowed
to publish the value, the correct thing to do is to simply leave the
value out of the response. There are a few required fields in RDAP,
but for the most part everything is optional.

I hope that helps.

-andy

On Thu, Aug 29, 2019 at 4:11 AM Marc Groeneweg
<Marc.Groeneweg=40sidn.nl@dmarc.ietf.org> wrote:
>
> All,
>
> Due to the release of the mobile app of Marc, Blanchet we saw we differ in interpretation of some fields we have in our RDAP implementation (for .politie and .amsterdam).
> Feedback from my development on the issues given Marc is that they have chosen for a direction, that is at least now not compliant with what the mobile app aspects.
>
> They are frustrated about this, since they have had an extensive period behind them with working on the specifications and building a sound RDAP implementation, that also is meant for .nl later this year. Intensive contact with ICANN resulted only in 'Sorry we don't know' and 'We don't have sufficient resources to give an answer now.'.
>
> So, we have our implementation live! But how can we make sure (if not ICANN but at least the community) what compliancy means... (e.g. we return a null when we don't have a value and "" when we have an empty string value. The mobile app wants "" in all empty situations... Just an interpretation?).
>
> I do not have the answers yet. Some of the points Marc gave us (in private mail exchange, for which I am grateful) will be solved. But that's not the point really.
>
> Hope to hear from you all :-).
>
> Best regards,
> Marc Groeneweg
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext